lhotari commented on issue #460:
URL:
https://github.com/apache/pulsar-helm-chart/issues/460#issuecomment-1956622985
In one case where it failed, I found this in the
pulsar-ci-pulsar-manager-init logs:
```
[pod/pulsar-ci-pulsar-manager-init-9drxm/pulsar-ci-pulsar-manager-init]
{"message":"Add super user success, please
login"}{"login":"success"}{"error":"This environment is error. Please check it"}
```
Looks like the error message comes from here:
https://github.com/apache/pulsar-manager/blob/ee83cd22c99c44091b3b37054cdcffec4284dadf/src/main/java/org/apache/pulsar/manager/controller/EnvironmentsController.java#L152-L154
@Mortom123 I guess a workaround could be to check that
`/pulsar/bin/pulsar-admin clusters list` runs smoothly on the CLI before
running pulsar-manager init job.
It would also be useful it the script in `ci::collect_k8s_logs` (in
`.ci/helm.sh`) could collect the actual Pulsar Manager logs from inside the
container so it would be possible to see what the failure was. The logs would
then be available for download after a job fails. Downloading of the logs is
available at least for maintainers. This also works for build jobs in your own
fork.
--
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]
