[bitnami/rabbitmq-cluster-operator] RabbitMQ Cluster and Messaging Topology Operators fail to start after image sha change on the same version

[ccodreanu]

Name and Version

bitnami/rabbitmq-cluster-operator/2.12.1

What architecture are you using?

None

What steps will reproduce the bug?

Container does not start up after digest of image is changed on the same version

Bad image

$ docker run --rm docker.io/bitnami/rabbitmq-cluster-operator:1.12.1@sha256:e67ef788ec8677c141d825fc71b5e6ce831478544436c8a4c53332df6fefc171

exec /manager: no such file or directory

Good image

$ docker run --rm docker.io/bitnami/rabbitmq-cluster-operator:1.12.1@sha256:900878696c88241d24d6b890cebce5b63594272033327f465ba206a1bdc2637f

{"level":"info","ts":"2025-02-05T09:55:25Z","logger":"setup","msg":"unable to find operator namespace"}

Notice the digest change between the two runs. The new digest seems to have been pushed to the repo at around 03:00 UTC on February 5th 2025.

What is the expected behavior?

No response

What do you see instead?

The operators should start

Additional information

No response

[javsalgar]

Hi,

Thank you so much for reporting. Just a note to let you know that we are fixing the issue.