Incorrect dropping of image meta properties not wanted for snapshotting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Daniel Berrange |
Bug Description
Back in July 20, there was a 'non_inheritabl
commit ae7adbb92babf2d
Author: Rick Harris <email address hidden>
Date: Fri Jul 20 22:35:10 2012 +0000
Adds non_inheritable
Some image-properties should not be inherited from the instance when
taking a snapshot because we want that functionality to only available
for the base-image, not subsequent snapshots.
As an example, we would like 'cache_in_nova' fast-cloning to be
available just for base-images and not customer snapshots created off a
base-image.
This patch adds a new configuration which allows operators to, at
runtime, select which image-properties should not be inherited by newly
created snapshots.
Change-Id: I8d7781b05ffd71
Although these properties were only really relevant to XenAPI, the logic was then moved into the compute manager api code for creating snapshots
commit 1c68e733ca0e536
Author: Kevin L. Mitchell <email address hidden>
Date: Thu Oct 4 16:23:14 2012 -0500
Move snapshot image property inheritance
The xenapi snapshotting code had support for inheriting properties
from the base image of the snapshot (by way of the system metadata
set on the snapshotted instance). The problem, however, came in the
fact that some image properties were set in nova.compute.api, but
those properties were not excluded from this inheritance logic
except through a configuration option called
"non_
default setting for this option to work around the bugs introduced
by setting image properties in two different locations, but now it
is time for the real fix.
This change moves the inheritance logic into
nova.
still set through the xenapi snapshotting logic: the "os_type" and
the "auto_disk_config" properties, which are presumed to be xenapi
specific. The change also alters the inheritance logic to ensure
that the work-around listing of image properties in
non_
default for this configuration option is updated accordingly.
(Note: It will not harm anything to have these image properties
still listed in non_inheritable
that override this option do not need to be altered.)
Change-Id: I3514da432cc10c
Next up in
commit 8e575be75c80ea7
Author: Xavier Queralt <email address hidden>
Date: Mon Aug 26 22:53:03 2013 +0200
Add methods to get image metadata from instance
This patch adds a couple of utility functions that enclose all the logic
for getting and parsing the image metadata stored in the instance's
system metadata.
First, this will try to fetch the metadata from the real image and will
prevent it from failing if it is not available. It will be then merged
with the image metadata stored during the instance creation.
Related to bug #1039662
Change-Id: I2130caf1985858
The nova.utils.
Finally many areas of the codebase are updated to use nova.utils.
commit 4389f2292a0177c
Author: Xavier Queralt <email address hidden>
Date: Mon Aug 26 22:55:46 2013 +0200
Avoid errors on some actions when image not usable
Using the metadata saved on instance creation, we can now get all the
image related metadata we need from the instance itself.
This patch replace the logic for getting the image metadata on some
actions that shouldn't fail when the image is not accessible (create
an snapshot, resize, migrate, rescue an instance or attach an
interface).
Fixes bug 1039662
Change-Id: Id8c2f13ca96908
This is a mistake, because the CONF.non_
tags: | added: compute xenserver |
Changed in nova: | |
milestone: | none → liberty-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | liberty-1 → 12.0.0 |
Fix proposed to branch: master /review. openstack. org/187250
Review: https:/