More investigation revealed that the bug affects only those setups that
do not use oslo.messaging (Icehouse and earlier), so the bug is invalid
for upstream.
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1505244
Title:
OVS agent can leave AMQP queues on startup failure
Status in neutron:
Invalid
Bug description:
If OVS agent initialization fails for any reason after report_state
thread is spawned, we can leave empty AMQP queues on AMQP broker. Any
failure between that thread startup and consume_in_threads() call may
result in it. One of the reasons is report_state that triggers RPC,
and since there is still no connection, it's established, and all
consumers defined for that connection are declared on AMQP broker
side:
https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_rabbit.py#L646
Another reason is that declare_consumer in oslo.messaging creates
Queue object thru kombu that immediately initializes it on AMQP side.
The fix would be to start the reporting thread only when we are ready
to consume, f.e. after consumer threads are spawned.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1505244/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
