yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #94883
[Bug 2088464] [NEW] Config drive not regenerated on power off/power on of VM
Public bug reported:
Description
===========
Config drive is not regenerated on power off/power on of VM.
So attached share_mapping cannot be included into it.
Steps to reproduce
==================
- Stop a VM
- Attach a share
- Start the VM
- Connect to the VM and check metadata --> share is part of metadata
- Check config drive, the config drive does not content metadata for share.
Expected result
===============
Share part of metadata in the config drive.
Actual result
=============
the config drive does not content metadata for share.
Environment
===========
Epoxy
Devstack
Links
=====
https://review.opendev.org/c/openstack/nova-specs/+/863884 link to a spec to fix this issue
** Affects: nova
Importance: Undecided
Status: Triaged
** Changed in: nova
Status: New => Triaged
--
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/2088464
Title:
Config drive not regenerated on power off/power on of VM
Status in OpenStack Compute (nova):
Triaged
Bug description:
Description
===========
Config drive is not regenerated on power off/power on of VM.
So attached share_mapping cannot be included into it.
Steps to reproduce
==================
- Stop a VM
- Attach a share
- Start the VM
- Connect to the VM and check metadata --> share is part of metadata
- Check config drive, the config drive does not content metadata for share.
Expected result
===============
Share part of metadata in the config drive.
Actual result
=============
the config drive does not content metadata for share.
Environment
===========
Epoxy
Devstack
Links
=====
https://review.opendev.org/c/openstack/nova-specs/+/863884 link to a spec to fix this issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2088464/+subscriptions