combining transport_url with legacy rabbit config options results in a mixed not-working configuration

[melanie witt]

Reported in the #openstack-nova channel [0] yesterday, owalsh observed an issue where when the transport_url configuration option was set *and* legacy rabbit configuration options were set, the result was a mixed configuration of the two that could not connect to rabbit.

We had thought that if both transport_url and legacy options (such as rabbit_hosts, rabbit_userid, rabbit_password, rabbit_virtual_host) were specified, that the transport_url would be preferred and the legacy options ignored, but that is not the current behavior.

We lack more detail about this bug at this time, but wanted to open it ahead just in case the problem could be easily spotted in the code.

[0] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-04-05.log.html#t2018-04-05T20:29:23

[Oliver Walsh (owalsh)]

I'll try to reproduce next week to confirm, but IIRC: transport_url and rabbit_port were set but nova could not connect to rabbit unless I also set rabbit_hosts, or removed rabbit_port.

[Ben Nemec (bnemec)]

I was not able to reproduce this behavior in a current devstack environment, so I think we'll need more details to proceed.

[Launchpad Janitor (janitor)]

[Expired for oslo.messaging because there has been no activity for 60 days.]