().
receiver close will sent MessageCancel and QueueDelete message to
broker(qpid server), so that all cinder-volume queue be removed.
I think that the reason of problem confused me.
But I don't know how to solve it.
2013/5/28 minmin ren rmm0...@gmail.com
I think I found some problems of qpid
Hi Ray,
Thanks for your reply.
try except change to line 386 only solve cinder-scheduler or
nova-compute service which is the similar implementation stop raise
exception.
However, all cinder-volume queue be removed when one of
multi-cinder-volume service stop. It is another problem.
I
I think I found some problems of qpid as rpcbackend, however I'm not sure
about it. Could anyone try to test it with your environment?
openstack grizzly version
config file need debug=True
1. service openstack-cinder-scheduler stop (nova-compute, nova-scheduler,
etc)
2. vi
My enviroment
two machines:
On one machine(node1), cinder-api cinder-volume cinder-scheduler and qpidd
are running
On other one(node2), only cinder-volume running and cinder-volume use the
same qpid with node1.
Normally, create/delete volume can work well.
However, I encountered a problem:
when I
4 matches
Mail list logo
