force_config_drive cannot be set to False from nova.conf
Bug #1319180 reported by
Dmitry Borodaenko
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Davanum Srinivas (DIMS) |
Bug Description
force_config_drive is not cast to boolean, so the only way to disable this option is not to have it in nova.conf. If it is set to 'false' it is treated as a string and evaluates to true in configdrive.
tags: | added: compute |
tags: | added: low-hanging-fruit |
Changed in nova: | |
assignee: | nobody → Gary Kotton (garyk) |
milestone: | none → juno-1 |
importance: | Undecided → Medium |
Changed in nova: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
I am not sure that this is a bug. The default value is None. If this is set as None then it has the same functionality as False.
An alternative is that we check if this is "False" and then the method required_by will not invoke the config drive