Ok, I think I've found the proper way to verify the bug against openstack-neutron. Here is what I did: 1. Installed RHEL 6.5, RHOS 4.0.z. 2. Deployed Openstack via packstack. 3. Set 'qpid_topology_version = 2' in neutron.conf. 3. checked available neutron-related topic exchanges: qpid-config exchanges -r | grep neutron 4. built 'drain' utility, started several of its instances to follow one of the topic exchanges: ./drain -f q-plugin & 5. checked that not more than one of those listeners receive topic messages from q-plugin exchange. === FYI: message looks as following when delivered to a 'drain' instance: Message(properties={qpid.subject:topic/neutron/q-plugin, x-amqp-0-10.routing-key:topic/neutron/q-plugin}, content='{oslo.message:{"_context_roles": ["admin"], "_context_read_deleted": "no", "args": {"agent_state": {"agent_state": {"binary": "neutron-dhcp-agent", "topic": "dhcp_agent", "host": "rhel65", "agent_type": "DHCP agent", "configurations": {"subnets": 0, "use_namespaces": true, "dhcp_lease_duration": 120, "dhcp_driver": "neutron.agent.linux.dhcp.Dnsmasq", "networks": 0, "ports": 0}}}, "time": "2014-01-02T16:13:35.501249"}, "namespace": null, "_unique_id": "5c87b1ada1a241c2b7429ed355e4114d", "_context_timestamp": "2014-01-02 16:13:35.501193", "_context_is_admin": true, "version": "1.0", "_context_project_id": null, "_context_tenant_id": null, "_context_user_id": null, "method": "report_state"}, oslo.version:2.0}') === The only question that I'm currently trying to clear out is whether setting topology as above is enough to make sure we test against correct QPID topology.
Answering to the question: as per /usr/share/neutron/neutron-dist.conf, that's the correct way to enforce new topology.
Based on verification results above, closing the bug as verified. I will also follow up upstream on why testing clients/servers that were used by original reporter produce incorrect behaviour.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0091.html