yahoo-eng-team team mailing list archive

Thread
Date
[Bug 1554942] [NEW] Floating ip Is not reachable when data nic is made up again ( in testing L3 HA VRRP feature)

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Abhishek G M <abhishek.gm@xxxxxxx>
Date: Wed, 09 Mar 2016 07:23:54 -0000
Reply-to: Bug 1554942 <1554942@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Public bug reported:

steps to reproduce:
1) create a router
2) set router gateway with the public network
3) router-interface-add with the submnet
4) boot a vm
5) create a floating ip
6) associate a floating ip with the booted vm port id
7) continuously ping floating ip
8) Make active controller data nic down
9) Make Previous active controller data nic up
Floating ip is not reachable after doing above steps

Before stating testing scenario
stack@padawan-ccp-c1-m1-mgmt:~$ neutron l3-agent-list-hosting-router b4fd1fd4-1c21-4be3-8672-e085c3e195f9
+--------------------------------------+------------------------+----------------+-------+----------+
| id                                   | host                   | admin_state_up | alive | ha_state |
+--------------------------------------+------------------------+----------------+-------+----------+
| da302b3f-b8c6-4068-9abd-6486cd6d0654 | padawan-ccp-c1-m3-mgmt | True           | :-)   | standby  |
| fc1cd20b-81dd-4bbc-bfb8-5652c08dc0c3 | padawan-ccp-c1-m1-mgmt | True           | :-)   | active   |
+--------------------------------------+------------------------+----------------+-------+----------+
After making data niic down of the active controller
stack@padawan-ccp-c1-m1-mgmt:~$ neutron l3-agent-list-hosting-router b4fd1fd4-1c21-4be3-8672-e085c3e195f9
+--------------------------------------+------------------------+----------------+-------+----------+
| id                                   | host                   | admin_state_up | alive | ha_state |
+--------------------------------------+------------------------+----------------+-------+----------+
| da302b3f-b8c6-4068-9abd-6486cd6d0654 | padawan-ccp-c1-m3-mgmt | True           | :-)   | active   |
| fc1cd20b-81dd-4bbc-bfb8-5652c08dc0c3 | padawan-ccp-c1-m1-mgmt | True           | :-)   | active   |
+--------------------------------------+------------------------+----------------+-------+----------+
After making data nic up of the previous active controller
stack@padawan-ccp-c1-m1-mgmt:~$ neutron l3-agent-list-hosting-router b4fd1fd4-1c21-4be3-8672-e085c3e195f9
+--------------------------------------+------------------------+----------------+-------+----------+
| id                                   | host                   | admin_state_up | alive | ha_state |
+--------------------------------------+------------------------+----------------+-------+----------+
| da302b3f-b8c6-4068-9abd-6486cd6d0654 | padawan-ccp-c1-m3-mgmt | True           | :-)   | standby  |
| fc1cd20b-81dd-4bbc-bfb8-5652c08dc0c3 | padawan-ccp-c1-m1-mgmt | True           | :-)   | active   |
+--------------------------------------+------------------------+----------------+-------+----------+
Below is the ping output of the floating ip
64 bytes from 172.21.11.11: icmp_seq=1 ttl=62 time=1.79 ms
64 bytes from 172.21.11.11: icmp_seq=2 ttl=62 time=1.52 ms
64 bytes from 172.21.11.11: icmp_seq=3 ttl=62 time=0.859 ms
64 bytes from 172.21.11.11: icmp_seq=4 ttl=62 time=0.937 ms
64 bytes from 172.21.11.11: icmp_seq=5 ttl=62 time=0.645 ms
64 bytes from 172.21.11.11: icmp_seq=6 ttl=62 time=1.45 ms
64 bytes from 172.21.11.11: icmp_seq=7 ttl=62 time=0.804 ms
64 bytes from 172.21.11.11: icmp_seq=8 ttl=62 time=0.872 ms
64 bytes from 172.21.11.11: icmp_seq=9 ttl=62 time=0.780 ms
64 bytes from 172.21.11.11: icmp_seq=10 ttl=62 time=0.719 ms
64 bytes from 172.21.11.11: icmp_seq=11 ttl=62 time=1.19 ms
64 bytes from 172.21.11.11: icmp_seq=12 ttl=62 time=1.40 ms
64 bytes from 172.21.11.11: icmp_seq=13 ttl=62 time=0.633 ms
64 bytes from 172.21.11.11: icmp_seq=14 ttl=62 time=0.888 ms
64 bytes from 172.21.11.11: icmp_seq=15 ttl=62 time=1.76 ms
64 bytes from 172.21.11.11: icmp_seq=16 ttl=62 time=0.906 ms
64 bytes from 172.21.11.11: icmp_seq=17 ttl=62 time=0.727 ms
64 bytes from 172.21.11.11: icmp_seq=18 ttl=62 time=1.38 ms
64 bytes from 172.21.11.11: icmp_seq=19 ttl=62 time=0.719 ms
64 bytes from 172.21.11.11: icmp_seq=20 ttl=62 time=0.778 ms
64 bytes from 172.21.11.11: icmp_seq=21 ttl=62 time=1.58 ms
64 bytes from 172.21.11.11: icmp_seq=22 ttl=62 time=0.717 ms
64 bytes from 172.21.11.11: icmp_seq=23 ttl=62 time=0.782 ms
64 bytes from 172.21.11.11: icmp_seq=24 ttl=62 time=1.01 ms
64 bytes from 172.21.11.11: icmp_seq=25 ttl=62 time=0.709 ms
64 bytes from 172.21.11.11: icmp_seq=26 ttl=62 time=1.03 ms
64 bytes from 172.21.11.11: icmp_seq=27 ttl=62 time=0.826 ms
64 bytes from 172.21.11.11: icmp_seq=28 ttl=62 time=0.715 ms
64 bytes from 172.21.11.11: icmp_seq=29 ttl=62 time=0.974 ms
64 bytes from 172.21.11.11: icmp_seq=30 ttl=62 time=0.826 ms
64 bytes from 172.21.11.11: icmp_seq=39 ttl=62 time=3.61 ms
64 bytes from 172.21.11.11: icmp_seq=40 ttl=62 time=0.841 ms
64 bytes from 172.21.11.11: icmp_seq=41 ttl=62 time=0.824 ms


And gateway also not pinging.
Floating ip works from router namespace but not from outside
stack@padawan-ccp-c1-m1-mgmt:~$ sudo ip netns exec qrouter-b4fd1fd4-1c21-4be3-8672-e085c3e195f9 bash
root@padawan-ccp-c1-m1-mgmt:/home/stack# ping 172.21.11.11
PING 172.21.11.11 (172.21.11.11) 56(84) bytes of data.
64 bytes from 172.21.11.11: icmp_seq=1 ttl=64 time=2.01 ms
64 bytes from 172.21.11.11: icmp_seq=2 ttl=64 time=1.17 ms

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1554942

Title:
  Floating ip Is not reachable when data nic is made up again ( in
  testing L3 HA VRRP feature)

Status in neutron:
  New

Bug description:
  steps to reproduce:
  1) create a router
  2) set router gateway with the public network
  3) router-interface-add with the submnet
  4) boot a vm
  5) create a floating ip
  6) associate a floating ip with the booted vm port id
  7) continuously ping floating ip
  8) Make active controller data nic down
  9) Make Previous active controller data nic up
  Floating ip is not reachable after doing above steps

  Before stating testing scenario
  stack@padawan-ccp-c1-m1-mgmt:~$ neutron l3-agent-list-hosting-router b4fd1fd4-1c21-4be3-8672-e085c3e195f9
  +--------------------------------------+------------------------+----------------+-------+----------+
  | id                                   | host                   | admin_state_up | alive | ha_state |
  +--------------------------------------+------------------------+----------------+-------+----------+
  | da302b3f-b8c6-4068-9abd-6486cd6d0654 | padawan-ccp-c1-m3-mgmt | True           | :-)   | standby  |
  | fc1cd20b-81dd-4bbc-bfb8-5652c08dc0c3 | padawan-ccp-c1-m1-mgmt | True           | :-)   | active   |
  +--------------------------------------+------------------------+----------------+-------+----------+
  After making data niic down of the active controller
  stack@padawan-ccp-c1-m1-mgmt:~$ neutron l3-agent-list-hosting-router b4fd1fd4-1c21-4be3-8672-e085c3e195f9
  +--------------------------------------+------------------------+----------------+-------+----------+
  | id                                   | host                   | admin_state_up | alive | ha_state |
  +--------------------------------------+------------------------+----------------+-------+----------+
  | da302b3f-b8c6-4068-9abd-6486cd6d0654 | padawan-ccp-c1-m3-mgmt | True           | :-)   | active   |
  | fc1cd20b-81dd-4bbc-bfb8-5652c08dc0c3 | padawan-ccp-c1-m1-mgmt | True           | :-)   | active   |
  +--------------------------------------+------------------------+----------------+-------+----------+
  After making data nic up of the previous active controller
  stack@padawan-ccp-c1-m1-mgmt:~$ neutron l3-agent-list-hosting-router b4fd1fd4-1c21-4be3-8672-e085c3e195f9
  +--------------------------------------+------------------------+----------------+-------+----------+
  | id                                   | host                   | admin_state_up | alive | ha_state |
  +--------------------------------------+------------------------+----------------+-------+----------+
  | da302b3f-b8c6-4068-9abd-6486cd6d0654 | padawan-ccp-c1-m3-mgmt | True           | :-)   | standby  |
  | fc1cd20b-81dd-4bbc-bfb8-5652c08dc0c3 | padawan-ccp-c1-m1-mgmt | True           | :-)   | active   |
  +--------------------------------------+------------------------+----------------+-------+----------+
  Below is the ping output of the floating ip
  64 bytes from 172.21.11.11: icmp_seq=1 ttl=62 time=1.79 ms
  64 bytes from 172.21.11.11: icmp_seq=2 ttl=62 time=1.52 ms
  64 bytes from 172.21.11.11: icmp_seq=3 ttl=62 time=0.859 ms
  64 bytes from 172.21.11.11: icmp_seq=4 ttl=62 time=0.937 ms
  64 bytes from 172.21.11.11: icmp_seq=5 ttl=62 time=0.645 ms
  64 bytes from 172.21.11.11: icmp_seq=6 ttl=62 time=1.45 ms
  64 bytes from 172.21.11.11: icmp_seq=7 ttl=62 time=0.804 ms
  64 bytes from 172.21.11.11: icmp_seq=8 ttl=62 time=0.872 ms
  64 bytes from 172.21.11.11: icmp_seq=9 ttl=62 time=0.780 ms
  64 bytes from 172.21.11.11: icmp_seq=10 ttl=62 time=0.719 ms
  64 bytes from 172.21.11.11: icmp_seq=11 ttl=62 time=1.19 ms
  64 bytes from 172.21.11.11: icmp_seq=12 ttl=62 time=1.40 ms
  64 bytes from 172.21.11.11: icmp_seq=13 ttl=62 time=0.633 ms
  64 bytes from 172.21.11.11: icmp_seq=14 ttl=62 time=0.888 ms
  64 bytes from 172.21.11.11: icmp_seq=15 ttl=62 time=1.76 ms
  64 bytes from 172.21.11.11: icmp_seq=16 ttl=62 time=0.906 ms
  64 bytes from 172.21.11.11: icmp_seq=17 ttl=62 time=0.727 ms
  64 bytes from 172.21.11.11: icmp_seq=18 ttl=62 time=1.38 ms
  64 bytes from 172.21.11.11: icmp_seq=19 ttl=62 time=0.719 ms
  64 bytes from 172.21.11.11: icmp_seq=20 ttl=62 time=0.778 ms
  64 bytes from 172.21.11.11: icmp_seq=21 ttl=62 time=1.58 ms
  64 bytes from 172.21.11.11: icmp_seq=22 ttl=62 time=0.717 ms
  64 bytes from 172.21.11.11: icmp_seq=23 ttl=62 time=0.782 ms
  64 bytes from 172.21.11.11: icmp_seq=24 ttl=62 time=1.01 ms
  64 bytes from 172.21.11.11: icmp_seq=25 ttl=62 time=0.709 ms
  64 bytes from 172.21.11.11: icmp_seq=26 ttl=62 time=1.03 ms
  64 bytes from 172.21.11.11: icmp_seq=27 ttl=62 time=0.826 ms
  64 bytes from 172.21.11.11: icmp_seq=28 ttl=62 time=0.715 ms
  64 bytes from 172.21.11.11: icmp_seq=29 ttl=62 time=0.974 ms
  64 bytes from 172.21.11.11: icmp_seq=30 ttl=62 time=0.826 ms
  64 bytes from 172.21.11.11: icmp_seq=39 ttl=62 time=3.61 ms
  64 bytes from 172.21.11.11: icmp_seq=40 ttl=62 time=0.841 ms
  64 bytes from 172.21.11.11: icmp_seq=41 ttl=62 time=0.824 ms


  And gateway also not pinging.
  Floating ip works from router namespace but not from outside
  stack@padawan-ccp-c1-m1-mgmt:~$ sudo ip netns exec qrouter-b4fd1fd4-1c21-4be3-8672-e085c3e195f9 bash
  root@padawan-ccp-c1-m1-mgmt:/home/stack# ping 172.21.11.11
  PING 172.21.11.11 (172.21.11.11) 56(84) bytes of data.
  64 bytes from 172.21.11.11: icmp_seq=1 ttl=64 time=2.01 ms
  64 bytes from 172.21.11.11: icmp_seq=2 ttl=64 time=1.17 ms

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