Tuesday, 2021-06-08

*** bhagyashris_ has joined #openstack-infra01:01
*** bhagyashris has quit IRC01:09
*** rlandy has quit IRC02:45
*** ykarel|away has joined #openstack-infra03:48
*** ykarel_ has joined #openstack-infra04:15
*** ykarel|away has quit IRC04:21
*** ykarel_ is now known as ykarel04:25
*** opendevreview has quit IRC04:26
*** thiagop has joined #openstack-infra04:35
*** outbrito has quit IRC04:35
*** vishalmanchanda has joined #openstack-infra04:39
*** abhishekk has joined #openstack-infra04:55
*** bhagyashris_ is now known as bhagyashris06:08
*** david-lyle has joined #openstack-infra06:20
*** dklyle has quit IRC06:20
*** soniya29 has joined #openstack-infra06:24
*** soniya has joined #openstack-infra06:27
*** soniya29 has quit IRC06:33
*** Adri2000 has joined #openstack-infra06:48
*** david-lyle has quit IRC06:50
*** odyssey4me has joined #openstack-infra06:59
*** odyssey4me has quit IRC07:00
*** odyssey4me has joined #openstack-infra07:01
*** ykarel_ has joined #openstack-infra07:01
*** ykarel has quit IRC07:03
*** andrewbonney has joined #openstack-infra07:29
*** rpittau|afk is now known as rpittau07:30
*** jpena|off is now known as jpena07:31
*** soniya29 has joined #openstack-infra07:33
*** soniya has quit IRC07:39
*** soniya has joined #openstack-infra07:42
*** soniya29 has quit IRC07:48
*** elodilles is now known as elodilles_pto07:55
*** yasufum has joined #openstack-infra07:59
*** ykarel_ is now known as ykarel08:00
*** derekh has joined #openstack-infra08:23
*** lucasagomes has joined #openstack-infra08:25
*** tosky has joined #openstack-infra08:39
*** lucasagomes has quit IRC08:41
*** gfidente has joined #openstack-infra08:44
*** lucasagomes has joined #openstack-infra08:53
*** lucasagomes has quit IRC09:03
*** lucasagomes has joined #openstack-infra09:25
*** abhishekk has quit IRC09:27
*** lucasagomes has quit IRC09:38
*** lucasagomes has joined #openstack-infra09:39
*** soniya29 has joined #openstack-infra09:59
*** lucasagomes has quit IRC10:01
*** soniya has quit IRC10:03
*** yamak16 has quit IRC10:08
*** lucasagomes has joined #openstack-infra10:18
*** lucasagomes has quit IRC10:29
*** lucasagomes has joined #openstack-infra11:00
*** lucasagomes has quit IRC11:08
*** odyssey4me has quit IRC11:16
*** jpena is now known as jpena|lunch11:31
*** rlandy has joined #openstack-infra11:45
*** odyssey4me has joined #openstack-infra12:01
*** jpena|lunch is now known as jpena12:31
*** soniya has joined #openstack-infra12:48
*** soniya29 has quit IRC12:54
*** lucasagomes has joined #openstack-infra13:23
*** abhishekk has joined #openstack-infra13:34
*** elodilles_pto has quit IRC13:41
*** elodilles has joined #openstack-infra13:43
*** lucasagomes has quit IRC13:59
*** lucasagomes has joined #openstack-infra14:03
*** opendevreview has joined #openstack-infra14:05
opendevreviewDmitrii Shcherbakov proposed openstack/project-config master: Add label-Verified to snaps.config  https://review.opendev.org/c/openstack/project-config/+/79534114:05
*** lucasagomes has quit IRC14:18
*** vishalmanchanda has quit IRC14:18
*** lucasagomes has joined #openstack-infra14:21
*** philroche has joined #openstack-infra14:31
*** soniya has quit IRC14:36
ade_leeykarel, fungi hey -- I'm seeing this on centos-8-stream jobs .. https://zuul.opendev.org/t/openstack/build/8c01115fed714a45ad922f5263e58bc8/console14:40
*** ykarel has quit IRC14:41
ade_leelooks like its failing at trying to connect to mysql?14:41
ade_leeI originally thought it might have something to do with fips -- but its not even getting to that point14:42
*** ykarel has joined #openstack-infra14:42
ade_leeykarel, did you see above ?14:43
ade_leelooks like its failing at trying to connect to mysql?14:43
ade_leeI originally thought it might have something to do with fips -- but its not even getting to that point14:43
ykarelade_lee, no /me didn't see, i had some network issues14:44
ade_leeykarel, ack -- I was asking about https://zuul.opendev.org/t/openstack/build/8c01115fed714a45ad922f5263e58bc8/console14:45
ade_leeykarel, I'm seeing this on centos-8-stream jobs14:45
*** ykarel has quit IRC14:46
fungilooks like ykarel is having connectivity issues14:46
fungier, still having i mean14:47
*** ykarel has joined #openstack-infra14:47
opendevreviewDmitrii Shcherbakov proposed openstack/project-config master: Add label-Verified to snaps.config  https://review.opendev.org/c/openstack/project-config/+/79534114:48
fungiade_lee: the log at least seems to confirm that the mariadb-server package was installed on the system prior to that14:50
*** dklyle has joined #openstack-infra14:50
fungidoes something maybe need to start the service?14:50
ade_leefungi, yeah maybe .. let me see if I can throw up a patch to do that -- I just wanted to check if this was a known issue14:52
fungiade_lee: also when did the failures start? we had a quota issue on our centos mirror volume which probably resulted in using packages from 2021-06-03 up through the middle of yesterday, so there's some ~4 days of package updates which happened on the mirror around then14:52
fungiwondering if something changed in how mariadb behaved by default in the latest 8-stream14:53
ade_leefungi, well not sure -- until the last change that fixed the repo problem - ie. moving to centos-stream - the builds had been failing for that first14:53
toskyfungi: re "long while", thanks for clarifying, I was trying to not be too hard as (I think) I was in other parts of that email!14:55
ykarelade_lee, yes seems like mariadb not running, so worth to check on that aspect14:57
ykarelalso doesn't seem that job is collecting system logs14:57
ade_leeykarel, yeah - not sure how to fix that -- maybe it conks out before that gets set up?14:58
ykarelmay be can try attempt local reproducer for this or try node held, that should be more easier i think14:58
ade_leeykarel, what's node held?15:00
ykarelade_lee, you can ask infra for node held, means not to delete the node on which job is running, and can access the node and debug15:06
ykarelbut for this case it looks simpler that mariadb is not running15:06
*** lamt has quit IRC15:06
ykarelmariadb do not start automatically15:06
*** lamt has joined #openstack-infra15:06
ykarelso u need to start mariadb.service explicitly15:06
ykarelbefore running tools/test-setup.sh15:07
fungiyeah, basically i'd set an autohold for the openstack-tox-functional-py36-fips with change 790536 in the openstack/glance project of zuul's openstack tenant, and the next time it gets a build failure for that it "holds" the node lock so that nodepool won't garbage collect th at build's nodeset15:08
fungiif you decide you need to manually inspect the failing environmen15:08
fungit15:08
ykarelor can hack https://review.opendev.org/c/openstack/glance/+/790536/1/tools/test-setup.sh#17 to start mariadb with sudo systemctl status mariadb.service15:09
ykareljust for testing, as not sure what service name is there in ubuntu or other distros15:09
ade_leeykarel, fungi ok - let me put up a test patch and see if it works15:12
ade_leeshould be quick - this usually fails pretty quickly15:13
*** tdasilva_ has joined #openstack-infra15:17
*** tdasilva has quit IRC15:17
*** thiago__ has joined #openstack-infra15:19
*** tdasilva_ has quit IRC15:19
opendevreviewMerged openstack/project-config master: Add label-Verified to snaps.config  https://review.opendev.org/c/openstack/project-config/+/79534115:21
opendevreviewMerged openstack/project-config master: New Project Request: airship/image-builder  https://review.opendev.org/c/openstack/project-config/+/79511815:31
*** tbrito has joined #openstack-infra15:57
*** thiagop has quit IRC15:57
clarkbfungi: gmann: re the d-g thread do you think that it is worth mentioning we have never required zuul or a specific version of zuul? but in those cases CI systems may need to sort things out from scratch? (I don't want to give the impression we're forcing them to make any particular changes here). Also, what are the risks with handing d-g over to another group? Is it old15:59
clarkbstable branches that still use d-g? should we maybe suggest they fork in that case?16:00
*** d34dh0r53 has joined #openstack-infra16:00
clarkbI mean upgrading to zuulv3 or newer sounds great, but thehy may be running jenkins and not zuul etc16:00
gmannclarkb: for stable branch which is until stable/ussuri (if project has not backported the zuulv3 migration work) we should keep it as it is. i mean under same group16:01
clarkbsounds like a fork would be appropriate if people want to keep it alive for modern development then16:01
gmannclarkb: fungi I am thinking to mark it deprecated and no-fix for master and fix acceptable for stable branch  only16:02
gmannclarkb: yeah16:02
clarkbgmann: d-g doesn't have stable branches, all development is on master16:02
gmanni mean support for stable branch16:02
clarkbbut I guess we can communicate the changes to master are for stable/old on other repos16:02
clarkb++16:02
*** ykarel is now known as ykarel|away16:02
gmannwe should do some official warning or mechanism to stop running it for >stable/wallaby or so16:03
gmanndo you think that is fine now?16:03
gmannthis one especially 'stop running it for >stable/wallaby '16:03
clarkbyes, why don't we add a warning (don't break it and make the situation for those CIs worse) and update the readme that this is maintenance for old branches only16:03
clarkbthen we can also respond to that thread suggesting they fork it if they want to keep using the tool for newer branches16:04
gmannok, so just warning but no hard error16:04
clarkbthat would be my vote16:05
gmannok but in that case anyone asking for fix and fixes for master is hard to deny. but fine i think16:05
clarkbgmann: agreed. If it works without changing anything we won't intentionally break you, but if you need fixes we will -2 those16:06
gmannsure16:06
clarkband we are happy for someone else to fork it and maintain it if they decide that is better for them than updating their CI systems16:06
clarkb(has to be a fork to avoid concerns with old stable branch testing)16:06
gmannand how about deprecation in governance ? I think we can do that16:07
clarkb++16:07
gmannwe would not be able to do in project gate or so as it is branchless but officially marking in governance will help16:08
clarkbbecause once those old stable branches die we can stop the projcet entirely16:08
gmannexactly16:08
clarkbsounds liek a good plan. Do you want to respond to the list with updates after the changes are pushed or would it help if I do that?16:08
fungidoesn't necessarily even need to wait for the old branches to reach eol, in a number of cases we've opted to reduce test coverage in em branches16:09
gmannI can push the change and then you can reply on email. I will push after nova meeting or so16:09
clarkbgmann: sounds good, thanks!16:09
*** ykarel|away has quit IRC16:13
gmannone more thing, on gate testing. as we will be supporting only stable branch, I am thinking to stop master jobs from there and only have stable branch jobs ? which is actually part of deprecation. what you say?16:13
clarkbgmann: ++16:13
gmannok, will do16:14
*** lucasagomes has quit IRC16:15
*** rpittau is now known as rpittau|afk16:31
*** jpena is now known as jpena|off16:33
*** akekane_ has joined #openstack-infra16:34
*** akekane_ has quit IRC16:35
opendevreviewMerged openstack/project-config master: Drop logstash filter jobs  https://review.opendev.org/c/openstack/project-config/+/79271016:37
*** abhishekk has quit IRC16:41
ade_leefungi, are we running postgres too?  restarting mariadb succeeded , but then postgres failed ..16:51
opendevreviewGhanshyam proposed openstack/project-config master: Move devstack-gate jobs list to in-tree  https://review.opendev.org/c/openstack/project-config/+/79537916:51
opendevreviewGhanshyam proposed openstack/devstack-gate master: Move devstack-gate jobs list to in-tree  https://review.opendev.org/c/openstack/devstack-gate/+/79538016:52
fungiade_lee: it's running whatever's in that script in the glance repo16:54
fungiade_lee: https://opendev.org/openstack/glance/src/branch/master/tools/test-setup.sh16:54
fungii assume glance has postgres-specific tests so sets it up to support those16:55
ade_leefungi, ack - trying to restart postgres too now16:55
fungiif glance has dropped their postgres tests, then they should probably clean up references in bindep.txt and tools/test_setup.sh16:55
fungiwould make their jobs faster too16:56
clarkbI think oslo.db has standardized migration testing for mysql and postgres16:56
ade_leefungi, in any case - its seems like restarting mariadb did move us further through the script -- so now we just need to put a restart somewhere16:57
ade_leeand make it non-platform specific16:57
clarkbgmann: will you use topic:"deprecate-devstack-gate" for the governance change too? if so I'll start drafting that email and use a topic lookup link for gerrit links16:58
clarkbade_lee: fungi: note that typically projects don't run unittests on rhel/fedora/centos this means you may run into all sorts of problems doing that conversion16:58
gmannclarkb: initially for governance yes. but later I need to change that to project-update16:58
clarkbalso I'd probably strongly recommend against doing that conversion now because centos8's lifetime is short and centos-8-stream isn't super stable16:58
clarkbubuntu gives you 5 years to run those jobs on which is useful for stable branch lifetime16:59
fungithough for this particular case, i wonder if ubuntu is as well-suited to running fips-centric deployments16:59
clarkbfungi: it may not be, just pointing out that switching wholesale to centos is likely to be problematic longer term17:00
ade_leeclarkb, yup - I'm seeing that this is indeed the case -- the reason I'm doing this is because I wanted to run fips specific tests -17:00
fungiand i probably underestimate the number of usa federal contracts canonical holds17:00
ade_leeclarkb, oh - I'm not thinking of switching out long term - just making them work for the fips tests17:01
ade_leeclarkb, fungi I'm ok with adding some code somewhere that says "if this is centos, restart mariadb and postgres"17:02
ade_leejust need to figure out where17:02
ade_leeI'm seeing the same problem in glance, cinder, nova ..17:03
fungiade_lee: yeah, most projects copied nova's tools/test_setup.sh file, which is why we made it into a defacto-standard with a common job role17:03
fungiade_lee: swift has some platform detection in theirs you could crib from: https://opendev.org/openstack/swift/src/branch/master/tools/test-setup.sh17:04
ade_leefungi, cool - I can do that then.17:05
*** ykarel|away has joined #openstack-infra17:06
ade_leefungi, so better to do in each projects test_setup.sh -- or is there somewhere earlier where we install mariadb and postgres where it would be better to put common code?17:07
fungialso comparing and contrasting nova's and swift's test_setup.sh provides a great example of the flexibility of that approach17:07
ade_leefair enough :)17:07
fungiade_lee: there is no common code around that. basically the test_setup.sh script was settled on as the stopgap for "my project has particular things which need to be done as root in addition to installing distro packages before some tests can be run"17:08
ade_leeok17:08
fungiso for swift, it creates an xfs filesystem to enable some of their file attribute functional testing17:09
fungifor nova, it preconfigures some database servers to support database functional testing17:09
fungibut it's intentionally arbitrary and turing-complete17:09
fungito the job role calling those scripts, they're a black box17:09
fungithe idea being developers can run precisely the same scripts to set up their local development environments17:10
fungiwe could probably find some commonalities between them and abstract them into a centralized library, but then you get into some interesting bootstrapping catch-22s17:11
ade_leefungi, can I get a node hold for https://review.opendev.org/c/openstack/glance/+/790536  ?  I tried restarting postgres - but ran into issues http://paste.openstack.org/show/806465/17:18
ade_leefungi, ah - it seems there is an init scrpt too -- I'll try run that17:23
opendevreviewGhanshyam proposed openstack/devstack-gate master: Add deprecation warning in README file  https://review.opendev.org/c/openstack/devstack-gate/+/79538317:28
clarkbgmann: I need to step out for a few, but I sent the email already and I'll do reviews when I get back17:29
gmannclarkb: thanks. I will work on job things after my lunch.17:29
*** andrewbonney has quit IRC17:32
fungiade_lee: do you still want the autohold or are you trying something else first?17:38
ade_leefungi, yeah - I got further - but I think I'm gonna need to get on a system to actually run things and see why they fail ..17:39
ade_leehttp://paste.openstack.org/show/806466/17:40
ade_leeI suspect I may need to add the zuul user to a postgres group or something maybe17:42
fungiade_lee: seems you have a lot of broken jobs reporting on that change, any one in particular you want the autohold for?17:43
*** ykarel|away has quit IRC17:43
fungiopenstack-tox-functional-py36-fips i guess?17:43
ade_leefungi, https://review.opendev.org/c/openstack/glance/+/790536  - the glance one17:43
ade_leeyup17:43
ade_leeif I fix that one, I can fix the rest (hopefully)17:44
fungiade_lee: the autohold is set, also you can trim out any jobs you don't care about in the .zuul.yaml within your wip change to speed up testing17:45
ade_leefungi, good idea thanks17:46
fungii do that all the time if i'm trying to isolate a problem with a single job, and then restore the .zuul.yaml after i've worked it out before dropping wip state17:46
fungiade_lee: also another option, for future reference, is to just locally boot our test images and try stuff out: https://nb01.opendev.org/images/17:47
ade_leefungi, ack - thanks17:48
ade_leebookmarking now17:48
fungiyou might compare against what's on nb02 if you want to make sure you have the very latest serial for a given label, the image build load is distributed between them at random17:48
fungithey use glean and expect a configdrive, and expect you to supply sshkey metadata17:50
fungibut other than that nothing too special about booting them17:50
fungino metadata server needed. can handle dhcp by default or static network configuration in the configdrive17:51
clarkbif you don't want to set up a config drive you can modify the image to include your ssh key and they will dhcp by default17:52
*** gfidente is now known as gfidente|afk18:02
opendevreviewRajath Av proposed openstack/project-config master: Changes to be committed: modified: zuul.d/projects.yaml Change-Id: Ib712abce33b5f552965be874d9965a24eb7ec105  https://review.opendev.org/c/openstack/project-config/+/79539618:29
opendevreviewRajath Av proposed openstack/project-config master: Changes to be committed: modified: zuul.d/projects.yaml Change-Id: Ib712abce33b5f552965be874d9965a24eb7ec105 Adding this change as networking-infoblox plugin has been migrated to support python3.6  https://review.opendev.org/c/openstack/project-config/+/79539618:30
ade_leefungi, ok -- so how do I get to my node -- will zuul tell me when its done?18:42
opendevreviewRajath Av proposed openstack/project-config master: Changes to be committed: modified: zuul.d/projects.yaml  https://review.opendev.org/c/openstack/project-config/+/79539718:42
clarkbade_lee: zuul will report the ip in its logs when the job fails, but y ouneed one of us to add your ssh key to it before you'll be able to get in. If you can point us to the job lgo when done that is helpful18:42
ade_leeclarkb, ok thanks -- I think its trying three times ..18:43
clarkboh is it failing in pre-run? zuul will only hold the last one18:43
ade_leeyup18:43
opendevreviewRajath Av proposed openstack/project-config master: Changes to be committed: modified: zuul.d/projects.yaml  https://review.opendev.org/c/openstack/project-config/+/79539618:43
opendevreviewRajath Av proposed openstack/project-config master: Changes to be committed: modified: zuul.d/projects.yaml  https://review.opendev.org/c/openstack/project-config/+/79539718:45
fungiade_lee: right, need to wait for that RETRY_LIMIT result to show up18:45
fungiseems wasteful in this particular case, but more generally it helps weed out intermittent failures due to things like network connectivity problems from actual job failures18:46
ade_leefungi, clarkb by the way - if you'll want to review https://review.opendev.org/c/zuul/zuul-jobs/+/788778 - I think it looks pretty good now18:47
ade_leeand we see that one working in the barbican patch -- https://review.opendev.org/c/openstack/barbican/+/76066518:48
ade_leefungi, clarkb not sure where the ip is -- https://zuul.opendev.org/t/openstack/build/607fb96cc15a4daa8c2844aa453455f3/log/job-output.txt18:49
ade_lee 158.69.66.94 ?18:49
ade_leeclarkb, fungi -- my key -- https://github.com/vakwetu.keys18:50
fungiyeah, https://zuul.opendev.org/t/openstack/build/607fb96cc15a4daa8c2844aa453455f3/log/zuul-info/inventory.yaml#1018:52
fungii can't seem to ssh to it though18:54
fungiaha, for some reason the node which was held is 23.253.236.418:55
clarkboh did it hold the first then? I know it only holds one18:57
fungitrying to figure that out, it's node 0025027287 anyway18:57
fungizuul debug log says it was build 3b662e15c3c54f43b44dccb9ca569619 which isn't in the db, maybe it hasn't reported yet?19:02
clarkbthat sounds like it held the first fail which doesn't get recordred otherwise19:03
clarkbneat19:03
fungimmm, interestingly the build history for that job does show "retry" result builds which aren't "retry_limit" though19:03
fungiand those seem to be the earlier builds19:04
fungibut they have different build ids than this one19:04
fungiaha, i think i see what happened. based on timestamps i believe this ran against 790536,4 but that never reported because it was aborted by the upload of 790536,519:12
fungianyway, this node *probably* has what you need, if it doesn't we can reset the trap and recheck when there are no new patchsets getting pushed19:13
ade_leefungi, yeah - it should be fine19:14
fungiade_lee: ssh root@23.253.236.419:14
opendevreviewRajath Av proposed openstack/project-config master: Changes to be committed: modified: zuul.d/projects.yaml  https://review.opendev.org/c/openstack/project-config/+/79539719:14
ade_leefungi, perfect - I'm in - thanks!19:15
ade_leefungi, I'll let you know when I'm done with it19:15
fungimuch obliged19:16
*** zxiiro has quit IRC19:23
fungiclarkb: so, anyway, to summarize, zuul does report the retry builds, but not aborted builds (which is what ended up being held, i guess because an abort counts as a hard failure for the autohold logic?)19:31
clarkbhuh I dind't think it did but your evidecnce seems to support that19:31
fungior more likely this was one which ended in a retry_limit but the buildset itself hadn't reported yet and got aborted19:31
fungiso by that time it had already triggered the hold19:32
*** stevebaker has quit IRC19:33
*** thiago__ is now known as tdasilva19:43
opendevreviewMerged openstack/project-config master: Changes to be committed: modified: zuul.d/projects.yaml  https://review.opendev.org/c/openstack/project-config/+/79539719:55
*** stevebaker has joined #openstack-infra20:19
*** derekh has quit IRC20:48
*** derekh has joined #openstack-infra21:01
*** derekh has quit IRC21:25
*** reed has joined #openstack-infra21:56
gmannclarkb: fungi is there any way to pick the job definition from stable branch (not from master) while running it on master gate?22:24
gmannI was checking if devstack-gate could run the neutron-grenade-multinode job from stable/stein version which is legacy job version not the master one which is zuulv3 native22:25
clarkbI think you may need to use a different job name? and have it fallback to doing the master lookup?22:26
clarkbthe pragma stuff won't work because that applies globally in the tenant making the branches equivalent22:26
clarkbyou maybe able to make a variant that applies to a specific branch?22:26
gmannbut neutron-grenade-multinode job name is same in stable and master in neutron repo22:31
gmannand if i inherit newjob rom 'neutron-grenade-multinode' still I need to add branch variant to master as devstack-gate master gate need to run it so it will pick base job from neutron's master ?22:33
clarkbyes inheritance alone won't do it as it will find the master job22:33
clarkbinstead I think you can add a job on master that overrides the branches that are used when the job runs22:34
clarkbthen that job will be used and run over the branches that you want22:34
gmannclarkb: but override branch using override-checkout is not I want here. I need devstack-gate run legacy version of job 'neutron-grenade-multinode' so that i test the d-g code path22:35
clarkbyes, I'm saying you need to copy the legacy version of the job to master and give it a new name and set the vars to older branches when you do that22:36
clarkbI don't think there is an easier way than that but I could be wrong22:36
clarkbZuul is built around the assumption that you basically never want to do this I think22:36
gmannhumm, copying is one option but maintaining that when it break is another issue instead of using neutron own one.22:37
gmannclarkb: we have legacy tempest job running in devstackl-gate. I was thinking to add one legacy grenade job also (which is not there currently also) for test coverage. but by seeing the copy-only option I am thinking we continue with the testing we have (legacy tempest based job only). what you say?22:39
gmannif somehow d-g is failed with any legacy grenade job then we can fix from the log/debug where it was failing22:39
clarkbgmann: ya I think the legacy tempest jobs are basically a copy paste since they have different names22:39
gmannotherwise preparing grenade legacy job version seems more work22:40
gmannclarkb: yes22:40
clarkband ya fixing things with depends on is probably easiest if we run into problems22:40
gmannyeah22:40
opendevreviewGhanshyam proposed openstack/devstack-gate master: Keep only legacy jobs which actually test the d-g code path  https://review.opendev.org/c/openstack/devstack-gate/+/79542622:47
gmannclarkb: ^^22:48
*** derekh has joined #openstack-infra22:56
*** tosky has quit IRC23:03
*** yamak16 has joined #openstack-infra23:52

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