[vCenter] Launch instance from a snapshot has failed

[Alexander Arzhanov]

Fuel 8.0 ISO #322

Enviroment:
Compute: QEMU + vCenter
Networking Setup: Neutron with VMware DVS (ML2 plugin)
Storage backends: default
Additional services: all by default

Settings:
VMware vCenter/ESXi datastore for images (Glance)

Nodes:
Controller
Controller
Controller
Compute, Cinder
Cinder-vmware
Compute-vmware

Steps to reproduce:
1. Get existing image by name.
2. Launch an instance using the default image (flavor m1.tiny)
3. Make snapshot of the created instance.
4. Delete the instance created in step 1.
5. Wait while instance deleted
6. Launch another instance from the snapshot created in step 2.

Observed behavior:
Error: Failed to perform requested operation on instance "test_vcenter3", the instance has an error status: Please try again later [Error: No valid host was found. There are not enough hosts available.].

After apply workaround from this bug - https://bugs.launchpad.net/fuel/+bug/1529056, we faced with this problem -http://paste.openstack.org/show/484618/

Upstream bug - https://bugs.launchpad.net/nova/+bug/1528114

[Andriy Kurilin (andreykurilin)]

Hi all!
Just an update about this bug:
 1) The exception occures while preparing an image(resizing it to the size of the flavor).
 2) The exception raises from vmware api. All parameters from the nova side match vmware api( https://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/vim.VirtualDiskManager.html#extendVirtualDisk )
 3) The exception is not thrown if expected size(while resizing) increased at least for 1 kB
 4) The exception is not thrown if bigger flavor(flavor with the bigger disk) is selected

[Roman Podoliaka (rpodolyaka)]

Ilya, please do not change the importance without a comment.

This is not Critical, as:

1) it's only reproduced on a non-default compute driver

2) it's not a basic use case

3) it has easy workarounds, described by Andrey

[Ilya Bumarskov (ibumarskov)]

Was raised to Critical because basic functionality doesn't work.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/275594

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/8.0
Review: https://review.openstack.org/275681

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: openstack-ci/fuel-8.0/liberty
Change author: Radoslav Gerganov <email address hidden>
Review: https://review.fuel-infra.org/16654

[Roman Podoliaka (rpodolyaka)]

This is already fixed in Mitaka:

https://review.openstack.org/#/c/168024/8

[Roman Podoliaka (rpodolyaka)]

Ilya, I removed release-notes and docs tags - we believe the proposed patch above fixes the issue.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/275594
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=4aece0ee5a90edbbacced28e95980c996edd8a58
Submitter: Jenkins
Branch: master

commit 4aece0ee5a90edbbacced28e95980c996edd8a58
Author: Ilya Bumarskov <email address hidden>
Date: Sun Jan 31 21:02:32 2016 +0300

    Add workaround for bug with launching vcenter instance from snapshot

    Change-Id: I224451a425448d65fc804e55d292fe4e9252e36f
    Related-bug: #1536795

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/275681
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=7bcddf18020f2d94a553a441ff57dff9632865df
Submitter: Jenkins
Branch: stable/8.0

commit 7bcddf18020f2d94a553a441ff57dff9632865df
Author: Ilya Bumarskov <email address hidden>
Date: Sun Jan 31 21:02:32 2016 +0300

    Add workaround for bug with launching vcenter instance from snapshot

    Change-Id: I224451a425448d65fc804e55d292fe4e9252e36f
    Related-bug: #1536795

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/16654
Submitter: Pkgs Jenkins <email address hidden>
Branch: openstack-ci/fuel-8.0/liberty

Commit: 76bcddc4016149d78a8169e332fba0a04facff7d
Author: Radoslav Gerganov <email address hidden>
Date: Wed Feb 3 13:01:05 2016

VMware: Handle image size correctly for OVA and streamOptimized images

The image size is different from the virtual disk size when the image is
streamOptimized or OVA. In this case we need to use the size of the
virtual disk which belongs to the temporary VM created by ImportVApp.
This works for both vSAN and VMFS datastores.

Related-Upstream-Bugs: #1240373 #1472955

Closes-Bug: #1536795

Change-Id: Ie7df9a78632ff01453b07ee9fed3dffdd8b4a0c7

[Roman Podoliaka (rpodolyaka)]

Fix merged ^

[Ilya Bumarskov (ibumarskov)]

Verified on Fuel 8.0 #569

[Ilya Bumarskov (ibumarskov)]

Verified on fuel 9.0 mos-iso#460