← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1384386] Re: Image block device mappings for snapshots of instances specify delete_on_termination=null

 

** Changed in: nova
       Status: Fix Committed => 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/1384386

Title:
  Image block device mappings for snapshots of instances specify
  delete_on_termination=null

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Nova Juno

  Scenario:
  1. Boot an instance from a volume.
  2. Nova snapshot the instance.  This produces a Glance image with a block device mapping property like this:
  [{"guest_format": null, "boot_index": 0, "no_device": null, "snapshot_id": "1a642ca8-210f-4790-ab93-00b6a4b86a14", "delete_on_termination": null, "disk_bus": null, "image_id": null, "source_type": "snapshot", "device_type": "disk", "volume_id": null, "destination_type": "volume", "volume_size": null}]

  3. Create an instance from the Glance image.  Nova creates a new Cinder volume from the image's Cinder snapshot and attaches it to the instance.
  4. Delete the instance.

  Problem:  The Cinder volume created at step 3 remains.

  The block device mappings for Cinder snapshots created during VM
  snapshot and placed into the Glance image should specify
  "delete_on_termination":  True so that the Cinder volumes created for
  VMs booted from the image will be cleaned up on VM deletion.

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


References