13:00:26 <haleyb> #startmeeting networking
13:00:26 <opendevmeet> Meeting started Tue Jun 24 13:00:26 2025 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:26 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:26 <opendevmeet> The meeting name has been set to 'networking'
13:00:28 <haleyb> Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, haleyb, ralonsoh
13:00:31 <mlavalle> \o
13:00:36 <obondarev> o/
13:00:36 <haleyb> hi everyone
13:00:37 <ralonsoh> hello
13:00:42 <slaweq> o/
13:02:02 <rubasov> o/
13:02:13 <haleyb> i'll get started
13:02:13 <haleyb> #announcements
13:02:20 <haleyb> We are currently in Week R-3 of Flamingo
13:02:32 <haleyb> Our next milestone in this development cycle will be Flamingo-2, on July 3rd
13:03:02 <haleyb> That is next Thursday 8-o
13:03:25 <haleyb> Final 2025.2 Flamingo release: October 3rd, 2025
13:03:31 <haleyb> #link https://releases.openstack.org/flamingo/schedule.html
13:03:50 <bcafarel> late o/
13:05:07 <haleyb> The next OpenInfra PTG[1] will take place October 27-31, 2025 and registration for the event is now open
13:05:31 <haleyb> #link https://ptg.openinfra.org/
13:05:48 <haleyb> it's virtual and free as it has been for a while
13:06:14 <haleyb> Reminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers
13:07:04 <haleyb> and last announcement
13:07:28 <haleyb> Openstack is changing from CLA to DCO starting July 1st
13:07:38 <lajoskatona> o/
13:08:16 <haleyb> i can't find the link to the ML thread, but it just means that signed-off-by will be mandatory in reviews
13:08:41 <haleyb> so change your workflow to 'git commit -a -s' or similar
13:09:12 <haleyb> and if anyone knows how to tweak .gitconfig to make that -s always take affect i'd love to know the trick
13:09:57 <haleyb> any other announcements?
13:10:31 <haleyb> #topic bugs
13:10:42 <haleyb> mlavalle was the deputy last week, his report is at
13:10:52 <haleyb> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/YNLD3OU44PAA5UOVKXMQDMYVUZHBIGUU/
13:11:38 <haleyb> first one is
13:11:41 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2114732
13:11:48 <haleyb> grenade-skip-level-always job fails with: Security Group None cannot perform precommit_delete due to Callback
13:12:03 <ralonsoh> I commented there
13:12:24 <ralonsoh> we can use WSGI in 2024.2, but it wasn't stable until we removed eventlet (that happened in 2025.1)
13:12:32 <ralonsoh> this is why we don't move to wsgi until 2025.1
13:12:39 <haleyb> ralonsoh: yes, just reading your note
13:12:52 <ralonsoh> so with 2024.2 will work, but with some issues
13:13:14 <ralonsoh> in any case, skip jobs are not mandatory in non-slurp releases (as is now)
13:13:28 <ralonsoh> so I would move this job to periodic, as we do in neutron
13:13:43 <haleyb> do we know what job this is failing with? i agree with your assessment
13:13:57 <ralonsoh> we had multiple issues in wsgi and eventlet
13:14:16 <ralonsoh> once we removed everything eventlet related from the API, everything started to work stable
13:14:44 <haleyb> oh grenade-skip-level-always i didn't know that was a job, wonder where it lives
13:14:54 <ralonsoh> in 2024.2+WSGI, the eventlet removal is not finished and we can't guarantee any stability, as we can see in the CI
13:15:16 <ralonsoh> in grenade repo
13:15:45 <haleyb> i see nova, swift and manila run it
13:16:02 <ykarel> ralonsoh, can't we remove "logger" mechanism driver from there to fix that job
13:16:05 <haleyb> manila has it non-voting
13:16:33 <ralonsoh> ykarel, I don't think this is the problem
13:16:46 <ralonsoh> in 2024.2+WSGI, we were still using eventlet
13:16:50 <ykarel> ack when i last checked that looked the issue but can cross check
13:16:58 <ykarel> iirc i mentioned that too
13:17:45 <ykarel> yes in ci meeting
13:17:46 <ykarel> <ykarel> and here i see Loaded mechanism driver names: ['ovn', 'logger']
13:17:46 <ykarel> <ykarel> so need to remove logger mechanism driver
13:18:09 <ralonsoh> we can try that, for sure
13:18:14 <ykarel> ++ let's do
13:18:15 <ralonsoh> I'll propose a patch
13:18:49 <rubasov> sidenote on git autosignoff: https://paste.opendev.org/show/828233/
13:19:09 <haleyb> thanks ralonsoh, and if that doesn't work can have them turn-off voting
13:19:39 <lajoskatona> https://opendev.org/openstack/tempest/src/branch/master/zuul.d/integrated-gate.yaml#L463
13:19:47 <lajoskatona> sorry
13:19:52 <haleyb> rubasov: thanks for that, autoSignOff=true is the trick :)
13:20:11 <ralonsoh> haleyb, rubasov it is better if we integrate it with the openstack hook
13:20:12 <rubasov> plus the git hook
13:20:13 <ralonsoh> for example: https://paste.opendev.org/show/bgqKZ49CDIOpv4ieeIUv/
13:20:25 <ralonsoh> ^^ that is at the end of the openstack hook
13:22:56 <haleyb> ralonsoh: i'm assuming someone will make a generic change to cover everything? we can worry when it's turned-on next week
13:23:33 <ralonsoh> no idea, this change can be done locally and copy/paste this hook to all repos you have
13:23:45 <ralonsoh> you only need setup your name + mail in git, that is mandatory
13:24:22 <haleyb> ack, i had done that a while back
13:24:32 <haleyb> next bug
13:24:36 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2115053
13:24:43 <haleyb> conntrack flow created for stateless SG rule
13:24:51 <haleyb> slaweq: looks like you picked that up today
13:25:14 <slaweq> yeap
13:25:31 <haleyb> ubuntu noble fails :(
13:25:44 <slaweq> I am triaging it but seems for me like ovn regression
13:26:06 <slaweq> yes, I am now trying to reproduce it on Centos 9 also
13:26:20 <slaweq> but that's still in progress
13:26:45 <haleyb> ack, i'll follow in case there is something that needs a downstream backport
13:27:29 <haleyb> all the other bugs have owners and/or patches
13:27:36 <haleyb> any others to discuss?
13:28:20 <haleyb> lajoskatona: i know we talked last week about you swapping bug deputy weeks with jlibosva, can you still take this week?
13:28:30 <haleyb> i forgot to update the calendar but will right after
13:28:34 <lajoskatona> Yes, I am on it
13:28:42 <haleyb> lajoskatona: ack, thanks!
13:29:29 <haleyb> and next week will be obondarev - is that Ok with you?
13:29:34 <obondarev> sure
13:29:47 <haleyb> great, thanks!
13:30:06 <haleyb> ok, moving on from bugs
13:30:11 <haleyb> #topic community goals
13:30:47 <haleyb> lajoskatona: any update on neutronclient?
13:31:24 <opendevreview> Merged x/whitebox-neutron-tempest-plugin master: [DVR] Add sleep after adding/removing FIPs  https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/951111
13:31:27 <lajoskatona> yes, I pushed one patch for  horizon, for rbac API
13:31:57 <lajoskatona> and I checked this morning and it seems only neutron quotas remained to move to SDK (have to double check again)
13:32:06 <lajoskatona> so quite close to finish one project it seems :-)
13:32:39 <lajoskatona> the rbac policies patch (wip): https://review.opendev.org/c/openstack/horizon/+/953116
13:32:52 <lajoskatona> that's all for SDK vs neutronclient topic
13:33:25 <haleyb> great, thanks for all the patches
13:33:55 <haleyb> ralonsoh: i'll let you talk about eventlet, it's made some progress as well
13:34:04 <ralonsoh> yes but we have a problem
13:34:09 <ralonsoh> fullstack CI
13:34:12 <ralonsoh> 1) Broken with OVS agent eventlet removal: https://review.opendev.org/c/openstack/neutron/+/937765
13:34:18 <ralonsoh> 2) Broken with the removal of eventlet server code: https://review.opendev.org/c/openstack/neutron/+/952659
13:34:34 <ralonsoh> I don't know how to replace the API part, to be honest
13:34:52 <ralonsoh> and the OVS agent doesn't work if executed in a eventlet process
13:35:14 <ralonsoh> so, at this point and in order to progress, I would suggest to deactivate the fullstack CI
13:35:32 <ralonsoh> and try to fix API part, if possible
13:35:38 <lajoskatona> yes I think I run into the same for the dhcp agent patch also
13:35:44 <ralonsoh> ^^ right
13:36:02 <ralonsoh> so I would suggest to migrate the jobs, as much as possible, to n-t-p
13:36:47 <ralonsoh> the fact the n-t-p and tempest work with the eventlet-less patches (dhcp, ovs, api) means these patches are working
13:37:04 <ralonsoh> but this fullstack CI is specifically tailor-made for eventlet
13:37:41 <lajoskatona> hard topic.....
13:37:44 <ralonsoh> I know
13:38:15 <ralonsoh> I think many fullstack jobs can be implemented in n-t-p
13:38:16 <haleyb> ralonsoh: ack, i guess we don't have a choice if we want to complete the work, but it will leave a gap
13:38:20 <lajoskatona> few weeks ago I mentioned that migrating to SDK also hard in fullstack as sdk has no no-auth mode.....
13:38:24 <haleyb> what do others think?
13:38:39 <ralonsoh> haleyb, yes but we can close it using neutron-tempest-plugin
13:38:54 <ralonsoh> to be honest, n-t-p is more accurate kind of testing that fullstack
13:39:10 <lajoskatona> let's check  if we can migrate those tests to n-t-p  and go fo it, we gain simpler gating perhaps
13:39:11 <ralonsoh> I know that for some API tests it was lighter
13:39:49 <lajoskatona> yeah in fullstack we did things like service restart, in pure tempest that is no possible
13:40:03 <haleyb> ralonsoh: understood, it's just it will take time is all
13:40:45 <ralonsoh> haleyb, right
13:40:53 <ralonsoh> lajoskatona, we can have this with tobiko, for example
13:41:10 <ralonsoh> if you don't mind (and if you agree with this, of course)
13:41:19 <ralonsoh> I'll send a mail informing about this
13:41:35 <ralonsoh> are you all OK?
13:42:00 <haleyb> i am Ok with it
13:42:16 <lajoskatona> yes, from side fine, for learning tobiko that's an interesting thing :-)
13:42:56 <ralonsoh> ok, I'll do it and I'll send a patch to remove fullstack
13:43:20 <haleyb> )-;
13:43:26 <ralonsoh> lajoskatona, send me what problems you had with sdk too
13:43:34 <lajoskatona> I can also spend some time on migrating some of the tests
13:43:35 <ralonsoh> just for documentation purposes in the mail
13:43:51 <ralonsoh> I'll create a LP bug related ^^
13:43:58 <lajoskatona> ralonsoh: ack, I will go back to that problem to collect my fading memories
13:44:10 <ralonsoh> thanks!
13:44:36 <haleyb> alright, moving to last topic
13:44:41 <haleyb> #topic on-demand
13:45:17 <haleyb> ralonsoh: i have a follow-on fix for the metadata-agent LoopingCall code in 2025.1 - https://review.opendev.org/c/openstack/neutron/+/953064
13:45:24 <haleyb> i broke it with my pep8 change
13:45:48 <ralonsoh> i didn't see it, let me check
13:46:20 <ralonsoh> what was the original change?
13:46:45 <haleyb> https://review.opendev.org/c/openstack/neutron/+/952561
13:47:05 <haleyb> there was a pep8 error that i just fixed, but should have tested it
13:47:30 <haleyb> pep8 was happy but code silently failed, and it has no tests...
13:47:30 <ralonsoh> ^ but this is my patch
13:48:23 <haleyb> ralonsoh: yes, i shouldn't have fixed the pep8 issue in PS3
13:48:49 <haleyb> your code was fine, i broke it
13:49:03 <haleyb> well, fine except for failing pep8 job
13:50:34 <ralonsoh> +2, let's merge it asap
13:50:57 <haleyb> either way it needs that change, and i proposed a similar change for all of neutron's calls to that Looping class to make sure they don't get broken
13:51:21 <haleyb> sometimes pylint is not your friend :(
13:51:46 <haleyb> that's all i had, any other topics?
13:52:12 <haleyb> ok, have a good week everyone!
13:52:15 <haleyb> #endmeeting