Description of problem:
Ironic has stale VIF ports during a race condition to lock the same node for overcloud nodes and VIF ports are not deleted upon instance deletion and all the subsequent instance spawning fails because of the stale VIF attached to the node.
Version-Release number of selected component (if applicable):
Red Hat OpenStack Platform 13
Steps to Reproduce:
1. Deploy a overcloud from director with just two nodes (one controller + one compute), one node have incorrect capabilities
2. deployment fails because of 2 instances trying to lock same node.
Deployment fails and leaves a stale VIF attached to the baremetal node.
Even if deployment fails, it shouldn't leave a stale VIF port.
Seems similar to https://bugzilla.redhat.com/show_bug.cgi?id=1535766.
Sai - can we see the version of openstack-ironic being used, to confirm they have that fix?
Is the issue that the deployment was done before the deletion was complete, so cleaning of the node was still in process?
Moving this to compute to take a look based on Comment 7.
I am closing this bug as it has not been addressed for a very long time. Please feel free to reopen if it is still relevant.