Before we stored flavors in instance_extra, certain fields, defined
in nova.compute.flavors.system_metadata_flavor_props, were stored
in the instance.system_metadata for the embedded instance.flavor.
The "disabled" field wasn't one of those keys, however, so really
old instances that had their embedded flavor converted to the
serialized instance_extra form won't have the disabled attribute
set and we need to default those here so callers, like the
versioned notfication FlavorPayload, don't explode trying to load
instance.flavor.disabled.
Reviewed: https:/ /review. openstack. org/579925 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=8df21c1e5fc 46f2774a7653e1c 9a4c2ac0b5dbfd
Committed: https:/
Submitter: Zuul
Branch: master
commit 8df21c1e5fc46f2 774a7653e1c9a4c 2ac0b5dbfd
Author: Matt Riedemann <email address hidden>
Date: Tue Jul 3 13:03:54 2018 -0400
Default embedded instance. flavor. disabled attribute
Before we stored flavors in instance_extra, certain fields, defined flavors. system_ metadata_ flavor_ props, were stored system_ metadata for the embedded instance.flavor. flavor. disabled.
in nova.compute.
in the instance.
The "disabled" field wasn't one of those keys, however, so really
old instances that had their embedded flavor converted to the
serialized instance_extra form won't have the disabled attribute
set and we need to default those here so callers, like the
versioned notfication FlavorPayload, don't explode trying to load
instance.
Change-Id: I72f8c11b8b2df1 416dec8e2d9250e ac0693a30e9
Closes-Bug: #1739325