Public network on interfaces of compute node
Bug #1589898 reported by
Julia Aranovich
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
In Progress
|
Medium
|
Nikolay Tymtsiv |
Bug Description
Steps to reproduce in Fuel UI:
1. create an environment (default wizard settings)
2. add 1 controller and 1 compute node
3. check nodes' interfaces: there should be Public network on controller node interfaces and there should be NO Public network on compute's interfaces
4. select the controller on Nodes tab and click Edit Roles button
5. change the selected node role from controller to compute
6. check interfaces of this new compute
Expected result: should be NO Public network on the compute's interfaces
Actual result: Public network is assigned to the compute's interface and presented on the interfaces configuration screen
tags: |
added: module-networks removed: team-network |
Changed in fuel: | |
importance: | Undecided → Medium |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → l23network (l23network) |
Changed in fuel: | |
milestone: | 10.0 → 10.1 |
To post a comment you must log in.
Networks mapping is applied to node just once - when node is added into environment. Then user can change it but there is no way to change the set of networks for particular node now (only via remove-readd the node into env). Recalculation of networks set can be added in certain cases (e.g. when roles set is changed for node) but for certain cases user should check the results of such remapping manually (e.g.: Compute node becomes controller and Public network is to be added there. There is no warranty that it will be mapped to right interface.).