lhotari commented on issue #460: URL: https://github.com/apache/pulsar-helm-chart/issues/460#issuecomment-1956663276
> @lhotari I do not think that the problem lies within the manager, but rather the underlying k8 deployment. The Pulsar Manager throws this issue because it cannot resolve the name `pulsar-ci-broker`, other tests (TLS/kube-prometheus) fail for the same reason. > > The logs from within the pulsar manager container are starting from here: https://github.com/Mortom123/pulsar-helm-chart/actions/runs/7929918393/job/21651157455#step:6:5240 The error is at: https://github.com/Mortom123/pulsar-helm-chart/actions/runs/7929918393/job/21651157455#step:6:5503 In this case, everything else passed: https://github.com/apache/pulsar-helm-chart/actions/runs/7989357049/job/21816701126#step:6:4990 The pulsar-ci-broker name cannot be resolved before the readiness probe passes. The init job should retry if it receives `{"error":"This environment is error. Please check it"}`. That's one way to handle this. [The quirk in pulsar-manager is that the REST call returns 200 even when there's a failure.](https://github.com/apache/pulsar-manager/blob/ee83cd22c99c44091b3b37054cdcffec4284dadf/src/main/java/org/apache/pulsar/manager/controller/EnvironmentsController.java#L152-L154) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
