Unable to rescue using volume snapshot based images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Lee Yarwood | ||
Ussuri |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Description
===========
While working on bug #1876330 it was observed that attempts to rescue an instance with a volume snapshot image were permitted but would ultimately fail to boot the instance with file based imagebackends *or* fail out right with the rbd imagebackend. This is due to these images being metadata containers and containing no image data, thus resulting in Nova attempting to rescue with zero length images.
Steps to reproduce
==================
* Launch a volume backed instance
* Snapshot the instance using the imageCreate API.
* Attempt to rescue the image using the created image.
Expected result
===============
The request is rejected as there is no support for rescuing using a volume snapshot based image.
Actual result
=============
The request is acceptable and either fails to boot the instance or fails earlier due to the zero length image.
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://
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
==============
See bug #1876330.
Changed in nova: | |
assignee: | nobody → Lee Yarwood (lyarwood) |
Fix proposed to branch: master /review. opendev. org/729261
Review: https:/