Comment 2 for bug 1156844

It appears that this problem may be able to be circumvented by specifying the ordering by adding '--nic net-id=<uuid1> --nic net-id=<uuid2>' . I think we were seeing the same problem on our systems and then it went away. I think we started specifying the ordering with --nic which would cause this fix to resolve the issue: https://review.openstack.org/#/c/15087/