Tuesday, 2024-06-04

opendevreviewZhouHeng proposed openstack/neutron master: Improve ACL comparison efficiency  https://review.opendev.org/c/openstack/neutron/+/88544900:16
opendevreviewZhouHeng proposed openstack/neutron master: Improve ACL comparison efficiency  https://review.opendev.org/c/openstack/neutron/+/88544900:19
opendevreviewLiushy proposed openstack/neutron-fwaas master: Support l3 stateless firewall based on OVN  https://review.opendev.org/c/openstack/neutron-fwaas/+/84575603:34
opendevreviewMerged openstack/neutron master: Add a default goto table=94 for openvswitch fw  https://review.opendev.org/c/openstack/neutron/+/90738205:36
opendevreviewyatin proposed openstack/neutron master: [DNM] check lp #2067869  https://review.opendev.org/c/openstack/neutron/+/92109106:05
*** elodilles_ooo is now known as elodilles06:32
zigoslaweq: Hi there! We're trying to implement bagpipe, to have 2 local network routed between 2 OpenStack region, and we came across this patch:08:57
zigohttps://review.opendev.org/c/openstack/networking-bagpipe/+/66230508:57
zigoWe're surprised that it's only modifying the tests, but not what the plugin actually does. I know it's been 5 years, but do you remember the details?08:57
sahido/09:23
sahidany chance to make this one happening https://review.opendev.org/c/openstack/neutron/+/907250 :-)09:23
lajoskatonasahid: Hi, on my list09:55
sahidlajoskatona: ++ thanks10:02
opendevreviewLajos Katona proposed openstack/os-ken master: Add periodic weekly job for os-ken  https://review.opendev.org/c/openstack/os-ken/+/91527311:31
opendevreviewLajos Katona proposed openstack/neutron-tempest-plugin master: UM only: change zed to use unmaintained/  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/91769611:38
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-bgp-agent master: Ensure cr-lrp ports are exposed  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/92127911:49
opendevreviewMerged openstack/neutron master: Make openstack-tox-py311-with-sqlalchemy-master non-voting  https://review.opendev.org/c/openstack/neutron/+/92089612:18
opendevreviewSahid Orentino Ferdjaoui proposed openstack/neutron master: ml2/ovs: avoid reconfig bridges/flows when reconnecting to OVS  https://review.opendev.org/c/openstack/neutron/+/92081912:51
opendevreviewMohammed Naser proposed openstack/neutron unmaintained/zed: [ML2/OVN] Add gateway_port support for FIP  https://review.opendev.org/c/openstack/neutron/+/92103513:35
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-bgp-agent master: Ensure cr-lrp ports are exposed  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/92127913:42
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-bgp-agent master: Ensure cr-lrp ports are exposed  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/92127913:43
mnaserdoes anyone know if there has been a change in linters for stable/2023.1 or something?13:46
mnaserhttps://review.opendev.org/c/openstack/neutron/+/921034 is a back port of change (that passed in zed and 2023.2 and master) and yet somehow it was unhappy in 2023.113:46
haleyb#startmeeting networking14:00
opendevmeetMeeting started Tue Jun  4 14:00:41 2024 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'networking'14:00
haleybPing list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki, haleyb, ralonsoh14:00
mlavalle\o14:00
obondarevo/14:00
ihrachyso/14:00
ykarelo/14:00
frickler\o14:01
rubasovo/14:01
bcafarelo/14:01
slaweqo/14:01
haleybgood crowd let's get started14:01
haleyb#topic announcements14:01
haleybWe are now in Dalmatian release week (R - 17)14:02
haleyb#link https://releases.openstack.org/dalmatian/schedule.html14:02
lajoskatonao/14:02
haleybso if there any features that haven't been proposed please get them out soon as we are more than halfway through cycle14:03
haleybReminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers14:04
haleybi might take this Friday off since there are no current topics afaik, will send an email thursday if canceled14:04
haleyblajoskatona: how was Openinfra Day Budapest yesterday?14:05
lajoskatonait was quiet14:06
haleyb:(14:06
lajoskatonaa lot of AI topics14:06
lajoskatonaan digital souverignity (sorryI can't write it ....)14:06
lajoskatonaSovereignty14:07
lajoskatonathose were in the middle of all discussions and presentations14:07
haleybAI does consume all the oxygen in the room compared to cloud and kubernetes these days14:07
bcafarelthat looks in line with Paris day (and same from Berlin from what I heard)14:07
lajoskatonalast week on another conf in Budapest in 2 hours there was a 14:08
lajoskatonapresentation which said that AI regenerate legacy code14:08
lajoskatonaand another that stated that we are dynosaurs and we (developers) will just become extinct :-)14:08
haleyband it fixed all the bugs while doing it?14:09
lajoskatona(it later changed that we have to use AI well and it will help us a lot)14:09
slaweqyeap14:09
lajoskatonayou mean the bugs it created  alone with artifical intellingence? I am abel to create bugs with m human intelligence14:09
haleybwe all are :)14:10
mlavalleI'm very good at that14:10
ihrachysAI is just a compute and network hungry workload *shrugs*14:10
haleybthat it is...14:12
haleybalright, we can bash AI all day, any other announcements?14:12
haleyb#topic bugs14:12
mlavallethnaks for the update lajoskatona :-)14:13
haleyblucas was the deputy last week, but i didn't see a report on the ML14:13
haleybdid anyone have any bugs to talk about? i will look quickly in the meanwhile14:14
haleyb#link https://bugs.launchpad.net/neutron/+bug/206751514:15
haleybneutron-lib: add a job running neutron unit test suite (maybe non-voting)14:15
haleybthis was something ihrachys noticed when a neutron-lib change broke the neutron gate14:16
haleybalthough neutron-lib has this same job, it runs only neutron-lib unit tests14:16
ihrachyswe disabled votes for the job now, so it's not as pressing. still good to have an early warning.14:16
haleybright, but the next step is - is it possible to run the neutron unit tests in the neutron-lib gate? which would have detected the issue14:17
haleybi'm not sure that's possible14:17
haleybihrachys: i actually wanted to talk about making that job non-voting today but realized i never pushed my comment to the patch14:18
ihrachysI'm sure it's possible! perhaps not as easy? I dunno. ykarel is it possible / easy?14:18
haleybthe only thing i worry about non-voting is that noone notices when there's a real bug there14:18
ykarelihrachys, haleyb i think should be possible and not that hard14:19
ykarelconsider similar jobs run in requirements patches14:19
haleyband having the latest sqlalchemy running correctly is a good thing14:19
ihrachyshaleyb let ci folks track if this job starts crashing? they do periodic group watching at charts I think.14:19
ykarela run https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_b27/920454/1/check/cross-neutron-py311/b27fe41/testr_results.html14:19
haleybihrachys: true, we are much better now at noticing14:19
ihrachys(and ideally, we have a non-voting job in neutron-lib and don't even merge anything without first checking how it fares)14:20
ykarel+!14:20
haleybihrachys: yes, that would be ideal, then we could make the neutron job voting again since it shouldn't break14:21
ihrachysykarel I'll be impolite and ask - is it something ci group will take care of?14:21
ihrachys:)14:21
ykarelhaleyb, it can still break as sqlalchemy patches are not gated14:21
ykarelso we can keep it still non-voting14:22
ykarelihrachys, yes sure, i think you already have a bug for that so can be tracked there14:22
haleybykarel: sure, understood14:22
ihrachysykarel ++ I don't think it's a good idea to keep it voting. it's exposed to the world, not isolated with constraints.14:22
ykarel+1 agree14:22
haleybykarel: can you take that bug and propose a neutron-lib patch?14:23
ykarelack will do14:24
ihrachysykarel thank you.14:24
haleybykarel: thanks!14:25
haleybi only noticed one other bug14:26
haleyb#link https://bugs.launchpad.net/neutron/+bug/206787114:26
haleybNo support on using domain name for ovn connection string in ml2_conf.ini14:26
ihrachysthought there was a fix in python-ovs from otherwiseguy for this14:27
haleybsince the help message states tcp:IP:PORT is the format, using a dns name is more of a enhancement14:27
haleybihrachys: oh, i don't know14:27
ihrachysI think this https://github.com/openvswitch/ovs/commit/4d55a364ff60d894dce4e2e97a489d81520dc66314:27
ykareli recall it's in ovs3.114:27
ykarelok so 3.2 as per above commit :)14:27
haleybit's unclear from that commit message it relates to this imho14:28
ihrachysunless it was backported. anyhoo, pretty recent. we needed it to point clients to a round-robin backed by k8s dns.14:29
ykarelapart from the ovs3.1 python3-unbound is required for that to work14:29
haleybbut the link to the ML is clearer14:29
ykarels/ovs3.1/ovs3.214:29
ihrachyshaleyb and yet it is related, 99% sure :)14:29
ihrachysthis was a discrepancy between python-ovs and C behavior (the latter was resolving before)14:30
haleybihrachys: ack, so it seems if we bump the requirement, change the help text and add a test we should be good14:31
haleybi can add that info to the bug14:32
ihrachysmeh. I don't think we promised anywhere it will work?..14:32
ihrachyswe can definitely mention somewhere that DNS may work, depending on your OVS version.14:32
haleyboh, this is in ovs not ovsdbapp14:33
haleybdoh14:33
ihrachysyep14:33
lajoskatonaPerhaps 2 bugs for os-ken: https://bugs.launchpad.net/neutron/+bug/2067970 & https://bugs.launchpad.net/neutron/+bug/206797314:34
lajoskatonaboth marked as vulnerability and as I see both come from a non-Neutron  usecase which we don't test in Openstack CI most probably14:35
haleybthat second one is private so maybe not visible14:35
ihrachysboth are 404 for me14:35
ihrachysso probably not a good idea to discuss it here :)14:36
lajoskatonaahh, ok14:36
lajoskatonajust a general thing to think about then: if it is not Openstack usecase how to handle this? do we want to take responsibility to the code part of os-ken that is not used by Openstack 14:37
lajoskatonajust inherited from ryu?14:37
ihrachys(not idea what we are talking about but) if it's not used, just yank it.14:37
ihrachysthat we carry dead code is a problem in itself imo14:38
lajoskatonaIt can be a topic of some of the coming meetings, driver or later the PTG perhaps to collect all these14:39
haleyblajoskatona: maybe propose that in the bug14:39
haleybto remove the unused (broken) code14:40
lajoskatonahaleyb: ack, I check them and add comment to them14:40
haleyb+114:40
haleyband just an update on the cover job bug14:41
haleyb#link https://bugs.launchpad.net/neutron/+bug/206582114:41
haleybwe landed a workaround that helps, using --concurrency 414:41
haleybi've tried different versions of the coverage tool and memory consumption seems similar14:41
haleybso i guess we've always been on the edge of failure14:42
haleybi'm still running tests and will update the bug and ML with more info14:42
haleybthe side-effect was learning about sql 'selectin' queries14:43
haleybi filed a bug for that and have two patches in-flight14:43
haleyb#link https://launchpad.net/bugs/206777014:43
ihrachysI saw them bloody red. is it an intrinsic problem with the switch or just some oversights when pushing? is there a lot more work there?14:43
haleybihrachys: the neutron-lib patch needs to land first, https://review.opendev.org/c/openstack/neutron-lib/+/92093614:44
haleybwith that applied locally things are fine14:44
ihrachysah. we need that non-voting job to run neutron tests :)14:44
haleybenv TOX_ENV_SRC_MODULES=../neutron-lib tox -e py3 -- neutron.tests.unit.db14:44
haleyb^^ that will use a local neutron-lib change14:45
ihrachysis there a way to run full neutron check pipeline against a neutron-lib patch?14:45
ykareldepends-on will do that14:45
haleybihrachys: no since it's a library, unless something has changed14:45
ihrachysykarel doesn't it still use neutron-lib released version?14:45
ykarelit should use neutron-lib from git atleast in devstack jobs14:46
slaweqwe have in experimental/periodic queue job which uses neutron-lib from master14:46
ykarelfor orther too it should work but can cross check14:46
slaweqfor that job depends-on should works14:46
ihrachysthat's news to me. you are saying it pulls master neutron-lib in devstack?14:46
ykarelyeap if there is depends-on14:46
haleyband the sqlalchemy job does too, but the patch has to have landed14:46
ihrachysI mean, SOME jobs like that sqlalchemy definitely check out from git and for them depends-on will work. for the rest - I dunno, I had different perception but I'd rely on ykarel who knows 100x more than me.14:47
slaweqykarel that's also new for me - IIRC in the past depends on wasn't working as neutron-lib was always installed from package14:47
ykarelhttps://github.com/openstack/devstack/blob/92d70a854322be9cb22f574618d7663be9a4e649/lib/neutron#L53114:47
ykarelso need to check if there is required-projects contain neutron-lib, if it does then only will work14:48
haleybykarel: right, but that assumes the neutron-lib patch has merged, correct?14:48
ihrachysnot necessarily. I think depends-on will prepare git clones in the env to include the patch depended-upon. then devstack will checkout from these "cooked" repos.14:49
ykareldepends-on with unmerged patches should also test that14:49
ihrachysok. I guess we can post a depends-on DNM patch and confirm in logs, should be easier than continuing arguing :p14:49
ykarelbut the requirement is it should be in required-projects list, now thinking more i don't think we have that as we want to test with u-c14:49
ykarelso what slaweq said if experimental jobs have that set, those could be used for such tests14:50
haleybykarel: so i should be able to add a depends-on to my neutron patch? you can explain later14:50
ykarel+114:50
ihrachysright. well, having SOME jobs tested against the patch is better than nothing.14:50
ykarelyes for test atleast we can hack it14:51
haleybbut please take a look at the patches, i think the neutron-lib is easy enough - https://review.opendev.org/q/topic:%22orm-selectin%2214:51
lajoskatona+1, thanks14:52
ihrachysthat's one of those cases where a single line change affects every single code path. reviewing the diff is 1% of validation.14:52
haleybjlibosva is deputy this week, can someone at RH ping him since i don't see him in channel14:52
ihrachyshe's busy with an escalation but I will ping, sec.14:52
haleybsure, just so he knows14:53
haleybanyone have other bugs to discuss?14:53
haleyb#topic on-demand14:54
haleybopen floor for any other topics14:54
ihrachysI want this in https://review.opendev.org/c/openstack/neutron-lib/+/917855 and then cut neutron-lib that is netaddr1 compliant14:55
ihrachys(this is the last bit for this)14:55
fricklerregarding the n-d-r spec you discussed on friday, I would prefer to just maintain n-d-r in the state it currently is, no new features added14:55
haleybihrachys: will take a look14:55
fricklerat least I don't have review capacity for anything more14:56
haleybfrickler: was that https://bugs.launchpad.net/neutron/+bug/2064120 ?14:56
frickleryes14:57
ihrachysfrickler there's another spec related to bgp where I was pushing for reusing the API for n-d-r. Wonder if this project is on life support, what Neutron project as a whole should do with it. APIs are still part of api-ref, so neutron as a whole care.14:57
fricklerihrachys: which spec are you referring to?14:58
ihrachyshttps://review.opendev.org/c/openstack/neutron-specs/+/92068114:58
frickleralso I don't mind if other neutron cores review n-d-r patches, it is just that I myself mostly won't other than real bug fixes14:59
ihrachysbut may mix n-d-r and bgpvpn; I'm a bit shaky on who's who.14:59
haleyband ovn-agent14:59
fricklerah, hadn't seens that one yet, will take a look later15:00
haleybor whatever it's called :)15:00
ihrachyshaleyb those pesky ovn engineers.15:00
haleybwe are at top of hour, thanks for attending and good discussions, let's go fix those bugs15:00
haleyband ci meeting is irc right now15:00
haleyb#endmeeting15:01
opendevmeetMeeting ended Tue Jun  4 15:01:10 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2024/networking.2024-06-04-14.00.html15:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2024/networking.2024-06-04-14.00.txt15:01
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2024/networking.2024-06-04-14.00.log.html15:01
lajoskatonao/15:01
opendevreviewMiguel Lavalle proposed openstack/neutron master: Fix trunk test_subport_delete functional test  https://review.opendev.org/c/openstack/neutron/+/92129615:01
slaweqo/15:01
ihrachysfrickler capacity concerns are totally understood. that's something for neutron team to clarify - if there's no cap to help the project stay alive, then api deprecation decisions or reprioritization may have to happen.15:01
ykarel#startmeeting neutron_ci15:01
opendevmeetMeeting started Tue Jun  4 15:01:31 2024 UTC and is due to finish in 60 minutes.  The chair is ykarel. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'neutron_ci'15:01
ykarelPing list: bcafarel, lajoskatona, mlavalle, mtomaska, ralonsoh, ykarel, jlibosva, elvira15:01
mlavalleo/15:01
haleybo/15:01
mlavalleonly irc today, right?15:02
bcafarelo/15:02
ykarelyeap15:03
lajoskatonao/15:04
ykarelhello everyone, let's start with topics from previous week15:04
ykarel#topic Actions from previous meetings15:04
ykarellajoskatona to look at failures at sfc and bagpipe15:05
lajoskatonaI checked but to tell the truth I have to check again since I forgot totally what I have done with it :-(15:06
ykarellajoskatona reported https://bugs.launchpad.net/neutron/+bug/2067452 for bagpipe15:06
ykarelatleast i recall ^ :)15:06
lajoskatonaykarel: you saved me15:06
ykarelthese are still failing but can discuss in next section15:07
lajoskatonaI reported an issue for exabgp, and they promised that it will be fixed in next exabp release15:07
ykarelthx much15:07
ykarelnext one on me15:07
ykarelykarel to report lp for volume tests15:07
ykareli reported https://bugs.launchpad.net/openstacksdk/+bug/2067869, cinder team looking at that15:07
ykarel#topic Stable branches15:08
ykarelbcafarel, any update15:08
bcafarelmostly good on the backports that went in15:08
bcafarelhaleyb: semi-related I found https://review.opendev.org/c/openstack/neutron/+/919516 2023.2 which was cherry-picked from (now merged) 2023.1 probably good to push15:09
haleybbcafarel: i'll remove my -W think that looks ok15:10
haleybbut there is no grenade job15:10
haleybthat's where the error was obvious15:10
ykarelthx bcafarel for the update15:11
ykarel#topic Stadium projects15:11
slaweqwhy there is no grenade job at all there?15:11
slaweqis that 'normal'?15:11
lajoskatonaperhaps it is not executed on non-slurp? 2023.2 was non/slurp am I right?15:12
slaweqbut 'regular' grenade jobs should still be run there15:12
lajoskatonathat is true15:13
slaweqslurp means we support and test upgrade from the N-2 release15:13
slaweqbut non-slurp still can be upgraded from N-115:13
ykarelseems we just missing ovn grenade from check/gate15:13
ykarel+1 to what slaweq said15:13
slaweqykarel you can assign this as AI for me - I will check why this job is not run there15:14
haleybgrenade is usually only in check queue15:14
slaweqand will propose fix if needed15:14
ykarel#action slaweq to include ovn grenade jobs in check queue15:14
haleybfor 2023.215:14
slaweqthx15:14
ykarelneutron-ovn-grenade-multinode15:15
ykarelgetting back to stadium15:15
ykarelsfc/bagpipe failures15:16
ykarelhttps://zuul.openstack.org/builds?job_name=openstack-tox-py312&project=openstack/networking-bagpipe15:16
ykarelfor bagpipe we already have https://bugs.launchpad.net/neutron/+bug/206745215:16
ykarelhttps://zuul.openstack.org/builds?job_name=networking-sfc-tempest&project=openstack%2Fnetworking-sfc&branch=master&skip=015:16
ykarellajoskatona, can you also check sfc failures15:16
lajoskatonasure, I will15:16
ykarel#action lajoskatona to check sfc failures15:17
ykarel#topic Rechecks15:17
ykarelthere were comparatively more rechecks/bare rechecks last week due to various known issues15:18
ykarelsqlalchemy-master, cover jobs, etc15:19
ykarel#topic Unit tests15:19
ykarelopenstack-tox-py311-with-sqlalchemy-master got broken with neutron-lib changes15:19
ykarelAlready Fixed with https://review.opendev.org/c/openstack/neutron/+/92089715:19
ykarelAsk for adding non-voting job in neutron-lib https://bugs.launchpad.net/neutron/+bug/206751515:19
ykareli will push that change15:19
ykarel#action ykarel to include neutron unit-test job in neutron-lib to catch such issues15:20
ykarelFor cover job we already have workaround applied, lajoskatona looking for actual fixes15:20
ykarel#topic fullstack/functional15:21
lajoskatonathat is haleyb, or am I?15:21
haleybthat's still me15:21
lajoskatona:-)15:21
lajoskatonajust to be sure :-)15:21
ykarelsorry it's haleyb :)15:22
haleybhow easy is it to use a different machine type for a job?15:22
haleybor node type or whatever it's called15:22
haleybi.e. moar memory15:23
haleybi'll have to look15:23
lajoskatonawith the label you can select, like: label: nested-virt-ubuntu-focal as I recall15:23
ykarelci nodes are mostly 8 gb nodes15:23
ykarelthere are some providers provides higher config nodes for specific use cases15:24
haleybykarel: ack, 8gb is sometimes not enough, i'll look for other options15:24
ykarelfor some cases we enable swap if 8gb is not enough15:25
lajoskatonaask on infra channel if that is possible15:25
haleybykarel: ah, the change you propsed15:25
ykarelif it need real ram then need to look for labels with high configuration15:25
haleybi was even thinking of splitting the testing up, as long as it's combined in the end15:26
ykarelif you looking for that cover job, using some swap should be enough as seen in that test patch15:27
haleybykarel: ack, i'll look closer at your patch might be the easiest option15:27
ykarelack15:27
ykarel#topic fullstack/functional15:28
ykarel- https://4329afd232bc8c0f7e08-a692672d2d4a5288ede7d6f3bc2193fe.ssl.cf5.rackcdn.com/periodic/opendev.org/openstack/neutron/master/neutron-functional-with-sqlalchemy-master/5e7fbe9/testr_results.html15:28
ykarel- https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_c48/periodic/opendev.org/openstack/neutron/master/neutron-fullstack-with-uwsgi-fips/c48922c/testr_results.html15:28
ykarelseen those once, need to dig further15:29
ykarelany volunteer to check those?15:29
mlavalleI'll check one15:29
mlavallewhichever15:29
ykarelk thx, i can check other than15:30
ykarel#action mlavalle to check failures in neutron-functional15:30
ykarel#action ykarel to check failures in neutron-fullstack15:30
mlavallebtw, proposed fix for another failure: https://review.opendev.org/c/openstack/neutron/+/92129615:30
ykarelthx mlavalle 15:31
mlavalleI'll address ihrachys comment and will be good to go15:31
ykarelthx15:31
ykarel#topic Periodic15:31
ykarelcentos stream 8 jobs needs to be dropped from unmaintained/yoga as failing since 8-stream EOL https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-and-centos-linux-7/15:31
ykarel   - https://zuul.openstack.org/build/fe688f48eefd4c55b38456f1c479b56a15:31
ykarel   - https://zuul.openstack.org/build/d060a6a68352463ea8df596cc954172c15:31
ykarelso the jobs needs to be dropped from unmaintained/yoga15:32
ykarelany volunteer to push that patch?15:32
ykareli can push it then15:33
ykarel#action ykarel to push patch to drop centos 8-stream jobs15:34
ykarel#topic Grafana15:34
ykarelhttps://grafana.opendev.org/d/f913631585/neutron-failure-rate15:34
ykarellet's have quick look at grafana too15:34
ykarelthere some spike in gate queue, and those are known issue with nova15:35
ykarelin check some are known issues, and others looks patch specific15:36
ykarelanything to add?15:36
mlavallenot from me15:37
lajoskatonanothing from me15:37
ykarelack15:38
ykarel#topic On Demand15:38
ykarelanything else you would like to raise here?15:38
mlavallenothing from me15:39
bcafarelall good15:39
ykarelthx everyone for joining, in that case let's close and have everyone 20 minutes back15:40
ykarel#endmeeting15:40
opendevmeetMeeting ended Tue Jun  4 15:40:38 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:40
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_ci/2024/neutron_ci.2024-06-04-15.01.html15:40
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_ci/2024/neutron_ci.2024-06-04-15.01.txt15:40
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_ci/2024/neutron_ci.2024-06-04-15.01.log.html15:40
lajoskatonaBye15:40
slaweqbye15:41
opendevreviewGaudenz Steinlin proposed openstack/neutron master: Use transient systemd units in Process fixture  https://review.opendev.org/c/openstack/neutron/+/91983415:43
opendevreviewGaudenz Steinlin proposed openstack/neutron master: Add L3 HA fullstack failover tests  https://review.opendev.org/c/openstack/neutron/+/91742915:43
opendevreviewGaudenz Steinlin proposed openstack/neutron master: Add conntrackd support to HA routers in L3 agent  https://review.opendev.org/c/openstack/neutron/+/91743015:43
mnaserhttps://review.opendev.org/c/openstack/neutron/+/921034 -- does anyone know why a back ported change would just blow up randomly and be fine in zed and 2023.2 but not 2023.1 ?15:46
mnaserI wanna avoid the recheck hammer15:46
ihrachyshaleyb question: let's say a new stable release of n-lib is cut; and let's say there's a neutron patch that someone wants to backport to this stable branch; but the patch would require the newly cut release, and it would not work without it. is it allowed to bump minimal version in reqs.txt in stable branches?15:58
mnaseris the neutron gate broken?16:06
mnaserhttps://review.opendev.org/c/openstack/neutron/+/91469716:06
mnaserthis change only ran docs and pep816:07
mnaseroh its happening to many `master` changes16:07
ihrachyshaleyb ^^16:08
* haleyb is in downstream meetings at the moment, but wonders if maybe the zuul negate patch broke something?16:09
haleybhttps://review.opendev.org/c/openstack/neutron/+/92097716:09
haleybnot sure what else would cause such issues16:09
mnaserhttps://review.opendev.org/c/openstack/neutron/+/907382 this for example even landed without testing16:10
mnaserlet me see16:10
mnaserits gotta be that imho16:10
haleybsigh16:11
ihrachysbut the RE2 patch gate run all jobs16:13
haleybit did. the test patch never got far enough to run any tests from waht i can tell16:14
* haleyb looks for other negate:true instances16:17
opendevreviewIhar Hrachyshka proposed openstack/neutron master: Revert "Use RE2 compatible regex for irrelevant-files"  https://review.opendev.org/c/openstack/neutron/+/92130616:17
ihrachysposted for in case we want to land it, so that it collects logs16:17
ihrachysruns jobs here https://zuul.opendev.org/t/openstack/status#92130616:18
haleybi think they're all missing a trailing $ perhaps?16:19
ihrachysthere was also one for tempest plugin https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/92097916:19
opendevreviewIhar Hrachyshka proposed openstack/neutron-tempest-plugin master: Revert "Use RE2 compatible regex for irrelevant-files"  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/92130716:20
ihrachyshaleyb I have to leave for today. I will check later if $ patch is up and review. you can ping with link here and I will eventually check it.16:21
haleybihrachys: ack, thanks, let me throw up a patch and see16:22
ihrachysbtw checked and I don't think we have any in-flight Workflow+1 patches for neutron so we won't land anything on top without testing, at least (assuming everyone is aware of this happening)16:24
haleybi will keep an eye16:24
mnasersome landed without that but they went through gate so I guess its ok™16:25
ihrachyslol. let's hope. worst case we'll have to include their reverts into RE2 revert (or a fix for $)16:25
haleybthe OVS one did, which had passed previously at least16:25
* haleyb is just doing the commit message now in his change16:25
opendevreviewBrian Haley proposed openstack/neutron master: Add missing '$' to regex lines zuul.d/*  https://review.opendev.org/c/openstack/neutron/+/92130916:26
haleybit that seems to work i'll propose a n-t-p one16:26
haleybmnaser: and i don't know why the 2023.1 gate is being more picky regarding pep816:28
ihrachysit's running check jobs as it should. does this affect check, right?16:28
haleybihrachys: it should affect both, i'll create a test job too16:29
opendevreviewBrian Haley proposed openstack/neutron master: DNM: test regex fix  https://review.opendev.org/c/openstack/neutron/+/92131016:30
ihrachysnope, the DNM runs just docs and pep16:32
haleybit shouldn't need a depends-on, but i'll try one16:32
* haleyb shakes fist at the gate16:32
opendevreviewBrian Haley proposed openstack/neutron master: DNM: test regex fix  https://review.opendev.org/c/openstack/neutron/+/92131016:33
opendevreviewIhar Hrachyshka proposed openstack/neutron master: DNM: test revert for RE2  https://review.opendev.org/c/openstack/neutron/+/92131116:33
haleybthat looks better at least16:34
opendevreviewIhar Hrachyshka proposed openstack/neutron master: DNM: test revert for RE2  https://review.opendev.org/c/openstack/neutron/+/92131116:35
ihrachyshaleyb so I think revert runs all jobs; and yours doesn't still16:37
ihrachysmine DNM for revert: https://zuul.opendev.org/t/openstack/status#92131116:37
ihrachysyour DNM for fix: https://zuul.opendev.org/t/openstack/status#92131016:37
ihrachyshaleyb I'd suggest to land revert now and think about a proper fix later when yatin can join too. ok now I really have to leave. see you.16:38
haleybyup. so what does (?!(project)) mean in regex context? did we just get the syntax wrong?16:38
haleybihrachys: right, gate fixed is priority16:38
haleybhttps://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions/Cheatsheet has an explanation16:43
haleybx(?!y) Matches "x" only if "x" is not followed by "y"16:44
haleybso zuul.d not followed by project.yaml ?16:45
opendevreviewBrian Haley proposed openstack/neutron master: Add missing '$' to regex lines zuul.d/*  https://review.opendev.org/c/openstack/neutron/+/92130916:54
opendevreviewBrian Haley proposed openstack/neutron master: DNM: test regex fix  https://review.opendev.org/c/openstack/neutron/+/92131016:54
opendevreviewBrian Haley proposed openstack/neutron master: Add missing '$' to regex lines zuul.d/*  https://review.opendev.org/c/openstack/neutron/+/92130917:06
opendevreviewBrian Haley proposed openstack/neutron master: DNM: test regex fix  https://review.opendev.org/c/openstack/neutron/+/92131017:07
ihrachyshaleyb the reverts got +1 from zuul. we need another vote?17:43
haleybihrachys: the neutron one is still running, right?17:45
ihrachysnevermind, it's arm17:45
ihrachyshaleyb so what does negate in irrelevant files mean? "ignore everything that doesn't match the filter?"17:49
ihrachysif so, perhaps we made it so that only changes to zuuk.d/project.yaml ran the jobs? we can post a patch touching the file and see if it triggers more jobs. sec.17:49
opendevreviewIhar Hrachyshka proposed openstack/neutron master: DNM testing if touching project.yaml runs all jobs  https://review.opendev.org/c/openstack/neutron/+/92131517:51
haleybright, i'm thinking it was saying 'everything in zuul.d except for this one file' ?17:51
ihrachyshaleyb so I touched the file and see that this runs all jobs17:52
ihrachysbut the meaning of the filter before the change was "any file that is in zuul.d that is not project.yaml is irrelevant"17:52
ihrachyswhich is different meaning.17:53
ihrachysso negate is not the right way to go about it, I think; it's not a matter of a regex fix17:54
haleybihrachys: i think my later change was closer to that meaning, but the DNM didn't run much17:55
ihrachyswhich of? ETOOMANYDNMs17:56
haleybhttps://review.opendev.org/c/openstack/neutron/+/921309 - i added the entire directory, then negated one file17:56
haleybi based that on what i saw ironic do17:57
haleybbut RE is like my kryptonite17:57
ihrachyshm. but I think these filters are ORed. so you have "anything in zuul.d is irrelevant OR anything that is not zuul.d/project.yaml is irrelevant"17:58
haleybi assumed this was correct, https://opendev.org/openstack/ironic/commit/df6342d1ab2dfaeff84733896ecee40c1b1225e417:59
haleybbut yes, these are ORed together17:59
ihrachyswelll... no bandit job e.g. here: https://review.opendev.org/c/openstack/ironic/+/92129418:01
ihrachysso maybe they also broke it; but their use of these regexes was not as prominent.18:01
haleybwe can always be smart, step back and say "what do we want to call irrelevant in zuul.d?"18:02
haleyb:)18:02
haleyb^zuul.d/(?!(project)).*\.yaml - i worry this doesn't mean what i think it means18:03
ihrachyslast time bandit job ran for ironic was May 22: https://zuul.opendev.org/t/openstack/builds?job_name=ironic-tox-bandit&project=openstack/ironic18:03
ihrachysbelieve it or not, RE patch landed May 2318:03
ihrachyshaleyb you mean, list all files as positive matches instead?18:04
haleybTheJulia: ^^ curious regarding RE2 ironic patch imo18:04
ihrachyshaleyb this means: anything in zuul.d that is not project.yaml. which is a more narrow filter than 'anything in the tree that is not zuul.d/project.yaml'18:05
haleybihrachys: no, just that my understanding of the RE syntax is wrong18:05
TheJuliahuh what?18:05
ihrachysTheJulia I think you disabled bandit job unintentionally with https://review.opendev.org/c/openstack/ironic/+/92027618:05
haleybTheJulia: neutron was able to disable part of our gate, so i went looking for other RE2 changes, just noticed the ironic one18:06
TheJuliayup, sure looks like it18:06
ihrachyshaleyb "part" really does some heavy lifting lol18:06
haleybihrachys: ok s/part/most18:07
haleybihrachys: it's almost like the filter should just be ^zuul.d/project\.yaml with no negate18:08
ihrachyshaleyb well no. the idea is to not trigger jobs defined in project.yaml for changes in other yamls; (and vice versa)18:10
TheJuliahaleyb: thanks for spotting that18:10
haleybTheJulia: you might want to look at other ironic* repos too18:10
haleyband i spotted by copying and failing18:10
TheJuliaI just pinged the person who pushed the changes18:10
ihrachysTheJulia wonder if other projects could be affected in a similar way. I suspect there may have been a lot of copying across repo boundaries. :)18:11
TheJuliayeah, quite possible18:11
ihrachyshaleyb I am not even sure RE2 would support it. see e.g. here: https://groups.google.com/g/re2-dev/c/SPgvHH3TULs some suggests that RE2 is not a good place to support this.18:17
ihrachyshttps://github.com/google/re2/issues/15618:18
ihrachys"As a matter of principle, RE2 does not support constructs for which only backtracking solutions are known to exist. Thus, backreferences and look-around assertions are not supported." and then closed18:18
ihrachys*shrugs*18:18
haleybyeah, this is considered a negative look-ahead18:19
haleybihrachys: so if i put this expression, ^zuul\.d/(?!(project)).*\.yaml into regex101.com along with some test filenames, it doesn't match zuul.d/project.yaml but does match other files with zuul.d prefix18:28
opendevreviewBrian Haley proposed openstack/neutron master: Fix regex lines zuul.d/* files  https://review.opendev.org/c/openstack/neutron/+/92130918:38
opendevreviewBrian Haley proposed openstack/neutron master: DNM: test regex fix  https://review.opendev.org/c/openstack/neutron/+/92131018:39
opendevreviewBrian Haley proposed openstack/neutron master: Fix regex lines in zuul.d/* files  https://review.opendev.org/c/openstack/neutron/+/92130919:04
opendevreviewBrian Haley proposed openstack/neutron master: DNM: test regex fix  https://review.opendev.org/c/openstack/neutron/+/92131019:05
*** jlibosva is now known as Guest861519:20
opendevreviewBrian Haley proposed openstack/neutron-tempest-plugin master: Fix regex lines in zuul.d/* files  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/92133019:31
haleybmlavalle: you around?19:50
haleybif so there are two reverts we need to land, https://review.opendev.org/q/topic:%22files-negate%2219:51
opendevreviewBrian Haley proposed openstack/neutron-tempest-plugin master: DNM: test regex fix  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/92133420:03
opendevreviewMerged openstack/neutron-tempest-plugin master: Fix regex lines in zuul.d/* files  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/92133023:22

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