yahoo-eng-team team mailing list archive

[John Garbutt <john@xxxxxxxxxxxxxxx>]

There is a blueprint for the fix for this:
https://blueprints.launchpad.net/nova/+spec/allow-image-to-be-specified-during-rescue

** Changed in: nova
       Status: Triaged => Invalid

-- 
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/1188141

Title:
  Deleting images breaks rescue mode for servers built from said images

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Rescue image is considered to be the image from which the instance is
  built from. If that image is deleted, the rescue fails

  Consider this scenario,
  The customer has a snapshot of an instance. He build another instance from the snapshot and deletes the snapshot. Now the customer tries to rescue the instance that was built from the snapshot, it fails because the rescue image is not available.

  Possible solutions -

  1. Recursively find the image that's available:
  The system_metadata of an instance has the "image_base_image_ref" as property set on it. This points to image from which it was built.
  Image has instance_uuid, if it's a snapshot. 
  We'll have to recursively find the base_install and use it as rescue image if the snapshot is deleted.

  2. Store the corresponding original image reference in all images. So
  that it's easier to find the rescue image.

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