Wednesday, 2020-05-06

*** jamesmcarthur has joined #openstack-meeting-300:37
*** jamesmcarthur has quit IRC01:17
*** jamesmcarthur has joined #openstack-meeting-302:33
*** baojg has joined #openstack-meeting-303:03
*** jamesmcarthur has quit IRC03:06
*** jamesmcarthur has joined #openstack-meeting-303:06
*** jamesmcarthur has quit IRC03:11
*** baojg has quit IRC03:18
*** dconde has joined #openstack-meeting-303:21
*** dconde has quit IRC03:21
*** dconde_ has joined #openstack-meeting-303:23
*** dconde has joined #openstack-meeting-303:27
*** dconde has left #openstack-meeting-303:27
*** dconde_ has quit IRC03:28
*** psachin has joined #openstack-meeting-303:36
*** jamesmcarthur has joined #openstack-meeting-303:41
*** openstack has joined #openstack-meeting-304:22
*** ChanServ sets mode: +o openstack04:23
*** jamesmcarthur has quit IRC05:04
*** jamesmcarthur has joined #openstack-meeting-305:05
*** jamesmcarthur has quit IRC05:11
*** jamesmcarthur has joined #openstack-meeting-305:11
*** diablo_rojo has quit IRC05:57
*** jamesmcarthur has quit IRC06:00
*** jamesmcarthur has joined #openstack-meeting-306:01
*** jamesmcarthur has quit IRC06:06
*** yamamoto has joined #openstack-meeting-306:18
*** yamamoto has quit IRC06:24
*** rubasov has quit IRC06:39
*** rubasov has joined #openstack-meeting-306:39
*** jamesmcarthur has joined #openstack-meeting-306:39
*** ralonsoh has joined #openstack-meeting-306:45
*** maciejjozefczyk has joined #openstack-meeting-306:52
*** belmoreira has joined #openstack-meeting-306:53
*** slaweq has joined #openstack-meeting-306:56
*** lpetrut has joined #openstack-meeting-307:19
*** witek has joined #openstack-meeting-307:25
*** openstack has joined #openstack-meeting-307:49
*** ChanServ sets mode: +o openstack07:49
*** mdelavergne has joined #openstack-meeting-308:00
ttxo/08:01
mdelavergneHi!08:01
ttx#startmeeting large_scale_sig08:01
openstackMeeting started Wed May  6 08:01:22 2020 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: large_scale_sig)"08:01
ttx#topic Rollcall08:01
openstackThe meeting name has been set to 'large_scale_sig'08:01
*** openstack changes topic to "Rollcall (Meeting topic: large_scale_sig)"08:01
ttxWho is here for the Large Scale SIG meeting ?08:01
ttxamorin, belmoreira maybe08:02
*** masahito has joined #openstack-meeting-308:02
belmoreirao/08:02
masahitoo/08:02
mdelavergneand me, hi everyone08:02
ttxmdelavergne: hi!08:02
ttxOur agenda for today is at:08:02
masahitoI completely forgot the time change at last meeting :-008:03
ttx#link https://etherpad.openstack.org/p/large-scale-sig-meeting08:03
ttxmasahito: it should not change anymore :)08:03
ttx#topic Progress on "Documenting large scale operations" goal08:03
*** openstack changes topic to "Progress on "Documenting large scale operations" goal (Meeting topic: large_scale_sig)"08:03
ttx#link https://etherpad.openstack.org/p/large-scale-sig-documentation08:03
ttxWe had one TODO left for amorin from last meeting (propose patch against Nova doc)08:04
ttxI don't think there was progress on that yet ?08:04
ttxamorin: what's blocking further progress on that goal? Is it more base information (like more scaling stories with config details), or more people to help with pushing the patches and writing the doc?08:06
ttx(trying to see what we should look for)08:06
ttxOK let's pass since amorin is not around, and discuss that next meeting08:08
ttxI'll push back the action item08:09
ttx#action amorin to propose patch against Nova doc08:09
ttx#topic Progress on "Scaling within one cluster" goal08:09
*** openstack changes topic to "Progress on "Scaling within one cluster" goal (Meeting topic: large_scale_sig)"08:09
ttx#link https://etherpad.openstack.org/p/large-scale-sig-cluster-scaling08:09
ttxmasahito: progress on oslo.metrics POC code release ?08:09
masahitoalmost ready.08:09
ttxGreat!08:09
ttxI'll push back the item08:10
masahitoI'm wondering where I will push the oslo.metrics side code.08:10
masahitoIs there any play ground repo about this activity?08:10
ttxSo you can push it on github, and we can create the Opendev repository from it08:10
ttxIt's usually the simplest08:10
ttxI could also create an empty repository and you would propose a single change08:11
ttxwhat would be your preference?08:11
masahitoOkay, my preference is empty repo under openstack namespace because there is a co-auther in the oslo.metrics. It's easy to add his name in the patch :-)08:13
ttxok, I can work to create that empty repo08:13
masahitoThank you, so much.08:13
ttxI'll have that ready by next meeting, or before if you think that will be ready before then08:13
ttxwill keep you posted08:14
masahitodepending on the date of next meeting :)08:14
ttx#action ttx to create an empty oslo-metrics repository08:14
masahitoI will be able to push the code in next two week.08:14
ttx#action masahito to finalize oslo.metric POC code release08:14
ttxOK, then I'll just let you know when the repository is ready08:15
ttxI talked to oneswig about his bare metal cluster scaling story08:15
ttxThat project has been delayed, he will come back to us once he made progress.08:15
ttxIn the mean time we'll stop tracking it in the meeting08:15
ttxAnything else on this topic?08:15
mdelavergnenot from me08:15
ttxOK, let's move to the virtual events...08:16
ttx#topic Opendev event on Large scale operations, June 29 - July 108:16
*** openstack changes topic to "Opendev event on Large scale operations, June 29 - July 1 (Meeting topic: large_scale_sig)"08:16
ttx#link https://etherpad.openstack.org/p/LargeScaleOps_OpenDev08:16
ttxbelmoreira, masahito: Did you finalize the list of topics that will be discussed?08:16
ttxthe etherpad has a bunch of suggestions08:16
belmoreirayes, we have a schedule. I think Allison will send the schedule today to the ML08:16
ttxHow do you think we can best leverage that event to recruit new members for the SIG?08:17
ttxI was thinking... maybe we should organize followup discussions at each of the SIG meetings after the event, or something08:17
ttxMake the SIG the natural place to "continue the discussion"08:18
belmoreiraI agree08:18
belmoreiraDuring the event the SIG should also be mentioned08:19
belmoreiraI think this will come naturally08:19
ttxSo... during the event, it would be great to identify people that are the most engaged and potentially willing to help, and get them to leave their email addresses so that we can invite them to the followup discussions08:19
ttxI suspect some topics will be more... conducive to followup discussions than others08:20
ttxso maybe we won;t need to follow up on every opendev topic08:20
ttxwill be good to identify the hottest topics that we should follow up on08:20
belmoreiraI will see the engagement in each topic and we should focus in the popular ones08:21
belmoreirayou write faster than me :)08:21
ttxwe still have time to organize, it's two months from now08:21
ttxanything else on opendev?08:22
ttx#topic PTG participation08:22
*** openstack changes topic to "PTG participation (Meeting topic: large_scale_sig)"08:22
ttxA bit more urgent...08:22
ttxWe have a virtual Project Teams Gathering coming up, to get teams to spend some (virtual) time together to plan future work and get things done08:22
ttxAs a SIG we could sign up for some meeting slots if we think that would be useful08:23
ttxThe deadline is end of this week08:23
mdelavergneSo quite urgent :D08:23
ttxI'm not sure we need more meetings at this point, at least not before teh Opendev08:23
ttxthe*08:23
ttxwhat's your take on it?08:24
ttxWould we benefit from a couple of hours in a videomeeting?08:24
ttx(June 1-5)08:24
*** felixhuettner has joined #openstack-meeting-308:26
ttxbelmoreira, masahito, mdelavergne: thoughts?08:26
mdelavergneFrom my part I don't know if I will be able to participate in the upcoming events, so I prefer not to give my opinion on this08:26
ttxok08:27
belmoreiraI don't have a strong opinion, but I think it will be difficult to keep people engaged in more video calls08:27
ttxI think we should focus on Opendev, personally08:27
masahitoSame for me.08:27
ttxIt will be hard enough :)08:27
ttxand has much more potential for growing the group08:27
ttx#info Large Scale SIG does not need PTG space, will focus on Opendev08:28
ttx#topic Next meeting08:28
*** openstack changes topic to "Next meeting (Meeting topic: large_scale_sig)"08:28
ttxTwo weeks from now places us on...08:28
ttx#info next meeting: May 20, 8:00UTC08:28
ttxI think that is all for today!08:28
ttxLast words, anyone?08:29
ttxAlright then, have a great week! Thanks for attending!08:29
mdelavergnethanks everyone!08:29
*** felixhuettner has left #openstack-meeting-308:29
masahitothanks. bye08:29
belmoreiraThanks08:30
ttx#endmeeting08:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:30
openstackMeeting ended Wed May  6 08:30:01 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-05-06-08.01.html08:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-05-06-08.01.txt08:30
openstackLog:            http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-05-06-08.01.log.html08:30
*** e0ne has joined #openstack-meeting-308:30
*** mdelavergne has quit IRC08:32
*** masahito has quit IRC08:34
*** baojg has joined #openstack-meeting-308:40
*** jamesmcarthur has quit IRC08:41
*** elod is now known as elod_pto08:43
*** jamesmcarthur has joined #openstack-meeting-309:16
*** jamesmcarthur has quit IRC09:26
*** jamesmcarthur has joined #openstack-meeting-309:57
*** jamesmcarthur has quit IRC10:07
*** baojg has quit IRC10:18
*** jamesmcarthur has joined #openstack-meeting-310:43
*** jamesmcarthur has quit IRC10:43
*** jamesmcarthur has joined #openstack-meeting-310:43
*** maciejjozefczyk_ has joined #openstack-meeting-310:43
*** jamesmcarthur has quit IRC10:44
*** maciejjozefczyk has quit IRC10:44
*** jamesmcarthur has joined #openstack-meeting-310:44
*** maciejjozefczyk has joined #openstack-meeting-310:44
*** maciejjozefczyk_ has quit IRC10:48
*** maciejjozefczyk_ has joined #openstack-meeting-310:49
*** maciejjozefczyk has quit IRC10:50
*** maciejjozefczyk has joined #openstack-meeting-310:50
*** jamesmcarthur has quit IRC10:51
*** maciejjozefczyk_ has quit IRC10:53
*** maciejjozefczyk_ has joined #openstack-meeting-310:55
*** maciejjozefczyk has quit IRC10:55
*** jamesmcarthur has joined #openstack-meeting-310:58
*** jamesmcarthur has quit IRC10:59
*** jamesmcarthur has joined #openstack-meeting-310:59
*** jamesmcarthur has quit IRC11:01
*** jamesmcarthur has joined #openstack-meeting-311:02
*** maciejjozefczyk_ has quit IRC11:04
*** maciejjozefczyk_ has joined #openstack-meeting-311:05
*** jamesmcarthur has quit IRC11:07
*** raildo has joined #openstack-meeting-311:37
*** witek has quit IRC11:39
*** yamamoto has joined #openstack-meeting-311:40
*** jamesmcarthur has joined #openstack-meeting-311:40
*** yamamoto has quit IRC11:42
*** jamesmcarthur has quit IRC12:25
*** jamesmcarthur has joined #openstack-meeting-313:01
*** ralonsoh has quit IRC13:08
*** ralonsoh has joined #openstack-meeting-313:11
*** jamesmcarthur has quit IRC13:21
*** maciejjozefczyk_ is now known as maciejjozefczyk13:37
*** jamesmcarthur has joined #openstack-meeting-314:01
*** jamesmcarthur has quit IRC14:22
*** belmoreira has quit IRC14:25
*** lpetrut has quit IRC14:30
*** belmoreira has joined #openstack-meeting-314:44
*** lajoskatona has joined #openstack-meeting-314:45
*** belmoreira has quit IRC14:54
*** belmoreira has joined #openstack-meeting-314:55
slaweq#startmeeting neutron_ci15:00
openstackMeeting started Wed May  6 15:00:01 2020 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
slaweqhi15: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
njohnstono/15:00
*** lpetrut has joined #openstack-meeting-315:00
bcafarelo/15:01
ralonsohhi15:02
slaweqok, I think we can start15:02
slaweq#topic Actions from previous meetings15:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"15:02
slaweqfirst one15:02
slaweqmaciejjozefczyk to take a look at ovn related functional test failures15:02
lajoskatonaHi15:02
slaweqI pinged maciejjozefczyk on neutron channel15:03
slaweqmaybe he will join soon15:03
maciejjozefczykhey15:04
maciejjozefczykok, so I took a look on those failures for functional tests15:04
maciejjozefczyk#link https://bugs.launchpad.net/neutron/+bug/186811015:06
openstackLaunchpad bug 1868110 in neutron "[OVN] neutron.tests.functional.plugins.ml2.drivers.ovn.mech_driver.ovsdb.test_ovn_db_sync.TestOvnNbSyncOverTcp.test_ovn_nb_sync_log randomly fails" [High,In progress] - Assigned to Maciej Jozefczyk (maciej.jozefczyk)15:06
maciejjozefczykI found that the test from this class failed only once recently, on the same which is: TimeoutException15:07
maciejjozefczykSo i think we have 2 possible solution: let it be, as per 1 failure per week is not that much15:07
maciejjozefczykor bump the timeout value15:07
bcafarelwhat's the current timeout?15:08
slaweqdidn't we lower this timeout already to solve this problem? :)15:08
maciejjozefczykI think that after bumping it from very litle value to 15 seconds we already have less occurance of this test failures15:08
maciejjozefczykslaweq, bcafarel default in the neutron configuration is 180 seconds15:08
bcafareloh right that was the one that was bumped15:09
maciejjozefczykwe had issues while it was 5 seconds set for functional tests, we updated to 15 seconds and I found only particular failure of this test class15:09
slaweqahh, it was 5 seconds and You bumped it to 15, right?15:09
slaweqwhy not use default value?15:09
maciejjozefczykslaweq, I think that the author a few years ago wanted to not have that high timeout value for functional tests because it causes the whole job to timeout15:09
maciejjozefczykbut we can try setting it to default15:10
slaweqso maybe we can try with e.g. 30 seconds for now and we will see :)15:10
*** belmoreira has quit IRC15:11
maciejjozefczykslaweq, yes15:11
maciejjozefczykbut for now, as I said, I found only 1 failure of the test, at least I was checking week ago :)15:12
slaweqmaciejjozefczyk: ok, IMO we can try to bump it a litte and see - maybe there will be no occurences anymore :)15:13
maciejjozefczykslaweq, sure15:13
slaweqralonsoh: njohnston bcafarel what do You think?15:13
ralonsoh+115:13
ralonsohto increase the time15:13
njohnstonI agree, it seems reasonable15:14
bcafarelyep, it is still an OK value15:14
slaweqok, maciejjozefczyk will You take care of it?15:14
maciejjozefczykslaweq, yes15:14
slaweqthx15:14
slaweq#action maciejjozefczyk will increase timeout in neutron.tests.functional.plugins.ml2.drivers.ovn.mech_driver.ovsdb.test_ovn_db_sync.TestOvnNbSyncOverTcp.test_ovn_nb_sync_log15:15
slaweqok, next one15:15
slaweqmaciejjozefczyk to report LP regarding failing neutron_tempest_plugin.scenario.test_trunk.TrunkTest.test_trunk_subport_lifecycle in neutron-ovn-tempest-ovs-release job15:15
maciejjozefczyk#link https://bugs.launchpad.net/neutron/+bug/187444715:15
openstackLaunchpad bug 1874447 in neutron "[OVN] Tempest test neutron_tempest_plugin.scenario.test_trunk.TrunkTest.test_trunk_subport_lifecycle fails randomly" [High,Confirmed]15:15
slaweqmaciejjozefczyk: thx15:16
slaweqbut I think Your comments to this LP are wrong :)15:16
maciejjozefczykI was investigating it, but at that time I also haven't found any occurance of that failure (afair the logs are rotated after a week?)15:16
slaweqlogs are gone after some time, I don't know exactly how long15:17
njohnstonI've been doing some experimenting with trunks on the 2 changes you cite, but I don't think I have had enough CI runs on them to account for the statsu you mention.15:17
njohnston*stats15:17
slaweqif You would found similar issues, please link them to this LP15:19
slaweqwe will see if that is serious issue15:19
maciejjozefczykok slaweq15:20
njohnston+115:20
slaweqthx15:20
slaweqok, next one15:20
slaweqralonsoh to check timeout during interface creation in functional tests15:20
ralonsoh#link https://review.opendev.org/#/c/722254/15:20
ralonsohand a patch in pyroute215:21
ralonsohhttps://github.com/svinota/pyroute2/issues/70215:21
ralonsohnow we can pass the PyDLL when creating a namespace context15:21
ralonsohwe need a new release in pyroyte2 0.5.1315:21
ralonsohsame problem as when calling create/delete namespaces15:21
ralonsohthat's all15:22
slaweqthx a lot15:22
ralonsohyw15:22
slaweqok, so that's all from the last week15:23
slaweqlets move to the next topic15:23
slaweq#topic Stadium projects15:23
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"15:23
*** belmoreira has joined #openstack-meeting-315:23
slaweqstandardize on zuul v315:23
slaweqEtherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop15:23
slaweqonly update which I have is that there is now zuulv3 grenade job15:23
slaweqso we can migrate our grenade jobs too15:24
slaweqit's already done for 2 of the neutron grenade jobs15:24
slaweqI will do the same for neutron-ovn job15:24
njohnstonI like the idea of an OVN grenade job to complement the existing ml2/ovs one15:24
slaweqand there is also networking-odl grenade job to migrate15:25
njohnstonso that just meanes the networking-odl-grenade job, and the regular zuulv3 transition for networking-midonet.  Any word from yamamoto recently?15:25
slaweqnjohnston: nope15:25
lajoskatonaI started tat and got some advices from Luigi Toscano15:25
njohnstonexcellent15:25
lajoskatonathat -^15:25
slaweqhe only told me that his time for openstack is "very limited" currently15:26
slaweqwe will need to review list of stadium projects again during the ptg probably15:26
slaweqthx lajoskatona for taking care of networking-odl15:27
lajoskatonaslaweq: np, we use it so its noral way of working ;)15:27
lajoskatonaby the way: could you check these please : https://review.opendev.org/#/q/I3aed8031c1b784c16dd7055afd41456ed935b7fc15:28
lajoskatonaas I know these are missing to make master and ussuri patches to be merged for reno etc...15:28
slaweqsure, I will15:29
slaweqok, anything else regarding stadium projects' ci for today?15:29
lajoskatonanothing from me at least15:30
njohnstonnope15:31
ralonsohno15:31
*** njohnston is now known as njohnston_15:31
bcafarelneutron-dynamic-routing fails tempest on train (though this was the first backport attempt): https://review.opendev.org/#/c/725790/15:31
*** njohnsto_ has joined #openstack-meeting-315:31
bcafarelrelated to that series of monkeypatch eventlet fixes15:32
slaweqModuleNotFoundError: No module named 'neutron_tempest_plugin'15:32
slaweqso IMO it's some issue with jobs definition15:34
njohnsto_yeah15:35
*** njohnsto_ is now known as njohnston15:35
bcafarelyes, in train tests were still in-repo15:35
slaweqthose are still legacy jobs15:35
*** belmoreira has quit IRC15:36
slaweqbcafarel: isn't that related to https://review.opendev.org/#/c/721277/3/devstack/plugin.sh ?15:37
slaweqmaybe those jobs in stable/train should use some pinned version of neutron-tempest-plugin?15:38
*** belmoreira has joined #openstack-meeting-315:39
bcafarelhmm yes it's possible (so the legacy job was actually using the installed version of the plugin?)15:39
slaweqbcafarel: idk really :/15:40
slaweqbcafarel: will You check that this week?15:40
bcafarelslaweq: I'll try at least :) and worst case fill a LP for it15:40
slaweqthx15:40
slaweq#action bcafarel to check neutron-dynamic-routing failurs in stable/train15:41
slaweqok, lets move on15:41
slaweq#topic Stable branches15:41
*** openstack changes topic to "Stable branches (Meeting topic: neutron_ci)"15:41
slaweqTrain dashboard: http://grafana.openstack.org/d/pM54U-Kiz/neutron-failure-rate-previous-stable-release?orgId=115:41
slaweqStein dashboard: http://grafana.openstack.org/d/dCFVU-Kik/neutron-failure-rate-older-stable-release?orgId=115:41
slaweqIMHO dashboards looks more or less fine15:42
bcafarelmost backports got in without too many rechecks yes15:43
bcafareldesignate gate even behaved :) mostly rally/grenade rechecks15:43
slaweqfor grenade it should be better when nova will backport fix for scheduler/placement15:44
slaweqin master it now works much better IMO15:44
slaweqok, next topic then15:44
slaweq#topic Grafana15:44
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"15:44
slaweqhttp://grafana.openstack.org/dashboard/db/neutron-failure-rate15:45
slaweqhere there is more results :)15:45
slaweq*more data15:45
slaweqand I see couple of problems there15:45
slaweqor potential problems15:45
slaweqneutron-ovn-tempest-slow (non-voting)15:46
slaweqneutron-ovn-tempest-full-multinode-ovs-master (non-voting)15:46
slaweqboth jobs are going to high failure rate today15:46
slaweqI don't know really if that is some new problem15:46
slaweqin most cases where I see it both jobs are TIMED_OUT15:47
slaweqe.g. https://review.opendev.org/#/c/725836/15:48
slaweqor https://review.opendev.org/#/c/724445/15:48
ralonsohI'll try to track those two jobs to see a possible problem15:49
ralonsohmaybe is just a matter of increasing the job timeout15:49
slaweqI now checked one such job https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_07c/717083/9/check/neutron-ovn-tempest-slow/07c6abc/job-output.txt15:49
slaweqit seems that all tests are failing due to "Failed to allocate the network(s), not rescheduling."15:50
slaweqso it seems like serious issue15:50
maciejjozefczykI can try to investigate that15:50
slaweqand I think that it's due to something from today or yesterday15:50
slaweqhttps://zuul.opendev.org/t/openstack/build/07c6abc773a84930b20a5ea1b46f666e/log/controller/logs/screen-q-svc.txt?severity=415:51
slaweqI think that this can be culprit :)15:51
slaweqor maybe not :) but at least it's IMO worth to check15:52
slaweqok, so ralonsoh maciejjozefczyk - to whom I should assign action to check that? :)15:53
maciejjozefczykMay 06 09:52:01.354607 ubuntu-bionic-rax-iad-0016398327 neutron-server[10171]: WARNING neutron.db.agents_db [None req-e6c8c261-b416-41da-beae-c05e137265bb None None] Agent healthcheck: found 1 dead agents out of 4:15:53
maciejjozefczykMay 06 09:52:01.354607 ubuntu-bionic-rax-iad-0016398327 neutron-server[10171]:                 Type       Last heartbeat host15:53
maciejjozefczykMay 06 09:52:01.354607 ubuntu-bionic-rax-iad-0016398327 neutron-server[10171]: OVN Controller Gateway agent 2020-05-06 09:52:01.334533 ubuntu-bionic-rax-iad-001639832715:53
maciejjozefczyk^ during one of failed tests15:53
ralonsohI can take it15:54
slaweqthx ralonsoh15:54
slaweqand thx maciejjozefczyk for help with this15:54
slaweq#action ralonsoh to check ovn jobs timeouts15:54
slaweqok, lets move on15:54
slaweqsome recheck stats from last weeks15:55
slaweqAverage number of rechecks in last weeks:15:55
slaweq    week 17 of 2020: 2.6215:55
slaweq    week 18 of 2020: 1.415:55
slaweq    week 19 of 2020: 1.7115:55
slaweqso it seems not very bad recently :)15:55
slaweqok, lets move quickly to the periodic jobs as we are almost out of time today15:55
slaweq#topic Periodic15:55
*** openstack changes topic to "Periodic (Meeting topic: neutron_ci)"15:55
slaweqneutron-ovn-tempest-ovs-master-fedora is failing since 26.0415:56
ralonsohagain?15:56
slaweqfirst it was failing with error like: https://d11d69999bcdac29c8fb-3dea60a35fb0d38e41c535f13b48e895.ssl.cf5.rackcdn.com/periodic/opendev.org/openstack/neutron/master/neutron-ovn-tempest-ovs-master-fedora/b12ec3a/job-output.txt15:56
slaweqand in the next days it changed a bit:15:56
slaweq    https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_dd7/periodic/opendev.org/openstack/neutron/master/neutron-ovn-tempest-ovs-master-fedora/dd76029/job-output.txt15:56
slaweq    and15:56
slaweq    https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_71e/periodic/opendev.org/openstack/neutron/master/neutron-ovn-tempest-ovs-master-fedora/71e5c2f/job-output.txt15:56
slaweqralonsoh: yeah - I don't like this fedora job ;)15:56
ralonsoh2020-04-26 06:28:30.004222 | controller | Error: Unable to find a match: kernel-devel-5.5.1715:57
ralonsohbut this is not the only error15:57
slaweqbut in next days it was failing with:15:57
slaweqconfigure: error: Linux kernel in /lib/modules/5.6.6-200.fc31.x86_64/build is version 5.6.6, but version newer than 5.5.x is not supported (please refer to the FAQ for advice)15:57
ralonsohand another one15:58
ralonsoh2020-05-02 06:18:55.602437 | controller | configure: error: source dir /lib/modules/5.6.7-200.fc31.x86_64/build doesn't exist15:58
slaweqyes15:58
slaweqso basically it is failing on compilation of ovs15:58
ralonsohexactly15:58
ralonsohwe can ping fedora guys in bugzilla15:58
ralonsoh(I think so)15:58
maciejjozefczykwe recently added compilation of ovs module while using qos15:58
slaweqmaciejjozefczyk: You was playing with this complile of the ovs module15:59
slaweqcan You take a look at this one?15:59
maciejjozefczykyes, that was me15:59
maciejjozefczykslaweq, ok15:59
slaweqthx a lot15:59
slaweq#action maciejjozefczyk to check failing compile of ovs in the fedora periodic job15:59
slaweqand we are out of time almost15:59
slaweqthx for attending16:00
slaweq#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Wed May  6 16:00:06 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-05-06-15.00.html16:00
slaweqo/16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-05-06-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-05-06-15.00.log.html16:00
bcafarelo/16:00
njohnstono/16:00
ralonsohbye16:00
maciejjozefczykbb!16:00
*** maciejjozefczyk has quit IRC16:01
*** njohnston has quit IRC16:01
*** maciejjozefczyk has joined #openstack-meeting-316:06
*** maciejjozefczyk_ has joined #openstack-meeting-316:07
*** lajoskatona has left #openstack-meeting-316:08
*** maciejjozefczyk has quit IRC16:11
*** jamesmcarthur has joined #openstack-meeting-316:20
*** psachin has quit IRC16:41
*** dconde has joined #openstack-meeting-316:54
*** dconde has quit IRC16:54
*** dconde has joined #openstack-meeting-316:54
*** jamesmcarthur has quit IRC16:55
*** maciejjozefczyk has joined #openstack-meeting-317:18
*** maciejjozefczyk_ has quit IRC17:20
*** irclogbot_3 has quit IRC17:20
*** maciejjozefczyk has quit IRC17:21
*** maciejjozefczyk has joined #openstack-meeting-317:21
*** jamesmcarthur has joined #openstack-meeting-317:21
*** maciejjozefczyk_ has joined #openstack-meeting-317:22
*** irclogbot_3 has joined #openstack-meeting-317:23
*** maciejjozefczyk_ has quit IRC17:23
*** maciejjozefczyk has quit IRC17:26
*** jamesmcarthur has quit IRC17:37
*** jamesmcarthur has joined #openstack-meeting-317:38
*** ralonsoh has quit IRC18:19
*** lpetrut has quit IRC18:22
*** e0ne has quit IRC18:34
*** jamesmcarthur has quit IRC19:25
*** jamesmcarthur has joined #openstack-meeting-319:30
*** belmoreira has quit IRC19:58
*** belmoreira has joined #openstack-meeting-320:10
*** diablo_rojo has joined #openstack-meeting-320:12
*** belmoreira has quit IRC20:25
*** jamesmcarthur has quit IRC20:50
*** jamesmcarthur has joined #openstack-meeting-320:51
*** jamesmcarthur has quit IRC21:10
*** jamesmcarthur has joined #openstack-meeting-321:16
*** slaweq has quit IRC21:26
*** e0ne has joined #openstack-meeting-321:35
*** e0ne has quit IRC21:44
*** raildo_ has joined #openstack-meeting-321:45
*** raildo has quit IRC21:48
*** jamesmcarthur has quit IRC21:55
*** raildo_ has quit IRC22:01

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