yahoo-eng-team team mailing list archive

Thread
Date
[Bug 1959884] [NEW] [stein][neutron] Static rules losed

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: andrea gargano <1959884@xxxxxxxxxxxxxxxxxx>
Date: Thu, 03 Feb 2022 10:23:22 -0000
Reply-to: Bug 1959884 <1959884@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx
Public bug reported:

Hi all,
we faced an inssue in our openstack, we have some private clouds with static rules, if the controller that own namespace with the static rule goes down, namespace moves to other controller but it loses the rule.
I can still see the rules inside the router on openstack but it doesn’t work until recreated.
Have you seen something like this?

Before controller reboot:

ip netns exec qrouter-808a7d28-5cf4-42c5-b74b-1d8b44193f13 netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
10.102.186.0    0.0.0.0         255.255.255.0   U         0 0          0 qr-c8ea8a1d-fe
169.254.0.0     0.0.0.0         255.255.255.0   U         0 0          0 ha-d030f1d9-d5
169.254.192.0   0.0.0.0         255.255.192.0   U         0 0          0 ha-d030f1d9-d5
192.168.69.0    10.102.186.251  255.255.255.0   UG        0 0          0 qr-c8ea8a1d-fe
192.168.100.0   0.0.0.0         255.255.255.0   U         0 0          0 qr-4b5d42cf-f4

After reboot on new controller node:

ip netns exec qrouter-808a7d28-5cf4-42c5-b74b-1d8b44193f13 netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
10.102.186.0    0.0.0.0         255.255.255.0   U         0 0          0 qr-c8ea8a1d-fe
169.254.0.0     0.0.0.0         255.255.255.0   U         0 0          0 ha-e7a4fd30-d5
169.254.192.0   0.0.0.0         255.255.192.0   U         0 0          0 ha-e7a4fd30-d5
192.168.100.0   0.0.0.0         255.255.255.0   U         0 0          0 qr-4b5d42cf-f4

Log l3 agent:

2022-02-03 10:36:32.241 11383 INFO neutron.agent.l3.agent [-] Finished a router update for 808a7d28-5cf4-42c5-b74b-1d8b44193f13, update_id eec87271-612e-4883-9ea4-75007de9f6cb. Time elapsed: 1.653
2022-02-03 11:09:46.107 11383 INFO eventlet.wsgi.server [-] <local> "GET / HTTP/1.1" status: 200  len: 115 time: 0.0016830
2022-02-03 11:09:46.108 11383 INFO eventlet.wsgi.server [-] <local> "GET / HTTP/1.1" status: 200  len: 115 time: 0.0015860
2022-02-03 11:09:48.107 11383 INFO neutron.agent.l3.ha [-] Router 43707d80-3449-4c4a-bd87-2fcb380bcdcf transitioned to master
2022-02-03 11:09:48.108 11383 INFO neutron.agent.l3.ha_router [-] Set router 43707d80-3449-4c4a-bd87-2fcb380bcdcf gateway device link state to up.
2022-02-03 11:09:48.109 11383 INFO neutron.agent.l3.ha [-] Router 808a7d28-5cf4-42c5-b74b-1d8b44193f13 transitioned to master
2022-02-03 11:09:48.109 11383 INFO neutron.agent.l3.ha_router [-] Set router 808a7d28-5cf4-42c5-b74b-1d8b44193f13 gateway device link state to up.

our config:

allow_automatic_l3agent_failover = True

l3_ha = True

max_l3_agents_per_router = 3

l3_ha_net_cidr = 169.254.192.0/18


Thank you in advance.

Andrea Gargano

** 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/1959884

Title:
  [stein][neutron] Static rules losed

Status in neutron:
  New

Bug description:
  Hi all,
  we faced an inssue in our openstack, we have some private clouds with static rules, if the controller that own namespace with the static rule goes down, namespace moves to other controller but it loses the rule.
  I can still see the rules inside the router on openstack but it doesn’t work until recreated.
  Have you seen something like this?

  Before controller reboot:

  ip netns exec qrouter-808a7d28-5cf4-42c5-b74b-1d8b44193f13 netstat -rn
  Kernel IP routing table
  Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
  10.102.186.0    0.0.0.0         255.255.255.0   U         0 0          0 qr-c8ea8a1d-fe
  169.254.0.0     0.0.0.0         255.255.255.0   U         0 0          0 ha-d030f1d9-d5
  169.254.192.0   0.0.0.0         255.255.192.0   U         0 0          0 ha-d030f1d9-d5
  192.168.69.0    10.102.186.251  255.255.255.0   UG        0 0          0 qr-c8ea8a1d-fe
  192.168.100.0   0.0.0.0         255.255.255.0   U         0 0          0 qr-4b5d42cf-f4

  After reboot on new controller node:

  ip netns exec qrouter-808a7d28-5cf4-42c5-b74b-1d8b44193f13 netstat -rn
  Kernel IP routing table
  Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
  10.102.186.0    0.0.0.0         255.255.255.0   U         0 0          0 qr-c8ea8a1d-fe
  169.254.0.0     0.0.0.0         255.255.255.0   U         0 0          0 ha-e7a4fd30-d5
  169.254.192.0   0.0.0.0         255.255.192.0   U         0 0          0 ha-e7a4fd30-d5
  192.168.100.0   0.0.0.0         255.255.255.0   U         0 0          0 qr-4b5d42cf-f4

  Log l3 agent:

  2022-02-03 10:36:32.241 11383 INFO neutron.agent.l3.agent [-] Finished a router update for 808a7d28-5cf4-42c5-b74b-1d8b44193f13, update_id eec87271-612e-4883-9ea4-75007de9f6cb. Time elapsed: 1.653
  2022-02-03 11:09:46.107 11383 INFO eventlet.wsgi.server [-] <local> "GET / HTTP/1.1" status: 200  len: 115 time: 0.0016830
  2022-02-03 11:09:46.108 11383 INFO eventlet.wsgi.server [-] <local> "GET / HTTP/1.1" status: 200  len: 115 time: 0.0015860
  2022-02-03 11:09:48.107 11383 INFO neutron.agent.l3.ha [-] Router 43707d80-3449-4c4a-bd87-2fcb380bcdcf transitioned to master
  2022-02-03 11:09:48.108 11383 INFO neutron.agent.l3.ha_router [-] Set router 43707d80-3449-4c4a-bd87-2fcb380bcdcf gateway device link state to up.
  2022-02-03 11:09:48.109 11383 INFO neutron.agent.l3.ha [-] Router 808a7d28-5cf4-42c5-b74b-1d8b44193f13 transitioned to master
  2022-02-03 11:09:48.109 11383 INFO neutron.agent.l3.ha_router [-] Set router 808a7d28-5cf4-42c5-b74b-1d8b44193f13 gateway device link state to up.

  our config:

  allow_automatic_l3agent_failover = True

  l3_ha = True

  max_l3_agents_per_router = 3

  l3_ha_net_cidr = 169.254.192.0/18


  Thank you in advance.

  Andrea Gargano

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