yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #82679
[Bug 1878583] Re: Unable to createImage/snapshot paused volume backed instances
Reviewed: https://review.opendev.org/728011
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cfde53e4b402e71d7f53b6e0ab232854dba160dc
Submitter: Zuul
Branch: master
commit cfde53e4b402e71d7f53b6e0ab232854dba160dc
Author: Lee Yarwood <lyarwood@xxxxxxxxxx>
Date: Thu May 14 10:49:07 2020 +0100
compute: Allow snapshots to be created from PAUSED volume backed instances
Iabeb44f843c3c04f767c4103038fcf6c52966ff3 allowed snapshots to be
created from PAUSED non-volume backed instances but missed the volume
backed use case.
This change simply adds PAUSED to the list of acceptable vm_states when
creating a snapshot from a volume backed instance in addition to the
already supported ACTIVE, STOPPED and SUSPENDED vm_states.
Closes-Bug: #1878583
Change-Id: I9f95a054de9d43ecaa50ff7ffc9343490e212d53
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1878583
Title:
Unable to createImage/snapshot paused volume backed instances
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Description
===========
Unable to createImage/snapshot paused volume backed instances.
Steps to reproduce
==================
- Pause a volume backed instance
- Attempt to snapshot the instance using the createImage API
Expected result
===============
A snapshot image is successfully created as is the case for paused instances that are not volume backed.
Actual result
=============
n-api returns the following error:
{'code': 409, 'message': "Cannot 'createImage' instance
bc5a7ae4-fca9-4d83-b1b8-5534f51a9404 while it is in vm_state paused"}
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://docs.openstack.org/releases/
master
2. Which hypervisor did you use?
(For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
What's the version of that?
N/A
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
What's the version of that?
N/A
3. Which networking type did you use?
(For example: nova-network, Neutron with OpenVSwitch, ...)
N/A
Logs & Configs
==============
As above.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1878583/+subscriptions
References