Bitnami Zookeeper container is failing the readiness probe
Summary
(Summarize the bug encountered concisely)
Steps to reproduce
(How one can reproduce the issue - this is very important)
What is the current bug behavior?
(What actually happens) Fails liveness and Readiness probe and continuously restarts Error Below:
` Warning Unhealthy 5m49s (x17 over 10m) kubelet Liveness probe failed: localhost [127.0.0.1] 2181 (eforward) │
│ : Connection refused │
│ Warning Unhealthy 49s (x73 over 10m) kubelet Readiness probe failed: localhost [127.0.0.1] 2181 (eforward │
│ ) : Connection refused │
│ `
What is the expected correct behavior?
Container starts properly
Relevant logs and/or screenshots
see above
Possible fixes
problem was NOT present in previous 3.8.0 (about 3 weeks ago). The issue was introduced within about the last 3 weeks, when attempting to launch with the opensource version from bitnami's bitbucket repo all starts properly. Appears to be an issue with the modifications made once pulled into the ironbank repos/modifications to image.
Tasks
-
Bug has been identified and corrected within the container
Edited by Paul Grawl