FIP isn't properly created for octavia loadbalancers

[Marek Grudzinski]

After upgrading from an earlier version of stable/stein to a newer version (released around 2020-02-20) , FIP's on newly created octavia loadbalancers stopped working.

So what we can see is that everything works except the snat namespaces never gets the ip assigned via rootwrap nor the iptables rules. It never happens and there are no errors around this.

Any old loadbalancers that exist work, but can't create new ones.
The loadbalancers themselves work great, using shared networks or tenant networks they work great too. Asked about it in the octavia irc but they pointed me to neutron.

Instances can be assigned FIP's normally without issues.

I could use some help/pointers on where to troubleshoot this.
Debug is enabled on neutron but there are simply no errors, everything just seems to be fine with whats happening.

I'm using DVR HA with OVS.

I'm not even sure what logs to attach since nothing is complaining or spitting out any errors.

[Hongbin Lu (hongbin.lu)]

I couldn't triage this bug because it doesn't have the necessary information to locate a problem. Perhaps, you can go to the neutron IRC channel for trouble-shorting hints and paste more information in here.

[Marek Grudzinski (ivve)]

Hi,

Decided to restart all l3 agents and found that restarting one of them solved the issue. All flips that were already assigned to loadbalancers got correctly configured in the snat namespaces. It is unfortunate that there was no error logs associated with this, so i have nothing to post or contribute with here. Also restarting l3 agents is something that we do as last resort as it takes nearly an hour to fully populate all the namespaces do to how they are created by neutron and its rootwrap scripts (have around 220+ atm). I would love to see some kind of improvement in speed on namespace creation :)

But please close this ticket as the issue is resolved.