Unable to attach volume to instance instance-00000001

asked 2017-01-01 06:19:15 +0200

ADarkDividedGem gravatar image

updated 2017-01-06 11:18:36 +0200

After a fresh install of v-magine (2016.2.0.0) on a hyper-converged deployment with Windows Server 2016 I tried to launch an instance of the "cirros" image but it failed with the common error message:

No valid host was found. There are not enough hosts available.

After ensuring nova service-list listed the "nova-compute" as "enabled" and "up" for my host (HV1) I looked at the /var/logs/nova-conductor.log which reported an error in nova.scheduler.utils

RescheduledException: Build of instance bde11dbc-e5a3-4635-89a4-034513f8efb5 was re-scheduled: <x_wmi: Array item cannot be NULL >

This exception was then repeated in the C:\OpenStack\Log\nova-compute.log log file which showed there were some issues with attaching the volume to the instance:

Unable to attach volume to instance instance-00000001
Traceback (most recent call last):
  File "C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\hyperv\nova\volumeops.py", line 115, in attach_volume
  File "C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\hyperv\nova\volumeops.py", line 281, in attach_volume
  File "C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\os_win\utils\compute\vmutils.py", line 496, in attach_volume_to_controller
    diskdrive.HostResource = [mounted_disk_path]
  File "C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\wmi\__init__.py", line 111, in func_wrapper
    raise x_wmi(err_msg, com_ex)
x_wmi: <x_wmi: Array item cannot be NULL >

It works when I create an instance without a volume which suggests there is something wrong with volume creation. I installed v-magine onto a Cluster Shared Volume that communicates between nodes via Server Message Block (SMB) 3 and 10GbE Remote-Direct Memory Access (RDMA) networking. I don't have a SAN (FC or iSCSI).

The full log files can be found here nova-conductor.log and here nova-compute.log any idea what might be going wrong?

edit retag flag offensive close merge delete


Seems like hyper-v can connect to target but cannot attach it to the VM. In powershell please try 'echo "san" | diskpart'. My suspicion is that san policy is online, which should be offline. If this is the case, try to put it offline 'san POLICY=OfflineShared'.

danardelean gravatar imagedanardelean ( 2017-01-06 17:11:50 +0200 )edit

The SAN Policy is already set to "Offline All", I changed it to "Offline Shared" and the problem still exits

ADarkDividedGem gravatar imageADarkDividedGem ( 2017-01-06 17:35:51 +0200 )edit

The volume.log (http://paste.openstack.org/show/594131/) reports "Attach volume completed successfully" followed by "Detach volume completed successfully." which suggests its attaching the volume then detaching it for some reason?

ADarkDividedGem gravatar imageADarkDividedGem ( 2017-01-06 18:12:58 +0200 )edit

Right after the instance fails, if you do a "echo 'list disk' | diskpart" in powershell, what does it say? At VM creation, chose a distinct volume size so you can easily see the disk in diskpart.

danardelean gravatar imagedanardelean ( 2017-01-06 18:53:27 +0200 )edit

After spamming the "list disk" command during the creation of the instance the 1Gig volume does appear briefly as "Disk 9 Offline 1024 MB 1024 MB" but then disappears.

ADarkDividedGem gravatar imageADarkDividedGem ( 2017-01-06 19:06:51 +0200 )edit