Description of problem: Checking the nova code, nova scrub should disassociate the network associated with the given tenant, but it fails to do so. There is no error in log. Version-Release number of selected component (if applicable): openstack-nova-api.noarch 2013.2.1-1.el6ost @puddle openstack-nova-cert.noarch 2013.2.1-1.el6ost @puddle openstack-nova-common.noarch 2013.2.1-1.el6ost @puddle openstack-nova-compute.noarch 2013.2.1-1.el6ost @puddle openstack-nova-conductor.noarch 2013.2.1-1.el6ost @puddle openstack-nova-console.noarch 2013.2.1-1.el6ost @puddle openstack-nova-network.noarch 2013.2.1-1.el6ost @puddle openstack-nova-novncproxy.noarch 2013.2.1-1.el6ost @puddle openstack-nova-objectstore.noarch 2013.2.1-1.el6ost @puddle openstack-nova-scheduler.noarch 2013.2.1-1.el6ost @puddle How reproducible: 100% Steps to Reproduce: Actual results: 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-0.3.1-x86_64-disk.vmdk --flavor m1.tiny foo_vm 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
Hi Jaroslav, Unclear if it matters in this case but was this when you were testing with the vCenter driver, or KVM? Thanks, Steve
(In reply to Stephen Gordon from comment #2) > Hi Jaroslav, > > Unclear if it matters in this case but was this when you were testing with > the vCenter driver, or KVM? > > Thanks, > > Steve I think this was with the vCenter (obviously there was vmdk image used), but i also think that it doesn't matter as IIRC the code doing the nova scrub is buggy general. I can retest it with libvirt with no, problem.
Can you reproduce this in libvirt? Also, are you using nova network?
I have reproduced it with libvirt and made 1083620. Resolution of this bug depends on what we decide to do with 1083620.
I believe all further discussion should be done on the LP bug.
"nova scrub" is a very limited command. All it tries to do is delete networks and security groups. It doesn't try to delete instances (by design). I updated the command help text to try to make this more clear: https://review.openstack.org/#/c/126975/