Notifications are emitted per-cell instead of globally
Bug #1700496 reported by
Sylvain Bauza
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Unassigned | ||
devstack |
Invalid
|
Undecided
|
Unassigned |
Bug Description
With https:/
That said, as notifications emit on a different topic but use the same transport URL than the component, it leads to our consumers missing notifications as they only subscribe to the original MQ.
While Nova can use multiple MQs, we should still offer the possibility to have global notifications for Nova so a consumer wouldn't require to modify their configs every time a new cell is issued.
That can be an oslo.messaging config option [1], but we certainly need to be more gentle in Devstack or depending jobs (like for Vitrage) could fail.
devstack version: pike
Changed in nova: | |
status: | New → Confirmed |
description: | updated |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in devstack: | |
status: | Incomplete → In Progress |
description: | updated |
tags: |
added: openstack-version.pike removed: needs.openstack-version |
Changed in nova: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We are going to need to document this in the nova cells devref as something to consider when doing multi-cell deployment.