Comment 0 for bug 1543535

This issue reproduced not is 100% of cases, and it is probably regression issue.
It is Critical because sometimes fuel can randomly change the mapping of ETH interfaces with logical networks and this will lead to fail of deployments / networks verification after the deployment.

This issue was found by MOS QA automated test suite (Neutron destructive suite)
Template which was used for deployment: https://github.com/Mirantis/mos-ci-deployment-scripts/blob/master/3_controllers_2compute_neutron_env_template.yaml

Steps To Reproduce:
1. Run fuel master node and 3 slave nodes
2. Configure environment with 3 controllers, 3 computes, Neutron VxVLAN, L2pop and L3 HA features enabled
3. Check networks configuration and make sure that everything works fine
4. Deploy the environment
5. Start networks check one more time after the deployment

Expected Result:
Deployment will pass, network connectivity checks will pass as well

Observed Result:
Deployment passed (in my case, it depends on the interfaces which will be affected be the issue during the deployment, in fact, it can fail the deployment)
Network verification fails with the error:
AssertionError: Task 'check_networks' has incorrect status. error != ready, 'Some untagged networks are assigned to the same physical interface. You should assign them to different physical interfaces. Affected:
"admin (PXE)", "storage" networks at node "slave-03_controller_cinder"'

Diagnostic snapshot and screenshots are attached.