After the vm unbinds the floating ip, there are residual ip rules in the qrouter namespace

[yuanshuo]

environment: Stein
We perform the following operations:
1.Bind floating IP to virtual machine
[root@openstack597 /home/yuanshuo1]# ip netns exec qrouter-f45f1272-5ad1-40fa-97a7-f19433bfb6b8 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: rfp-f45f1272-5@if39: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb state UP qlen 1000
    link/ether ea:40:b9:51:9c:41 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 169.254.102.246/31 scope global rfp-f45f1272-5
       valid_lft forever preferred_lft forever
    inet 169.254.120.48/31 scope global rfp-f45f1272-5
       valid_lft forever preferred_lft forever
    inet 169.254.94.174/31 scope global rfp-f45f1272-5
       valid_lft forever preferred_lft forever
    inet6 fe80::e840:b9ff:fe51:9c41/64 scope link
       valid_lft forever preferred_lft forever
531: qr-6644cff4-ea: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN qlen 1000
    link/ether fa:16:3e:b7:ec:1c brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.1/24 brd 192.168.100.255 scope global qr-6644cff4-ea
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:feb7:ec1c/64 scope link
       valid_lft forever preferred_lft forever
[root@openstack597 /home/yuanshuo1]# ip netns exec qrouter-f45f1272-5ad1-40fa-97a7-f19433bfb6b8 ip rule
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
52469: from 192.168.100.128 lookup 16
3232261121: from 192.168.100.1/24 lookup 3232261121

2.restart the l3-agent service
systemctl restart neutron-l3-agent.service

3.The virtual machine unbinds the floating IP, observes the ip rule in the qrouter namespace, and finds that the configuration remains
[root@openstack597 /home/yuanshuo1]# ip netns exec qrouter-f45f1272-5ad1-40fa-97a7-f19433bfb6b8 ip rule
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
52469: from 192.168.100.128 lookup 16
3232261121: from 192.168.100.1/24 lookup 3232261121
[root@openstack597 /home/yuanshuo1]# ip netns exec qrouter-f45f1272-5ad1-40fa-97a7-f19433bfb6b8 ip route show table 16
default via 169.254.94.175 dev rfp-f45f1272-5

This problem will cause the virtual machine to fail to access the Internet

[Nate Johnston (nate-johnston)]

yuanshuo, does this happen 100% of the time? I was unable to reproduce on my setup.

[Brian Haley (brian-haley)]

I'm confused by Step 3 above - "The virtual machine unbinds the floating IP" - do you mean a call to the API to dis-associated the floating IP?

Can you give an example of the API calls you're making here so we can try and reproduce better? Thanks