Wednesday, 2020-06-24

*** jamesmcarthur has joined #openstack-meeting-300:30
*** jamesmcarthur has quit IRC00:50
*** jamesmcarthur has joined #openstack-meeting-300:51
*** jamesmcarthur has quit IRC00:58
*** diablo_rojo has quit IRC01:01
*** jamesmcarthur has joined #openstack-meeting-301:14
*** jamesmcarthur has quit IRC01:23
*** markvoelker has joined #openstack-meeting-301:30
*** markvoelker has quit IRC01:35
*** yamamoto has joined #openstack-meeting-301:40
*** jamesmcarthur has joined #openstack-meeting-301:42
*** jamesmcarthur has quit IRC01:50
*** yamamoto has quit IRC02:04
*** jamesmcarthur has joined #openstack-meeting-302:11
*** jamesmcarthur has quit IRC02:11
*** jamesmcarthur has joined #openstack-meeting-302:11
*** yamamoto has joined #openstack-meeting-302:37
*** jamesmcarthur has quit IRC02:57
*** huyupeng has joined #openstack-meeting-303:01
huyupengwill large scale meeting be held at CST 16:00 today ?03:02
*** jamesmcarthur has joined #openstack-meeting-303:02
*** artom has joined #openstack-meeting-303:07
*** markvoelker has joined #openstack-meeting-303:31
*** markvoelker has quit IRC03:36
*** huyupeng has quit IRC03:36
*** psachin has joined #openstack-meeting-303:43
*** jamesmcarthur has quit IRC04:31
*** markvoelker has joined #openstack-meeting-304:34
*** jamesmcarthur has joined #openstack-meeting-304:37
*** markvoelker has quit IRC04:39
*** apetrich has quit IRC04:43
*** jamesmcarthur has quit IRC04:58
*** jamesmcarthur has joined #openstack-meeting-304:58
*** jamesmcarthur has quit IRC05:04
*** links has joined #openstack-meeting-305:19
*** jamesmcarthur has joined #openstack-meeting-305:33
*** jamesmcarthur has quit IRC05:42
*** huyupeng has joined #openstack-meeting-306:09
*** slaweq_ has joined #openstack-meeting-306:12
*** jamesmcarthur has joined #openstack-meeting-306:13
*** slaweq has quit IRC06:13
*** huyupeng has quit IRC06:14
*** markvoelker has joined #openstack-meeting-306:14
*** markvoelker has quit IRC06:20
*** jamesmcarthur has quit IRC06:22
*** ralonsoh has joined #openstack-meeting-306:55
*** huyupeng has joined #openstack-meeting-307:21
*** maciejjozefczyk has joined #openstack-meeting-307:29
*** belmoreira has joined #openstack-meeting-307:49
*** slaweq_ is now known as slaweq07:49
ttxhuyupeng: we'll meet starting in 10 minutes yes07:50
*** brinzhang_ has joined #openstack-meeting-307:53
*** weichch has joined #openstack-meeting-307:57
ttx#startmeeting large_scale_sig08:00
openstackMeeting started Wed Jun 24 08:00:02 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
ttx#topic Rollcall08:00
openstackThe meeting name has been set to 'large_scale_sig'08:00
*** openstack changes topic to "Rollcall (Meeting topic: large_scale_sig)"08:00
ttxWho is here for the Large Scale SIG meeting ?08:00
amorinhello!08:00
ttxbelmoreira: ping08:00
belmoreirao/08:00
belmoreirattx: thanks for the ping08:01
ttxhuyupeng: hi!08:01
huyupenghello08:01
ttxhuyupeng: first time joining?08:01
huyupengyes08:01
brinzhang_\o08:02
ttxhuyupeng: care to introduce yourself, and let us know what you're interested in?08:02
ttxOr we can jump right in today's meeting agenda:08:03
ttx#link https://etherpad.openstack.org/p/large-scale-sig-meeting08:03
huyupengok, i am intersted in concurrency, resource utilize , data plane performance when we deploy large scale openstack cloud08:04
ttxhuyupeng: sounds like you found the right group to discuss it. I think those are concerns that the group shares08:04
ttx#topic 'Large scale operations' OpenDev event next week08:04
*** openstack changes topic to "'Large scale operations' OpenDev event next week (Meeting topic: large_scale_sig)"08:05
ttx#link https://www.openstack.org/events/opendev-2020/08:05
ttxAre y'all ready for the event next week?08:05
ttxRemember that our goal is to start new discussions, and motivate new organizations to engage publicly08:05
ttxThe Large Scale SIG should be used to continue those discussions, we don't want this to be a one-off thing without follow-up08:05
ttxSo the idea will be to heavily promote the SIG during all those discussions08:06
ttxWe should point to our wiki page08:06
*** pandaboy has joined #openstack-meeting-308:06
ttx#link https://wiki.openstack.org/wiki/Large_Scale_SIG08:06
ttxWe should also point to our next meeting, July 8, 8utc on #openstack-meeting-308:06
ttxAnd also to the meeting etherpad for people to add items to the agenda.08:06
ttxbelmoreira: Anything else we need to prepare before next week event?08:06
belmoreirawe have the "Upgrades" session on Monday. It would be great to have all your experience there for discussion08:07
*** belmoreira has quit IRC08:08
*** belmoreira has joined #openstack-meeting-308:09
ttxAlso don;t forget to register, it's free08:09
huyupengi care about how rabbitmq behavie when there are a lot client publish message and receive message. how to tunning the rabbitmq08:09
belmoreirasorry got disconnected... not sure if you got my msg08:09
belmoreirawe have the "Upgrades" session on Monday. It would be great to have all your experience there for discussion08:09
amorinbelmoreira: ack08:09
amorinhuyupeng: we all struggle on rabbitmq tuning :p08:10
ttxhuyupeng: we identified this as a scaling bottleneck too. We are working to instrument oslo.messaging to get better data08:10
ttxin a new library called oslo.metrics08:10
ttxwe'll talk about it in a minute08:10
ttx#topic Progress on "Documenting large scale operations" goal08:10
*** openstack changes topic to "Progress on "Documenting large scale operations" goal (Meeting topic: large_scale_sig)"08:10
ttx#link https://etherpad.openstack.org/p/large-scale-sig-documentation08:10
ttxFor the newcomers, this is one of our current goals for the SIG - produce better documentation to help operators setting up large deployments.08:10
ttxIn particular, documenting better configuration values when you start hitting issues with default values at a certain scale08:11
ttxamorin has been leading that effort08:11
amorinI havn't be able to move forward on that topic in the past 2 weeks08:11
ttxOK I'll push the action item back08:11
amorinso if we can copy back my action,08:11
ttx#action amorin to add some meat to the wiki page before we push the Nova doc patch further08:11
amorinthanks08:11
ttxWe also had a TODO for all to describe briefly how you solved metrics/billing in your deployment08:11
ttxBut not much contribution to that yet08:11
amorincompletely forgot about that08:12
ttxhuyupeng: one objective of the SIG is to share experience08:12
amorindo we have a etherpad to fill?08:12
ttxlike how various groups solved common problems08:12
ttxI added it into https://etherpad.openstack.org/p/large-scale-sig-documentation08:12
amorinack08:12
ttxfeel free to drop a line there08:12
ttxI'll keep that work item open too08:13
ttx#action all to describe briefly how you solved metrics/billing in your deployment in https://etherpad.openstack.org/p/large-scale-sig-documentation08:13
ttxThere seems to be a lot of custom solution in that space, which points to shortcomings in the openstack services offering08:13
ttxAnything else on this topic?08:14
ttx#topic Progress on "Scaling within one cluster" goal08:15
*** openstack changes topic to "Progress on "Scaling within one cluster" goal (Meeting topic: large_scale_sig)"08:15
ttx#link https://etherpad.openstack.org/p/large-scale-sig-cluster-scaling08:15
ttxFor the newcomers, this is the other current goal of the SIG - identify, measure and push back common scaling limitations within one cluster08:15
ttxLike RabbitMQ starting to fall off first08:15
*** markvoelker has joined #openstack-meeting-308:16
ttxOne key effort within that goal is to work on bringing LINE's work on instrumenting oslo.messaging into upstream OpenStack08:16
ttxI had a TODO on solving merge conflict and push initial oslo.metrics code in08:16
ttxIt's now in at: https://opendev.org/openstack/oslo.metrics/08:16
ttxIt's mostly at POC stage, but would be great if this group could look it up and tell us if that sounds like a good idea, and how to improve it08:17
ttxWe also had a bunch of patches in to make the code more OpenStacky, thanks to hberaud08:17
ttxsmcginnis and I did the reviews.08:17
ttxI think for the more feature-oriented reviews coming in the future, it would be good to have one of the original authors from LINE in the core review team for oslo-metrics08:17
ttxI'll try to see with masahito if he would be interested in being added08:17
ttxThe next step will be to add basic tests so that we are reasonably confident we do not introduce regressions08:18
ttxI suspect masahito will mention it next week during the Opendev event08:18
*** jamesmcarthur has joined #openstack-meeting-308:18
ttxAnything else on that topic?08:19
huyupengdoes oslo.metrics has something to do with rabbitmq tunning ?08:19
ttxyes, let me point to teh presentation LINE did at the Summit in Shanghai08:20
*** markvoelker has quit IRC08:21
ttxhttps://www.openstack.org/videos/shanghai-2019/how-we-used-rabbitmq-in-wrong-way-at-a-scale08:21
ttxThat will give you the background08:21
ttx#topic Large Scale SIG slide for OpenStack 10th birthday campaign08:21
*** openstack changes topic to "Large Scale SIG slide for OpenStack 10th birthday campaign (Meeting topic: large_scale_sig)"08:21
ttxHelena on the OSF staff reached out to SIG with the following information:08:21
huyupengthanks, i will see later08:21
ttx"OpenStack will be turning 10 years old in less than a month! We are sending out a slide deck to the event organizers who are organizing the 10 years of OpenStack celebration. For this slide deck, is there anything about the Large Scale SIG you would like to include?"08:21
ttxI was thinking we could make a slide with high-level goals for the SIG and pointers to our meeting time08:22
ttxAnyone interested in working on that? Or I can make a draft and propose it next meeting08:22
ttx#action ttx to produce a draft of the 10th birthday slide for the SIG08:22
*** jamesmcarthur has quit IRC08:23
ttxhuyupeng: in the etherpad links I provided above, you will find other ways to get involved in those SIG goals, like providing scaling stories08:23
ttxScaling stories are accounts of scaling experiences in your deployment -- what broke first, how did it break, and how you moved past it08:24
huyupengok,copy that08:24
ttxWe hope to find common pain points this way (RabbitMQ being an obvious one)08:24
ttxWe document those in https://etherpad.openstack.org/p/scaling-stories08:25
ttxand then copy them to https://wiki.openstack.org/wiki/Large_Scale_Scaling_Stories for long-term storage08:25
ttxWe hope to have more starting next week after the Opendev event!08:25
ttx#topic Next meeting08:26
*** openstack changes topic to "Next meeting (Meeting topic: large_scale_sig)"08:26
*** pandaboy has quit IRC08:26
ttxNext meeting in two weeks... That's the week just after the Opendev event, so if we get contacts of people excited to join the SIG, we can strike that iron while it's hot.08:26
ttx#info next meeting: Jul 8, 8:00UTC08:26
amorinok08:26
ttxAnything else before we close ?08:26
ttxIf there is a topic you want to discuss next time, make sure to add it in advance to the meeting agenda on https://etherpad.opendev.org/p/large-scale-sig-meeting !08:27
ttxAlright, if nothing else for today, have a great day, and hope to see you all virtually at Opendev next week08:28
ttxThanks everyone!08:28
ttx#endmeeting08:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:28
openstackMeeting ended Wed Jun 24 08:28:55 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-06-24-08.00.html08:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-06-24-08.00.txt08:28
openstackLog:            http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-06-24-08.00.log.html08:29
amorinthanks, bye08:29
*** mdelavergne has joined #openstack-meeting-308:33
*** weichch has quit IRC08:42
*** apetrich has joined #openstack-meeting-308:43
*** huyupeng has quit IRC08:45
*** e0ne has joined #openstack-meeting-309:23
*** brinzhang_ has quit IRC09:52
*** markvoelker has joined #openstack-meeting-310:05
*** markvoelker has quit IRC10:09
*** jamesmcarthur has joined #openstack-meeting-310:20
*** jamesmcarthur has quit IRC10:32
*** psachin has quit IRC10:57
*** raildo has joined #openstack-meeting-311:21
*** artom has quit IRC11:35
*** mdelavergne has quit IRC11:49
*** markvoelker has joined #openstack-meeting-311:55
*** markvoelker has quit IRC11:59
*** jamesmcarthur has joined #openstack-meeting-312:29
*** jamesmcarthur has quit IRC12:34
*** liuyulong has joined #openstack-meeting-314:06
*** jamesmcarthur has joined #openstack-meeting-314:15
*** links has quit IRC14:38
*** jamesmcarthur has quit IRC14:54
*** jamesmcarthur has joined #openstack-meeting-314:54
slaweq#startmeeting neutron_ci15:00
openstackMeeting started Wed Jun 24 15:00:27 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
slaweqhi15:00
openstackThe meeting name has been set to 'neutron_ci'15:00
ralonsohhi15:00
bcafarelhello15:01
slaweqfirst of all15:01
slaweq#link  http://grafana.openstack.org/dashboard/db/neutron-failure-rate15:01
*** lajoskatona has joined #openstack-meeting-315:01
slaweqplease open now to have it ready for later :)15:02
lajoskatonao/15:02
slaweqok, lets start15:03
maciejjozefczyk\o15:03
slaweq#topic Actions from previous meetings15:03
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"15:03
slaweqwe have only one action from last week15:03
slaweqslaweq to add additional logging for fullstack's firewall tests15:03
slaweq    I found the issue again in https://zuul.opendev.org/t/openstack/build/c5451e9e66fe4c14b2a09339a77fc44915:04
slaweq    After checking it seems for me that failure was at the beginning of the test, when connectivity with ncat was checked15:04
slaweq    I proposed patch https://review.opendev.org/#/c/737741/ for now.15:04
slaweq    After that lets see what will happen more15:04
njohnstono/15:04
slaweqthat's all update from me about this15:05
slaweq#topic Stadium projects15:05
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"15:05
slaweqI don't have any updates about stadium projects today15:05
slaweqbut maybe You have something15:05
lajoskatonanothing special from me, but if you have time please look there for things to review :-)15:06
bcafarelnot from me, we had enough CI trouble in neutron itself to keep busy15:06
njohnstonnothing for me either15:06
slaweqok, sure lajoskatona I will check list of opened patches in stadium projects15:06
slaweqok, so next topic15:06
slaweq#topic Stable branches15:07
*** openstack changes topic to "Stable branches (Meeting topic: neutron_ci)"15:07
slaweqUssuri dashboard: http://grafana.openstack.org/d/pM54U-Kiz/neutron-failure-rate-previous-stable-release?orgId=115:07
slaweqTrain dashboard: http://grafana.openstack.org/d/dCFVU-Kik/neutron-failure-rate-older-stable-release?orgId=115:07
slaweqfor ussuri and train it seems that it works fine now15:07
lajoskatonaslaweq: thanks15:07
slaweqbut for older releases, like rocky and queens, I think we still have uwsgi issue15:07
slaweqbcafarel: are You aware of it?15:07
slaweqI got many failures e.g. on https://review.opendev.org/#/c/737703/ today15:07
bcafarelyes for EM branches we have lingering issue with grenade jobs ( gmann mentioned them in recent mail update)15:08
bcafarelhttps://review.opendev.org/737414 should workaround it for the time being15:08
bcafarelonce it works, and backported to older branches15:08
slaweqbcafarel: but it's only for grenade15:10
slaweqand in my patch I saw failures in all tempest jobs too15:10
slaweqbasicaly everything except UT and pep8 was red15:10
bcafareloh sigh15:10
bcafarelI did not check rocky thoroughly yet, still on stein :/15:11
slaweqI see error like: "ls: cannot access 'uwsgi*': No such file or directory" in devstack log15:11
*** jamesmcarthur has quit IRC15:12
bcafarelack there was mention on uwsgi + rocky and older still WIP http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015558.html15:13
slaweqbcafarel: do You have cycles to check that this week?15:13
*** jamesmcarthur has joined #openstack-meeting-315:13
bcafarelslaweq: yes, at least to get some up-to-date status on it!15:13
slaweqthx15:13
slaweq#action bcafarel to check gate status on rocky and queens (uwsgi problem)15:13
slaweqok15:14
slaweqlets move on15:14
slaweq#topic Grafana15:14
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"15:14
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate15:14
slaweqin master branch it looks ok this week IMO15:15
njohnston+115:17
slaweqso lets talk about some issues in specific jobs15:18
slaweq#topic fullstack/functional15:18
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"15:18
slaweqfirst functional tests15:18
slaweqI found today some db migration errors (again), like https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_ec3/736269/3/check/neutron-functional-with-uwsgi/ec30046/testr_results.html15:18
slaweqralonsoh: is it something what You want to address with Your db migration script changes?15:18
ralonsohyes15:19
ralonsohthose errors in test_walk_versions15:19
ralonsohand test_has_offline_migrations_all_heads_upgraded15:19
slaweqok15:19
slaweqin general I think that those failures are due to slow node where it was run15:20
slaweqbut will be good if we can get rid of at least some of them15:20
slaweqI also have other issue15:21
slaweqhttps://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_63a/711425/11/check/neutron-functional/63ac4ca/testr_results.html15:21
slaweqthis seems for me like somethig related to our privileged ip_lib or pyroute215:21
slaweqas there are issues that interfaces are not found in namespace None15:22
slaweqand there are also issue with _check_bridge_datapath_id() method in tests there15:22
ralonsohwell, maybe that's correct and the interface was not created15:22
*** jamesmcarthur has quit IRC15:23
slaweqralonsoh: can be15:23
slaweqso at least we should probably fix exception message IMO15:24
maciejjozefczykthere is also this failure test_ovsdb_monitor.TestNBDbMonitorOverTcp.test_floatingip_mac_bindings (IndexError: list index out of range)... I can take a look on that one15:24
slaweqor not, nvm :)15:24
slaweqthx maciejjozefczyk15:24
ralonsohI can take a look at the bridge.get_datapath_id problem15:25
ralonsohif I  have some time this week15:25
slaweqthx ralonsoh15:25
slaweq#action maciejjozefczyk will check test_ovsdb_monitor.TestNBDbMonitorOverTcp.test_floatingip_mac_bindings failiure in https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_63a/711425/11/check/neutron-functional/63ac4ca/testr_results.html15:25
slaweq#action ralonsoh will check get_datapath_id issues in https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_63a/711425/11/check/neutron-functional/63ac4ca/testr_results.htm15:26
slaweq#undo15:26
openstackRemoving item from minutes: #action ralonsoh will check get_datapath_id issues in https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_63a/711425/11/check/neutron-functional/63ac4ca/testr_results.htm15:26
slaweq#action ralonsoh will check get_datapath_id issues in https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_63a/711425/11/check/neutron-functional/63ac4ca/testr_results.html15:26
slaweqI will check this errors with non existing devices15:27
slaweq#action slaweq will check errors with non existing interface in https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_63a/711425/11/check/neutron-functional/63ac4ca/testr_results.html15:28
slaweqok, lets move on15:28
slaweq#topic Tempest/Scenario15:28
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"15:28
slaweqin scenario tests I found one interesting issue this week15:29
slaweqit happend only once I think but maybe worth to deeper look15:29
slaweqhttps://11b28b714aaa0f2eaa01-115c1089095738e3e088969e8724f0ca.ssl.cf1.rackcdn.com/712640/9/check/neutron-tempest-plugin-scenario-openvswitch/2ad316a/testr_results.html15:29
slaweqerror with address already allocated in subnet15:29
slaweqmaybe some bug in tests?15:29
ralonsohdidn't I sent a patch for this?15:30
ralonsohsend*15:30
slaweqralonsoh: I don't remember15:30
ralonsoh(checking)15:30
slaweqahh, right15:30
slaweqI think that now I remember15:30
ralonsohhttps://review.opendev.org/#/c/731267/15:30
slaweqok, this failure was before Your patch was merged15:31
slaweqso we should be good now15:31
slaweqthx ralonsoh15:31
ralonsohahhh ok perfect15:31
bcafarelralonsoh: fixing CI issues before slaweq complains about them, nice!15:32
ralonsohhahaha15:32
slaweqhaha15:32
slaweqtrue15:32
maciejjozefczykralonsoh++ :D15:32
slaweqok, so one last topic for today15:32
slaweq#topic Periodic15:32
*** openstack changes topic to "Periodic (Meeting topic: neutron_ci)"15:32
slaweqall except one job looks fine there15:33
slaweqbut neutron-ovn-tempest-ovs-master-fedora is broken again15:33
maciejjozefczyksigh15:33
slaweqand it's broken on compilation of ovs15:33
slaweqhttps://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_b03/periodic/opendev.org/openstack/neutron/master/neutron-ovn-tempest-ovs-master-fedora/b039158/job-output.txt15:33
*** yamamoto has quit IRC15:34
slaweqmaciejjozefczyk: can You take a look into that one?15:34
maciejjozefczykslaweq, yes15:35
slaweqthx15:35
maciejjozefczykslaweq, I fixed that failure some time ago and it is failing again.. strange15:35
maciejjozefczykI'll take a closer look on that, thanks15:35
slaweq#action maciejjozefczyk to check failing neutron-ovn-tempest-ovs-master-fedora periodic job15:35
slaweqthx a lot15:35
slaweqok, that's all from me today15:35
slaweq(that was fast ;))15:35
slaweqanything else You want to discuss today?15:36
ralonsohno thanks15:36
slaweqif not, I think I can give You back about 20 minutes today :)15:37
bcafarelI just realized "stadium projects" section we had also community goals mixed in15:37
bcafarelshort update on that I started to fill https://etherpad.opendev.org/p/neutron-victoria-switch_to_focal15:37
bcafarelhopefully it will be more complete by next week :)15:38
slaweqthx bcafarel15:38
lajoskatonabcafarel: good point,15:38
slaweqbtw, speaking about focal, it seems from https://review.opendev.org/#/c/737370/ that neutron is running fine there15:38
lajoskatonaI checked with odl but I got weird failures, and thought to wait some time till the waves go down :-)15:38
slaweqthere are some problems realated to cinder in tempest jobs15:39
lajoskatonabcafarel, slaweq: for odl I had this:  https://review.opendev.org/73670315:40
bcafarellajoskatona: indeed, main patches in devstack and tempest should clear out most of issues - and most of our jobs will inherit directly15:40
lajoskatonaand it fails with nodeset not found or similar15:40
lajoskatonabcafarel: that was my feeling as well :-)15:41
bcafarellajoskatona: or depending on https://review.opendev.org/734700 should help to get the nodes and job definitions15:41
slaweqthx bcafarel and lajoskatona15:41
lajoskatonabcafarel: thanks, I do a try with that, the wf -1 though a little frightening15:42
lajoskatonabut that's perhaps just some timing from gmann15:42
bcafarelyes it is in "heavy progress" there15:44
bcafarelthough just for inheriting the nodeset it should be safe enough for testing15:44
gmannyeah, 734700 is right to test. i was waiting for gate result there and i will announce the same on ML also.15:44
lajoskatonagmann, bcafarel: thanks, I check it15:44
slaweqgmann: in our tests in https://review.opendev.org/#/c/737370/ I saw some cinder related failures15:45
slaweqgmann: do You know if cinder team is aware of them?15:45
gmannbcafarel: if your job override nodeset then you need to change otherwise 734700 can take care of devstack base job nodeset switch to focal15:45
slaweqor maybe I should open LP for them?15:45
gmannslaweq: current known bug is this https://bugs.launchpad.net/nova/+bug/188252115:45
openstackLaunchpad bug 1882521 in OpenStack Compute (nova) "Failing device detachments on Focal" [Undecided,New]15:45
bcafarelgmann: ack I am making a list of jobs that will need some action (more than just 734700)15:46
gmannwhich is volume detach issue but i have not checked your patch failure15:46
gmannbcafarel: +115:46
slaweqgmann: seems like the same one15:47
slaweqthx15:47
slaweqok, I think we can finish meeting now15:49
slaweqthx for attending15:49
maciejjozefczyk\o15:49
slaweqand see You o/15:49
slaweq#endmeeting15:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:50
openstackMeeting ended Wed Jun 24 15:49:59 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:50
lajoskatonaBye15:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-06-24-15.00.html15:50
ralonsohbyw15:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-06-24-15.00.txt15:50
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-06-24-15.00.log.html15:50
*** lajoskatona has left #openstack-meeting-315:50
bcafarelo/15:50
*** ricolin has joined #openstack-meeting-315:55
*** liuyulong has quit IRC15:56
*** yamamoto has joined #openstack-meeting-316:04
*** yamamoto has quit IRC16:10
*** markvoelker has joined #openstack-meeting-316:24
*** markvoelker has quit IRC16:28
*** markvoelker has joined #openstack-meeting-317:09
*** markvoelker has quit IRC17:14
*** ricolin has quit IRC17:20
*** apetrich has quit IRC17:20
*** apetrich has joined #openstack-meeting-317:24
*** e0ne has quit IRC17:42
*** apetrich has quit IRC18:15
*** apetrich has joined #openstack-meeting-318:16
*** diablo_rojo has joined #openstack-meeting-318:23
*** belmoreira has quit IRC18:33
*** irclogbot_0 has quit IRC18:34
*** irclogbot_3 has joined #openstack-meeting-318:38
*** yamamoto has joined #openstack-meeting-318:53
*** yamamoto has quit IRC18:58
*** markvoelker has joined #openstack-meeting-319:10
*** markvoelker has quit IRC19:15
*** ralonsoh has quit IRC19:26
*** markvoelker has joined #openstack-meeting-319:33
*** markvoelker has quit IRC19:38
*** markvoelker has joined #openstack-meeting-319:59
*** markvoelker has quit IRC20:04
*** belmoreira has joined #openstack-meeting-320:21
*** belmoreira has quit IRC20:26
*** maciejjozefczyk has quit IRC21:08
*** raildo has quit IRC21:09
*** slaweq has quit IRC21:36
*** slaweq has joined #openstack-meeting-321:46
*** slaweq has quit IRC21:52
*** markvoelker has joined #openstack-meeting-322:00
*** markvoelker has quit IRC22:05
*** markvoelker has joined #openstack-meeting-322:49
*** markvoelker has quit IRC22:54
*** markvoelker has joined #openstack-meeting-323:37
*** markvoelker has quit IRC23:47

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