14:00:07 #startmeeting networking 14:00:07 Meeting started Tue Sep 5 14:00:07 2023 UTC and is due to finish in 60 minutes. The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:07 The meeting name has been set to 'networking' 14:00:09 o/ 14:00:13 o/ 14:00:13 o/ 14:00:14 hi 14:00:17 o/ 14:00:17 o/ 14:00:19 hello all 14:00:23 \o 14:00:45 we have quorum today, I'll wait 30 more seconds 14:01:19 o/ 14:01:20 o/ 14:01:23 #topic announcements 14:01:35 the schedule 14:01:37 #link https://releases.openstack.org/bobcat/schedule.html 14:01:46 this week is the 14:01:47 * Election Email Deadline 14:01:52 * Election Campaigning Begins 14:01:54 Merged openstack/neutron master: Check the device ID and host ID during virtual port binding https://review.opendev.org/c/openstack/neutron/+/892564 14:02:16 but, of course, we know who is going to be our future PTL 14:02:24 late o/ 14:02:26 so, in advance, thanks haleyb for proposing yourself 14:02:32 +1 14:02:43 o/ 14:03:09 ++ 14:03:15 you'll have my support during the next cycle, for sure 14:03:27 looking forward to leading the project 14:03:52 we had the library releases last week 14:04:01 n-lib created some problems in n-d-r 14:04:12 and a new Bobcat beta version of Neutron was created 14:04:15 the 3rd one 14:04:24 for now, so far so good 14:04:42 now you need to make a last review of the highlights 14:04:45 #link https://review.opendev.org/c/openstack/releases/+/893174 14:04:52 that should be approved during this week 14:05:29 and the last topic I have for this section is a new episode in the openinfra web 14:05:32 #link https://openinfra.dev/live/#all-episodes 14:05:37 "Cyber Resilience Act: What Now?" 14:05:57 any other topic in this section?? 14:06:30 ok, let's jump to the next topic 14:06:35 #topic bugs 14:06:46 last week report is from elvira 14:06:53 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034958.html 14:07:16 there are still some pending bugs not assigned/to be discussed 14:07:18 #link https://bugs.launchpad.net/neutron/+bug/2033651 14:07:23 [fullstack] Reduce the CI job time 14:07:37 I opened this bug, I think the goal is clear 14:07:53 fullstack job is taking between 2 and 3 hours, depending on the node 14:08:03 and sometimes it times out 14:08:19 so we need to find a way to reduce the tests, combine them or improve the code 14:08:29 but I think that is a long term goal 14:08:35 good goal 14:08:54 and not easy, for sure, but we can do small steps 14:09:14 right. seems more like tech depth than a bug. 14:09:28 anyone can help on this, so you are welcome 14:09:45 the next one is 14:09:47 #link https://bugs.launchpad.net/neutron/+bug/2033293 14:09:54 "dns integration saying plugin does not match requirements" 14:10:03 but frickler couldn't reproduce it 14:10:14 so we are waiting for more logs 14:10:26 frickler, any comment on this one? 14:11:31 ok, we can keep the "incomplete" tag for now until new logs (neutron server) are provided 14:11:47 the last one is 14:11:53 #link https://bugs.launchpad.net/neutron/+bug/2033683 14:11:59 openvswitch.agent.ovs_neutron_agent fails to Cmd: ['iptables-restore', '-n']" 14:12:09 ykarel commented on this one 14:12:21 this job has been working fine for months 14:12:34 but now it seems that a binary is missing 14:13:12 but yes nothing for neutron in this, i asked for more details and suggested what needs to be fixed in tripleo side 14:13:49 as you mentioned, in https://review.opendev.org/c/openstack/kolla/+/761182 "iptables-restore" is missing 14:14:02 to be honest, I don't know why that worked before 14:14:23 but they maybe bumped the iptables library, that also affects these tools 14:14:33 not iptables-restore but /usr/bin/update-alternatives 14:14:38 sorry, not iptables but nftables 14:14:49 yes, because of nftables 14:15:14 I'll mark this bug as "invalid" from the Neutron point of view 14:15:18 ok /me not aware about the relation b/w update-alternatives and nftables 14:15:19 +1 14:15:53 nftables provide all the iptables legacy support 14:16:24 so thanks for taking care of this one 14:16:38 in kolla iirc we needed to fix a mismatch between what is happening inside the container and outside and what docker does 14:17:17 maybe the situation in tripleo is similar 14:17:25 but not a neutron issue I agree 14:18:26 I think any command is executed from inside the containers, so we don't use any external binary 14:18:57 I only remember one issue related to "ip-netns" but due to some missing permissions 14:19:13 anyway, we can skip this one 14:19:18 but docker does that, and then nftables and legacy iptables may collide 14:19:36 or rather the nftables rule do not get used or something similar 14:20:13 sorry, I used kolla many years ago and I'm not familiar with this tool, to be honest 14:20:37 nevermind, let's go on 14:20:58 I don't have any other bug in the list 14:21:00 do you? 14:21:06 regarding 2033293 I suspect a misconfiguration, but need more data as mentioned in order to confirm 14:21:31 yeah, we can wait for this information if you couldn't reproduce it 14:21:57 this week ykarel is the deputy, next week will be mtomaska 14:21:59 ack? 14:22:03 ack 14:22:09 ack 14:22:10 cool, thanks! 14:22:30 I'm jumping to the next section 14:22:37 #topic community_goals 14:22:37 any progress on the OVN MTU issue? 14:23:05 no, I had some internal issues and I coudbn't spend a single moment on this 14:23:18 we are also in the release weeks 14:23:24 and everything seems to fail! 14:24:09 ok, let's continue 14:24:11 1) Add support for the service role in neutron API policies 14:24:21 #link https://review.opendev.org/c/openstack/neutron/+/886724 14:24:40 (I don't think you spend much time on this one last week, right?) 14:24:52 slaweq, 14:25:25 no, nothing new this week 14:25:27 it is still in merge conflict by gerrit 14:25:37 ok, this will be a C release feature but you are free to review the patch ^^ 14:26:03 the next one is 14:26:04 2) Neutron client deprecation 14:26:12 lajoskatona, please 14:26:21 There's 3 open patche that can fit to Bobcat: 14:26:23 https://review.opendev.org/q/topic:bug/1999774+project:openstack/python-neutronclient+status:open 14:27:01 these are all for neutronclient, as SDK release happened with the SDK side of these 14:27:46 that's it for this topic from me 14:27:52 qq: you are not bumping the openstacksdk library in any of them 14:28:12 that should be necessary to receive the dependant sdk patch 14:28:24 As I know we got the highest from upper-constraints and that was bumped 14:28:31 perfect 14:28:40 I said that because we had an issue last week 14:28:43 related to this 14:28:57 #link https://review.opendev.org/c/openstack/python-neutronclient/+/893346 14:29:14 this was the bump: https://review.opendev.org/c/openstack/requirements/+/893351 14:29:32 yes last week there was some central issue with requ bumps 14:29:51 yeah, but I was talking about the neutronclient min reqs 14:30:22 ah, true, that is necessary 14:30:37 please check what sdk version has each patch 14:30:44 and bump it correspondingly 14:30:47 ack 14:30:55 thanks a lot 14:31:08 and that's all 14:31:36 #topic on_demand 14:31:44 any topic you want to bring here? 14:31:55 not me 14:32:07 I added one 14:32:27 it is a heads up: Nova EOL-ed Train branch 14:32:40 yes, good topic 14:32:44 what should we do? 14:32:46 perhaps elodilles has more background 14:32:57 we still accept Train patches 14:33:17 well, nova had some CVE fix that did not land on train, hence the team decided to EOL train 14:33:40 so i'm not insisting anymore to keep train open for neutron either o:) 14:33:58 yes something like that, so it can be that we do the same or keep the branch open 14:33:58 we still don't have this problem. Some users asked us to keep it open, months ago 14:34:12 but I didn't see any activity on this branch 14:34:16 but anyway as things going most projects close most of these branches soon I suppose 14:34:39 ok, I can send a mail (again) to propose the EOL of Train in Neutron 14:34:49 and we can receive feedback of the community 14:34:55 ralonsoh: ++ 14:35:00 +1 14:35:03 (it still can be kept open, but then we have to create a patch for devstack to consume train-eol from nova) 14:35:04 IMO, this branch is old enough at this point 14:35:28 ok then, I'll send the mail today. Thanks! 14:35:35 any other topic? 14:35:36 thanks too 14:35:43 elodilles, thanks! 14:36:09 maybe this: since we have talked about python-neutronclient: https://review.opendev.org/c/openstack/releases/+/893615 14:36:09 so please remember the CI meeting is in 25 mins in this channel 14:36:20 video or irc? 14:36:37 elodilles, ups, I missed this patch 14:36:42 irc 14:36:45 we can delay that some days 14:36:51 until we have lajoskatona's patches 14:36:52 ack ykarel 14:37:15 lajoskatona, so please, check your nclient patches asap 14:37:16 ralonsoh: no problem, you are not late :) 14:37:23 and then I'll update the release hash 14:37:56 ralonsoh: no this is currently a virtual instance, although we do see the same issue on BareMetal as well.. 14:37:57 note that *client libs freeze was last week 14:38:14 this is just a stable/2023.2 branch cut patch 14:38:26 right 14:38:43 ok, so the above 3 patches are anyway to C 14:38:55 actually for nclient we'll need to release a new stable version to have them in Bobcat 14:39:00 yes 14:39:24 lajoskatona, is that a problem or we need to have them in Bobcat? 14:39:35 I dont think so 14:39:50 ok then 14:40:03 nothing will break if don't have these, and we don't have a deadline for it as I know 14:40:22 right 14:40:41 so please folks check the non-client libs freeze https://review.opendev.org/c/openstack/releases/+/893615 14:40:50 and that's all 14:40:58 thank you all for attending 14:41:06 #endmeeting