Red Hat Bugzilla – Bug 1025025
[Tracking] openstack-cinder-volume service doesn't reconnect to qpidd after qpidd restart
Last modified: 2016-04-26 17:41:45 EDT
Description of problem:
When the qpidd service is restarted, openstack-cinder-volume requires a restart to reconnect to the qpidd service.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start qpidd and openstack-cinder-volume and verify cinder functionality (create/delete volumes, etc.)
2. Restart qpidd service
3. Again, try to create/delete cinder volumes.
Volumes fail to create/delete - displayed as in error state in dashboard
Volumes create/delete successfully.
Created attachment 817591 [details]
errors in volume.log file
Created attachment 817592 [details]
qpid errors in /var/log/messages
Created attachment 823631 [details]
Here is my attempt to reproduce this -- I couldn't. No qpid errors generated in /var/log/messages and behavior is as expected.
Dan: Any more info you can give about how to reproduce this? It doesn't seem to happen on my machine. (3.0.z on RHEL 6.5 Beta)
Sadly, no, I don't have any more details right now. I'll try to reproduce the problem when I find some spare time (buwahahahaha! I crack me up), but I don't see that happening any time soon. :/
I'm ok with closing the ticket and if/when I run into it again, I'll re-open with more details.
Closing since I can't find any way to make this happen. Note that the errors in the volume log appear to be related to driver issues and not AMQP.
Let's leave this open for the next couple of weeks.
If/when the problem reproduces itself, we won't touch the volume service and you can log in and see what it's failing on. Sound like a plan?
The qpidd errors sound like it might be https://bugzilla.redhat.com/show_bug.cgi?id=1041575 (see https://bugs.launchpad.net/cinder/+bug/1187298).
Bug 1050215 could be related/helpful here.
Since this is a test only bug and the bug it's tracking is closed already as well as us not being able to reproduce it, I'm moving to ON_QA.
This specific issue is not reproduced but we have a different one which I will open a bug for.
closing this as verified with the following packages
[root@orange-vdsf ~]# rpm -qa |grep cinder
root@puma31 ~]# rpm -qa |grep qpid
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.