Nova notifications now seem to be using the default rabbit exchange
Bug #914418 reported by
Matt Dietz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
High
|
Monsyne Dragon | ||
Bug Description
Rather than using the "nova" exchange, notifications appear to be using the default exchange.
As such, any existing notifications configurations are broken. They can be fixed in the interim by setting the exchange type to be None (depending on the library you use)
Please include unit tests to ensure this doesn't happen again
| Changed in nova: | |
| importance: | Undecided → High |
| milestone: | none → essex-3 |
| status: | New → Confirmed |
| Changed in nova: | |
| assignee: | nobody → Monsyne Dragon (mdragon) |
| Changed in nova: | |
| milestone: | essex-3 → none |
Revision history for this message
| Monsyne Dragon (mdragon) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #2 |
| Changed in nova: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #3 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → essex-4 |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Was finally able to replicate. Problem does not actually seem to be the wrong exchange. Rather, the 'durable' flag is not being applied correctly to the notification queues, which is where the issue was noted.