Network template's order cannot be specified for set of roles
Bug #1540374 reported by
slava valyavskiy
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
slava valyavskiy | ||
7.0.x |
Fix Released
|
High
|
MOS Maintenance | ||
8.0.x |
Fix Released
|
High
|
slava valyavskiy | ||
Mitaka |
Fix Released
|
High
|
slava valyavskiy |
Bug Description
For example we have following network template and 'default-common' is representing set of actions what should be performed in the end of network actions in any case:
templates_
compute:
- cpu
- default-common
virt:
- virt
- default-common
Our current python implementation[0] will handle this template for node with roles 'virt+compute' in following order:
- cpu
- default-common
- virt
So, there is no way to move 'default-common' scheme in the end of network templates queue.
tags: | added: customer-found |
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
Changed in fuel: | |
milestone: | none → 9.0 |
no longer affects: | fuel/future |
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: area-python team-network |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → slava valyavskiy (slava-val-al) |
Changed in fuel: | |
status: | Confirmed → In Progress |
tags: |
added: move-to-9.0 removed: move-to-mu |
tags: | added: feature |
tags: | added: sla1 |
summary: |
- Network template's order is not taking in account for set of roles + Network template's order cannot be specified for set of roles |
tags: | added: on-verification |
tags: | added: on-verification |
tags: | added: on-verification |
tags: | added: on-verification |
To post a comment you must log in.
This will not get fixed by 8.0 HCF. Moving to 8.0 updates