routing works even when neutron router attribute admin_state_up is set to False

Bug #1352822 reported by Kumar Harsh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R1.1
Won't Fix
Medium
Sachin Bansal
R2.0
Won't Fix
Medium
Sachin Bansal
R2.1
Won't Fix
Medium
Sachin Bansal
R3.0
New
Medium
Sachin Bansal
R3.1
New
Medium
Sachin Bansal
Trunk
Confirmed
Medium
Sachin Bansal

Bug Description

root@nodec6:~# neutron net-create net1
Created a new network:
+-----------------+--------------------------------------+
| Field | Value |
+-----------------+--------------------------------------+
| admin_state_up | True |
| id | 57fa18b6-2b60-4822-9627-047e29ad16e8 |
| name | net1 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | |
| tenant_id | 87e2db2f6e9b499180a03bed262ba419 |
+-----------------+--------------------------------------+
root@nodec6:~#
root@nodec6:~#
root@nodec6:~#
root@nodec6:~# neutron subnet-create net1 10.0.0.0/24
Created a new subnet:
+------------------+--------------------------------------------+
| Field | Value |
+------------------+--------------------------------------------+
| allocation_pools | {"start": "10.0.0.2", "end": "10.0.0.254"} |
| cidr | 10.0.0.0/24 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 10.0.0.1 |
| host_routes | |
| id | ff0262e3-cfd6-4ddc-b021-7c56358b1752 |
| ip_version | 4 |
| name | |
| network_id | 57fa18b6-2b60-4822-9627-047e29ad16e8 |
| tenant_id | 87e2db2f6e9b499180a03bed262ba419 |
+------------------+--------------------------------------------+
root@nodec6:~#
root@nodec6:~#
root@nodec6:~# neutron net-create net2
Created a new network:
+-----------------+--------------------------------------+
| Field | Value |
+-----------------+--------------------------------------+
| admin_state_up | True |
| id | d27ad315-6d77-447a-a0fe-6057141c0a8c |
| name | net2 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | |
| tenant_id | 87e2db2f6e9b499180a03bed262ba419 |
+-----------------+--------------------------------------+
root@nodec6:~#
root@nodec6:~#
root@nodec6:~# neutron subnet-create net2 10.0.1.0/24
Created a new subnet:
+------------------+--------------------------------------------+
| Field | Value |
+------------------+--------------------------------------------+
| allocation_pools | {"start": "10.0.1.2", "end": "10.0.1.254"} |
| cidr | 10.0.1.0/24 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 10.0.1.1 |
| host_routes | |
| id | 6e483b2a-e9d5-441e-9498-d83388254709 |
| ip_version | 4 |
| name | |
| network_id | d27ad315-6d77-447a-a0fe-6057141c0a8c |
| tenant_id | 87e2db2f6e9b499180a03bed262ba419 |
+------------------+--------------------------------------------+
root@nodec6:~#
root@nodec6:~# neutron router-create router1
Created a new router:
+-----------------------+--------------------------------------+
| Field | Value |
+-----------------------+--------------------------------------+
| admin_state_up | True |
| external_gateway_info | |
| id | 95efa3a3-1307-493c-a7ee-34741755a149 |
| name | router1 |
| status | ACTIVE |
| tenant_id | 87e2db2f6e9b499180a03bed262ba419 |
+-----------------------+--------------------------------------+
root@nodec6:~#
root@nodec6:~#
root@nodec6:~# neutron router-interface-add router1 ff0262e3-cfd6-4ddc-b021-7c56358b1752
Added interface e576be97-2bcb-4b68-a612-e8843e0c6bec to router router1.
root@nodec6:~# neutron router-interface-add router1 6e483b2a-e9d5-441e-9498-d83388254709
Added interface 97f6a97a-b6b8-48e7-85b5-bdcaff2af93a to router router1.

vm-list :
root@nodec6:~# nova list
+--------------------------------------+----------+--------+------------+-------------+---------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+----------+--------+------------+-------------+---------------+
| d2e15ee6-2cb0-4609-bc21-ba89c61413e7 | vm1_net1 | ACTIVE | None | Running | net1=10.0.0.2 |
| fb2770a3-546a-4e33-a3c1-5ba56f9ee27a | vm2_net2 | ACTIVE | None | Running | net2=10.0.1.2 |
+--------------------------------------+----------+--------+------------+-------------+---------------+

Ping to vm1_net1 from vm2_net2 :
ubuntu@vm2-net2:~$ ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_req=1 ttl=64 time=1.67 ms
64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.532 ms
64 bytes from 10.0.0.2: icmp_req=3 ttl=64 time=0.664 ms
^C
--- 10.0.0.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 0.532/0.958/1.678/0.511 ms

Set router1 --admin_state_up to False :

root@nodec6:~# neutron router-update router1 --admin_state_up False
Updated router: router1

root@nodec6:~# neutron router-show router1
+-----------------------+--------------------------------------+
| Field | Value |
+-----------------------+--------------------------------------+
| admin_state_up | False |
| external_gateway_info | |
| id | 95efa3a3-1307-493c-a7ee-34741755a149 |
| name | router1 |
| status | ACTIVE |
| tenant_id | 87e2db2f6e9b499180a03bed262ba419 |
+-----------------------+--------------------------------------+

Try ping again Ping to vm1_net1 from vm2_net2 :

ubuntu@vm2-net2:~$ ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_req=1 ttl=64 time=1.51 ms
64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.598 ms
64 bytes from 10.0.0.2: icmp_req=3 ttl=64 time=0.607 ms
64 bytes from 10.0.0.2: icmp_req=4 ttl=64 time=0.618 ms
64 bytes from 10.0.0.2: icmp_req=5 ttl=64 time=0.619 ms
^C
--- 10.0.0.2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.598/0.792/1.519/0.363 ms

Ping still Passes not expected .

Changed in juniperopenstack:
milestone: none → r1.10-fcs
importance: Undecided → High
assignee: nobody → Sachin Bansal (sbansal)
information type: Proprietary → Public
Revision history for this message
Ashish Ranjan (aranjan-n) wrote :

We will consider this post 1.10.

For now user will have to delete router or remove the subnet to prevent routing.

tags: added: releasenote
Changed in juniperopenstack:
status: New → Confirmed
importance: High → Medium
Revision history for this message
Nagabhushana R (bhushana) wrote :

won't fix for 1.1 FCS but to be release noted.

Changed in juniperopenstack:
milestone: r1.10-fcs → none
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.