zmq doesn't listen to the right node topics

Bug #1282297 reported by Cory Stone on 2014-02-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oleksii Zamiatin

Bug Description

Since this change zmq doesn't seem to work with any messages directed to a specific node. Creating a volume gets picked up by the scheduler, but not by the volume manager.

For example, the volume manager listens to 'cinder-volume' on 'host' on ipc:///var/run/openstack/zmq_topic_cinder-volume.<host>.

This happens by: topic = '.'.join((topic, CONF.rpc_zmq_host))

This doesn't work for node topics, as those already have the host in them, so the manager listens to '' on ipc:///var/run/openstack/zmq_topic_cinder-volume.<host>.<host>.

When zmq sends a message, it sends it to zmq_topic_cinder-volume.<host>.

Maybe we just need to register node_topic with a different arg so it doesn't join the host again? or maybe the zmq code needs to be smarter about picking the topic when sending a direct message?

Tags: zmq Edit Tag help
Cory Stone (corystone) wrote :

Update, this is for stable/havana.

Changed in oslo.messaging:
assignee: nobody → Oleksii Zamiatin (ozamiatin)
Changed in oslo.messaging:
status: New → In Progress
Li Ma (nick-ma-z) wrote :

I cannot find this bug from icehouse.
The listened topic is ipc:///var/run/openstack/zmq_topic_cinder-volume.<host>

Li Ma (nick-ma-z) wrote :

I'm not cinder expert. Anyone can reproduce this bug?

Li Ma (nick-ma-z) on 2015-03-23
tags: added: zmq
Changed in oslo.messaging:
status: In Progress → Invalid
Sean McGinnis (sean-mcginnis) wrote :

Not sure the full history on this, but zmq support in cinder is being addressed with the following blueprint:

Changed in cinder:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers