yahoo-eng-team team mailing list archive

[Vipin Balachandran <vbala@xxxxxxxxxx>]

Public bug reported:

Steps to reproduce:

* Attach volume with ID = foo to nova instance
* Verify instance VM's vmx file in ESX host  (should contain entry volume-foo = <volume-vmdk-uuid>)
* Detach volume
*  Verify instance VM's vmx file in ESX host  (still contains entry volume-foo = <volume-vmdk-uuid>)

Expected behavior:

After volume detach, the vmx file shouldn't contain volume related
entry.

** Affects: nova
     Importance: Undecided
     Assignee: Vipin Balachandran (vbala)
         Status: In Progress


** Tags: vmware

** Changed in: nova
     Assignee: (unassigned) => Vipin Balachandran (vbala)

-- 
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/1477159

Title:
  VMware: volume's vmdk uuid exists in instance's vmx file even after
  volume detach

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Steps to reproduce:

  * Attach volume with ID = foo to nova instance
  * Verify instance VM's vmx file in ESX host  (should contain entry volume-foo = <volume-vmdk-uuid>)
  * Detach volume
  *  Verify instance VM's vmx file in ESX host  (still contains entry volume-foo = <volume-vmdk-uuid>)

  Expected behavior:

  After volume detach, the vmx file shouldn't contain volume related
  entry.

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