*** This bug is a duplicate of bug 1648840 ***
https://bugs.launchpad.net/bugs/1648840
Marking this as a duplicate of bug 1648840.
** This bug has been marked a duplicate of bug 1648840
libvirt driver leaves interface residue after failed start
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1572794
Title:
nova sometimes doesn't clean up neutron ports when VM spawning fails
Status in OpenStack Compute (nova):
New
Status in nova-cloud-controller package in Juju Charms Collection:
Invalid
Bug description:
Hi,
It appears that sometimes, nova doesn't clean up ports when spawning
the instance fails. I'm using SR-IOV so I'm creating ports manually.
Example :
Create port with :
$ neutron port-create <net_id> --name direct --binding:vnic_type direct
Boot instance using said port :
$ nova boot --image <image> --flavor <flavor> --key-name admin_key --nic
port-id=<port-id from above> vm_direct
If VM creation fails and the failed VM gets deleted, the port is still bound :
$ neutron port-show direct2
+-----------------------+-----------------------------------------------------------------------------------------------------------+
| Field | Value
|
+-----------------------+-----------------------------------------------------------------------------------------------------------+
| admin_state_up | True
|
| allowed_address_pairs |
|
| binding:host_id | xxxxxx
|
| binding:profile | {"pci_slot": "0000:04:10.2", "physical_network":
"physnet1", "pci_vendor_info": "8086:10ca"} |
| binding:vif_details | {"port_filter": false, "vlan": "1234"}
|
| binding:vif_type | hw_veb
|
| binding:vnic_type | direct
|
| device_id | 2aecc61b-e3c9-4b1f-9e47-574733705a91
|
| device_owner | compute:None
|
| dns_assignment | {"hostname": "host-10-190-5-35", "ip_address":
"10.190.5.35", "fqdn": "host-10-190-5-35.openstacklocal."} |
| dns_name |
|
| extra_dhcp_opts |
|
| fixed_ips | {"subnet_id":
"72cfdfed-e614-4add-b880-f4c9d3bb89cc", "ip_address": "10.190.5.35"}
|
| id | f34b55c1-f10e-44c9-8326-5a42996c691a
|
| mac_address | fa:16:3e:5d:da:16
|
| name | direct
|
| network_id | 200d501c-13df-4625-9f46-d7e28ee18dc2
|
| security_groups | feb7b440-450b-4c7b-aa3f-92f498cd2841
|
| status | BUILD
|
| tenant_id | 09fae15a5f6f4acf838a97d202786d25
|
+-----------------------+-----------------------------------------------------------------------------------------------------------+
$ nova show 2aecc61b-e3c9-4b1f-9e47-574733705a91
ERROR: No server with a name or ID of '2aecc61b-e3c9-4b1f-9e47-574733705a91'
exists.
This is similar to LP#1423845, but I do have the fix from that bug
already in my code.
Package versions are : 2:12.0.2-0ubuntu1~cloud0, running on trusty
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1572794/+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
