OLM workflow is broken

[mkuratczyk]

Failed for 2.12 and 2.11 (2.10 is the latest on Operatorhub):
https://github.com/rabbitmq/cluster-operator/actions/runs/12431649991/job/34709473574
https://github.com/rabbitmq/cluster-operator/actions/runs/11326986094/job/31497073792

[bo0ts]

That is really unfortunate for users that relied on OperatorHub to install the operator and keep it up to date. Any chance to fix this?

[DanielePalaia]

Hi @bo0ts

I can investigate on this but it will not be something immediate (probably at some point in the next days/weeks).

If you feel you'd like to contribute, investigate and improve this process, you are welcome to submit a PR.
These are the repositories used during the publishing process:

This is the publishing action on this same repo:

https://github.com/rabbitmq/cluster-operator/blob/main/.github/workflows/testing_and_publishing_OLM_bundle.yml

using this script to generate the OLM packaging:

https://github.com/rabbitmq/OLM-Package-Repo

which is pushing the OLM manifests generated on these repos:

https://github.com/rabbitmq/community-operators
https://github.com/rabbitmq/community-operators-prod

[DanielePalaia]

It was a small issue on the cluster operator manifest path we passed to the script to generate the bundle for openshift-marketplace.

This PR should fix the action:

#1812

as tested here:

https://github.com/rabbitmq/cluster-operator/actions/runs/12909404544

Unfortunately I think at this point we need to wait the next cluster-operator release to have the all process executed and everything in sync (images, versions, crds and security objects) and then publish the manifest on operatorhub/openshift-marketplace

[DanielePalaia]

Hey 2.12.1 was published both in operator.io and openshift-marketplace:

https://github.com/k8s-operatorhub/community-operators/tree/main/operators/rabbitmq-cluster-operator/2.12.1
https://github.com/redhat-openshift-ecosystem/community-operators-prod/tree/main/operators/rabbitmq-cluster-operator/2.12.1

I also made some modifications on the automation in order to hopefully correctly automate the next releases, but in case of issues feel free to open a new issue for this.