[Yahoo-eng-team] [Bug 1853495] Re: Unable to create an instance based on an encrypted volume snapshot
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/train
Importance: Undecided
Status: New
** Changed in: nova/train
Status: New => In Progress
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nova/train
Assignee: (unassigned) => Lee Yarwood (lyarwood)
** Changed in: nova/stein
Assignee: (unassigned) => Lee Yarwood (lyarwood)
--
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/1853495
Title:
Unable to create an instance based on an encrypted volume snapshot
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) stein series:
In Progress
Status in OpenStack Compute (nova) train series:
In Progress
Bug description:
Description
===
Nova is currently unable to create and then boot from volumes from encrypted
volume snapshots when the original volume_type is not provided as part of the
block_device_mapping request to n-api. Failure to provide this will result in
the following error when attempting to launch the instance:
Details: {'code': 500, 'created': '2019-11-21T16:56:58Z', 'message':
'Build of instance 176ff71f-1dff-433b-92c7-5a15bade375f aborted:
Invalid input received: Invalid input received: Invalid volume_type
provided: 9142150e-70fe-4b14-942f-015025de4a68 (requested type is not
compatible; recommend omitting the type argument). (H'}"
Steps to reproduce
==
* Create an encrypted volume snapshot
* Attempt to create an instance based on this without providing a volume_type
in the block_device_mapping.
Expected result
===
Nova copies the original volume_type if one is not provided in the request.
Actual result
=
Nova fails to copy the original volume_type leading to a failure when
attempting to create a volume based on the encrypted volume snapshot as the
types do not match.
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?
Libvirt + KVM
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
==
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1853495/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1853495] Re: Unable to create an instance based on an encrypted volume snapshot
Reviewed: https://review.opendev.org/694497
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=5679a0bf99c17ff336fa520c9cdfad5156c6c9d2
Submitter: Zuul
Branch:master
commit 5679a0bf99c17ff336fa520c9cdfad5156c6c9d2
Author: Lee Yarwood
Date: Fri Nov 15 09:57:27 2019 +
block_device: Copy original volume_type when missing for snapshot based
volumes
Attempts to launch an instance from an encrypted volume snapshot would
previously fail if a volume_type was not specified in the
block_device_mapping of the boot request.
To avoid such failures DriverVolSnapshotBlockDevice will now attempt to
lookup and use the volume_type of the original volume that the snapshot
is based on. This should allow the eventual volume creation request
based on the snapshot to succeed in cases where a volume_type is
required but not provided in the boot request.
Closes-Bug: #1853495
Change-Id: Ic749c49e227e41732dbe04acea303b303acd264a
** 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/1853495
Title:
Unable to create an instance based on an encrypted volume snapshot
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Description
===
Nova is currently unable to create and then boot from volumes from encrypted
volume snapshots when the original volume_type is not provided as part of the
block_device_mapping request to n-api. Failure to provide this will result in
the following error when attempting to launch the instance:
Details: {'code': 500, 'created': '2019-11-21T16:56:58Z', 'message':
'Build of instance 176ff71f-1dff-433b-92c7-5a15bade375f aborted:
Invalid input received: Invalid input received: Invalid volume_type
provided: 9142150e-70fe-4b14-942f-015025de4a68 (requested type is not
compatible; recommend omitting the type argument). (H'}"
Steps to reproduce
==
* Create an encrypted volume snapshot
* Attempt to create an instance based on this without providing a volume_type
in the block_device_mapping.
Expected result
===
Nova copies the original volume_type if one is not provided in the request.
Actual result
=
Nova fails to copy the original volume_type leading to a failure when
attempting to create a volume based on the encrypted volume snapshot as the
types do not match.
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?
Libvirt + KVM
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
==
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1853495/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
