Public bug reported:
Description:
After updating the image property and rebuilding the instance with that
image, resize/migrate will result in metadata inconsistencies.
Details:
Metadata for an image is managed as "instance_system_metadata" table. Usually,
this metadata has the following parameters
hw_vif_model: virtio, e1000e, etc...
If not specified, default value is chosen and the default value depends on
libvirtd or virt-qemud configuration.
These metadata are stored the following object in creating a VM
- "RequestSpecs" object: never updated. (Keep on holding an initial state)
- "ImageMeta" object: this is same as "instance_system_metadata" and "rebuild"
operation updates from the latest image data.
The above condition leads metadata inconsistency on driver layer in generating
virsh XML definition.
Step to reproduce:
1. Create an image with no "hw_vif_model"
2. Create a VM with the above image
(At that moment, let's assume a default hw_vif_model was "virtio")
3. Update the image to add "hw_vif_model=e1000e"
4. Rebuild the VM
After that, VM's interface type has changed into "e1000e" on virsh XML layer
5. Resize/Migrate the VM
After that, VM's interface type has changed into "virtio" on virsh XML layer
Environment:
Caracal release (2024.1)
** Affects: nova
Importance: Undecided
Assignee: Masanori Kuroha (mkuroha)
Status: New
** Changed in: nova
Assignee: (unassigned) => Masanori Kuroha (mkuroha)
** Summary changed:
- mageMeta never updated in VM resize/migrate
+ ImageMeta never updated in VM resize/migrate
--
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/2088949
Title:
ImageMeta never updated in VM resize/migrate
Status in OpenStack Compute (nova):
New
Bug description:
Description:
After updating the image property and rebuilding the instance with
that image, resize/migrate will result in metadata inconsistencies.
Details:
Metadata for an image is managed as "instance_system_metadata" table.
Usually, this metadata has the following parameters
hw_vif_model: virtio, e1000e, etc...
If not specified, default value is chosen and the default value depends on
libvirtd or virt-qemud configuration.
These metadata are stored the following object in creating a VM
- "RequestSpecs" object: never updated. (Keep on holding an initial state)
- "ImageMeta" object: this is same as "instance_system_metadata" and
"rebuild" operation updates from the latest image data.
The above condition leads metadata inconsistency on driver layer in
generating virsh XML definition.
Step to reproduce:
1. Create an image with no "hw_vif_model"
2. Create a VM with the above image
(At that moment, let's assume a default hw_vif_model was "virtio")
3. Update the image to add "hw_vif_model=e1000e"
4. Rebuild the VM
After that, VM's interface type has changed into "e1000e" on virsh XML
layer
5. Resize/Migrate the VM
After that, VM's interface type has changed into "virtio" on virsh XML
layer
Environment:
Caracal release (2024.1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2088949/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
