nova scrub doesn't remove a vm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Low
|
Ryan Hallisey | ||
python-novaclient |
Invalid
|
Medium
|
Unassigned |
Bug Description
Checking the code, nova scrub should disassociate the network associated with the given tenant, but it fails to do so. There is no error in log.
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
nova-manage --nodebug network list | head
keystone tenant-create --name foo
keystone user-role-add --user admin --role Member --tenant foo
OS_TENANT_NAME=foo nova boot --image cirros-
nova list --all-tenants
nova-manage network list | head
nova scrub foo
nova list --all-tenants
nova-manage --nodebug network list | head
######## The network is still associated in this point.
keystone tenant-delete foo
nova-manage --nodebug network list | head
nova list --all-tenants
######## Here as well
tags: | added: network |
Changed in nova: | |
assignee: | nobody → Ryan Hallisey (rthall14) |
Changed in nova: | |
assignee: | Ryan Hallisey (rthall14) → nobody |
assignee: | nobody → Ryan Hallisey (rthall14) |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in python-novaclient: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Confirmed → Invalid |
I have found that not-disassociating the network is caused by leftover VMs in that network. I think nova scrub should remove the VMs first, then it should disassociate the network.