You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ kubectl describe po test-rabbitmq-0 ......................Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 55s default-scheduler Successfully assigned default/test-rabbitmq-0 to worker230 Normal Pulled 50s kubelet Container image "registry-1.docker.io/bitnami/rabbitmq:3.13.2-debian-12-r0" already present on machine Normal Created 50s kubelet Created container prepare-plugins-dir Normal Started 49s kubelet Started container prepare-plugins-dir Normal Pulled 46s kubelet Container image "registry-1.docker.io/bitnami/rabbitmq:3.13.2-debian-12-r0" already present on machine Normal Created 46s kubelet Created container rabbitmq Normal Started 46s kubelet Started container rabbitmq Warning Unhealthy 24s kubelet Readiness probe failed: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed\r 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0\r 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 127.0.0.1 port 15672 after 0 ms: Couldn't connect to server
$ kubectl exec -i test-rabbitmq-0 -- curl -f --user rabbit.user:rabbit.pass 127.0.0.1:15672/api/health/checks/local-alarmsDefaulted container "rabbitmq" out of: rabbitmq, prepare-plugins-dir (init) % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 127.0.0.1 port 15672 after 1 ms: Couldn't connect to servercommand terminated with exit code 7
The text was updated successfully, but these errors were encountered:
Name and Version
bitnami/rabbitmq 14.1.2
What architecture are you using?
amd64
What steps will reproduce the bug?
Username or password cannot contain char
.
What do you see instead?
My yaml helmfile
The text was updated successfully, but these errors were encountered: