Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

Autoscaler "asnozzle" pods crashed when enabled multi_az #1681

Open
aqan213 opened this issue Jan 12, 2021 · 0 comments
Open

Autoscaler "asnozzle" pods crashed when enabled multi_az #1681

aqan213 opened this issue Jan 12, 2021 · 0 comments
Assignees
Labels
Type: Bug Something isn't working

Comments

@aqan213
Copy link
Contributor

aqan213 commented Jan 12, 2021

Describe the bug
When enabled multi_az, the asnozzle pods can not start due to the cert error.

{"data":{"error":"x509: certificate is valid for metricsserver.service.cf.internal, metricsserver.service.cf.internal, asmetrics, *.asmetrics, asmetrics-0, not asmetrics-z0-0","session":"3"},"log_level":2,"log_time":"2021-01-12T01:10:03Z","message":"metricsgateway.EnvelopeEmitter.failed-to-start-emimtter","source":"metricsgateway","timestamp":"1610413803.693451881"}
{"data":{"error":"x509: certificate is valid for metricsserver.service.cf.internal, metricsserver.service.cf.internal, asmetrics, *.asmetrics, asmetrics-0, not asmetrics-z0-0"},"log_level":2,"log_time":"2021-01-12T01:10:03Z","message":"metricsgateway.failed to start emitter","source":"metricsgateway","timestamp":"1610413803.693587542"}

And in asnozzle , the metricsgateway.yaml shows that metrics_server address are like

metric_server_addrs: ['wss://asmetrics-z0-0:7103','wss://asmetrics-z1-0:7103']
kubectl get pods -n kubecf
NAME                                     READY   STATUS             RESTARTS   AGE
api-z0-0                                 17/17   Running            1          13h
api-z1-0                                 17/17   Running            14         13h
asactors-z0-0                            8/8     Running            0          50m
asactors-z1-0                            8/8     Running            0          50m
asapi-z0-0                               8/8     Running            0          50m
asapi-z1-0                               8/8     Running            0          50m
asdatabase-0                             6/6     Running            0          50m
asmetrics-z0-0                           7/7     Running            0          50m
asmetrics-z1-0                           7/7     Running            0          50m
asnozzle-z0-0                            5/6     CrashLoopBackOff   13         50m
asnozzle-z1-0                            5/6     CrashLoopBackOff   13         50m
auctioneer-z0-0                          6/6     Running            1          13h
auctioneer-z1-0                          6/6     Running            1          13h
cc-worker-z0-0                           6/6     Running            0          13h
cc-worker-z1-0                           6/6     Running            0          13h

To Reproduce
Enabled autoscaler and also multi_az in values file, then run helm install.

Expected behavior
All the pods of autoscaler should be started.

Environment
kubecf-v2.7.1
cf-operator-v7.0.6-0.g2d07254

Additional context
Add any other context about the problem here.

@aqan213 aqan213 added the Type: Bug Something isn't working label Jan 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants