Move rabbitmq notifications queue to controlplane level

[morenod]

Move rabbitmq notifications queue from enabling at nova/cinder/watcher level to openstack controlplane level after that usage is available since openstack-k8s-operators/openstack-operator#1591.

delayStartSeconds parameter removed from rabbitmq notifications queue creation because it is not necessary, it is automatically added by controlplane when creating a new queue

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/b79c31cff8fb479caf80a059fe7823bc

✔️ openstack-meta-content-provider-master SUCCESS in 2h 34m 14s
✔️ watcher-operator-validation-master SUCCESS in 1h 53m 39s (non-voting)
✔️ openstack-meta-content-provider-epoxy SUCCESS in 2h 53m 41s
✔️ watcher-operator-validation-epoxy SUCCESS in 1h 54m 50s
❌ watcher-operator-validation-epoxy-ocp4-16 FAILURE in 20m 07s
✔️ noop SUCCESS in 0s
✔️ watcher-operator-kuttl SUCCESS in 43m 57s

[morenod]

check-rdo

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/f9416ac601264548b137ce1f44fe627c

✔️ openstack-meta-content-provider-master SUCCESS in 2h 40m 26s
✔️ watcher-operator-validation-master SUCCESS in 1h 56m 22s (non-voting)
✔️ openstack-meta-content-provider-epoxy SUCCESS in 2h 31m 17s
✔️ watcher-operator-validation-epoxy SUCCESS in 1h 51m 30s
❌ watcher-operator-validation-epoxy-ocp4-16 FAILURE in 19m 19s
✔️ noop SUCCESS in 0s
✔️ watcher-operator-kuttl SUCCESS in 41m 38s

[morenod]

check-rdo

[morenod]

CI Results:

• watcher-operator-validation-master (notifications enabled):

  • Openstack Control Plane CRS
  • Watcher CRS
  • Nova CRS
  • Cinder CRS
  • RabbitMQ Notifications Queue

• Notifications examples on decision engine:
  2025-10-07 10:24:06.260 1 INFO watcher.decision_engine.model.notification.nova [None req-c440e984-43d6-442f-835a-3546a3fc11c1 92b444a9c39a48a68af149e6c12b4cd6 2a13312658fd42d787f39d6ba1cdda55 - - - -] Event 'instance.create.start' received from nova-compute:compute-0.ctlplane.example.com with metadata {'message_id': 'b779ffa6-791a-4b11-a238-7ffbbf1b5a59', 'timestamp': '2025-10-07 10:24:06.249984'}

[cescgina]

/lgtm

I think this is good to go. @morenod not sure the openshift-ci bot added the do-not-merge label, maybe it's because you have [WIP] in the PR title

[amoralej]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amoralej

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [amoralej]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment