Fuel 6.0 lose network-interface assignment

[Gleb]

We use Fuel 6.0 with postdeployment plugin that creates linux bonds.
Usually it works fine and after the deployment some nodes send their updated network interface configuration and Fuel starts represent bond interface instead of single interfaces in Fuel UI.
But some nodes still represented in Fuel without bond (with 2 single interfaces in Fuel UI).
Probably it depends on what MAC address is used for bonding. It doesn't create any troubles.

The trouble is at times some node loses the network-interface assignment after the deployment. It looks in Fuel UI
as there is no Public, Management, Storage and Private networks assigned on the node.
If it happens I can't deploy new node to the cloud because of error 'There is no public network assigned'.

The only way to fix this is manually insert some records to nailgun.net_nic_assignments.

I can't give you steps for reproducing this bug, but I'd like to get you know about it at least.

[Alexander Gordeev (a-gordeev)]

I'm pretty sure that this issue is valid for 6.0, but it's not critical, so, it probably will stuck in "won't fix" state.

However, it could be resolved for 6.1/7.0, and that needs to be checked.

[Aleksey Kasatkin (alekseyk-ru)]

This https://bugs.launchpad.net/fuel/5.1.x/+bug/1425901 seems to be related. Problem was happening when the bond is configured and MACs were reported as equal for all interfaces included in bond. Nailgun loose interfaces in that case. Another problem https://bugs.launchpad.net/fuel/+bug/1425907 : if some interface is not present in Nailgun agent's data for some time and that interface has some networks mapped to it, those networks became unmapped to particular node and user cannot remap them again. Only node removal and readding the node to environment helps in that case.

[Denis Meltsaykin (dmeltsaykin)]

Setting this as Won't fix, as we have no delivery channel for Fuel fixes in 6.0