-
Story
-
Resolution: Done
-
Minor
-
None
-
CL110 - RHOSP 10.1 1
-
None
-
14
-
ILT, VT
-
en-US (English)
URL:
Reporter RHNID: rodolfocasas2
Section: -
Language: en-US (English)||||||||
Workaround:
Description: If in one of the labs, one student complains that he/she can't create a volume,
You go and check, and when doing openstack volume list, you see that the volume is in error state.
You go to all-in-one, check all services, restart all services, but everything seems fine.
You try vgs command to see if the VG and lvs to see if that's ok, and you see NOTHING
You check the cinder logs and see something like this:
==> volume.log <==
2018-03-09 11:02:07.930 25884 ERROR cinder.service [-] Manager for service cinder-volume allinone.lab.example.com@lvm is reporting problems, not sending heartbeat. Service will appear "down".
There is a bug, that when you restart the controller (allinone) lvm is incapable of coming back up again, something to do with the loopback devices.)
https://bugzilla.redhat.com/show_bug.cgi?id=1412661
I tried restarting controller, but it didn't work. Tried with the workaround there, but it didn't work.
Had to reset all
CHeers