Closed dciabrin closed 6 months ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
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://review.rdoproject.org/zuul/buildset/b80c80b4a0eb4d76ad73b8715a22e928
:heavy_check_mark: openstack-k8s-operators-content-provider SUCCESS in 1h 44m 28s :x: podified-multinode-edpm-deployment-crc FAILURE in 1h 08m 58s :x: cifmw-crc-podified-edpm-baremetal FAILURE in 1h 03m 46s :x: openstack-operator-tempest-multinode FAILURE in 1h 14m 50s
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://review.rdoproject.org/zuul/buildset/b3ca8fb0b27f4568b32228b485df4781
:heavy_check_mark: openstack-k8s-operators-content-provider SUCCESS in 1h 32m 10s :x: podified-multinode-edpm-deployment-crc FAILURE in 1h 10m 07s :x: cifmw-crc-podified-edpm-baremetal FAILURE in 1h 05m 58s :x: openstack-operator-tempest-multinode FAILURE in 1h 13m 09s
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dciabrin, stuggi
The full list of commands accepted by this bot can be found here.
The pull request process is described here
When TLS is enabled in RabbitMQ with FIPS engaged, the RabbitMQ server has to be given specific TLS options in the RabbitMQ configuration otherwise the rabbitmq Erlang application will fail to create TLS sockets with:
{insufficient_crypto_support {'tlsv1.3',{versions,['tlsv1.3','tlsv1.2']}}}}}}}}}
We now reuse the same config as we had in previous versions of Openstack as they were known to work with FIPS. Moreover the configuration has to be passed as an Erlang structure to ensure the right orderning of option ssl_options.versions.
Related: OSPRH-6889