yahoo-eng-team team mailing list archive

[Eric Brown <browne@xxxxxxxxxx>]

Public bug reported:

The resize operation when using the VCenter driver ends up resizing the
original VM and not the newly cloned VM.

To recreate:
1) create a new VM from horizon using default debian image.  I use a flavor of nano.
2) wait for it to complete and go active
3) click on resize and choose a flavor larger than what you used originally.  i then usually choose a flavor of small.
4) wait for horizon to prompt you to confirm or revert the migration.
5) Switch over to vSphere Web Client.  Notice two VMs for your newly created instance.  One with a UUID name and the other with a UUID-orig name.  "-orig" indicating the original.
6) Notice the original has be resized (cpu and mem are increased, disk is not, but that's a separate bug) and not the new clone.  This is problem #1.
7) Now hit confirm in horizon.  It works, but the logs contain a warning: "The attempted operation cannot be performed in the current state (Powered on).".  I suspect its attempting to destroy the orig VM, but the orig was the VM resized and powered on, so it fails.  This is problem #2.
Results in a leaked VM.

** Affects: nova
     Importance: High
     Assignee: Sidharth Surana (ssurana)
         Status: New


** Tags: icehouse-rc-potential vmware

** Changed in: nova
     Assignee: (unassigned) => Sidharth Surana (ssurana)

** Description changed:

  The resize operation when using the VCenter driver ends up resizing the
  original VM and not the newly cloned VM.
  
  To recreate:
  1) create a new VM from horizon using default debian image.  I use a flavor of nano.
  2) wait for it to complete and go active
  3) click on resize and choose a flavor larger than what you used originally.  i then usually choose a flavor of small.
  4) wait for horizon to prompt you to confirm or revert the migration.
- 5) Switch over to vSphere Web Client.  Notice two VMs for your newly created instance.  One with a UUID name and the other with a UUID-orig name.  "-orig" indicating the original.  
+ 5) Switch over to vSphere Web Client.  Notice two VMs for your newly created instance.  One with a UUID name and the other with a UUID-orig name.  "-orig" indicating the original.
  6) Notice the original has be resized (cpu and mem are increased, disk is not, but that's a separate bug) and not the new clone.  This is problem #1.
  7) Now hit confirm in horizon.  It works, but the logs contain a warning: "The attempted operation cannot be performed in the current state (Powered on).".  I suspect its attempting to destroy the orig VM, but the orig was the VM resized and powered on, so it fails.  This is problem #2.
+ Results in a leaked VM.

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

Title:
  VMware: resize operates on orig VM and not clone

Status in OpenStack Compute (Nova):
  New

Bug description:
  The resize operation when using the VCenter driver ends up resizing
  the original VM and not the newly cloned VM.

  To recreate:
  1) create a new VM from horizon using default debian image.  I use a flavor of nano.
  2) wait for it to complete and go active
  3) click on resize and choose a flavor larger than what you used originally.  i then usually choose a flavor of small.
  4) wait for horizon to prompt you to confirm or revert the migration.
  5) Switch over to vSphere Web Client.  Notice two VMs for your newly created instance.  One with a UUID name and the other with a UUID-orig name.  "-orig" indicating the original.
  6) Notice the original has be resized (cpu and mem are increased, disk is not, but that's a separate bug) and not the new clone.  This is problem #1.
  7) Now hit confirm in horizon.  It works, but the logs contain a warning: "The attempted operation cannot be performed in the current state (Powered on).".  I suspect its attempting to destroy the orig VM, but the orig was the VM resized and powered on, so it fails.  This is problem #2.
  Results in a leaked VM.

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