vms loose acess to config drive with CONF.force_config_drive=True after hard reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
sean mooney |
Bug Description
The fix to bug https:/
https:/
changed the behavior of nova.virt.
to depend on instance.
https:/
but did not reorder
https:/
as a result when nova.compute.
is called instance.
as a result instance.
this results in a vm that is spawned on a host with force_config_
with a config drive but loosing it after a hard reboot.
for any deployment that uses config driver for vendor data or device role tagging because they do not deploy the metadata service this is a regressions as they cannot fall back to the metadta service.
this also might cause issue for deployment that support the deprectated file injection api that is part of the v2.1 api as the files are only stored in the config drive and are not part metadta endoint
note: i have not checked if we autoset instnace.
the fix is simple jsut swap the order of https:/
and then instance will have there instnace.
and it will be sticky for the lifetime of the instance.
Changed in nova: | |
assignee: | sean mooney (sean-k-mooney) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → sean mooney (sean-k-mooney) |
tags: | added: train-rc-potential |
Changed in nova: | |
assignee: | sean mooney (sean-k-mooney) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → sean mooney (sean-k-mooney) |
note i set this to medium since we were looking at backporting /bugs.launchpad .net/nova/ +bug/1827492 config_ drive seperately
https:/
and we might have data lost in the file injection case if that does not auto
set instance.