Wednesday, 2020-08-26

*** slaweq_ has joined #openstack-meeting-300:10
*** slaweq has quit IRC00:12
*** yamamoto has quit IRC00:14
*** apetrich has quit IRC02:14
*** yamamoto has joined #openstack-meeting-302:43
*** psahoo has joined #openstack-meeting-303:31
*** psachin has joined #openstack-meeting-303:57
*** psahoo has quit IRC04:35
*** psahoo has joined #openstack-meeting-305:00
*** psahoo has quit IRC05:11
*** psahoo has joined #openstack-meeting-305:27
*** belmoreira has joined #openstack-meeting-305:46
*** belmoreira has quit IRC05:47
*** psahoo has quit IRC05:55
*** psahoo has joined #openstack-meeting-306:12
*** slaweq_ has quit IRC06:14
*** slaweq_ has joined #openstack-meeting-306:17
*** slaweq_ has quit IRC06:21
*** slaweq_ has joined #openstack-meeting-306:34
*** tsmith2 has quit IRC06:40
*** tsmith2 has joined #openstack-meeting-306:40
*** ralonsoh has joined #openstack-meeting-306:42
*** slaweq_ is now known as slaweq06:48
*** belmoreira has joined #openstack-meeting-307:13
*** tosky has joined #openstack-meeting-307:40
*** Luzi has joined #openstack-meeting-307:55
ttx#startmeeting large_scale_sig08:00
openstackMeeting started Wed Aug 26 08:00:04 2020 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: large_scale_sig)"08:00
openstackThe meeting name has been set to 'large_scale_sig'08:00
ttx#topic Rollcall08:00
*** openstack changes topic to "Rollcall (Meeting topic: large_scale_sig)"08:00
ttxWho is here for the Large Scale SIG meeting ?08:00
ttxamorin, belmoreira, tobberydberg maybe08:01
belmoreirao/08:01
belmoreirathanks for the ping08:02
*** masahito has joined #openstack-meeting-308:02
masahitoo/08:02
tobberydbergI'm here, but haven't been much part in the Large Scale SIG though ;-)08:02
ttxheh08:02
ttxAlright, let's start and see if anyone else joins08:02
ttxOur agenda for today is at:08:03
ttx#link https://etherpad.openstack.org/p/large-scale-sig-meeting08:03
ttx#topic Discuss fail of first EU-US meeting08:03
*** openstack changes topic to "Discuss fail of first EU-US meeting (Meeting topic: large_scale_sig)"08:03
ttxAs you know we recently decided to create a meeting rotation, to create a US-friendly meeting time08:03
ttxTwo weeks ago we had our first EU-US friendly meeting, but then we did not get anyone new showing up08:03
ttxObviously creating a new meeting in the middle of August is not optimal, but still that was disappointing08:03
ttxWe will need to make a bit more noise for the next one, and if nobody shows up again, reconsider our decision08:04
ttx(There is no point in making it harder for APAC folks if we do not really get new members)08:04
ttxThoughts on that?08:04
belmoreira+108:04
belmoreirathere are large deployments in the US. Should we try to contact people directly?08:05
ttxI had a few direct contacts based on https://etherpad.opendev.org/p/large-scale-sig08:05
ttxand tried to send them direct email08:05
ttxBeth said she can;t do IRC, the others said IRC was fine but did not show up at that first meeting08:06
ttxBut I agree, we should do personal contacts where we can08:06
ttxin advance of the next one08:06
ttxlike people who participated actively to the opendev on large scale infra08:07
ttx(James Penick, Erik Andersson...)08:07
ttxIf you have a personal contact that could be interested, don;t hesitate to ping them... like the week before08:08
*** mdelavergne has joined #openstack-meeting-308:08
belmoreirasure08:08
*** mdelavergne has left #openstack-meeting-308:09
ttx#action all to contact US large deployment friends to invite them to next EU-US meeting08:09
ttxok, moving on08:09
ttx#topic PTG/Summit plans08:09
*** openstack changes topic to "PTG/Summit plans (Meeting topic: large_scale_sig)"08:09
ttxWe need to discuss if we want to do anything around the Summit and PTG in October08:09
*** mdelavergne has joined #openstack-meeting-308:09
ttxAs a reminder, our next summit will be virtual and happen on Oct 19-23, 202008:09
amorinhello08:09
ttxThere will be "forum sessions" there that we could leverage to get more input08:09
amorinsorry I am late08:09
ttxamorin: hi!08:09
mdelavergneHi, sorry I am late too08:10
ttxThere will also be a PTG (project teams gathering) on Oct 26-30, 202008:10
ttxThis is more of a work event, where we could have a video meeting to discuss future SIG work if we wanted08:10
ttxIn both cases if we are interested we should engage quickly to book slots08:10
ttxPersonally I think we should definitely ask for a Forum session, for example around gathering scaling stories08:10
ttxTo act as a recruitment function but also to learn new things08:10
ttxI'm less convinced that with the current level of activity/size of the group  we need a PTG group meeting.08:11
ttxIRC is plenty enough to coordinate our slow work, so unless there is a particular activity we'd like to book time to synchronously work on...08:11
ttxThoughts?08:11
belmoreirahaving a video meeting will be definitely more engaging, I think08:11
ttxbelmoreira: just for PTG or all the time?08:12
masahitoIf there is chance to talk each other, the short video meeting seems to be nice.08:12
belmoreiraI was thinking for the PTG08:12
ttxOK, so maybe a short one08:12
ttxor two to match the two timezones08:13
amorinhow are working forum sessions, is it going to be with video meeting as well?08:13
ttxI'm not sure yet... I assumed it would be opendev-style08:13
ttx(opendev-the-event style)08:14
amorinso with video on zoom, right?08:14
ttxlike a zoom meeting with a couple of moderators08:14
ttxor meetpad08:14
ttxright08:14
amorinso if it is like that, maybe forum session is enough, we can meet over there and recruit new members / find new stories08:14
ttxOK, so how about... a Forum session specifically to find new stories, a bit like that session at opendev-the-event08:15
amorin+108:15
belmoreira I think it will be good for the group and it's also an opportunity to fin/interact with other people08:15
ttx+ one hour of video meeting to replace our regular meeting08:15
ttx(at the PTG)08:15
belmoreira+108:15
amorinworks for me08:15
ttxthen if we identify potential new mebers in the Forum session we can follow up at the PTG08:16
ttxOK, I'll fill the forms and file then with the required authorities08:16
ttxI'll try to be close to our usual meeting times08:17
ttxif those slots are still available08:17
*** dosaboy has quit IRC08:17
*** dosaboy has joined #openstack-meeting-308:17
ttx#agreed One Forum session on scaling stories, One PTG short meeting to replace our regular meeting that week08:18
ttx#action ttx to request Forum/PTG sessions08:18
ttxok, moving on to our regular topics08:18
ttx#topic Progress on "Documenting large scale operations" goal08:18
*** openstack changes topic to "Progress on "Documenting large scale operations" goal (Meeting topic: large_scale_sig)"08:18
ttx#link https://etherpad.openstack.org/p/large-scale-sig-documentation08:18
ttxFirst, osarchiver...08:18
ttx(which was just mentioned again on openstack-discuss)08:18
ttxWhat's the status of moving that upstream? I think it's stalled waiting on progress on OSops resurrection?08:19
amorinon OVH side, we worked on applying some changes based on comments we receive on the ml08:19
amorinwe removed debian folder for example08:19
ttxhah yes that will please zigo for sure08:19
amorinyes08:20
amorinso, for us it's good08:20
ttxamorin: so next step is to make progress on resurrecting OSops08:20
amorinyes08:20
ttxbelmoreira: we'll need to work with smcginnis to make progress on the governance side of it08:21
ttxI might raise it on the TC channel08:21
belmoreiragreat08:21
belmoreiraI'm happy to help on that08:21
ttx#action ttx to push for OSops resurrection08:21
ttxbelmoreira: thanks08:21
*** apetrich has joined #openstack-meeting-308:22
ttx#action belmoreira, ttx to push for OSops resurrection08:22
ttxSecond, we still need more config options on the Large scale configuration wiki page before we can push for a link in Nova doc08:22
ttxamorin: do you have enough matter to work on, or should we just pause that until we have more participants working on it?08:22
amorinyes, unfortunately I am not able to find enough time08:22
amorinmaybe we can pause that for now08:22
amorinand stay focus on resurrecting osops?08:23
ttxIf the issue is more time than data, I'm fine carrying the work item over08:23
ttxIf you miss data to do it, then we should just pause it08:23
amorinon the other end, we recently disccuss about rabbit binding issues on the ml08:23
amorinand things in this topic could also be copied back to documentation08:23
ttxamorin: your call, I can just carry over the #action, or just stop mentioning it every meeting :)08:24
amorinok, about nova, we can pause, we dont have enough data08:24
ttxok, done08:24
ttxAnd finally our last workstream is around collecting metrics/billing stories08:25
ttxLast I looked we only had OVH entry on that one08:25
ttxbelmoreira, masahito: do you think you could contribute CERN/LINE take on that?08:26
ttx(line 36 of https://etherpad.opendev.org/p/large-scale-sig-documentation)08:26
belmoreirayes, I can. The problem is committing when I'm going to do it.08:27
ttxNo commitment really. I just will continue to pester you for it regularly :)08:27
belmoreira:)08:27
ttx#action all to describe briefly how you solved metrics/billing in your deployment in https://etherpad.openstack.org/p/large-scale-sig-documentation08:27
ttxAnything else on this topic?08:27
masahitoyes.08:28
ttxmasahito: yes you can contribute story, or yes you have something else on this topic?08:28
ttxAssuming that was yes you can contribute story, and moving on to next topic08:29
masahitoah, sorry. yes I can contribute story.08:30
ttx#topic Progress on "Scaling within one cluster" goal08:30
*** openstack changes topic to "Progress on "Scaling within one cluster" goal (Meeting topic: large_scale_sig)"08:30
ttx#link https://etherpad.openstack.org/p/large-scale-sig-cluster-scaling08:30
ttxFirst, update on the healthcheck/middleware ping discussion08:30
ttx#link https://review.opendev.org/#/c/735385/08:30
ttxI think we collectively made good progress to get it merged in oslo.messaging...08:30
ttxI was hoping we'd have a go-ahead from sean-k-mooney or dansmith on your last reply:08:30
ttx#link http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016697.html08:30
ttxbut I'll leave it to bnemec to get the approval timing right08:31
amorinok08:31
ttxSecond workstream is on oslo.metrics08:31
ttxhttps://opendev.org/openstack/oslo.metrics08:32
amorinshould we ping back bnemec for this?08:32
ttxamorin: I think he'll get to it. I think he's leaving some time for last minute objections08:32
amorinok08:32
*** tosky has quit IRC08:32
amorinso we wait for now, right?08:32
ttxyes08:32
amorinack08:32
*** tosky has joined #openstack-meeting-308:33
ttxSo on the oslo.metrics side, we need to make progress on two sides: try to find other users interested in running it, and improve the code base to make it more openstack-y08:33
amorinI will ask someone at OVH if we can test this08:33
ttxI'll try to work on adding basic tests, unless someone beats me to it08:34
ttxso that we feel more comfortable with proposed changes08:34
ttxmasahito: the code we have in https://opendev.org/openstack/oslo.metrics is what you run at LINE currently? Or is there a difference?08:34
masahitoBasically same. But we have some improvement since I pushed the patch...08:35
ttxmasahito: ok, would be great to push it to oslo.metrics as well, when you get the chance08:36
ttxI'd like to make a release with Victoria release08:36
masahitoI try to.08:36
ttx#action masahito to push latest patches to oslo.metrics08:37
ttx#action ttx to look into a basic test framework for oslo,metrics08:37
ttx#action amorin to see if oslo.metrics could be tested at OVH08:37
ttxLast workstream... we still need more scaling stories08:37
ttxhttps://etherpad.openstack.org/p/scaling-stories08:38
ttxwe'll likely need to do a campaign to collect those, as our current outreach is not very efficient08:38
ttxA forum session at next summit centered on that will help imho08:38
ttxAnything else on this topic/goal?08:38
mdelavergnenot from my side08:39
ttx#topic Next meeting08:39
*** openstack changes topic to "Next meeting (Meeting topic: large_scale_sig)"08:39
ttxNext meeting will be US-EU on Sept 9, 16utc.08:39
ttxThat's the one we'll need to make more noise about08:39
ttxWho from this meeting will likely be able to also participate to this one?08:39
amorinI do08:40
ttxThanks!08:40
ttxThen next EU-APAC meeting will be Sept 23, 8utc.08:40
ttxHow does that sound?08:40
amoringood08:41
belmoreiragood08:41
ttx#info next meetings: Sep 9, 16:00UTC; Sep 23, 8:00UTC08:41
ttxThat's all I had... Any last thoughts? requests?08:41
ttxOK then... thanks everyone!08:42
ttx#endmeeting08:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:42
openstackMeeting ended Wed Aug 26 08:42:26 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-08-26-08.00.html08:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-08-26-08.00.txt08:42
openstackLog:            http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-08-26-08.00.log.html08:42
mdelavergneThanks, see you!08:42
masahitothanks08:43
*** mdelavergne has quit IRC08:43
amorinthanks08:44
belmoreirathanks08:45
*** yamamoto has quit IRC09:27
*** yamamoto has joined #openstack-meeting-309:49
*** baojg has quit IRC09:52
*** baojg has joined #openstack-meeting-309:53
*** apetrich has quit IRC10:31
*** Luzi has quit IRC10:42
*** apetrich has joined #openstack-meeting-310:51
*** masahito has quit IRC11:03
*** yamamoto has quit IRC11:10
*** yamamoto has joined #openstack-meeting-311:44
*** raildo has joined #openstack-meeting-311:44
*** yamamoto has quit IRC11:51
*** yangyapeng has left #openstack-meeting-312:19
*** _erlon_ has joined #openstack-meeting-312:22
*** bnemec has joined #openstack-meeting-312:59
*** Adri2000 has joined #openstack-meeting-313:05
*** yamamoto has joined #openstack-meeting-313:48
*** yamamoto has quit IRC13:58
*** dustinc has joined #openstack-meeting-314:37
*** lpetrut has joined #openstack-meeting-314:46
*** lpetrut has quit IRC14:58
slaweq#startmeeting neutron_ci15:00
slaweqhi15:00
openstackMeeting started Wed Aug 26 15:00:21 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
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
bcafarelo/15:00
slaweqand please give me 3 minutes before we start15:00
ralonsohhi15:01
slaweqok, I'm back15:02
slaweqand I think we can 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 check timing out neutron-ovn-tempest-full-multinode-ovs-master jobs15:03
ralonsohslaweq, sorry but I didn't spend time on this15:03
ralonsoh(and at this point I barely remember it)15:03
slaweqralonsoh: bug is here https://bugs.launchpad.net/neutron/+bug/188680715:04
openstackLaunchpad bug 1886807 in neutron "neutron-ovn-tempest-full-multinode-ovs-master job is failing 100% times" [High,Confirmed] - Assigned to Maciej Jozefczyk (maciejjozefczyk)15:04
*** lajoskatona has joined #openstack-meeting-315:04
slaweqI think it is failing like that still15:04
lajoskatonao/15:04
ralonsohslaweq, I'll check it this week15:04
slaweqthx ralonsoh15:04
slaweq#action ralonsoh to check timing out neutron-ovn-tempest-full-multinode-ovs-master jobs - bug https://bugs.launchpad.net/neutron/+bug/188680715:05
slaweqnext one15:05
slaweqslaweq to move uwsgi jobs to periodic queue and promote -uwsgi ones to be gating15:05
slaweq    Patch https://review.opendev.org/74582215:05
*** psahoo has quit IRC15:05
slaweqplease review it :)15:05
slaweqand the last one on my list:15:05
slaweqmaciejjozefczyk to check https://bugs.launchpad.net/neutron/+bug/189044515:05
openstackLaunchpad bug 1890445 in neutron "[ovn] Tempest test test_update_router_admin_state failing very often" [Critical,Confirmed]15:05
slaweqI don't think maciek will look into this so we will need new volunteer15:06
slaweqI will ask jlibosva and lucasgomes if they can take a look into that one15:06
ralonsoh(thanks)15:07
slaweq#action slaweq to ask jlibosva and lucasgomes if they can check https://bugs.launchpad.net/neutron/+bug/189044515:07
openstackLaunchpad bug 1890445 in neutron "[ovn] Tempest test test_update_router_admin_state failing very often" [Critical,Confirmed]15:07
slaweqthat are all actions from last meeting15:07
slaweqso lets move to the next topic15:07
slaweq#topic Switch to Ubuntu Focal15:07
*** openstack changes topic to "Switch to Ubuntu Focal (Meeting topic: neutron_ci)"15:07
slaweqany updates about that one?15:07
ralonsohbcafarel, pushed a change to update the lower contrains15:08
ralonsohhttps://review.opendev.org/#/c/748168/15:08
bcafarelsorry it took some trials to get this one passing, it is OK locally now (and testing in progress in https://review.opendev.org/#/c/734304/ )15:09
slaweqok, so with that we should be good with functional/fullstack jobs to be moved to focal15:10
slaweqright?15:10
ralonsohI think so15:10
bcafarelyes they work fine with ncat installed, just need to pass that pesky cI15:10
slaweqgood15:10
bcafarelalthough we could just drop depends-on in https://review.opendev.org/#/c/734304/ and merge the change, we would be ready then15:11
slaweqfor other jobs we need this https://review.opendev.org/#/c/731207/ to be merged, right?15:11
lajoskatonanot much activity on it recently15:12
slaweqor can we simply change nodeset in e.g. neutron-tempest-plugin jobs now and move on with that?15:12
slaweqwdyt?15:12
ralonsohI don't think this will work15:12
ralonsohwe need this devstack change15:12
slaweqwhy?15:13
bcafarelhttps://review.opendev.org/#/c/738163/ still has a few red jobs (in addition to ft/functional/lower constraints)15:13
ralonsohhmmmm you are right15:13
ralonsohjust changing the node set could work15:13
ralonsohyes, you are right15:13
ralonsohwe can try it in a DNM patch15:13
lajoskatona+115:13
slaweqlet me try to propose patch for neutron-tempest-plugin to change that and see15:13
ralonsohsure!15:13
slaweq#action slaweq to propose neutron-tempest-plugin switch to focal nodes15:14
lajoskatonaif devstack change wil be merged we can remove the nodesets15:14
slaweqlajoskatona: right15:14
ralonsohyeah, correct15:14
slaweqlajoskatona: what about https://review.opendev.org/#/c/736703/ - is that ready to go?15:15
lajoskatonaI check again rally15:16
lajoskatonabut as I see it is not worse than with bionic15:16
slaweqlajoskatona: great15:16
slaweqso lets review this patch and move on with it15:17
slaweqthx15:17
slaweqI think that's all regarding migration to Focal15:17
slaweqso lets move on to the next topic15:17
slaweq#topic Stadium projects15:17
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"15:17
slaweqanything You want to discuss regarding stadium's ci?15:17
ralonsohno15:18
lajoskatonanot really15:18
bcafarelnothign here15:18
slaweqok, that's fast :)15:18
slaweqlets move to the next topic then15:18
slaweq#topic Stable branches15:18
*** openstack changes topic to "Stable branches (Meeting topic: neutron_ci)"15:18
slaweqanything here?15:18
slaweqIMO ci of stable branches is pretty ok still15:18
bcafarelnot much either :) (still catching up from backlog)15:18
bcafarelyep from what I saw everything seems to be in good shape15:19
slaweqgreat, at least ci of stable branches is stable :)15:19
slaweqok, so lets move on15:20
slaweq#topic Grafana15:20
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"15:20
slaweqtoday I added neutron-tempest-plugin-scenario-ovn job to the grafana https://review.opendev.org/74822315:20
slaweqas we are missing it there15:20
slaweqexcept that, it looks pretty good now15:21
slaweqI don't see any major problems with any of the jobs15:22
slaweqmaybe except pep8 failures like:15:22
slaweqhttps://zuul.opendev.org/t/openstack/build/6c8fbf9b97b44139bf1d70b9c85455bb15:22
slaweqdid You saw something similar recently?15:22
bcafarelit may be caused by recent pylint bump (so existing reviews can start to fail pep8)15:23
ralonsohslaweq, if I'm not wrong15:24
ralonsohthis is when you implement a DictModel15:24
ralonsohyou need to define the parameters passed to this dict15:24
ralonsoh(very bad description)15:25
slaweqok, so we will need to fix that issue15:25
ralonsohlet me check this patch and I'll try to find what is happening15:25
ralonsohdo you have a patch?15:25
slaweqhttps://review.opendev.org/#/c/715482/21/neutron/agent/linux/dhcp.py15:26
slaweqit failed here15:26
slaweqthose lines were not touched by the patch but file was changed15:26
ralonsohslaweq, ok, I'll debug this today or tomorrow morning15:26
slaweqthx ralonsoh15:27
slaweq#action ralonsoh to check issue with pep8 failures like https://zuul.opendev.org/t/openstack/build/6c8fbf9b97b44139bf1d70b9c85455bb15:27
slaweqthat's all what I have regarding grafana15:27
slaweqdo You have anything else or can we move on?15:28
ralonsohI'm ok15:28
bcafarelall good15:28
slaweqok, lets move on15:28
slaweq#topic Tempest/Scenario15:28
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"15:28
slaweqDue to recent issue https://bugs.launchpad.net/neutron/+bug/1890842 I would like to add neutron-tempest-plugin-api to be running on neutron-lib patches,15:29
openstackLaunchpad bug 1890842 in neutron "API test test_create_port_without_propagate_uplink_status fails with neutron-lib 2.5.0" [Critical,Fix released] - Assigned to Slawek Kaplonski (slaweq)15:29
slaweqPatch proposed https://review.opendev.org/74583015:29
slaweqthis patch has already 3x +215:29
slaweqbut needs +W :)15:29
slaweqcan one of You +W it?15:29
ralonsohI'll do it15:29
slaweqthx a lot15:29
ralonsohand thanks for this patch15:29
slaweqthe other issue which we have is15:29
slaweqhttps://bugs.launchpad.net/neutron/+bug/189201715:29
openstackLaunchpad bug 1892017 in neutron "Neutron server logs are too big in the gate jobs" [High,Fix released] - Assigned to Slawek Kaplonski (slaweq)15:29
slaweqmelwitt reported us that q-svc logs are very big15:30
slaweqI already proposed https://review.opendev.org/#/c/746714/ and it's merged15:30
slaweqthis reduces log file for about 50%15:30
slaweqbut it's still around 40MB15:30
slaweqso infra guys for now disabled indexing of q-svc logs in logstash15:31
ralonsohyeah, the resource extend logging was excesive in this case15:31
slaweqI will try to check there what else we can reduce there15:31
slaweqbut if You have any ideas, feel free to propose patches15:31
ralonsoh(remove debug logs!!)15:31
slaweqralonsoh: yeah15:32
slaweqbut that may make our life harder :P15:32
slaweqnext thing15:32
slaweqralonsoh found and reported today issue https://bugs.launchpad.net/neutron/+bug/189303115:33
openstackLaunchpad bug 1893031 in neutron "[tempest] "test_dns_domain_and_name" is failing 100% of times" [Undecided,New]15:33
slaweqit should be fixed with https://review.opendev.org/#/c/748140/ which is now in the gate15:33
ralonsohcorrect15:33
slaweqfrom other issues I found today one failure of qos test in linuxbridge job15:34
slaweqhttps://fb1e48505d4c8944956b-dc45e57a445c28f373928001a4323ec4.ssl.cf5.rackcdn.com/696926/23/check/neutron-tempest-plugin-scenario-linuxbridge/086d79c/testr_results.html15:34
slaweqdid You saw something similar before?15:34
ralonsohlet me check15:35
ralonsohbytes_per_second = 385961, expected_bw = 19200015:35
ralonsohhmmmm twice the speed15:35
slaweqyes, that's why I raised it here15:36
ralonsohno sorry, I never saw this15:36
slaweqbecause it seems "interesting" for me :)15:36
*** belmoreira has quit IRC15:36
ralonsohand LB is the most stable backend15:36
ralonsoh(I never said that)15:36
ralonsohin QoS15:36
slaweqxD15:37
ralonsohis this the first time you see it?15:37
ralonsohor is this something recurrent?15:37
slaweqyes15:37
ralonsohok15:37
ralonsohI'll save it, just in case15:37
slaweqok15:38
slaweqI will try to look deeper into logs, maybe I will find something interesting there15:39
slaweq#slaweq to check logs of qos failure in LB job https://fb1e48505d4c8944956b-dc45e57a445c28f373928001a4323ec4.ssl.cf5.rackcdn.com/696926/23/check/neutron-tempest-plugin-scenario-linuxbridge/086d79c/testr_results.html15:39
slaweqspeaking about qos and scenario tests15:40
slaweqlong time ago I proposed patch https://review.opendev.org/#/c/721235/15:40
slaweqplease review it when You will have some time15:40
slaweqand that's all from me for today15:40
slaweqperiodic jobs seems to be working fine15:40
slaweqanything else You want to talk about today?15:41
ralonsohone quick question15:41
ralonsohduring those two weeks15:41
ralonsohwith the oslo.privsep change (un-monkey patching the daemon(15:41
ralonsohand the latests pyroute2 lib version15:41
ralonsohdid you notice the functional/fullstack tests more stable?15:42
ralonsohin other works15:42
ralonsohwords15:42
ralonsohdid you see timeouts?15:42
slaweqlooking at http://grafana.openstack.org/d/Hj5IHcSmz/neutron-failure-rate?viewPanel=24&orgId=1&from=now-30d&to=now I don't think it is more stable than it was15:42
slaweqmaybe slightly better15:43
slaweqfullstack seems to be pretty good recently15:43
ralonsohyes, a 0.001% better15:43
ralonsohhehehehe15:43
slaweq:)15:43
bcafarel:)15:43
ralonsohonce we have George15:44
slaweqbut even if it's 0.001% better, it's step in good direction15:44
ralonsohwe can think about moving some fullstack tests to George15:44
slaweqyes, I was reviewing George patches today15:44
ralonsohusing containers will help to isolate some noisy tests15:44
slaweqlooks good and very interesting15:44
ralonsoha lot!!15:44
ralonsohthat's what fullstack test should have been implemented15:44
ralonsohbut this is easy to say this now15:44
slaweqyes15:44
slaweqok, if You don't have anything else for today, lets finish this meeting earlier15:46
slaweqthx for attending15:46
ralonsohbye!15:46
slaweq#endmeeting15:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:46
slaweqo/15:46
openstackMeeting ended Wed Aug 26 15:46:44 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-08-26-15.00.html15:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-08-26-15.00.txt15:46
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-08-26-15.00.log.html15:46
bcafarelo/15:47
lajoskatonaBye15:47
toskyups, I missed the last minute15:47
slaweqtosky: hi15:48
slaweqtosky: do You want to discuss something specific?15:48
slaweqtosky: regarding migration to zuulv3, I'm still working on neutron-grenade-ovn job but I hope it will be ready soon15:48
slaweqand regaring networking-midonet, I'm still waiting for info from someone who wanted to maintain the project but it doesn't seems like he will be able to do that15:49
slaweqso probably we will simply drop those midonet legacy jobs soon15:49
slaweqtosky: and that's all update which I have regarding this15:50
toskyand the 3 jobs in openstack-zuul-jobs?15:50
slaweqtosky: those I didn't touch yet15:50
slaweqsorry15:50
toskylet's jump on the neutron channel maybe15:50
slaweqsure15:50
toskyI have a question about 2 of them which may help15:50
*** yamamoto has joined #openstack-meeting-315:55
*** yamamoto has quit IRC16:05
*** artom has quit IRC16:10
*** dosaboy has quit IRC16:19
*** dosaboy has joined #openstack-meeting-316:19
*** psachin has quit IRC16:21
*** yamamoto has joined #openstack-meeting-316:38
*** yamamoto has quit IRC16:47
*** lpetrut has joined #openstack-meeting-316:49
*** lpetrut has quit IRC16:49
*** ralonsoh has quit IRC16:51
*** artom has joined #openstack-meeting-316:56
*** bnemec has quit IRC17:18
*** lajoskatona has quit IRC17:27
*** artom has quit IRC17:45
*** belmoreira has joined #openstack-meeting-317:57
*** belmoreira has quit IRC18:30
*** belmoreira has joined #openstack-meeting-318:32
*** e0ne has quit IRC18:34
*** baojg has quit IRC18:52
*** baojg has joined #openstack-meeting-318:53
*** belmoreira has quit IRC19:12
*** e0ne has joined #openstack-meeting-319:18
*** tosky has quit IRC19:38
*** artom has joined #openstack-meeting-319:55
*** e0ne has quit IRC19:58
*** bnemec has joined #openstack-meeting-320:40
*** yamamoto has joined #openstack-meeting-320:44
*** yamamoto has quit IRC20:51
*** slaweq has quit IRC21:18
*** bnemec has quit IRC21:42
*** yamamoto has joined #openstack-meeting-321:45
*** bnemec has joined #openstack-meeting-321:52
*** yamamoto has quit IRC22:00
*** raildo_ has joined #openstack-meeting-322:01
*** raildo has quit IRC22:04
*** bnemec has quit IRC22:09
*** bnemec has joined #openstack-meeting-322:21
*** bnemec has quit IRC22:44
*** bnemec has joined #openstack-meeting-322:48
*** bnemec has quit IRC22:54
*** yamamoto has joined #openstack-meeting-323:16
*** baojg has quit IRC23:21
*** bnemec has joined #openstack-meeting-323:21
*** baojg has joined #openstack-meeting-323:22
*** bnemec has quit IRC23:28
*** bnemec has joined #openstack-meeting-323:50

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