Comment 9 for bug 1432656

There are machines, equipped with several network adapters.
Such machines may be configured to boot the following way.
1. List of network adapters. Not the single but list to try
2. HDD.
So, it is possible one configured node to boot from the list of NICs.

At first boot machine PXE boots from the first NIC in the list and get registered on master node.
At the deployment Cobbler orders to boot this machine to OS distro - by PXE one more time.
Then provisions new system and deploys OpenStack.
Then - reboots the machine. Not sure how it handles boot from the second NIC this time, probably system is locked during deployment.
Then, after node is deployed, Cobbler or Nailgun locks this system another way.

So, next time the node is restarted, it asks PXE boot with first NIC - gets NO from master node. Then, it asks PXE boot with second NIC and somehow master node does not recognize this node as already deployed and PXE boots it with another NIC.

We need to check this scenario.