14:00:08 #startmeeting networking 14:00:09 Meeting started Tue Sep 22 14:00:08 2020 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:12 The meeting name has been set to 'networking' 14:00:26 hi 14:00:33 hi 14:00:47 o/ 14:01:30 Hi 14:01:50 o/ 14:02:11 ok, I think we can start 14:02:20 welcome everyone! 14:02:22 #topic Announcements 14:02:44 First of all: we are now in the Victoria RC-1 week 14:03:02 so at the end of the week we should have Victoria RC-1 done 14:03:46 I will sync with amotoki later this week and will check release patches for neutron 14:03:53 next 14:03:57 TC/PTL nomination starts 22.09 23:45 UTC (today): http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017306.html 14:04:31 so if You want to be Neutron PTL or join TC group, it's almost time to send Your nomination 14:05:50 I'm going to nominate myself for next cycle as neutron PTL 14:06:30 +1 14:06:30 Long live the King :-) 14:07:05 thx :) 14:07:06 +1 14:07:28 ok, next one 14:07:43 also related to the end of the release cycle a bit 14:07:43 late +1, go Hulk PTL! 14:07:46 Virtual PTG in October (26-30): http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016424.html 14:07:58 etherpad: https://etherpad.opendev.org/p/neutron-wallaby-ptg - please add ideas of the topics there, it is still almost empty 14:08:37 we have scheduled with gibi one nova-neutron session for Wednesday 1400 UTC 14:08:50 o/ 14:08:55 hi gibi :) 14:09:07 * gibi is lurking 14:10:14 and that's all announcements/reminders from me for today 14:10:22 anything else You want to share with the team? 14:11:36 to confirm with amotoki (from this morning's discussion), but we will also probably make stable releases to go along rc-1 14:13:04 bcafarel++ 14:13:37 ok, lets move on 14:13:38 #topic Blueprints 14:13:56 I moved 3 BPs for RC-1 https://launchpad.net/neutron/+milestone/victoria-rc1 14:14:17 https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6 is just missing some tempest scenario tests and patches are in the gate already 14:14:36 https://bugs.launchpad.net/neutron/+bug/1882804 and https://blueprints.launchpad.net/neutron/+spec/local-ip-prefix-in-metering-rules got FFE 14:14:37 Launchpad bug 1882804 in neutron "RFE: allow replacing the QoS policy of bound port" [Wishlist,Confirmed] - Assigned to Lajos Katona (lajos-katona) 14:14:59 patches for both are close to merge IMO 14:15:07 please review them asap if You can: 14:15:12 https://review.opendev.org/#/q/topic:bug/1882804+(status:open+OR+status:merged) 14:15:17 https://review.opendev.org/#/q/topic:bug/1889431+(status:open+OR+status:merged) 14:15:48 other not finished BPs I moved to "neutron next" for now and I will schedule them for Wallaby cycle later 14:16:00 anything You want to add regarding BPs? 14:17:36 \regarding the metadata over ipv6 test 14:17:45 is anybody writing them? 14:18:04 mlavalle: yes 14:18:07 ok 14:18:13 rubasov did them already, see https://review.opendev.org/#/q/topic:metadata-ipv6+(status:open+OR+status:merged) 14:18:26 there is neutron-tempest-plugin patch with those tests 14:19:36 btw. most important patches related to BPs scheduled for rc1 are in https://tinyurl.com/vezk6n6 14:19:48 please check this list and review those patches 14:20:02 ok 14:20:16 I would like to have it merged before thursday so we can release rc1 with them already 14:21:33 ok, lets move on 14:21:36 #topic Community Goals 14:21:56 any updates about zuul v3 or migration to Ubuntu 20.04 ? 14:22:51 I've only observed a few updates, but I'm not sure about the stauts 14:22:53 status* 14:23:09 (the 2 legacy grenade jobs left) 14:23:32 yeah, odl is one 14:23:38 for neutron-ovn-grenade job I'm almost done 14:23:42 patch is https://review.opendev.org/#/c/729591/ 14:23:47 and it works fine now 14:23:58 but it needs patch https://review.opendev.org/#/c/752412/ in devstack 14:24:01 slaweq: last i saw that was not installing ovs? no ovsdb-tool ? 14:24:04 ah 14:24:18 haleyb: yes, but now it works fine 14:24:43 slaweq: isn't there a POST_FAILURE? 14:24:44 I think that we have another bug there as in fact ovn_agent module can't install ovn in other way than compiling it from source 14:24:56 tosky: damm, it is 14:25:03 but previous run was passing 14:25:23 so I'm not done and I will need to verify it again 14:25:43 I commented on neutron-tempest-plugin review, it seems to be mostly OK (1 or 2 tests failing on recheck, but different each time) 14:26:40 ( https://review.opendev.org/#/c/748367/ ) 14:27:54 tosky: I see that all tests passed in that grenade job 14:28:07 I'm not sure why it failed really at the end 14:28:24 can You maybe take a look also, as You probably have more experience with grenade jobs then me :) 14:28:28 slaweq: it seems it failed while collecting the logs on the compute node: https://zuul.opendev.org/t/openstack/build/be55c09398164f03ad32e74fd06ddb98/console 14:28:54 not sure why it happens, the base grenade job should be multinode-enabled 14:29:35 I rechecked it so lets see if that will happen again 14:29:46 as I said, I saw this job passing in previous run 14:30:17 and it passed in revision 17, and failed in 18 and newer 14:30:43 but there are no structural changes 14:30:46 mmhhh 14:31:34 there are only logs added by haleyb https://review.opendev.org/#/c/729591/17..18/zuul.d/grenade.yaml 14:32:06 yes, copied those from another ovn review 14:32:31 if it will fail again, I will check without those logs to ensure that this isn't a culprit 14:34:24 ok, so I think we discussed zuulv3 migration 14:35:11 and speaking about focal, I think that as bcafarel mentioned in the comment to https://review.opendev.org/#/c/748367/ - it seems that it may be related to issue which nova have on focal 14:35:38 I think we will need to wait a bit until this will be solved and try then again 14:36:01 because now our scenario jobs aren't stable for sure on Ubuntu Focal 14:37:11 with that I think we can move on to the next topic 14:37:19 thx for updates on community goals 14:37:25 #topic Bugs 14:37:32 not sure what is the 'offcial' solution, but for bgpvpn I disabled those failing tests temprorary 14:38:00 lajoskatona: yes, but for neutron-tempest-plugin we would need to disable all scenario tests basically :) 14:38:46 ok, lets get back to bugs 14:38:54 hongbin was bug deputy last week 14:39:03 his report is at http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017432.html 14:39:24 I see there 4 bugs which aren't assigned to anyone 14:39:36 2 ovn related things: 14:39:38 https://bugs.launchpad.net/neutron/+bug/1896205 14:39:39 Launchpad bug 1896205 in neutron "AttributeError: 'NoneType' object has no attribute 'db_find_rows' during neutron-server startup" [Undecided,New] 14:39:40 and 14:39:44 https://bugs.launchpad.net/neutron/+bug/1896203 14:39:45 Launchpad bug 1896203 in neutron "TypeError: Cannot look up record by empty string in check_for_igmp_snoop_support task" [Undecided,New] 14:40:03 maybe jlibosva You can take a look and triage them 14:40:08 * jlibosva looks 14:40:32 thx jlibosva :) 14:40:39 I think the db_find_rows error happens when there is no active connection to OVN DBs 14:40:45 we have a patch for that in ovsdbapp 14:40:59 https://review.opendev.org/#/c/752092/ 14:41:00 would be great, so please just link patch there :) 14:41:48 we have also one related to L3HA https://bugs.launchpad.net/neutron/+bug/1895950 14:41:49 Launchpad bug 1895950 in neutron "keepalived can't perform failover if the l3 agent is down" [Medium,New] 14:41:58 if there will be no other volunteers I will take a look into that 14:42:13 and I think that haleyb's proposal there is good way to solve this 14:42:48 slaweq: by migrating to OVN? :) 14:42:52 but if You have any other ideas, please write a comment (or assign it to Your self :)) 14:43:09 haleyb: yeah, that would also works but I think it's not that easy :P 14:43:56 and there is one more bug which I wanted to talk about 14:43:58 https://bugs.launchpad.net/neutron/+bug/1895933 14:43:59 Launchpad bug 1895933 in neutron "Admin user can do anything without the control of policy.json" [Medium,Confirmed] 14:44:33 we have in Neutron everywhere hardcoded that if context.is_admin() then we are allowing everything 14:44:46 do You know why it is like that? 14:45:26 but this is the goal of the admin user 14:45:30 isn't it? 14:45:54 ralonsoh: I don't really know 14:46:33 because it can be specified in policy.json and You can theoretically forbid something for such user 14:46:47 at least that was my understanding of bug description 14:47:00 do You know how other projects works with that? 14:47:05 no idea 14:47:21 but we need context.is_admin() to perform some actions 14:47:30 to retrieve, for example, everything from the DB 14:47:56 ralonsoh: so maybe we should just close this LP as won't fix 14:48:07 I'll check it too 14:48:07 that's why I wanted to ask others during the meeting :) 14:48:29 amotoki can't give advice, usually He has better view of policies? 14:48:44 yes but I didn't saw him around recently 14:48:51 maybe he is on some pto, idk 14:49:49 ok 14:50:55 I will try to ping amotoki about that bug later this week 14:51:18 and that are all bugs from hongbin's report which I wanted to discuss today 14:51:26 this week our bug deputy is haleyb 14:51:30 and next week is lajoskatona's turn 14:51:59 haleyb: lajoskatona are You ok with that? 14:52:11 slaweq: yes 14:52:28 yes, good with that 14:52:30 great, thx 14:52:40 any other bugs anyone wants to discuss today? 14:53:06 or anything else You want to discuss with the team today as I don't have anything else 14:54:36 ok, I guess this silence means "no" so we can finish earlier today :) 14:54:42 thx for attending the meeting 14:54:46 o/ 14:54:50 o/ 14:54:51 have a great week! 14:54:52 o/ 14:54:55 #endmeeting