yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #05050
[Bug 1083944] Re: RPC exchange name defaults to 'openstack'
** Changed in: neutron/folsom
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1083944
Title:
RPC exchange name defaults to 'openstack'
Status in OpenStack Neutron (virtual network service):
Fix Released
Status in neutron folsom series:
Won't Fix
Status in OpenStack Compute (Nova):
Fix Released
Status in OpenStack Compute (nova) folsom series:
Fix Released
Status in OpenStack Manuals:
Fix Released
Bug description:
Nova on stable/folsom is using 'openstack' as its exchange name.
Openstack-common was updated on stable/folsom with this change:
https://review.openstack.org/#/c/16532/
Which brought in this change that removed the default 'nova' exchange config option:
https://review.openstack.org/#/c/12876/
"""
Make projects define 'control_exchange'.
The 'control_exchange' option needs to have a project-specific default
value. Just don't register this option and expect it to be registered
by the project using this code, at least for now.
****** IMPORTANT NOTE WHEN IMPORTING THIS CHANGE ******
If you are importing this change into a project that uses rpc, you must
add the control_exchange option in your code!
*******************************************************
Change-Id: Ida5a8637c419e709bbf22fcad57b0f11c31bb959
"""
But stable/folsom nova.conf was never updated.
The control_exchange option has been removed from nova.conf on master too now:
https://review.openstack.org/#/c/15940/
Found this debugging a situation where a child cell couldn't eceive
messages from a parent cell. Strangely, setting
control_exchange='openstack' fixed our problem. We're still trying to
work out *why* there was a mismatch in exchange names at all, given
that all cells were running the same nova code and nearly identical
configs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1083944/+subscriptions