Comment 18 for bug 1523638

The root cause of this is that the Linux bridge agent was exploding during the setup loop on an unrelated port. This would cause the port we are working with to go back into the BUILD state on the server after already being ACTIVE and telling nova to the VM. So then the list ports call from tempest that filtered on ACTIVE would not see the port.