yahoo-eng-team team mailing list archive

[Lucian Petrut <1907216@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

After an instance is unshelved, the instance image ref will point to the
original image instead of the snapshot created during the shelving
[1][2].

Subsequent instance operations will use the wrong image id. For example,
in case of cold migrations, Hyper-V instances will be unable to boot
since the differencing images will have the wrong base [3]. Other image
related operations might be affected as well.

As pointed out by Matt Riedemann on the patch [1], Nova shouldn't set
back the original image id, instead it should use the snapshot id.

[1] I3bba0a230044613e07122a6d122597e5b8d43438
[2] https://github.com/openstack/nova/blob/22.0.1/nova/compute/manager.py#L6625
[3] http://paste.openstack.org/raw/800822/

** Affects: nova
     Importance: Undecided
     Assignee: Lucian Petrut (petrutlucian94)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Lucian Petrut (petrutlucian94)

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

Title:
  Wrong image ref after unshelve

Status in OpenStack Compute (nova):
  New

Bug description:
  After an instance is unshelved, the instance image ref will point to
  the original image instead of the snapshot created during the shelving
  [1][2].

  Subsequent instance operations will use the wrong image id. For
  example, in case of cold migrations, Hyper-V instances will be unable
  to boot since the differencing images will have the wrong base [3].
  Other image related operations might be affected as well.

  As pointed out by Matt Riedemann on the patch [1], Nova shouldn't set
  back the original image id, instead it should use the snapshot id.

  [1] I3bba0a230044613e07122a6d122597e5b8d43438
  [2] https://github.com/openstack/nova/blob/22.0.1/nova/compute/manager.py#L6625
  [3] http://paste.openstack.org/raw/800822/

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