discoverd incorrectly reports False from validate when disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Medium
|
Dmitry Tantsur |
Bug Description
When support for ironic-discoverd is disabled by config option (and this is the current default behavior), calling "ironic node-validate" incorrectly reports that the interface fails validation:
| Interface | Result | Reason |
+------
| inspect | False | ironic-discoverd support is disabled in configuration, set [discoverd]enabled to true to enable |
This indicates to users that they have done something wrong -- when in fact it is a configuration option that the operator has set.
Unsupported interfaces should return a value of "None", not "False".
Changed in ironic: | |
status: | New → Triaged |
assignee: | nobody → Devananda van der Veen (devananda) |
importance: | Undecided → High |
Changed in ironic: | |
status: | Triaged → In Progress |
Changed in ironic: | |
assignee: | Devananda van der Veen (devananda) → Dmitry "Divius" Tantsur (divius) |
Changed in ironic: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in ironic: | |
milestone: | kilo-3 → 2015.1.0 |
This currently only affects the "fake" driver, since no other drivers instantiate the DiscoverdInspect class yet. Changing to Medium as it doesn't affect any users.