Unassigned networks check blocks interfaces configuration on UI

[Julia Aranovich]

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://bugs.launchpad.net/fuel/+bug/1606177/comments/5

[Vladimir Kuklin (vkuklin)]

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

[Alexey Stupnikov (astupnikov)]

I was unable to reproduce this issue on MOS8 with latest MU installed. Here is what was done:

- installed Fuel 8

- updated to latest MU

- added network-group test:
[root@localhost ~]# fuel network-group --create --nodegroup 1 --name test --cidr 192.168.168.0/24

- changed VLAN ID range in UI, saved settings.

Changing status to invalid for 8.0-updates milestone.

[Alexey Stupnikov (astupnikov)]

Steps from previous comment didn't worked on MOS10 (ISO #803), still unable to reproduce the bug. Changing status to Invalid for 10.1 milestone.