Add rabbitmq vhost usage on edpm ci scenario

[morenod]

Modified CI Jobs
watcher-operator-validation-master: Now tests with vhost enabled on rabbitmq cluster, both for messagingBus and notificationsBus

Assisted-by: claude

[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/baae7866422d4db2b84d85f9037ab5e5

✔️ openstack-meta-content-provider-master SUCCESS in 2h 12m 17s
❌ watcher-operator-validation-master FAILURE in 32m 47s
✔️ openstack-meta-content-provider-epoxy SUCCESS in 3h 28m 02s
✔️ watcher-operator-validation-epoxy SUCCESS in 1h 55m 05s
✔️ watcher-operator-validation-epoxy-ocp4-16 SUCCESS in 2h 17m 12s
✔️ noop SUCCESS in 0s
✔️ watcher-operator-kuttl SUCCESS in 56m 13s

[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/afd5b11d50d244848e3963b80b938d11

✔️ openstack-meta-content-provider-master SUCCESS in 2h 56m 18s
❌ watcher-operator-validation-master FAILURE in 2h 11m 15s
✔️ openstack-meta-content-provider-epoxy SUCCESS in 2h 15m 44s
✔️ watcher-operator-validation-epoxy SUCCESS in 1h 53m 51s
❌ watcher-operator-validation-epoxy-ocp4-16 FAILURE in 1h 50m 35s
✔️ noop SUCCESS in 0s
✔️ watcher-operator-kuttl SUCCESS in 48m 02s

[morenod]

recheck

[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/5f082a35a99343de81cf620f448d54a1

✔️ openstack-meta-content-provider-master SUCCESS in 2h 52m 45s
❌ watcher-operator-validation-master FAILURE in 2h 12m 04s
✔️ openstack-meta-content-provider-epoxy SUCCESS in 2h 27m 23s
✔️ watcher-operator-validation-epoxy SUCCESS in 1h 49m 53s
✔️ watcher-operator-validation-epoxy-ocp4-16 SUCCESS in 2h 05m 33s
✔️ noop SUCCESS in 0s
✔️ watcher-operator-kuttl SUCCESS in 49m 48s

[amoralej]

vhosts are not being configured, see vhost in status in:

https://logserver.rdoproject.org/75a/rdoproject.org/75ab4e4b9cf5430296ee577c35d305d7/controller/ci-framework-data/logs/openstack-must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-1663223401da21aaf5f4d8d59101f0d65b9026b7fe7df6e028cefcd367dd2d15/namespaces/openstack/crs/transporturls.rabbitmq.openstack.org/watcher-watcher-transport.yaml

https://logserver.rdoproject.org/75a/rdoproject.org/75ab4e4b9cf5430296ee577c35d305d7/controller/ci-framework-data/logs/openstack-must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-1663223401da21aaf5f4d8d59101f0d65b9026b7fe7df6e028cefcd367dd2d15/namespaces/openstack/crs/transporturls.rabbitmq.openstack.org/cinder-cinder-transport.yaml

According to the code, I guess this is kind of expected:

1. In the infra-operator, the vhosts are only created when the user is also specified (see https://github.com/openstack-k8s-operators/infra-operator/blob/main/internal/controller/rabbitmq/transporturl_controller.go#L590-L593) . This applies to all services except to watcher where the user is added.
2. The openstack-operator only takes the top-level messagingBus and notificationsBus when it is undefined in the service section. It does not copy individual fields so it's not taking the vhost from the top-level.

I'd say this is the expected behavior.

[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/4a49c7d080ab4eb78cf7464fcbbe9d52

✔️ openstack-meta-content-provider-master SUCCESS in 2h 16m 01s
❌ watcher-operator-validation-master FAILURE in 1h 37m 39s
✔️ openstack-meta-content-provider-epoxy SUCCESS in 2h 31m 09s
❌ watcher-operator-validation-epoxy RETRY_LIMIT in 3m 38s
✔️ watcher-operator-validation-epoxy-ocp4-16 SUCCESS in 2h 09m 45s
✔️ noop SUCCESS in 0s
✔️ watcher-operator-kuttl SUCCESS in 47m 43s

[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/65b65a172a5d4e418ef46411a075f1cd

✔️ openstack-meta-content-provider-master SUCCESS in 3h 04m 16s
✔️ watcher-operator-validation-master SUCCESS in 1h 57m 50s
✔️ openstack-meta-content-provider-epoxy SUCCESS in 2h 13m 50s
✔️ watcher-operator-validation-epoxy SUCCESS in 1h 51m 55s
❌ watcher-operator-validation-epoxy-ocp4-16 FAILURE in 26m 29s
✔️ noop SUCCESS in 0s
✔️ watcher-operator-kuttl SUCCESS in 50m 22s

[raukadah]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: raukadah

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [raukadah]

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

[morenod]

/cherry-pick 18.0-fr5

[openshift-cherrypick-robot]

@morenod: new pull request created: #347

Details

In response to this:

/cherry-pick 18.0-fr5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.