yahoo-eng-team team mailing list archive

[Lee Yarwood <lyarwood@xxxxxxxxxx>]

Public bug reported:

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://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
==============

See bug #1876330.

** Affects: nova
     Importance: Undecided
     Assignee: Lee Yarwood (lyarwood)
         Status: In Progress


** Tags: rescue volumes

** Changed in: nova
     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/1879500

Title:
  Unable to rescue using volume snapshot based images

Status in OpenStack Compute (nova):
  In Progress

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://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
  ==============

  See bug #1876330.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1879500/+subscriptions