VMWARE : create volume fails if targeted datastore's host is in maintenace mode.

Bug #1371489 reported by satyadev svn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Confirmed
High
Vipin Balachandran

Bug Description

pre req : move two hosts to maintenace mode in cluster. Now I create a profile with those host's datastore mapped to profile. and user create volume type with profile. say [ profile name : bronze]

Test steps :
as admin user create a volume type with bronze profile. [cinder type-create bronze ; cinder type-key bronze set vmware:storage_profile=bronze]

Now create volume from above volume type. [cinder create --volume-type bronze 1]

log snipet :

2014-09-17 14:47:44.777 [01;31mERROR cinder.volume.drivers.vmware.vmdk [[01;36mreq-40c5a6ac-2310-482c-8ba9-ffb24134f298 [00;36m02b8c430f4e347528939f69c874ddf80 755e658cd34b44448418d7a31ec2ab7d[01;31m] [01;35m[01;31mException in copying the image to the volume: (VimFaultException('Unable to access the virtual machine configuration: Unable to access file [local-0 (2)]',),).[00m
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00mTraceback (most recent call last):
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m File "/opt/stack/cinder/cinder/volume/drivers/vmware/vmdk.py", line 1277, in copy_image_to_volume
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m image_size_in_bytes, image_adapter_type, image_disk_type)
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m File "/opt/stack/cinder/cinder/volume/drivers/vmware/vmdk.py", line 1130, in _create_volume_from_non_stream_optimized_image
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m vmdk_path.get_descriptor_ds_file_path(), dc_ref)
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m File "/opt/stack/cinder/cinder/openstack/common/excutils.py", line 82, in __exit__
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m six.reraise(self.type_, self.value, self.tb)
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m File "/opt/stack/cinder/cinder/volume/drivers/vmware/vmdk.py", line 1117, in _create_volume_from_non_stream_optimized_image
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m disk_type)
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m File "/opt/stack/cinder/cinder/volume/drivers/vmware/volumeops.py", line 1042, in clone_backing
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m task_info = self._session.wait_for_task(task)
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m File "/opt/stack/cinder/cinder/volume/drivers/vmware/api.py", line 288, in wait_for_task
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m return loop.start(self._task_poll_interval).wait()
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m File "/usr/local/lib/python2.7/dist-packages/eventlet/event.py", line 121, in wait
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m return hubs.get_hub().switch()
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 293, in switch
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m return self.greenlet.switch()
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m File "/opt/stack/cinder/cinder/openstack/common/loopingcall.py", line 81, in _inner
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m self.f(*self.args, **self.kw)
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m File "/opt/stack/cinder/cinder/volume/drivers/vmware/api.py", line 319, in _poll_task
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m raise excep
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00mVimFaultException: Unable to access the virtual machine configuration: Unable to access file [local-0 (2)]
[01;31m2014-09-17 14:47:44.777 TRACE cinder.volume.drivers.vmware.vmdk [01;35m[00m
2014-09-17 14:47:44.779 [01;31mERROR cinder.volume.flows.manager.create_volume [[01;36mreq-40c5a6ac-2310-482c-8ba9-ffb24134f298 [00;36m02b8c430f4e347528939f69c874ddf80 755e658cd34b44448418d7a31ec2ab7d[01;31m] [01;35m[01;31mFailed to copy image c42a16fe-36ee-48da-845f-76227790666d to volume: 3b47f53e-0a27-4923-8e1b-f55998dee91b, error: Unable to access the virtual machine configuration: Unable to access file [local-0 (2)][00m
2014-09-17 14:47:44.780 [00;32mDEBUG taskflow.engines.action_engine.runner [[01;36mreq-40c5a6ac-2310-482c-8ba9-ffb24134f298 [00;36m02b8c430f4e347528939f69c874ddf80 755e658cd34b44448418d7a31ec2ab7d[00;32m] [01;35m[00;32mExiting old state 'SCHEDULING' in response to event 'wait'[00m [00;33mfrom (pid=20239) on_exit /opt/stack/taskflow/taskflow/engines/action_engine/runner.py:156[00m
2014-09-17 14:47:44.780 [00;32mDEBUG taskflow.engines.action_engine.runner

Tags: drivers vmware
Revision history for this message
satyadev svn (svnsatya) wrote :
Revision history for this message
satyadev svn (svnsatya) wrote :

VC cluster have 4 hosts [so move 2 hots to maintenace mode].

profile mapped to all hosts datastores.

satyadev svn (svnsatya)
summary: - create volume fails if targeted datastore's host is in maintenace mode.
+ VMWARE : create volume fails if targeted datastore's host is in
+ maintenace mode.
Revision history for this message
satyadev svn (svnsatya) wrote :

- create volume of bronze profile with image as source.
Attaching logs [host-15 in maintenance mode and local-0(2) is present that host.]

Changed in cinder:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Vipin Balachandran (vbala)
Revision history for this message
Vipin Balachandran (vbala) wrote :

Volume create won't fail due to hosts in maintenance mode. As per the logs, clone backing failed and this is due to bug 1380602.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.