Lock the ability to change interface settings in Fuel UI if a node is in Error state
Bug #1604470 reported by
Serhii Ovsianikov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
High
|
Fuel UI Team | ||
| 6.0.x |
In Progress
|
High
|
Julia Aranovich | ||
| 6.1.x |
Won't Fix
|
High
|
Fuel UI Team | ||
| 7.0.x |
Won't Fix
|
High
|
Fuel UI Team | ||
| 8.0.x |
Won't Fix
|
High
|
Fuel UI Team | ||
| Mitaka |
Invalid
|
High
|
Fuel UI Team | ||
Bug Description
Fuel 6.0.
When we tried to add a Compute node to the cluster, we forgot to assign a network interface and the deploy failed. After realizing that we had made a mistake, we assigned network via Fuel UI to the correct interface and continued to deploy.
As a result, a loop in the network was created because Puppet created bridges on different interfaces.
Please create a patch for Fuel 6.0 which will lock the ability to change interface settings if a node is in Error state.
| Changed in fuel: | |
| milestone: | none → 6.0-updates |
| assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
| status: | New → Confirmed |
| tags: | added: area-python |
Revision history for this message
| Dmitry Pyzhov (dpyzhov) wrote | #1 |
| Changed in fuel: | |
| milestone: | 6.0-updates → 10.0 |
| status: | Confirmed → New |
| assignee: | Fuel Sustaining (fuel-sustaining-team) → Fuel UI Team (fuel-ui) |
| status: | New → Invalid |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to fuel-web (stable/6.0) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on fuel-web (stable/6.0) | #3 |
Revision history for this message
| Vitaly Sedelnik (vsedelnik) wrote | #4 |
To post a comment you must log in.
For Newton and Mitaka original bug is fixed in bug #1593190. AFAIK the bug already fixed in 6.1 but it needs to be checked anyway. So we need patches for all the rest branches.