Composable networks imposes order-of-operations of environment includes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Dan Sneddon |
Bug Description
Composable networks generates the environments/
The problem is that this introduces a regression where the Management network ports won't be created if network-
In order to avoid this regression, the network-
Example:
network-
OS::TripleO:
(the above line was previously not included in the network-
network-
OS::TripleO:
If the network-
We shouldn't need to use noop.yaml at all in the network environment files. We already set all ports to noop.yaml in the role definitions and overcloud-
Changed in tripleo: | |
status: | New → Triaged |
milestone: | none → queens-1 |
importance: | Undecided → High |
Changed in tripleo: | |
importance: | High → Medium |
assignee: | nobody → Dan Sneddon (dsneddon) |
Changed in tripleo: | |
status: | Triaged → In Progress |
To clarify, wasn't this always order dependent, as we previously had hard-coded noops in the network- isolation. yaml?