Hide Forgot
+++ This bug was initially created as a clone of Bug #1038641 +++ Description of problem: See upstream bug: https://bugs.launchpad.net/oslo/+bug/1257293 Note well: this bug _only_ affects those QPID configurations that have applied the fix of the following bug: https://bugs.launchpad.net/oslo/+bug/1178375 _AND_ are have configured "qpid_topology_version=2" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from RHEL Product and Program Management on 2013-12-05 09:44:55 EST --- Since this issue was entered in bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. --- Additional comment from Dave Allan on 2013-12-05 10:11:18 EST --- Checking into risk of fix; may want to take for 4.0GA --- Additional comment from Perry Myers on 2013-12-05 11:30:41 EST --- This seems important enough to be an RC blocker for 4.0. But doesn't this bug need to be cloned to Nova, Ceilometer, Neutron, etc (every component that copies and pastes the code from Oslo for RPC?)
I have tested Heat 2013.2 with QPID in devstack, and it does not fan out to every node, but instead load balances. In any regard, we don't support multiple heat-engines either upstream or down presently, so this is a non-issue. Horizontal scalability is something that should be addressed in Icehouse. The only way this bug would affect heat is if multiple heat-engines (which are the subscribers to the message queues) were launched, which results in an unsupportable Heat environment.