yahoo-eng-team team mailing list archive

[Jaroslav Henner <jhenner@xxxxxxxxxx>]

Public bug reported:

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-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

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

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1280389

Title:
  nova scrub doesn't remove a vm

Status in OpenStack Compute (Nova):
  New

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-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

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1280389/+subscriptions