Tuesday, 2018-01-30

Shrewspabelanger: clarkb: i think i have a programmatic solution to the wedged provider issue you found tonight (it was bugging me we don't handle that better)00:02
Shrewswill throw something up tomorrow00:02
clarkbShrews: ok00:02
pabelangergreat00:03
clarkbI'm assuming something that avoids blocking there and instead declines requests somehow would work00:03
Shrewsclarkb: yep. if request would put us at our max-servers quota, and all of our current nodes are ready&unlocked (meaning not used) and none of them have the needed label, decline it00:04
Shrewsi don't think we ever considered the case of us being at quote with all unused nodes (caused here by a zuul restart)00:05
Shrewss/quote/quota/00:06
openstackgerritliusheng proposed openstack-infra/zuul master: Fix AttributeError when handle periodic job with github driver  https://review.openstack.org/53664500:52
*** myoung|bbl is now known as myoung01:12
*** gigaset has joined #zuul01:12
gigaset2!list01:13
*** gigaset has left #zuul01:16
*** harlowja has quit IRC02:10
*** Wei_Liu has joined #zuul02:30
*** rlandy|bbl is now known as rlandy02:31
*** rlandy has quit IRC03:42
*** elyezer has quit IRC03:48
*** elyezer has joined #zuul03:49
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement a static driver for Nodepool  https://review.openstack.org/53555304:08
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: nodeutils: use socket.getaddrinfo instead of ipaddress  https://review.openstack.org/53908604:08
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement a static driver for Nodepool  https://review.openstack.org/53555304:16
*** harlowja has joined #zuul04:21
*** harlowja has quit IRC04:26
*** harlowja has joined #zuul04:26
*** harlowja has quit IRC04:27
*** sshnaidm|afk has quit IRC05:14
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement a static driver for Nodepool  https://review.openstack.org/53555305:27
*** sshnaidm has joined #zuul05:31
*** sshnaidm has quit IRC05:43
*** bhavik1 has joined #zuul05:45
*** bhavik1 has quit IRC05:53
*** jappleii__ has quit IRC06:01
*** sshnaidm has joined #zuul06:02
*** bhavik1 has joined #zuul06:14
*** bhavik1 has quit IRC06:36
tobiashpabelanger: hrm, it's not as easy as I thought, modifying the test is not sufficient07:56
* tobiash needs to do some whiteboarding to really understand nodepool request handling07:56
*** sshnaidm is now known as sshnaidm|afk08:15
*** lennyb has quit IRC08:50
*** jpena|off is now known as jpena08:50
*** sshnaidm|afk is now known as sshnaidm09:04
*** lennyb has joined #zuul09:34
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: zuul autohold: allow filtering per commit  https://review.openstack.org/53699309:54
*** elyezer has quit IRC11:09
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: zuul autohold: allow filtering per commit  https://review.openstack.org/53699311:11
*** elyezer has joined #zuul11:11
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: [WIP] zuul web: add admin endpoint, enqueue commands  https://review.openstack.org/53900411:15
*** sshnaidm is now known as sshnaidm|afk12:39
*** jpena is now known as jpena|lunch12:45
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Fix relaunch attempts when hitting quota errors  https://review.openstack.org/53693013:15
tobiashpabelanger, Shrews: sooo, this took me half a day but I got the test working... ^^13:15
tobiashstill needs some cleanup but have to think about different things now13:16
*** sshnaidm|afk is now known as sshnaidm13:19
*** rlandy has joined #zuul13:28
*** weshay|ruck|afk is now known as weshay|ruck13:31
*** jpena|lunch is now known as jpena13:46
Shrewsclarkb: pabelanger: i found a problem with my proposed solution last night. we're going to have to go with max-ready-age for now until we can come up with something better14:22
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add buildset-artifacts-location and fetch roles  https://review.openstack.org/53067914:31
tobiashhrm, locally that test worked :/14:31
*** elyezer has quit IRC14:36
*** elyezer has joined #zuul14:37
openstackgerritFabien Boucher proposed openstack-infra/zuul-jobs master: Propose to move submit-log-processor-jobs and submit-logstash-jobs in zuul-jobs  https://review.openstack.org/53784714:40
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Set remote url on every getRepo in merger  https://review.openstack.org/53571615:15
*** myoung is now known as myoung|food17:44
*** electrofelix has quit IRC17:49
*** electrofelix has joined #zuul17:50
*** bhavik1 has joined #zuul18:02
*** bhavik1 has quit IRC18:10
corvusmordred: good news and bad news: the change to use override-branch to solve the ansible/devel problem should be in production.  bad news is that merge failure reports are pipeline-global, so any merge hiccup on ansible will report.  due to that, i removed the ansible/ansible project definition until we work it out.18:11
mordredcorvus: yah - I saw the removal of ansible/ansible ... and the global merge-failure reports is ... fun isn't it?18:11
corvusmordred: the minimal solution is, i think, to make the merging more robust so that github hiccups don't cause errors.  we need to do that regardless...18:12
mordredyup. must do that18:12
corvusmordred: even if we do that, we could have systemic errors though -- like mergers run out of space, or whatever -- main point is -- *something* in the future will cause a spurious merge error, and we'll report it.18:12
mordredor, even a real merge error18:13
corvusmordred: heh, yeah, that could happen too :)18:13
corvusmordred: so i think we have to ask -- if we're *generally* good citizens, but occasionally that happens, is that okay?  or do we need to find a way to never report merge failures for specific projects?18:13
mordredcorvus: I think the failures exposed an edge-case where the current behavior does not match what people might expect ... which is that a zuul, such as ours, that only has jobs configured to report on a subset of a given repo wouldn't be expected to report merge errors to changes that didn't touch those files18:13
corvusmordred: indeed -- though, in the case of an actual merge failure, how do you know? :)18:14
mordredcorvus: I think we do - I'm thinking about openstack third-party CI's too18:14
mordredcorvus: that's an excellent questoin! :)18:14
mordredcorvus: (sort of thinking of 20 third-party CIs all reporting "I couldn't merge this change" to nova patches)18:15
corvusmordred: yeah, though they generally turn of merge reports for their pipelines18:16
mordredcorvus: good point18:16
corvusbut we're putting ansible into our existing check pipeline18:17
corvuswe could create a new pipeline just for third-party check18:17
mordredcorvus: good point. we could also add ansible/ansible in a second tenant with its own pipelines ... although that seems a bit more extreme18:18
corvusi think that would let us proceed with no further zuul changes.  or we could look into disabling merge failure reports per-project.  i think that's something we may want to do, but that also opens the can-o-worms that SpamapS wanted to open with the project-customized slack reporter, and i kinda wanted to keep that closed until after the release18:18
mordredcorvus: yah. project-specific reporter config is a thing that could be desirable, but seems like a thing to talk about in dublin18:19
corvusso maybe we should make a third-party-check pipeline in openstack zuul, add ansible/ansible to it.  i think we can still do all the cross-testing we need.  gating is, obviously, not a problem right now.18:19
corvusthen maybe collapse that back into check later18:19
mordredcorvus: yah. I thnk that's a good idea18:21
mordredcorvus: that would also let lower its priority as well18:21
mordreds/let/let us/18:21
mordredcorvus: I can make that patch real quick18:22
corvusmordred: kk thx18:23
corvusi'm going to take a little break; i have a bit more energy today, but not quite enough.18:24
mordredcorvus: kk. take a break - no need to push yourself and get sicker18:24
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: zuul autohold: allow filtering per commit  https://review.openstack.org/53699318:27
*** myoung|food is now known as myoung18:34
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: zuul autohold: allow filtering per commit  https://review.openstack.org/53699318:59
*** jpena is now known as jpena|off19:00
mordredcorvus: https://review.openstack.org/#/c/539286/ how's that look?19:11
*** harlowja has joined #zuul19:17
tobiashmordred: wow, I didn't know yet that merge failure can be its own reporting category19:19
tobiashone never stops learning...19:23
mrhillsmanmordred corvus have either of you confirmed your cicd f2f attendance yet?19:37
mrhillsmanasking because there is an overview on day one and need someone to do zuul19:37
mrhillsmanor clarkb19:37
corvusmrhillsman: what event is this?19:37
mrhillsmanthe one fatih reached out about19:37
corvusmrhillsman: i think i put my name in the etherpad, is there something more formal than that?19:38
mrhillsmancross community f2f cicd19:38
clarkbmrhillsman: last I heard it still wans't confirmed as happening so I haven't bought tickets or ldoging yet but do intend on attending19:38
mrhillsmani think fatih sent to confirmation, let me check to make sure19:38
mrhillsmancorvus we are doing the agenda and just wanted to be sure a zuul expert would be available for the overview19:39
mordredmrhillsman: I'll be there for sure19:39
clarkbmrhillsman: I intend on being there19:39
mrhillsmanok cool, he sent an email on the 23rd but i see how it is not clear19:40
mrhillsmanhe basically just said we have got a room19:40
mrhillsmanthx gents, will confirm we have someone to do zuul overview :)19:41
mordredmrhillsman: awesome! thanks19:43
mrhillsmanwelcome20:02
*** sshnaidm is now known as sshnaidm|afk20:38
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: WIP: Provider wedge test  https://review.openstack.org/53931620:40
Shrews^^ tests the wedge scenario, but still no fix so it should rightly fail20:40
Shrewssimplest test case I could conjure up20:41
tobiashcorvus, mordred: are we ready to land 535518?21:08
tobiashlooks like this might have been forgotten some time ago21:09
mordredtobiash: yah. I thnk so21:17
tobiashok21:18
* tobiash ends his review evening21:34
*** elyezer has quit IRC21:34
openstackgerritMerged openstack-infra/zuul master: Remove zuul._projects  https://review.openstack.org/53551821:37
*** threestrands has joined #zuul21:40
*** elyezer has joined #zuul21:44
openstackgerritMerged openstack-infra/nodepool master: zk: check for client in properties  https://review.openstack.org/53555921:58
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Merger: retry network operations  https://review.openstack.org/53935623:11
corvusmordred: ^ that may hopefully smooth over github network hiccups23:11
mordredcorvus: cool!23:14
SpamapScorvus: we should look at bringing in tenacity at some point23:37
corvusSpamapS: heh, yes.  i almost wrote that myself, but stopped.  :)23:41
SpamapSso much hair on that yak23:41
*** elyezer has quit IRC23:43
mordredSpamapS: don't know if you saw - but we're running shade tests on ansible PRs as of now!23:44
*** elyezer has joined #zuul23:44
SpamapSmordred: ssswwwweeeeeetttt23:48
SpamapSI had a nice internal demo of our zuul today btw. Folks interested in the scalability. :)23:48
mordredSpamapS: yay!23:49

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!