[Openstack-discuss][Cinder] Fail to mount the volume on the target node
Hi. After I installed Cinder, I have had a problem which I cannot make instances with volume storage. I created an instance on Horizon and it always has failed. Actually, I'm using Xen as the hypervisor and there was not any special log about Nova. But, in the Xen's log (/var/log/xen/bootloader.5.log), I saw the hypervisor cannot find the volume which is provided by Cinder: Traceback (most recent call last):
File "/usr/lib/xen/bin/pygrub", line 929, in <module> raise RuntimeError, "Unable to find partition containing kernel" RuntimeError: Unable to find partition containing kernel
And, I also found something noticeable in the Cinder's log ('/var/log/cinder/cinder-volume.log' on the Block storage node): 2018-12-31 04:08:11.189 12380 INFO cinder.volume.manager
[req-93eb0ad3-6c6c-4842-851f-435e15d8639b bb1e571e4d64462bac80654b153a88c3 96ad10a59d114042b8f1ee82c438649a - default default] Attaching volume 4c21b8f1-ff07-4916-9692-e74759635978 to instance bea7dca6-fb04-4791-bac9-3ad560280cc3 at mountpoint /dev/xvda on host None.
It seems that Cinder cannot receive information of the target node ('on host None' above) so, I think it can cause the problem that Cinder fails to provide the volume due to lack of the host information. Since I could not find any other logs except that log, I need more hints. Please give me some help Thanks! Regard,
On 31/12, Minjun Hong wrote:
Hi. After I installed Cinder, I have had a problem which I cannot make instances with volume storage. I created an instance on Horizon and it always has failed. Actually, I'm using Xen as the hypervisor and there was not any special log about Nova. But, in the Xen's log (/var/log/xen/bootloader.5.log), I saw the hypervisor cannot find the volume which is provided by Cinder:
Traceback (most recent call last):
File "/usr/lib/xen/bin/pygrub", line 929, in <module> raise RuntimeError, "Unable to find partition containing kernel" RuntimeError: Unable to find partition containing kernel
And, I also found something noticeable in the Cinder's log ('/var/log/cinder/cinder-volume.log' on the Block storage node):
2018-12-31 04:08:11.189 12380 INFO cinder.volume.manager
[req-93eb0ad3-6c6c-4842-851f-435e15d8639b bb1e571e4d64462bac80654b153a88c3 96ad10a59d114042b8f1ee82c438649a - default default] Attaching volume 4c21b8f1-ff07-4916-9692-e74759635978 to instance bea7dca6-fb04-4791-bac9-3ad560280cc3 at mountpoint /dev/xvda on host None.
It seems that Cinder cannot receive information of the target node ('on host None' above) so, I think it can cause the problem that Cinder fails to provide the volume due to lack of the host information. Since I could not find any other logs except that log, I need more hints. Please give me some help
Thanks! Regard,
Hi, The "on host None" message looks like Nova is either not sending the "host" key in the connector information or is sending it set to '' or None. You'd need to see the logs in DEBUG level to know which it is. And that is strange, because the "host" key is set by os-brick when Nova calls the "get_connector_properties": props['host'] = host if host else socket.gethostname() So even if Nova doesn't have the "host" config option set, os-brick should get the hostname of the node. But from Cinder's perspective I don't think that's necessarily a problem. How was the volume created? Because that looks like a problem with the contents of the volume, as it is not complaining about not being able to map/export it or attach it. Cheers, Gorka.
participants (2)
-
Gorka Eguileor
-
Minjun Hong