Binaries only use default topics
Bug #1057831 reported by
Michael H Wilson
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Michael H Wilson |
Bug Description
Found the bug in Essex 2012.2, but it appears to also be affecting folsom release candidates and the current head.
When you specify topics for different nova components their binaries don't start them up with that topic. This seems inconsistent with the rest of the messaging API which always refers to FLAGS.binary_topic. I had to fix this by patching all the nova binaries and by patching nova.service.
I did not patch nova-all, I'm not sure if people still use this, I don't.
Changed in nova: | |
assignee: | nobody → Michael H Wilson (geekinutah) |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
milestone: | none → grizzly-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
Updated the patch to include breakage in nova/db/ sqlalchemy/ api.py.