| 2014-03-20 21:35:20 |
Eric Brown |
bug |
|
|
added bug |
| 2014-03-20 21:36:43 |
Eric Brown |
nova: assignee |
|
Sidharth Surana (ssurana) |
|
| 2014-03-20 21:37:13 |
Eric Brown |
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. |
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. |
|
| 2014-03-20 21:38:31 |
Tracy Jones |
tags |
vmware |
icehouse-rc-potential vmware |
|
| 2014-03-20 21:38:36 |
Tracy Jones |
nova: importance |
Undecided |
High |
|
| 2014-03-20 21:42:37 |
Tracy Jones |
nova: milestone |
|
icehouse-rc1 |
|
| 2014-03-21 12:52:36 |
Russell Bryant |
nova: status |
New |
In Progress |
|
| 2014-03-22 01:33:01 |
Tracy Jones |
tags |
icehouse-rc-potential vmware |
icehouse-rc1-potential vmware |
|
| 2014-03-24 13:40:26 |
Russell Bryant |
tags |
icehouse-rc1-potential vmware |
icehouse-rc-potential vmware |
|
| 2014-03-24 15:05:03 |
Russell Bryant |
tags |
icehouse-rc-potential vmware |
vmware |
|
| 2014-03-31 10:45:45 |
Mark McLoughlin |
tags |
vmware |
icehouse-rc-potential vmware |
|
| 2014-03-31 10:46:06 |
Mark McLoughlin |
tags |
icehouse-rc-potential vmware |
vmware |
|
| 2014-03-31 13:53:51 |
Russell Bryant |
nova: milestone |
icehouse-rc1 |
|
|
| 2014-03-31 13:54:02 |
Russell Bryant |
tags |
vmware |
icehouse-rc-potential vmware |
|
| 2014-04-07 15:14:43 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
| 2014-04-07 15:26:38 |
Russell Bryant |
nova: milestone |
|
icehouse-rc2 |
|
| 2014-04-07 17:58:14 |
OpenStack Infra |
nova: status |
Fix Committed |
Fix Released |
|
| 2014-04-17 09:19:03 |
Thierry Carrez |
nova: milestone |
icehouse-rc2 |
2014.1 |
|
