Validate driver composition config across conductors
Bug #1686124 reported by
Jim Rollenhagen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Opinion
|
Medium
|
Unassigned | ||
Bug Description
This todo needs to be done: https:/
From the spec: "A warning will be issued on conductor start up, if it detects that other conductors have a different set of interfaces for the same enabled hardware type. This will also track the default interface for each hardware type and interface type combination." http://
| Changed in ironic: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in ironic: | |
| status: | Confirmed → Triaged |
| tags: | added: conductor driver |
Revision history for this message
| Julia Kreger (juliaashleykreger) wrote | #1 |
| Changed in ironic: | |
| status: | Triaged → Opinion |
To post a comment you must log in.
Some operators intentionally run varying configuration clusters. As such, a warning is still a good idea, but not something we should error on.