Comment 3 for bug 1827746

I agree with gibi, it sounds like we could do something similar to "local delete" (when nova-compute is down and delete is requested, we deallocate ports, volumes, and placement resources) in nova-api for the detach-interface API. There might be some resistance to the idea as "local delete" has been a popular source of bugs in the past. But as always, it's a tradeoff, and if detach-interface while nova-compute is down is a greater pain point, it might be worth adding a "local detach" ability.

I think the only concern here will be the case where nova-compute is down and comes back up, but somehow the RPC message is lost and it never detaches the vif but the port is free to be bound to a new server. Would that be a problem or would it work OK because the port was unbound (and not cause two servers to potentially respond to the same IP, if the port gets bound to a new server)?