[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1548278
Title:
rabbitmq q-agent-notifier-port-
update_fanout_91e5c8311b1b47a2b39ede94dad9a56b is blocked
Status in neutron:
Expired
Bug description:
Queue q-agent-notifier-port-
update_fanout_91e5c8311b1b47a2b39ede94dad9a56b be blocked ( please
refer to the attached picture)
Version: RabbitMQ 3.6.0 release, openstack kilo
This phenomeno comes up sometimes when in the large-scale environment,
when one rabbitmq message-queue be created，if no consume binded to it but
the producers publish messages to queue continuously, then the queue will not
be dropped!
If I want the queue which hasn't been binded with consumers or producers to
be dropped,
how can I do?
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1548278/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
