nova instance snapshot does not wait for volume snaps
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Undecided
|
Vladislav Belogrudov |
Bug Description
Currently when snapping a boot-from-volume instance nova immediately returns success and glance reports active image. Snapping of disks can take some time and if we try to launch a new instance from that image as soon as we get active image state we get error. Nova should wait until all snaps are ready before returning success.
relevant code lines:
https:/
because in my backend setup snaps are somewhat long I always fail multiattach tempest test:
{0} tearDownClass (tempest.
Captured traceback:
~~~~~~~~~~~~~~~~~~~
Traceback (most recent call last):
File "/opt/stack/
raise value.with_
File "/opt/stack/
teardown()
File "/opt/stack/
raise testtools.
testtools.
Details: {'code': 400, 'message': 'Invalid volume: Volume status must be available or error or error_restoring or error_extending or error_managing and must not be migrating, attached, belong to a group, have snapshots, awaiting a transfer, or be disassociated from snapshots after volume transfer.'}, <traceback object at 0x7f622cbbdc80>)
This happens because we try to delete boot volume and snap while snap is not ready. Also this trace is while trying to create a new instance from 'active' image:
юл 04 11:13:10 openstack-dev-00 nova-compute[
Changed in nova: | |
assignee: | nobody → Vladislav Belogrudov (vlad-belogrudov) |
Fix proposed to branch: master /review. opendev. org/c/openstack /nova/+ /848638
Review: https:/