Tuesday, 2021-03-16

*** macz_ has joined #openstack-meeting-300:00
*** e0ne has quit IRC00:03
*** macz_ has quit IRC00:04
*** tosky has quit IRC00:35
*** ianychoi_ has joined #openstack-meeting-301:03
*** rubasov_ has joined #openstack-meeting-301:08
*** ianychoi has quit IRC01:12
*** SotK has quit IRC01:12
*** rubasov has quit IRC01:13
*** bcafarel has quit IRC01:13
*** SotK has joined #openstack-meeting-301:13
*** bcafarel has joined #openstack-meeting-301:20
*** mlavalle has quit IRC01:43
*** psachin has joined #openstack-meeting-303:38
*** DinaBelova has quit IRC03:49
*** DinaBelova has joined #openstack-meeting-303:53
*** rubasov_ has quit IRC05:47
*** rubasov has joined #openstack-meeting-305:52
*** rubasov has quit IRC05:52
*** rubasov has joined #openstack-meeting-305:52
*** slaweq has joined #openstack-meeting-306:50
*** hemanth_n has joined #openstack-meeting-306:59
*** eolivare has joined #openstack-meeting-307:32
*** zigo has joined #openstack-meeting-308:29
*** tosky has joined #openstack-meeting-309:00
*** lpetrut has joined #openstack-meeting-309:02
*** lee2 has joined #openstack-meeting-309:24
*** lee2 is now known as lyarwood09:24
*** e0ne has joined #openstack-meeting-310:00
*** e0ne has quit IRC10:03
*** psahoo has joined #openstack-meeting-310:37
*** dosaboy has quit IRC11:49
*** dosaboy has joined #openstack-meeting-311:50
*** Luzi has joined #openstack-meeting-311:57
*** eolivare_ has joined #openstack-meeting-312:21
*** eolivare has quit IRC12:24
*** hemanth_n has quit IRC12:25
*** psahoo has quit IRC12:41
*** macz_ has joined #openstack-meeting-312:43
*** macz_ has quit IRC12:48
*** psahoo has joined #openstack-meeting-312:57
*** hemanth_n has joined #openstack-meeting-313:12
*** hemanth_n has quit IRC13:16
*** artom has quit IRC13:21
*** artom has joined #openstack-meeting-313:22
*** psahoo has quit IRC13:39
*** psahoo has joined #openstack-meeting-313:41
*** psahoo has quit IRC13:46
*** psahoo has joined #openstack-meeting-313:59
slaweq#startmeeting networking14:00
openstackMeeting started Tue Mar 16 14:00:47 2021 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
slaweqhi14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
*** mlavalle has joined #openstack-meeting-314:00
mlavalleo/14:01
slaweqo/14:01
rubasovhi14:01
*** obondarev has joined #openstack-meeting-314:01
obondarevhi14:01
haleybhi14:02
*** lajoskatona has joined #openstack-meeting-314:02
slaweqlet's start14:02
slaweq#topic announcements14:02
*** openstack changes topic to "announcements (Meeting topic: networking)"14:02
lajoskatonaHi14:02
slaweqWallaby cycle calendar https://releases.openstack.org/wallaby/schedule.html14:02
slaweqnext week is RC1 week14:03
slaweqso we are almost there with Wallaby14:03
slaweqrelease highlights merged https://review.opendev.org/c/openstack/releases/+/77948714:03
ralonsohhi (sorry for being late)14:03
slaweqwe also have accepted RFE for new neutron-lib release for Wallaby: http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021077.html14:03
slaweqrelease patch was just approved by release team https://review.opendev.org/c/openstack/releases/+/78055014:03
slaweqwe are now after feature freeze deadline so please don't accept patches related to any new features in next weeks14:04
slaweqwe can accept such patches after we will have stable/wallaby branch created14:04
slaweqnext reminder is about PTG which will be 19-23th April: http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020778.html14:05
slaweqDoodle https://doodle.com/poll/cc2ste3emzw7ekrh?utm_source=poll&utm_medium=link is still active, if You haven't fill it yet, please do so14:05
slaweqnext week is deadline for booking virtual rooms for the team14:06
slaweqthere is also etherpad https://etherpad.opendev.org/p/neutron-xena-ptg created14:06
slaweqif You have any proposals for topics to discuss during the PTG, please add them there14:07
slaweqok, next one14:07
*** psahoo has quit IRC14:07
slaweqPTL nominations are now over14:07
slaweqthere was only one candidate for the Neutron PTL so there is no election14:07
slaweqand You will have to live with me one more cycle :)14:08
mlavalleThanks for being our PTL another cycle!14:09
slaweqthanks mlavalle14:09
obondarevthanks Slawek!14:09
slaweqthx :)14:09
slaweqthat are all announcements from today from me14:09
slaweqdo You have anything else to add/announce to the team?14:10
mlavallenot me14:11
slaweqok, I guess that this means "no"14:11
slaweqso let's move forward14:11
slaweq#topic Blueprints14:11
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:11
slaweqWallaby RC1 https://bugs.launchpad.net/neutron/+milestone/wallaby-rc114:11
slaweqI today set https://blueprints.launchpad.net/neutron/+spec/address-groups-in-sg-rules as implemented14:12
slaweqand I moved other BPs to neutron-next as we don't have any BP for RC114:12
mlavalle+114:12
slaweqthx mlavalle and Your team for working on that address-groups BP14:13
slaweqone more update from me, regarding secure-rbac14:13
slaweqhttps://blueprints.launchpad.net/neutron/+spec/secure-rbac-roles14:13
mlavalleThanks to hangyang14:13
slaweqwe have merged all patches which introduced new policies14:13
slaweqso we have that in neutron for Wallaby14:13
slaweqlbragstad found bug related to the access of the resources by system reader14:14
slaweqhttps://bugs.launchpad.net/neutron/+bug/191850614:15
openstackLaunchpad bug 1918506 in neutron "Neutron doesn't honor system-scope" [High,Fix committed] - Assigned to Slawek Kaplonski (slaweq)14:15
slaweqfix is in neutron lib and that's why we needed that new release of neutron-lib14:15
slaweqthere is also additional issue with those roles, that project admin was able to get e.g. system resources which should be available only for system admin/reader14:16
slaweqlike e.g. list of agents14:16
slaweqfix for that is proposed https://review.opendev.org/c/openstack/neutron/+/78054814:16
slaweqplease review that patch when You will have some time14:17
slaweqtoday I found one more thing with those new personas14:18
slaweqthis time about network creation14:18
slaweq new rules allows create e.g. provider network only for system admin: https://github.com/openstack/neutron/blob/5f6fbcb155e19d0a46cef0e7bbfee553f0472ef3/neutron/conf/policies/network.py#L123 - in context of such system admin user, there is no project_id, so such admin needs always to pass --project_id to specify owner of the network - should we allow it also for project_admin?14:18
ralonsohhow can you know he is a project_admin without project id?14:19
slaweqproject_admin is different role14:19
ralonsohyes, but project_admin is the admin of a single project14:19
ralonsohand you don't have it14:19
slaweqso system_admin is role which is set when there is system_scope='all' in context and there is no project_id then14:20
slaweqbut project_admin is role where in context IS project_id given14:20
slaweqhttps://github.com/openstack/neutron/blob/master/neutron/conf/policies/base.py#L6014:20
slaweqso the issue is that14:21
slaweq1. with old rules there was only one type of ADMIN and such admin user belong to some tenant always, so when such user created network with e.g. provider_network given it was fine as tenant_id was in context14:22
slaweq2. now, with new rules we set that such call with provider:physical_network can be done just by SYSTEM_ADMIN and when such user makes API request there is no tenant_id in context14:23
slaweqso neutron fail as it needs tenant_id for network14:23
slaweqso there are 2 possibilities IMO:14:23
slaweqa) we leave it as it is now and update our docs that such SYSTEM_ADMIN user needs to always pass tenant-id for which network is created14:23
slaweqb) we will modify our new policy rules to allow creation of e.g. network with provider:physical_network also for users with role PROJECT_ADMIN14:24
ralonsoha) that's safe but changes the API14:24
slaweqis the problem clear now?14:24
ralonsohb) is less secure but no API change14:24
slaweqralonsoh: yes, exactly14:25
slaweqb) mimics what we have now with "less secure rules"14:25
ralonsohto avoid API changes (and problems), I would prefer b)14:25
slaweqby "less secure" I mean old rules14:25
ralonsohI know14:25
ralonsohwe can improve that later14:25
slaweqof course user can modify it on own deployment, it's just matter of defaults14:26
slaweqI have patch for option b) ready but I wanted to know Your opinion first14:26
lajoskatonaif I understand well b) is like what we have now14:27
mlavalleand we should probably document profusely if we go with b14:27
slaweqlajoskatona: more or less - yest14:27
slaweq*yes14:27
lajoskatonaI mean before the policy cahnges merged (victoria and before)14:27
*** macz_ has joined #openstack-meeting-314:27
lajoskatonaso b) looks like a way forward but worth a mail perhaps to list14:28
ralonsohagree14:28
slaweqmail about what exactly?14:28
ralonsoh(anyway, if I prefer (b) now is for not changing the API jsut right now, at the end of the cycle)14:28
slaweqthat we will go with "less secure" default rules to mimic old behaviour?14:28
lajoskatonaexactly14:28
slaweqralonsoh: TBH by default old, deprecated rules are still working fine14:29
lajoskatonawe keep the old behaviour with API but from the new rules perspective it is less secure14:29
slaweqso API isn't really changed until You will not switch some config knobs to enable usage of new rules only14:29
ralonsohwhat lajoskatona said14:29
ralonsohnew rules but same policing14:30
slaweqok, I will send that patch to mimic old rules in new ones as much as possible14:30
slaweqwe can improve/change them in the future if there will be need for that14:30
slaweqthx for Your opinions about it14:30
slaweqand with that I think we are done with BPs for today14:31
slaweqdo You want to talk about any other BP?14:31
slaweqok, let's move on14:33
slaweq#topic Community Goals14:33
*** macz_ has quit IRC14:33
*** openstack changes topic to "Community Goals (Meeting topic: networking)"14:33
slaweqralonsoh: any updates about privsep migration?14:33
ralonsohnot for now14:33
slaweqk14:33
slaweqso we can move on to the next topic14:34
slaweq#topic Bugs14:34
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:34
slaweqhongbin was bug deputy, report: http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021064.html14:34
slaweqI see there 2 bugs which needs some attention14:34
slaweqhttps://bugs.launchpad.net/neutron/+bug/1918914 - ovn and DHCP issue14:34
openstackLaunchpad bug 1918914 in neutron "Toggling dhcp on and off in a subnet causes new instances to be unreachable" [Medium,Confirmed]14:34
slaweqralonsoh I saw You were commenting on it14:34
slaweqwill You take care of that LP?14:34
ralonsohslaweq, ok but I still can't reproduce it14:35
slaweqyes, I saw14:35
ralonsohI don't know why is confirmed (even with c#3)14:35
slaweqplease keep an eye on it, maybe there will be some more data about how to reproduce it14:35
ralonsohin any case, I'll check it14:36
slaweqthx a lot14:36
slaweqand second one is14:36
slaweqhttps://bugs.launchpad.net/neutron/+bug/1918145 - API slowdown14:36
openstackLaunchpad bug 1918145 in neutron "Slownesses on neutron API with many RBAC rules" [Medium,Confirmed]14:36
slaweqobondarev I was hoping that maybe You could take a look at that one14:36
slaweqas You are doing a lot of performance improvements on API/DB level recently :)14:36
obondarev@slaweq, yes, this is part of internal activity. Let me check that one. Not promising however I'll have enough time for this in coming days :)14:37
slaweqobondarev: thank You14:37
slaweqother bugs from the report are at least assigned as far as I checked14:38
slaweqso we should be good with them14:38
slaweqthis week our bug deputy is haleyb :)14:38
slaweqand next week will be lajoskatona14:38
slaweqare You ok with that?14:38
haleyback from me14:39
slaweqlajoskatona: if You couldn't do it next week, please let me know :)14:39
lajoskatonaYes, I made notes o fit14:40
slaweqok, and that's all regarding bugs from my side14:40
slaweqthx lajoskatona14:40
slaweqany other bugs You want to talk about today?14:40
slaweqor any other topics to discuss?14:40
slaweqok, if not I will give You 19 minutes back today14:41
slaweqthx for attending the meeting and have a great week14:41
slaweqo/14:42
lajoskatonao/14:42
ralonsohbye14:42
slaweq#endmeeting14:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:42
openstackMeeting ended Tue Mar 16 14:42:14 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2021/networking.2021-03-16-14.00.html14:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2021/networking.2021-03-16-14.00.txt14:42
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2021/networking.2021-03-16-14.00.log.html14:42
rubasovo/14:44
*** Luzi has quit IRC14:53
*** macz_ has joined #openstack-meeting-314:54
slaweq#startmeeting neutron_ci15:00
openstackMeeting started Tue Mar 16 15:00:38 2021 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"15:00
openstackThe meeting name has been set to 'neutron_ci'15:00
slaweqhi15:00
slaweqralonsoh: lajoskatona: are You going to attend ci meeting?15:01
ralonsohhi15:01
lajoskatonaHi, yes, I am here, just left in some half downstream stuff :-)15:02
slaweqgreat15:02
slaweqso lets start15:02
slaweqGrafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate15:02
slaweq#topic Actions from previous meetings15:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"15:02
slaweqralonsoh to try to check how to limit number of logged lines in FT output15:02
ralonsohI'm on it (again)15:03
ralonsohI have two places: the DB and the engine facade15:03
ralonsohwe can remove the n-lib condition about .session and ._session15:03
ralonsohabout the DB... still checking15:03
slaweqby engine facade You mean that "deprecation" warning?15:03
ralonsohI'll push both pachtes15:03
ralonsohyes15:03
slaweqhttps://review.opendev.org/c/openstack/neutron-lib/+/779720\15:04
slaweqit's there already15:04
ralonsohand I did that before you, some months ago15:04
slaweqbut we decided to wait with it after release of wallaby15:04
ralonsohbut it wasn't working fine15:04
slaweqI know, I missed that Your patch15:04
slaweqhttps://review.opendev.org/c/openstack/neutron/+/77972115:04
slaweqI needed also that ^^ patch in neutron15:05
ralonsohok, so for X then15:05
slaweqyes15:06
slaweqbut I think that this db issue logged many times is more problematic there15:07
ralonsohyes and I'm still checking this15:07
slaweqthx15:07
slaweq#action ralonsoh to try to check how to limit number of logged lines in FT output15:07
slaweqjust a reminder for next week :)15:08
slaweqok, next one15:10
slaweqjlibosva to fix collecting ovn logs in functional jobs15:10
slaweqI just pinged him, maybe he will join15:10
*** jlibosva has joined #openstack-meeting-315:11
jlibosvao/15:11
slaweqhi jlibosva15:11
slaweqwe are checking actions from last week15:11
slaweqjlibosva to fix collecting ovn logs in functional jobs15:11
jlibosvayeah, so I found out that functional job doesn't run ovn-controller, we have fake chassis there15:12
jlibosvaas for the LP bug - I still need to investigate, I didn't get to it. My apologies15:12
slaweqok, will You try to check it this week?15:13
jlibosvamaybe early next week, I'll try before the next ci mtg15:13
slaweqok, thx15:13
slaweqjlibosva: just to be sure, it was related to https://bugs.launchpad.net/neutron/+bug/1918266, right?15:14
openstackLaunchpad bug 1918266 in neutron "Functional test test_gateway_chassis_rebalance failing due to "failed to bind logical router"" [High,Confirmed]15:14
jlibosvaslaweq: yes15:14
slaweqok15:14
slaweq#action jlibosva to check LP https://bugs.launchpad.net/neutron/+bug/191826615:14
slaweqjust as a reminder for next meeting :)15:15
slaweqand with that I think we can move on15:15
slaweq#topic Stadium projects15:15
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"15:15
slaweqlajoskatona: anything new regarding ci of stadium?15:15
lajoskatonanothing15:15
lajoskatonaall is quiet15:15
slaweqwhich is good news :)15:15
slaweqthx lajoskatona15:16
slaweq#topic Stable branches15:16
*** openstack changes topic to "Stable branches (Meeting topic: neutron_ci)"15:16
slaweqI didn't had time today to check stable branches ci15:16
slaweqdo You have anything related to them?15:17
ralonsohno15:17
slaweqok, so next topic15:18
slaweq#topic Grafana15:18
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"15:18
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate15:18
*** obondarev has quit IRC15:19
slaweqI don't see anything going very bad there15:20
slaweqstill functional tests are most problematic15:21
ralonsohyes but better than 4 weeks ago15:21
ralonsohwe still have some timeout problems15:21
ralonsohbut fewer15:21
slaweqtrue15:21
ralonsoh(and, I promise, I'm still working on this)15:21
ralonsohbut is quite difficult to reproduce it locally15:22
slaweqthe issue with sql_connection parameter in functional tests?15:22
ralonsohno no15:22
ralonsohthe FT timeouts15:22
slaweqahh, true15:22
ralonsohsql problem is almost trivial15:23
slaweqthat will be hard to reproduce15:23
slaweqIMO You can first fix the issue with sql, and it is very likely that timeouts will be gone15:23
slaweqand speaking about functional tests15:25
slaweq#topic fullstack/functional15:25
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"15:25
slaweqI found couple of failures last week15:25
slaweqfirst one15:25
slaweqtimeout while spawning metadata proxy:15:25
slaweqhttps://b5d154aeef4479021ab9-b7d34d92d3c0fa84052da2d7ba8871be.ssl.cf1.rackcdn.com/777535/1/check/neutron-functional-with-uwsgi/bb88e2f/testr_results.html15:25
slaweq    https://175b7ab9447c4ad3cb55-7660c6eb3fc520d2639a30e0db226704.ssl.cf2.rackcdn.com/765846/7/gate/neutron-functional-with-uwsgi/0099700/testr_results.html15:26
slaweq    https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_334/773283/15/check/neutron-functional-with-uwsgi/334549a/testr_results.html15:26
slaweqat least 3 times15:26
slaweqdid You saw it maybe?15:26
ralonsohno15:26
ralonsohbut I can check it15:26
slaweqthx ralonsoh15:26
slaweqdo You want me to report LP for that?15:26
ralonsohperfect for me15:27
slaweqok15:27
slaweqI will do it just after the meeting15:27
slaweq#action ralonsoh to check timeout while spawning metadata proxy in functional tests15:27
slaweqnext one is timeout while disabling processes:15:27
slaweq    https://cb02acb070cff5b90918-a2819ce1e1d01d4ba47cf0d26d5585a5.ssl.cf5.rackcdn.com/778993/6/gate/neutron-functional-with-uwsgi/ebebe12/testr_results.html15:27
slaweq    https://0ee130e4a5a2946be1c4-63ec39ca44f5300255d15df097f93e08.ssl.cf1.rackcdn.com/780054/2/check/neutron-functional-with-uwsgi/bc96480/testr_results.html15:27
slaweq    https://2593fe2c1676d625fafc-b5f24c1063ad83372f17d0890078a578.ssl.cf5.rackcdn.com/765846/7/check/neutron-functional-with-uwsgi/29b9cdc/testr_results.html15:27
slaweq    https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_b83/763231/16/check/neutron-functional-with-uwsgi/b836250/testr_results.html15:28
slaweqralonsoh: isn't that "second part" of one of the LPs which You were working on?15:28
ralonsohnot really15:28
ralonsohthat was related to the ns creation15:28
slaweqok15:29
*** hemanth_n has joined #openstack-meeting-315:29
slaweqso that is something new15:29
ralonsohbut I've seen this message last week many times15:29
ralonsohwhat I don't understand is how we can timeout killing a process15:29
ralonsohno process will catch this signal15:29
slaweqit is calling privsep15:30
slaweqso maybe it's some issue in privsep or how we call that lib15:30
ralonsohyes and uses "kill -9"15:30
ralonsohI tried some time ago to use os.kill15:30
ralonsohbut it was a disaster15:30
ralonsohok, now we have moved almost everything to privsep, I'll try again this patch15:31
slaweqIMO it is timeing out in privsep while waiting to response15:32
ralonsohshould work the same as cmd "kill" but natively15:32
ralonsohyes15:32
slaweqwould be good to try15:32
slaweqthx15:32
ralonsohperfect then15:32
ralonsohwill you open a LP?15:32
slaweq#action ralonsoh to try to move to os.kill15:32
slaweqyes, I will15:32
ralonsohperfect15:32
slaweqthank You15:32
slaweqnext one15:33
slaweqfailure in neutron.tests.functional.agent.l3.test_dvr_router.TestDvrRouter.test_dvr_ha_router_failover_without_g15:33
slaweq    https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_415/779149/2/check/neutron-functional-with-uwsgi/4158175/testr_results.html15:33
slaweq    https://a1a9878be58cf3e65212-2851babb3178649b1b47ad8e0ca050d1.ssl.cf1.rackcdn.com/780054/2/check/neutron-functional-with-uwsgi/4a7ea78/testr_results.html15:33
slaweqI saw it twice15:33
slaweqin that case it's waiting for router to switch to "backup"15:33
slaweqI can take a look at it15:34
ralonsohthanks15:34
slaweq#slaweq to check failing neutron.tests.functional.agent.l3.test_dvr_router.TestDvrRouter.test_dvr_ha_router_failover_without_gw15:34
slaweqother failures which I found was single failures so I listed them in https://etherpad.opendev.org/p/neutron-ci-meetings but I don't think we need to check each of them now15:35
slaweqlets see if they will happen more often first15:35
*** psachin has quit IRC15:36
slaweqok, I think we can move on15:36
slaweq#topic periodic15:37
*** openstack changes topic to "periodic (Meeting topic: neutron_ci)"15:37
slaweqneutron-lib from master is causing UT failures: https://bugs.launchpad.net/neutron/+bug/191928015:37
openstackLaunchpad bug 1919280 in neutron "UT are failing when runs with neutron-lib master" [Critical,Confirmed] - Assigned to Slawek Kaplonski (slaweq)15:37
slaweqthis is new issue15:37
slaweqand ralonsoh is already on it15:37
ralonsohhttps://review.opendev.org/c/openstack/neutron/+/78080215:37
ralonsohit has a depends-on because neutron-lib 2.10.0 is not in openstack/requirements15:37
ralonsohbut should be the same15:37
ralonsohhttps://zuul.opendev.org/t/openstack/status#78080215:38
slaweqdepends-on will not work here15:38
ralonsohI still need to check some UTs15:38
ralonsohwhy?15:38
slaweqin UT jobs neutron-lib isn't installed from source15:38
slaweqbut from pypi15:38
ralonsohupssss15:38
ralonsohok then15:38
ralonsohnow I understand those 4 UTs failing15:39
ralonsohsame as when I executed py38 locally15:39
slaweqso You need to bump neutron-lib version in requirements repo and in neutron15:39
ralonsohwithout patching n-lib15:39
slaweqand then it will install new version of neutron-lib15:39
ralonsohI'll push the patch for requirements now15:39
slaweqthx15:39
slaweqplease give me link, I will +1 it asap15:40
ralonsohhttps://review.opendev.org/c/openstack/requirements/+/78086015:40
lajoskatonaThe releases patch is merged, and the u-c change is under review: https://review.opendev.org/c/openstack/requirements/+/78086015:40
ralonsohalready there...15:40
slaweqralonsoh: so please update Your patch to bump neutron-lib version in requirements.txt and lower-constraints.txt15:41
ralonsohsure15:41
slaweqand You can make Your patch depend-on https://review.opendev.org/c/openstack/requirements/+/78086015:41
slaweqthen it should works15:41
slaweqthx ralonsoh for taking care of it15:42
slaweqand that was last thing from me for today15:42
slaweqdo You have anything else regarding ci?15:42
ralonsohno15:42
slaweqso I will give You some minutes back :)15:43
slaweqthx for attending the meeting15:43
slaweqo/15:43
slaweq#endmeeting15:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:43
openstackMeeting ended Tue Mar 16 15:43:34 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2021/neutron_ci.2021-03-16-15.00.html15:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2021/neutron_ci.2021-03-16-15.00.txt15:43
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2021/neutron_ci.2021-03-16-15.00.log.html15:43
ralonsohbye15:43
lajoskatonabye15:45
*** hemanth_n has quit IRC15:51
*** Luzi has joined #openstack-meeting-316:21
*** e0ne has joined #openstack-meeting-316:33
*** Luzi_ has joined #openstack-meeting-316:46
*** Luzi has quit IRC16:46
*** lajoskatona has quit IRC17:16
*** e0ne has quit IRC17:20
*** jlibosva has quit IRC17:27
*** lajoskatona has joined #openstack-meeting-317:30
*** Luzi_ has quit IRC17:31
*** eolivare_ has quit IRC17:43
*** lajoskatona has left #openstack-meeting-317:45
*** jlibosva has joined #openstack-meeting-317:50
*** jlibosva has quit IRC17:55
*** lpetrut has quit IRC18:00
*** jlibosva has joined #openstack-meeting-318:26
*** jlibosva has quit IRC18:30
*** ralonsoh has quit IRC18:51
*** jlibosva has joined #openstack-meeting-318:58
*** jlibosva has quit IRC19:05
*** persia has quit IRC19:46
*** persia has joined #openstack-meeting-319:47
*** persia has quit IRC19:52
*** persia has joined #openstack-meeting-319:54
*** persia has quit IRC20:01
*** persia has joined #openstack-meeting-320:02
*** tosky has quit IRC20:05
*** tosky has joined #openstack-meeting-320:05
*** slaweq has quit IRC20:26
*** slaweq has joined #openstack-meeting-320:29
*** jlibosva has joined #openstack-meeting-321:01
*** jlibosva has quit IRC21:06
mlavalle?exit21:13
*** mlavalle has quit IRC21:13
*** slaweq has quit IRC21:24
*** dosaboy_ has joined #openstack-meeting-322:30
*** dosaboy has quit IRC22:35
*** mlavalle has joined #openstack-meeting-322:50
*** jlibosva has joined #openstack-meeting-323:03
*** jlibosva has quit IRC23:07

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!