DVR: router namespace can't be deleted if bulk delete VMs

Bug #1496201 reported by shihanzhang
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Medium
Unassigned

Bug Description

With DVR router, if we bulk delete VMs on from a compute node, the router namespace will remain(not always happen, but for most part)
reproduce steps:
1. create a DVR router, add a subnet to this router
2. create two VMs on one compute node, note that these are only these two VMs on this compute
3. bulk delete these two VMs through Nova API

the router namespace will remain for the most part.

tags: added: l3-dvr-backlog
Changed in neutron:
importance: Undecided → Medium
Edgar Magana (emagana)
Changed in neutron:
assignee: nobody → Kasey Alusi (kasey-alusi)
Revision history for this message
Swaminathan Vasudevan (swaminathan-vasudevan) wrote :

Need to triage this bug.

Revision history for this message
Swaminathan Vasudevan (swaminathan-vasudevan) wrote :
Download full text (11.2 KiB)

I tried reproducing this issue in the Master branch . Here are the steps that I followed.

--+--------+
stack@ubuntu-ctlr:~/devstack$ nova boot --flavor 42 --image cirros-0.3.4-x86_64-uec --nic net-id=683e91b2-64aa-46a4-8810-a5fe46fa1522 --availability-zone=nova:ubuntu-new-compute mycirros1
+--------------------------------------+----------------------------------------------------------------+
| Property | Value |
+--------------------------------------+----------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-SRV-ATTR:host | - |
| OS-EXT-SRV-ATTR:hostname | mycirros1 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | - |
| OS-EXT-SRV-ATTR:instance_name | instance-00000001 |
| OS-EXT-SRV-ATTR:kernel_id | e51fa786-4586-4d64-8f53-0dc8b53493c9 |
| OS-EXT-SRV-ATTR:launch_index | 0 |
| OS-EXT-SRV-ATTR:ramdisk_id | 44a667bf-894f-417b-8a0c-b8a6dc8b7a45 |
| OS-EXT-SRV-ATTR:reservation_id | r-auugjv8r |
| OS-EXT-SRV-ATTR:root_device_name | - |
| OS-EXT-SRV-ATTR:user_data | - |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| OS-SRV-USG:launched_at | - |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | SwbAufd5APR4 |
| config_drive | |
| created | 2015-11-11T21:23:04Z |
| flavor | m1.nano (42) |
| hostId | |
| id | c2e1e...

Revision history for this message
Swaminathan Vasudevan (swaminathan-vasudevan) wrote :

I am not seeing it happen in the Master branch.

Changed in neutron:
status: New → Incomplete
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 240 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
assignee: Kasey Alusi (kasey-alusi) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.