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:
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.