allow nova delete to continue if quantum port delete fails

[dan wendlandt]

while doing some testing, I noticed that when terminating a nova VM, if the quantum port delete failed because of a bug in quantum, nova would not delete the VM. It seemed bad to prevent the reclamation of compute resources because of an issue releasing network resources. Compounding the issue is that there's no tenant visible feedback for why the delete fails.

So instead I propose changing the v2 quantum integration code to work like (I believe) the v1 quantum integration worked, which is that if a port delete fails, we log it, but keep on deleting. This may leave orphaned ports in Quantum, but that seems ok, as it is quantum's fault if it could not properly delete a port.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/11842

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/11842
Committed: http://github.com/openstack/nova/commit/7c87f262c9cb19ed452e96c3ce8c2b524f74cb90
Submitter: Jenkins
Branch: master

commit 7c87f262c9cb19ed452e96c3ce8c2b524f74cb90
Author: Dan Wendlandt <email address hidden>
Date: Wed Aug 22 11:46:07 2012 -0700

    continue deleting instance even if quantum port delete fails

    bug 1040385

    Change-Id: Idb289437e40c7a1522b3a3f34f6c14ffe420c077