yahoo-eng-team team mailing list archive

[Alan Pevec <1241350@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova/havana
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1241350

Title:
  VMware: Detaching a volume from an instance also deletes the volume's
  backing vmdk (ESXDriver only)

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) havana series:
  Fix Released

Bug description:
  I found that when I run:

  % nova volume-detach my_instance c54ad11f-4e51-41a0-97db-7e551776db59

  where the volume with given id is currently attached to my running
  instance named my_instance, the operation completes successfully.
  Nevertheless a subsequent attach of the same volume again will fail.
  So:

  % nova volume-attach my_instance c54ad11f-4e51-41a0-97db-7e551776db59
  /dev/sdb

  fails with the error that the volume's vmdk file is not found.

  Cause:

  During volume detach a delete_virtual_disk_spec is used to remove the
  device from the running instance. This spec also "destroy"s the
  underlying vmdk file. The offending line is :
  https://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/vm_util.py#L471

  Possible fix:
  The fileOperation field of the device config during this reconfigure operation should be left unset. We should continue setting device_config.operation field to "remove". This will remove the device from the VM without deleting the underlying vmdk backing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1241350/+subscriptions