Public bug reported:
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. This is because report_state 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
The fix would be to start the reporting thread only when we are ready to
consume, f.e. after consumer threads are spawned.
** Affects: neutron
Importance: Medium
Assignee: Ihar Hrachyshka (ihar-hrachyshka)
Status: Confirmed
** Tags: ovs
--
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:
Confirmed
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. This is because report_state 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
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
