notification queues are created in rabbit but never consumed
Bug #1188643 reported by
Michael Kerrin
This bug affects 11 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Medium
|
Unassigned | ||
OpenStack Identity (keystone) |
Invalid
|
Medium
|
Unassigned | ||
devstack |
Invalid
|
Undecided
|
Unassigned | ||
oslo.messaging |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
The following queues are created in rabbit but there are no consumers for them. notifications.info, notifications.warn and notifications.
notifications.info in particular collects a large number of events very quickly
All events should be published to an exchange and it should be up the consumers on how to configure any queues in rabbit and how they should be consumed.
Changed in oslo: | |
status: | New → Confirmed |
Changed in nova: | |
assignee: | nobody → Jian Wen (wenjianhn) |
affects: | oslo-incubator → oslo.messaging |
Changed in devstack: | |
status: | Incomplete → Invalid |
tags: | added: ops |
Changed in nova: | |
status: | Confirmed → Won't Fix |
Changed in oslo.messaging: | |
status: | Confirmed → Won't Fix |
Changed in nova: | |
assignee: | Jian Wen (wenjianhn) → nobody |
Changed in keystone: | |
status: | Confirmed → Invalid |
To post a comment you must log in.
Good point, in the case of notifications, we don't want to create the queues. The fix is actually in oslo, so i'm going to add it as an affected project.