This bug was reported in liberty, where an instance that failed with NoValidHost did not have its ports cleaned up.
This is the exception handling block for liberty where we'd handle NoValidHost:
https://github.com/openstack/nova/blob/liberty-eol/nova/conductor/manager.py#L740-L746
and we weren't cleaning up the network in that case.
In newer code, I find that we are cleaning up networks upon NoValidHost or MaxRetriesExceeded since this change:
https://review.openstack.org/#/c/243477/
so, I think this bug has been fixed since then.
This bug was reported in liberty, where an instance that failed with NoValidHost did not have its ports cleaned up.
This is the exception handling block for liberty where we'd handle NoValidHost:
https:/ /github. com/openstack/ nova/blob/ liberty- eol/nova/ conductor/ manager. py#L740- L746
and we weren't cleaning up the network in that case.
In newer code, I find that we are cleaning up networks upon NoValidHost or MaxRetriesExceeded since this change:
https:/ /review. openstack. org/#/c/ 243477/
so, I think this bug has been fixed since then.