| Thread Previous • Date Previous • Date Next • Thread Next |
By default neutron server sends fanout on all events when resource state
changes. Some are consumed by current agents (like port update, etc.),
some may be consumed or not, depending on
plugins/drivers/extensions/agents used in current installation. I guess
with your set of drivers q-agent-notifier-network-delete is not consumed
by anybody, but it doesn't mean that there is no other agents that might
need this info.
** Changed in: neutron
Status: New => 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/1634884
Title:
Unknown service q-agent-notifier-network-delete
Status in neutron:
Invalid
Bug description:
While testing oslo.messaging zmq driver, we came across with the
following behavior of neutron: it sends fanout messages to the target
<Target topic=q-agent-notifier-network-delete, version=1.0,
fanout=True>, although there are no such services. Zmq driver uses
redis as a matchmaker for coordination between rpc clients and
servers, and each server registers itself in redis so that clients can
find it. In our particular case redis has no records associated with
the topic q-agent-notifier-network-delete, and our current behavior is
to retry (20 seconds at most, 2 seconds between attempts) to get
available hosts from redis, and drop the message afterwards. As a
result we get failed tests. By the way, if we drop those messages
immediately, everything works fine.
For example, here is the link to tempest logs:
http://logs.openstack.org/44/388044/1/check/gate-tempest-neutron-dsvm-
src-oslo.messaging-
zmq/925c9ee/logs/screen-q-svc.txt.gz#_2016-10-18_17_39_59_053
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1634884/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
