force_config_drive gives inconsistent instance state
Bug #1403889 reported by
Matthew Gilliard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Gary Kotton |
Bug Description
Default devstack install leaves
force_
in /etc/nova/nova.conf (slightly contradicting the docs: http://
An instance booted on this system does not have a config drive according to 'nova show', and does not get an entry in the config_drive column of the instances table. However the libvirt xml does show a config drive, and of course it's visible on the instance.
Changed in nova: | |
importance: | Undecided → Low |
Changed in nova: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
This is only evident when force_config_drive is used. If that is not set and an instance is booted with '--config_drive true' then the state is consistent.