Ask Your Question
0

Another "volume not yet found at" issue

asked 2017-06-08 12:57:58 -0500

tiger gravatar image

I have read a lot of instances of this condition, but always attracts low quality crap answers. This would be a whole lot easier if the developers used meaningful log file entries. So it tries to do something five times. What is it trying to do? What is the expected outcome of doing whatever it is it is trying to do? Anyway, I am not expecting an answer. Just letting others know I have the same issue.

nova-compute.log:2017-06-08 17:32:23.933 10143 INFO os_brick.initiator.connectors.iscsi [req-f432a1e3-cb36-4450-b5fe-24dbdae9ca0f 2e0c56b94de54592b04f64136d981dac c421598b9a4e4eac816faaa840eecd80 - - -] Multipath discovery for iSCSI not enabled.
nova-compute.log:2017-06-08 17:32:23.933 10143 INFO os_brick.initiator.connectors.iscsi [req-f432a1e3-cb36-4450-b5fe-24dbdae9ca0f 2e0c56b94de54592b04f64136d981dac c421598b9a4e4eac816faaa840eecd80 - - -] Trying to connect to iSCSI portal 192.168.140.217:3260
nova-compute.log:2017-06-08 17:32:23.959 10143 INFO os_brick.initiator.connectors.iscsi [req-f432a1e3-cb36-4450-b5fe-24dbdae9ca0f 2e0c56b94de54592b04f64136d981dac c421598b9a4e4eac816faaa840eecd80 - - -] ISCSI volume not yet found at: [u'/dev/disk/by-path/ip-192.168.140.217:3260-iscsi-iqn.2010-10.org.openstack:volume-deb44af9-5bec-4e53-b431-c6cc9e6b6400-lun-0']. Will rescan & retry.  Try number: 0.
nova-compute.log:2017-06-08 17:32:24.966 10143 INFO os_brick.initiator.connectors.iscsi [req-f432a1e3-cb36-4450-b5fe-24dbdae9ca0f 2e0c56b94de54592b04f64136d981dac c421598b9a4e4eac816faaa840eecd80 - - -] ISCSI volume not yet found at: [u'/dev/disk/by-path/ip-192.168.140.217:3260-iscsi-iqn.2010-10.org.openstack:volume-deb44af9-5bec-4e53-b431-c6cc9e6b6400-lun-0']. Will rescan & retry.  Try number: 1.
nova-compute.log:2017-06-08 17:32:28.974 10143 INFO os_brick.initiator.connectors.iscsi [req-f432a1e3-cb36-4450-b5fe-24dbdae9ca0f 2e0c56b94de54592b04f64136d981dac c421598b9a4e4eac816faaa840eecd80 - - -] ISCSI volume not yet found at: [u'/dev/disk/by-path/ip-192.168.140.217:3260-iscsi-iqn.2010-10.org.openstack:volume-deb44af9-5bec-4e53-b431-c6cc9e6b6400-lun-0']. Will rescan & retry.  Try number: 2.
nova-compute.log:2017-06-08 17:32:37.983 10143 INFO os_brick.initiator.connectors.iscsi [req-f432a1e3-cb36-4450-b5fe-24dbdae9ca0f 2e0c56b94de54592b04f64136d981dac c421598b9a4e4eac816faaa840eecd80 - - -] ISCSI volume not yet found at: [u'/dev/disk/by-path/ip-192.168.140.217:3260-iscsi-iqn.2010-10.org.openstack:volume-deb44af9-5bec-4e53-b431-c6cc9e6b6400-lun-0']. Will rescan & retry.  Try number: 3.
nova-compute.log:2017-06-08 17:32:53.990 10143 INFO os_brick.initiator.connectors.iscsi [req-f432a1e3-cb36-4450-b5fe-24dbdae9ca0f 2e0c56b94de54592b04f64136d981dac c421598b9a4e4eac816faaa840eecd80 - - -] ISCSI volume not yet found at: [u'/dev/disk/by-path/ip-192.168.140.217:3260-iscsi-iqn.2010-10.org.openstack:volume-deb44af9-5bec-4e53-b431-c6cc9e6b6400-lun-0']. Will rescan & retry.  Try number: 4.
edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
1

answered 2017-06-08 14:25:57 -0500

Bernd Bausch gravatar image

updated 2017-06-08 14:31:51 -0500

This is not necessarily a "condition". nova-compute is trying to connect to an iSCSI target. The expected outcome is that the target is available at the cited device file. This is necessary to attach the volume to an instance; it might take a while until a newly created volume becomes available, so nova-compute tries a few times.

My guess is that this happens when you boot from an image that is copied to a volume rather than ephemeral storage. This seems to be the default recently when launching an instance from Horizon.

If there is no message to the effect that the volume wasn't found, there is no problem.

What exactly are you trying to do? Is anything failing? If yes, where does the volume reside that you are trying to attach, and what do you see in the corresponding cinder volume log? If you don't have conclusive information in the logs, enable debug logging and try again.

edit flag offensive delete link more

Comments

Yeah, it fails miserably. At first I thought OpenStack had crashed. Rebooted host. All the VM were in the shutoff state. The VM built using ephemeral storage turned back up fine. The three built using cinder block volumes, refused to get past "powering on".

tiger gravatar imagetiger ( 2017-06-08 14:43:06 -0500 )edit

I had used 'dd' to make a 400GB file. Then used losetup / fdisk / pvcreate / vgextend to donate the 400GB to "cinder-volumes". Looked like it worked fine. Then used "cinder create" to create volumes, loading previously made images, themselves made from vendor-supplied QCOW

tiger gravatar imagetiger ( 2017-06-08 14:44:25 -0500 )edit

So after making the three VM using cinder block storage, O/S appeared to crash. I have since created two of the three VM using ephemeral and they are OK. I have one image that insists on having a 265GB block storage. I have tried to delete the now unnecessary cinder volumes. "Error deleting volume"

tiger gravatar imagetiger ( 2017-06-08 14:45:58 -0500 )edit

What fails before rebooting, and what are the symptoms for failure? It's normal that VMs are shut off when you reboot the compute host; this comes from libvirt or KVM, not OpenStack. Have you checked the status of your loopback device and LVM after the reboot? Do all expected LVM volumes exist?

Bernd Bausch gravatar imageBernd Bausch ( 2017-06-08 14:56:11 -0500 )edit

Also, what is in the cinder volume log?

Bernd Bausch gravatar imageBernd Bausch ( 2017-06-08 14:56:29 -0500 )edit
0

answered 2017-06-14 06:30:32 -0500

cinderela gravatar image

updated 2017-06-14 06:31:56 -0500

Hi @tiger, have you checked the status of cinder and your iSCSI target at ip = 192.168.140.217? Can you show the output of :

cinder type-list

and

cinder list --all-tenants

edit flag offensive delete link more
0

answered 2017-06-14 08:46:48 -0500

tiger gravatar image

Thank you both for your answers, but like usual I just blew it away and reinstalled, hoping for better luck this next time. God, this is getting old. The logfile entries are rubbish.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-06-08 12:57:58 -0500

Seen: 136 times

Last updated: Jun 14