Comment 4 for bug 2037239

I also didn't see any recent changes in this area. Looking through reviews, this was the first one where I saw these jobs fail, which was September 22nd 7pm:

https://review.opendev.org/c/openstack/neutron/+/896299

And looking at the logs this was the parent when the job ran:

commit 8e38e57b8000ca6ce9ab84692a9aba6220556a3d
Merge: dbe4ba910b 2c0e9cfa71
Author: Zuul <email address hidden>
Date: Thu Sep 21 17:52:23 2023 +0000

    Merge "Create a single method to set the quota usage dirty bit"

It does seem only the master and 2023.2 gates are affected, at least looking at the n-t-p change introducing the new 2023.2 checks, https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/895516

And the above change is only on master, not 2023.2.

The only thing I've noticed is that when the l3-agent complains about an interface not existing in the namespace, looking at the ovs-vswitchd log shows the interface in question was added to br-int just a few milliseconds later. The l3-agent then proceeds to fail doing a lot of sysctl calls, but it's unclear if it's all related yet.

I will try and continue looking for clues tomorrow.