Description of problem: if creation of instance failed and instance go error state, than when trying to delete the instance the sr-iov port will not be deleted Version-Release number of selected component (if applicable): How reproducible: the flow is like that: * create SR-IOv port via neutron port-create * attach the port to instance, if the instance managed to boot OK the port will be assignd and when the instance will be deleted the port also will be deleted, BUT if the instance going to ERROR state than the port will not be deleted when the instance wil be deleted Steps to Reproduce: 1. 2. 3. Actual results: the sriov port not deleted Expected results: if sriov port are attached to instance he should be deleted with the instance Additional info:
Does it happen with non SR-IOV port? I think this is not related to SR-IOV. If you create a normal port, launch an instance with this port attached and the instance moves to error state - deleting the instance doesn't remove the port.
Itzik is correct. This is by design and effectively not a bug - the port should simply be updated to remove the host and instance info. I recommend closing as NOTABUG
Closing per comment #4. This is the expected behavior when using this flow. Nir