Hi Bhuvan,
I think this is just a Neutron Error.
It seems that when the failure occurred, the network where the VM was running
was marked as 'external'.
This is consistent with the following scenario:
- boot VM on 'regular' network
- with admin right, set network as external
- destroy VM
I think to this aim that we should prevent updates of network's external
attributes when there are active VM ports, at least for the nicira
plugin. Please let me know if that will work for you.
Salvatore
** Changed in: neutron
Status: New => Incomplete
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1263735
Title:
NVP plugin does not support VIF ports error
Status in OpenStack Neutron (virtual network service):
Incomplete
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Unable to delete a server using nova api. No errors logged at nova
side.
On neutron side, it complain that it doesn't support regular VIF ports
on external networks.
2013-12-23 17:19:11,516 (NeutronPlugin): ERROR NeutronPlugin _nvp_delete_port
NVP plugin does not support regular V
IF ports on external networks. Port 6d382dfd-f826-45d3-8818-48c34f8a8908 will
be down.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1263735/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp