Unassigned networks check blocks interfaces configuration on UI
Bug #1641082 reported by
Julia Aranovich
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Fuel Sustaining | ||
8.0.x |
Invalid
|
High
|
Fuel Sustaining | ||
Mitaka |
Invalid
|
High
|
Fuel Sustaining |
Bug Description
Steps to reproduce:
- install Fuel 8
- install Fuel 8 MU2
- create environment (neutron)
- create nodes, map networks
- !!do not deploy changes!!
- create custom networks using fuel network-group --create
- try to configure interfaces on nodes in "Pending Addition" state (any change in networks, settings)
Expected results: the changes can be saved successfully.
Actual result: the changes can not be saved. Nailgun returns error (see the attached screenshot).
Proposed solution: https:/
To post a comment you must log in.
I tried to reproduce this with 9.x and failed to do so. When I create a new network group and start configuring the interfaces - there is an 'unassigned networks' tab. I can easily pick the unassigned network group and assign it onto some interface. After that, I can easily save the configuration. So this bug seems to be either already fixed or invalid