Bug 1284455

Summary: vmwareapi instance resize leads to the vm being cloned
Product: Red Hat OpenStack Reporter: Lee Yarwood <lyarwood>
Component: openstack-novaAssignee: Lee Yarwood <lyarwood>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: high    
Version: 6.0 (Juno)CC: berrange, dasmith, dmaley, eglynn, jchronis, kchamart, ndipanov, sbauza, sferdjao, sgordon, vromanso, yeylon
Target Milestone: asyncKeywords: Triaged, ZStream
Target Release: 6.0 (Juno)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-nova-2014.2.3-45.el7ost Doc Type: Bug Fix
Doc Text:
Cause: VMware guests would be cloned when resizing an instance using the vmwareapi backend. Consequence: As a result of cloning the underlying VMware guest volumes would be copied across datastores and ephemeral disks placed on inaccessible datastores. Fix: To correct this vmwareapi now resizes the VMware guest in place without cloning. Result: Resizing instances no longer clones the underlying VMware guest leaving volumes and ephemeral disks in place. Note: To upgrade to this version please ensure no active resize operations are in progress.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-12 22:07:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lee Yarwood 2015-11-23 11:50:41 UTC 
Description of problem:

An instance resize using vmwareapi leads to the associated instance VM being cloned. This in turn copies any attached volume vmdk files into instance instead of using a shadow VM that itself can be stored on a separate datastore to the instance.

This issue and many others relating to the cloning of the VM during a resize were addressed in Kilo by the following change :

VMware: address instance resize problems
https://review.openstack.org/#/c/145007/

Version-Release number of selected component (if applicable):
openstack-nova-api-2014.2.3-25.el7ost.noarch
openstack-nova-cert-2014.2.3-25.el7ost.noarch
openstack-nova-common-2014.2.3-25.el7ost.noarch
openstack-nova-compute-2014.2.3-25.el7ost.noarch
openstack-nova-conductor-2014.2.3-25.el7ost.noarch
openstack-nova-console-2014.2.3-25.el7ost.noarch
openstack-nova-novncproxy-2014.2.3-25.el7ost.noarch
openstack-nova-scheduler-2014.2.3-25.el7ost.noarch
python-nova-2014.2.3-25.el7ost.noarch
python-novaclient-2.20.0-1.el7ost.noarch

How reproducible:
Always.

Steps to Reproduce:
1. resize vmwareapi instance.


Actual results:
VMWare VM is cloned causing any attached volume vmdk files to be copied into the instance instead of using a shadow VM.

Expected results:
VMWare VM is not cloned and only resized.

Additional info:
Comment 14 Lon Hohberger 2016-01-12 22:07:45 UTC 
openstack-nova-2014.2.3-48.el7ost was shipped live, which contains a fix for this issue.  If this issue is not addressed, please reopen this bugzilla or file a new one.