Wednesday, 2017-08-30

*** smyers has quit IRC00:01
*** smyers has joined #zuul00:01
*** olaph1 has joined #zuul00:38
*** olaph has quit IRC00:38
*** olaph1 is now known as olaf00:45
*** olaf is now known as olaph00:45
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Create zuul_executor_dest variable for fetch-sphinx-output  https://review.openstack.org/49862400:57
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Fix errors in mirro-workspace-git-repos  https://review.openstack.org/49899700:58
*** timrc has quit IRC01:12
*** timrc has joined #zuul01:13
*** yolanda has quit IRC05:21
*** hashar has joined #zuul06:23
*** yolanda has joined #zuul06:57
*** jamielennox has quit IRC07:09
*** jamielennox has joined #zuul07:14
*** MaciekW has joined #zuul07:40
MaciekWHi, I have problem with zuul 2.5.2 - zuul is not triggering new jobs, on zuul's status page Queue lengths: reached over 600 events. I don't see any usefull information in any of the logs. Do you have any idea what could be wrong?07:44
MaciekWserver where zuul is launch is not overloaded - load is less than 1 and there is huge amount of free memory07:44
MaciekWwe have already restarted zuul few times but after a while problem happens again07:45
MaciekWcould you suggest me how we can investigate the root cause of the problem?07:47
MaciekWCan anyone can help me ?08:05
*** electrofelix has joined #zuul09:23
*** hashar has quit IRC09:39
*** hashar has joined #zuul09:39
*** hashar has quit IRC09:42
*** hashar has joined #zuul09:44
*** hashar has quit IRC10:07
*** hashar has joined #zuul10:07
*** hashar_ has joined #zuul10:13
*** hashar has quit IRC10:13
*** jkilpatr has quit IRC10:36
*** jkilpatr has joined #zuul11:09
*** hashar_ is now known as hashar11:36
*** hashar has quit IRC12:07
*** olaph has quit IRC12:07
*** Shrews has quit IRC12:07
*** lennyb has quit IRC12:07
*** jeblair has quit IRC12:07
*** jeblair_ has joined #zuul12:07
*** hashar has joined #zuul12:20
*** olaph has joined #zuul12:22
*** Shrews has joined #zuul12:22
*** lennyb has joined #zuul12:22
mordredMaciekW: hi! I'm not the world's best at diagnosing such things - but it seems like perhaps you don't have build nodes registered with zuul12:51
mordredpabelanger: ^^ thoughts?12:51
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Add comment to top of zuul.yaml pointing to other files  https://review.openstack.org/49914713:16
*** dkranz has joined #zuul13:19
Shrewson line 62 of https://review.openstack.org/#/c/498623/5/zuul.yaml , can you set dependencies there, or do they need to be under the job definition itself?13:27
Shrewshttps://docs.openstack.org/infra/zuul/feature/zuulv3/user/config.html#attr-job.dependencies implies it's part of the job def13:28
Shrewsoops, mordred: ^^^^13:30
mordredShrews: they can be in either place13:31
mordredShrews: so in this case I did not put them on the job def themselves because announce-release could also be (potentially) be used after a javascript or go release13:31
mordredShrews: (although Ido not think the scripts it uses actually support that today)13:31
Shrewshrm. that should be in the documentation somewhere (unless it already is and i missed it)13:32
mordredShrews: agree. it may be in the job variant section - or it may be implied in the job variant section and need to be spelled out more explicitly13:32
Shrewsah, it is.  "Each item of this list may be a string, in which case it is treated as a job name, or it may be a dictionary, in which case it is treated as a job variant local to this project and pipeline."13:33
mordredShrews: (essentially what this is doing is creating a pipeline variant of that job that adds the dependency)13:33
mordredyes13:33
Shrewslots of hidden little gems13:34
mordredyah - it all hangs together pretty nicely as you're writing stuff, but it's also a *very* rich system so communicating up-front all the things you can do it going to be a really fun challenge for us13:34
pabelangermordred: MaciekW: possible there are no ready nodes online?13:59
openstackgerritMerged openstack-infra/zuul-jobs master: Add comment to top of zuul.yaml pointing to other files  https://review.openstack.org/49914714:05
openstackgerritMerged openstack-infra/zuul-jobs master: Fix errors in mirro-workspace-git-repos  https://review.openstack.org/49899714:08
openstackgerritMerged openstack-infra/zuul-jobs master: Create zuul_executor_dest variable for fetch-sphinx-output  https://review.openstack.org/49862414:11
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Revert "Add comment to top of zuul.yaml pointing to other files"  https://review.openstack.org/49916514:13
jeblair_mordred: let's discuss that further please ^ :)14:16
*** jeblair_ is now known as jeblair14:17
openstackgerritMerged openstack-infra/zuul-jobs master: Add a role to remove an ssh private key  https://review.openstack.org/49853014:23
openstackgerritMerged openstack-infra/zuul-jobs master: Delete .pypirc file at end of task  https://review.openstack.org/49884314:29
openstackgerritMerged openstack-infra/zuul-jobs master: Move .pypirc into tmpfs  https://review.openstack.org/49884414:30
*** olaph1 has joined #zuul14:31
*** olaph has quit IRC14:32
mordredjeblair: I'm cool with that - maybe we leave the first two lines of the top comment then remove the ENTIRE comment that's already there about tox-docs not being the OpenStack docs job?14:36
jeblairmordred: that works for me.14:38
mordredjeblair: I'll push that up real quick14:38
jeblairkk14:38
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Partially Revert "Add comment to top of zuul.yaml pointing to other files"  https://review.openstack.org/49916514:39
Shrewsoh, well ^^^ has an interesting -2 from zuul14:50
jeblairShrews: probably this bug: https://review.openstack.org/49887214:50
jeblairlooks like it got lost in a restart, ironically :)14:51
jeblairi'll see if i can confirm that with logs and if so, restart14:51
jeblairyep -- there was a github api ratelimit error during reconfiguration14:52
jeblairthe other question is -- were we running with the patches that should have prevented that error14:53
mordredjeblair: 2.5.3.dev1117 is what my zuul status page shows14:54
mordredbut that may not be accurate, as locally my repo shows 2.5.4.dev19114:55
jeblairmordred: how'd you get that local version number?14:55
mordredjeblair: python setup.py --version14:55
fungiis there a do you have a local 2.5.3 tag maybe?14:56
mordredoh - maybe I do - I think I was testing something14:56
jeblair2.5.3.dev1117 is my local setup.py output14:56
fungilooks like 2.5.2 is the latest on origin anyway14:56
mordredjeblair: yes - I now get that14:57
jeblairmordred: hrm -- why would the running version be so new?14:58
jeblairoh, last restart seems to have been at 12:4615:00
mordredjeblair: I restarted this morning to pick up main.yaml changes - although I totally should have just done a service reload instead15:00
jeblairmordred: np, it's convenient in this case anyway :)  [but a reload should work]15:00
jeblairso we do know we're running the github fixes15:00
mordredalso really need to get puppet to trigger the reload on file changes patch done15:01
mordredjeblair: the gh fixes and also your fix to not bail on reconfig issue too, right?15:01
jeblairmordred: no that hasn't landed yet15:01
jeblaironly the gh fixes have15:01
mordredah15:02
mordredjeblair: https://review.openstack.org/#/c/498872/ it's got 2x+2 - shall we push it in?15:03
fungii don't suppose we're using a common review topic for the zuul v3 job migration work... i know it's mostly unique to a pretty limited set of repos plus a set of files in project-config... does anyone have a gerrit query handy they've been using for all that maybe?15:03
jeblairfungi: 'zuulv3'15:03
fungiahh, okay so some patches are using that just not all15:03
mordredyah - trying to remember - sometimes forget15:04
jeblairfungi: yeah, it's most important on project-config15:04
fungik, i'll put together some string of project names plus that topic15:05
jeblairso something like (project:openstack-infra/openstack-zuul-jobs OR project:openstack-infra/openstack-zuul-roles OR project:openstack-infra/zuul-jos OR (project:openstack-infra/project-config AND topic:zuulv3))15:05
jeblairso something like (project:openstack-infra/openstack-zuul-jobs OR project:openstack-infra/openstack-zuul-roles OR project:openstack-infra/zuul-jobs OR (project:openstack-infra/project-config AND topic:zuulv3))15:05
jeblair(typo)15:05
clarkbjeblair: dmsimard: ianw left a good comment and suggestion on the fix disk revert revert change. Would be good if you could take a look at that (and so we can hopefully just get that behind us)15:05
jeblairclarkb: cool, will look in a few mins15:05
jeblairmordred, jlk: here's a recent api rate limit bust: http://paste.openstack.org/show/619907/15:06
dmsimardclarkb: yes, I talked with ianw last night15:06
dmsimardclarkb: Basically udevadm settle --timeout 10 --exitsomething is equivalent to our while loop15:06
jeblairmordred, jlk: and here's the error that tanked the reconfig: http://paste.openstack.org/show/619908/15:06
clarkbdmsimard: ya he was suggseting that we try it with timeout 0 though to confirm that is the problem (udev events queued and unprocessed)15:07
fungithanks jeblair!15:07
clarkband then maybe we switch to udevadm with a nice long comment explaining what is going on (just to make it easier to understand in the future)15:07
dmsimardclarkb: I'll get to it after the openstack/RDO release crunch :)15:08
clarkbdmsimard: sounds good, thanks15:08
clarkbalso tripleo must've gotten the overlay thing sorted out?15:08
pabelangerYa, I fixed it for them15:08
mordredpabelanger: woot15:10
jeblairmordred, jlk: looking at that first paste -- http://paste.openstack.org/show/619907/ -- do we need some more debug lines in there?  we're getting api rate limit log lines, but nothing else -- does that mean we're performing api calls but not logging what they are?15:11
jeblairmordred, jlk: ie, does that mean we performed 3 api ops, 2 authenticated, one not?15:11
jeblairor was the third a search api which is lower?15:12
*** weshay is now known as weshay_interview15:17
dmsimardclarkb: yeah, pabelanger copied the entire function in their tree15:18
dmsimardಠ_ಠ15:18
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Only add changes to status page with jobs  https://review.openstack.org/49919115:18
dmsimardI guess that extinguished the fire15:18
mordredjeblair: how about that ^^?15:18
mordredjeblair: looking at paste15:18
dmsimardclarkb, pabelanger: I'll send a patch after the release crunch to add a reliable and non-voting multinode job (standard job, doesn't run in the tripleo cloud) to try and catch if there's any other shenanigans like that15:19
mordredjeblair: yah - I think a smidge more logging would be helpful - I was looking at the code yesterday wanting the debug logging to be able to tell us what org/user the connection is for15:19
*** olaph has joined #zuul15:26
*** olaph1 has quit IRC15:27
*** MaciekW has quit IRC15:28
clarkbreviewing a thing for ironic has poitned out to me how complicated ironic's jjb is. Their jobs may make a good tester of the conversion stuff15:30
clarkbmordred: ^ fyi15:30
mordredclarkb: ++15:31
mordredclarkb, jeblair: also, once we think devstack-legacy is ready - we can do a manual migration of the nodepool dsvm job and add a nodepool-dsvm-legacy job since nodepool is already in v315:31
SpamapSCurious.. has anyone ever suggested IRC or Slack triggers for Zuul?15:35
SpamapSIt would be rather useful for me to be able to go "hey zuulbot, deploy region4" and have that trigger a CD job.15:35
SpamapSand report, obviously, via IRC/Slack too.15:36
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Added more debug logging for github requests  https://review.openstack.org/49920715:41
mordredjeblair, jlk, SpamapS: ^^15:41
mordredSpamapS: yah - I think the thinking was that once we add the fedmsg driver, we can use the tools already written for fedmsg to get triggers and reporters15:42
mordredSpamapS: without having to write triggers/reporters for each of the slack/irc/hipchat/jabber/gnome/etc.15:42
SpamapSmordred: yay middleware ;)15:45
pabelanger+1 for fedmsg15:46
clarkbmordred: SpamapS do easy buttons support fedmsg?15:47
SpamapSI do wonder if fedmsg can be trusted to pass along things like whether or not a user was authenticated though.15:47
SpamapSzomg I want an easy button that publishes to fedmsg now ;)15:47
SpamapSclarkb: is that a joke or is there a library called easybuttons ;-)15:47
clarkbSpamapS: a joke but I agree it should be a thing15:48
SpamapSLike that's the thing. I was pretty sure it was a joke.. but...15:48
clarkb"that was easy" and you are deployed15:48
SpamapSI would love to have a team of people who all have actual big red buttons on their desks.15:48
SpamapSwell it doesn't say "that was easy" until the deploy succeeds ;)15:48
pabelangerah, github rate limit again15:56
*** weshay_interview is now known as weshay16:03
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Added more debug logging for github requests  https://review.openstack.org/49920716:12
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Try getting project branches authenticated  https://review.openstack.org/49922216:23
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Cache branches for a project and use it on rate limit errors  https://review.openstack.org/49922316:23
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Keep a cache of branches for projects and update on events  https://review.openstack.org/49922416:23
mordredjeblair, SpamapS, jlk: ^^ there are some more thoughts on followups we can do16:24
mordredjeblair: check me on my comments on the last of them - I'm pretty sure that wants to be an event, but I wanted to get the idea up to discuss it real quick before doing that16:24
jeblairmordred: i fixed your logging change so you'll need to rebase that stack16:24
mordredjeblair: okie - and thanks16:24
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Cache branches for a project and use it on rate limit errors  https://review.openstack.org/49922316:25
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Try getting project branches authenticated  https://review.openstack.org/49922216:25
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Keep a cache of branches for projects and update on events  https://review.openstack.org/49922416:25
mordredjeblair, jlk, SpamapS: I have verified that github does not emit an event when branch protection is added :(16:29
jeblairmordred: reviewed all 316:32
jeblairmordred: i also just realized a subtle aspect of this situation that makes it worse than i would normally expect... i will explain with a patch16:33
mordredjeblair: cool16:34
mordredSpamapS: y'all have chatted with the github folks before - what's the best way to do that?16:35
jeblairmordred: nevermind, i was wrong.  :)16:39
jeblairmordred: what we might consider doing with your third change is to just use the cache (ie, no api calls) when we perform a tenant-reconfiguration (which is the thing we do when a config change lands).  but use the api-call-with-cache-fallback behavior on full system-reconfiguration (ie, sighup)16:41
jeblairmordred: (i mean that as a followup to your 3rd change)16:41
jeblairthat may strike the right balance of "as long as we're watching for branch creation events, the cache should usually be correct" but still give the system a way to resync if something goes awry.16:42
jeblairmordred: another problem in 499207; you want to fix it this time?16:44
funginow that i have an awesome gertty dashboard for zuul v3 migration, i'm crawling through open changes oldest first and finding a bunch which should probably be abandoned. i've been setting them to wip with comments explaining why, in order to help focus reviewing16:45
fungi(just a heads up)16:45
jeblairfungi: thank you16:45
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Cache branches for a project and use it on rate limit errors  https://review.openstack.org/49922316:48
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Try getting project branches authenticated  https://review.openstack.org/49922216:48
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Added more debug logging for github requests  https://review.openstack.org/49920716:48
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Keep a cache of branches for projects and update on events  https://review.openstack.org/49922416:48
jeblairmordred: nevermind i did it :)16:48
mordredjeblair: sorry - was verifying something for https://review.openstack.org/49922216:53
mordredjeblair: I have verified that it is possible to get the branches list authenticated16:53
mordredjeblair: and I like your suggestion for subhup vs. config change16:54
mordredjeblair: EXCEPT - that we don't get events when protection is added to or removed from a branch16:54
jeblairmordred: yeah.  i think 207 222 and 223 are good to go now.  224 should be harmless (though see my comment on that one).16:55
jeblairi'd like to at least get up through 223 in asap and then restart16:55
jeblairanyone else want to review some github debug changes + fixes?16:56
mordredjeblair: so for the "only use proteced branches" logic, there's no way to track it16:57
mordredjeblair: another option -looking at the github3.py code, is that these calls take an optional etag parameter16:57
mordredjeblair: so I think we can cache the etag we get back from the call, then supply that to the next call and hopefully that will cause things to work properly and not count as an extra api call?16:58
mordredjeblair: lemme do that patch real quick16:59
pabelanger+3 on github-ratelimit stack,minus 22416:59
*** hashar is now known as hasharAway17:02
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Added more debug logging for github requests  https://review.openstack.org/49920717:16
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Try getting project branches authenticated  https://review.openstack.org/49922217:16
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Cache branches for a project and use it on rate limit errors  https://review.openstack.org/49922317:16
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Update config cache only after all cat jobs complete  https://review.openstack.org/49887217:18
jeblairi made a small fix to that change; i'm going to self-re-approve17:29
pabelangerwfm17:32
mordredjeblair: ok. SO - I have learned a couple of things - and then I have also realized I'm somewhat dumb17:38
mordredjeblair: things I've learned:17:38
mordreda) github3.py does not expose an etag parameter for github.repository() which does a GET on 'https://api.github.com/repos/{org}/{repo}' in order to get a repository object on which you can call .branches()17:39
mordredb) the github REST API DOES properly work with an etag on that call (yay for once again python wrapper libraries not being as good as the direct REST API itself)17:40
jeblairmordred: re (a) -- is it possible for github.repository *not* to make that GET call?  i mean, we're pretty sure that repo is there :)17:42
mordredc) we're using cachecontrol already, which should be automatically reading and adding etag/if-none-match headers for us on all of these calls17:42
mordredjeblair: well, it is if you reach in and just use REST17:42
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Update config cache only after all cat jobs complete  https://review.openstack.org/49887217:43
mordredjeblair: http://paste.openstack.org/show/619925/ is my sample code for poking17:43
mordredjeblair: (there is stuff missing from that)17:43
fungimordred: sorry to interrupt, but can you confirm whether 482650 is still needed or is a dead fork in the road for bindep role work? it's failing to get tested in such a way that i'm going to need to dig into local zuul integration testing or checking the debug logs on zuulv3.o.o to work out the problem17:48
fungialso hasn't been touched in a month, so i'm dubious it's wanted any longer17:48
mordredfungi: thanks- abandoned17:49
fungiappreciated!17:49
mordredjeblair: do we re-create Connection objects when we reconfigure?17:55
SpamapSmordred: jlk did most of the chatting with github, so he should be able to tell you. I did open a feedback ticket about dropping approved reviews after force push, so I can look again at how I did that.17:56
jeblairmordred: oh, i think so (on the full system reconfig (not the tenant reconfig when a change lands)), let me double check17:56
*** electrofelix has quit IRC18:01
jeblairmordred: nerp, i'm wrong.  here's what happens:  on startup only, we initialize drivers+connections (so a full restart is required to change a [connection] in zuul.conf).  during any kind of reload (system or tenant), we call driver.reconfigure(tenant) for every driver.  github doesn't implement that, so nothing will happen in those cases.18:01
jeblairmordred: so both the driver and connection objects are very persistent (which i assume is where you're going with that).18:02
jeblairmordred: it's probably worth treating the connection object as being as persistent as the connection in zuul.conf.  ie, in the future, i think the only reason we would drop/recreate a connection object is in the case that something in zuul.conf changed.  that probably still matches fairly well to what we need here.18:03
mordredjeblair: ok. cool18:04
jlko/18:04
jlkreading scrollback18:04
mordredjeblair: then I actually expect that we should be using cache via cachecontrol18:04
mordredjeblair: it's in-memory so will get zeroed on a full restart18:04
mordredjeblair: although a followup patch to add optional external persistent cache via file or redis would not be super hard18:05
jeblairi'm restarting zuulv3 now with all the github changes and my reload fix18:05
mordredcool18:05
jlkso we're still rate limiting busting. :(18:05
mordredmorning jlk !18:05
mordredjlk: well, we've added a few new toys :)18:05
jlkit's really unfortunate we never got BonnyCI sufficiently off the ground to catch these :(18:05
mordredjlk: well, the upside is that I have learned a whole bunch of things this morning, which is good18:06
jlkthat means you looked closer at my code, I'm afraid!18:06
mordred:)18:06
jeblairjlk: aside from things still in review and discussion, you'll want to be aware of these already-merged changes: https://review.openstack.org/499207 https://review.openstack.org/499222 https://review.openstack.org/49922318:07
jeblairjlk: (normally we would have waited for your feedback, but i thought it better to get these in production to put out fires and collect more data)18:07
jlkopening18:07
jlkyeah18:07
jlkI was having a slow morning, so I approve of that direction18:07
mordredjlk: the only rage I've had at all has been at github3.py18:08
mordredjlk, jeblair: we can also add cachecontrol debug logging into our logging config so we can see what it's caching or not18:08
jlkyeah...18:08
jlkthat's been on the chopping block18:08
jlkI had wanted to toss it with the move to graphql, but there were some roadblocks to graphql usage.18:09
jlkThat would be good, getting that cachecontrol18:09
jlkWe used to get some logging of etag and cache hits/misses18:09
jlkand timeouts18:09
SpamapSjlk: did we ever report the deficiencies in graphql to GH?18:10
SpamapSIIRC, it was a lack of certainfields.18:10
jlkYeah I opened a forum thread about it (which was the official way)18:10
jlkI have to loop back and see if there has been any change. THere haven't been any notification emails to me about replies18:11
jlkother than some "me too!"s18:11
jlkI'll make that a priority today.18:11
SpamapSShould I laugh that GH has a hard time managing bugs in their own software? ;-)18:11
fungiand considers web forum threads the best means of providing specs for api features18:12
fungiseems like we do a lot more things in git than they do18:13
jlkmordred: looking at https://review.openstack.org/#/c/499222 the app API does allow us to get a list of branches, see https://developer.github.com/v3/repos/branches/#list-branches there is a little "i" in a circle that mouse over indicates that it's available to apps.18:15
mordredjlk: wow. that's how I find thatout? neat -thanks, that was going to be one of my questions for you18:16
mordredjlk: my solution was to make a script that authenticated as an app and geta list of branches - I should remove that comment18:16
jlkLooking at https://review.openstack.org/#/c/499223 , I feel like just doing a cache work around for branch data is just kicking the can down the road for the next API call. But perhaps that's fine, we just keep moving that can from API to API?18:17
mordredjlk: agree18:17
mordredjlk: I'm actually a little more concerned about why this isn't being handled via cachecontrol for us already18:17
jlkyeah that's a good question.18:18
mordredjlk: and then yah - more broadly I think not kicking the can down the road is a better idea18:18
mordredjlk: although sad panda that we can't get events to tell us to update our cached branch protection information18:18
jlkI wonder if the cache control is per-github object18:19
mordredjlk: ALTHOUGH - if cachecontrol does its thing I would expect just querying for branches to use cache most of the time unless protection has changed18:19
jlkand we make new github objects all the time.18:19
mordredjlk: I just checked that18:19
mordredjlk: it's not - we have a global one18:19
jlkah okay18:19
mordredjlk: and I verified that we don't recreate the Connection object it lives on18:20
mordredjlk: pointed you at it in infra channel, but I also just made a logging config change to turn on cachecontrol logging so we can see it18:20
jlkyup18:20
jlkWe should do the same in default upstream if it's not there already18:21
jlkIIRC when I was messing with things yesterday, I thought it was getting protected branches on repeated calls within a short amount of time and it was finding the cached data and using it18:22
jlkbut if enough time expires then it will consider the cache stale. Unless that particular API call has an etag that we can pass along?18:22
mordredgood. so it might just be that even with that around a restart the unauthenticated api limit is small enough that we were hitting it18:23
jlksomething about the etags, it lets the github API see if what you ahve (even if old) is unchanged.18:23
jeblairmordred: http://paste.openstack.org/show/619928/18:23
jlkoh yeah, unauth is pretty low limits. If there are any other unauth calls we should kill 'em18:23
mordredjlk: cachecontrol is suppsed to be doing18:23
mordredgah18:23
mordredjeblair: onit18:23
jlkyeah it does18:23
mordredBAH typo18:24
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Consume the variable with the same name it's set  https://review.openstack.org/49925118:25
mordredjeblair: ^^18:25
jeblairmordred: approved and rechecked (i manually downgraded zuul so it would start)18:26
jeblaironce that lands, we can upgrade and re-restart18:26
mordredjeblair: cool. wanna update the logging config while we're at it?18:26
jeblairmordred: yah, if puppet hasn't done it by the time we're ready (that's also approved)18:27
mordredcool18:27
jeblairmordred: i have to afk for lunch now; i can do that when i get back or feel free yourself18:28
mordredokie. I'll restart it once it lands18:29
jlkI found a couple more places we're not using the app for calls, where I think we could.18:33
jlkactually18:39
jlkit looks like the only places we do that is a call to search (for Depends-On) and I think we learned yesterday that search has it's own API limits, and a call to get user information (which we cache internally heavily anyway).18:40
dmsimardclarkb: is the sync and partprobe required if we're adding in the udevadm settle ?18:40
dmsimardI guess it doesn't hurt to keep them there, was just curious18:40
mordredjlk: yah - there's that whole User object18:41
clarkbdmsimard: ya I don't think it hurts but probably not necessary especially since they didn't fix the problem18:41
mordreddmsimard: I'd say not - since I think those were just attempts to ...18:41
mordredyah what clarkb said18:41
dmsimardok, let me try and take those out.18:42
mordredclarkb, dmsimard: I almost asked this yesterday and then wanted to die inside a little - but would this be helped at all by udev rules and/or systemd units? (I try to stay away from both if I can help it, but I believe we had to do a udev rule for glean didn't we?)18:43
clarkbmordred: I don't think it would because we still ahve to manually partition things so making swap creation automagic and mounting /opt automagically after partitioning manually is probably more effort than it is worth18:43
dmsimardsystemd has stuff for udev yeah18:43
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add cachecontrol logging to the default config  https://review.openstack.org/49925518:46
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Consume the variable with the same name it's set  https://review.openstack.org/49925118:47
mordredclarkb: nod18:49
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Log cachecontrol info by default  https://review.openstack.org/49925718:49
mordredclarkb: you know what would be neat? if those fancy block_device_mapping parameters were a) documented b) worked everywhere18:50
mordredclarkb: since I _think_ those would allow us to actually set up swap, etc beforehand - but last I checked they're still terrifying undocumented magic18:50
mordredclarkb: maybe next time we get, you know, bored with no work on our plates, we can go learn how they work, test them everywhere and document them18:51
clarkbthat would be nice though it won't fix things for systems without an ephemeral drive (so really everything but rax now)18:52
mordredrestarted v3 scheduler18:57
jlkoh hrm. Github apps flat out do not support GraphQL anyway19:03
mordredjlk: that's awesome19:05
mordredjlk: so - I see thingsin the log that make me agree that we are using cachecontrol (I was stupid and restarted before the cachecontrol logging patch landed, but oh well - I see two calls one after the other with the same ratelimit number)19:07
mordredjlk: 2017-08-30 18:59:41,138 DEBUG zuul.GithubConnection: Got reviews for PR ansible/ansible#2883319:07
mordred2017-08-30 18:59:41,189 DEBUG zuul.GithubConnection: GitHub API rate limit remaining: 29 reset: 150412264819:07
mordredjlk: looks like getting reviews is using the unauth'd connection19:08
jlkremaining 29.19:08
jlkthat's pretty low19:08
jlkso, it might not be using unauthed, but it might be using the non-app way19:08
mordredjlk: nod19:09
mordredjlk: well- I don't see ANY log lines with the second form I added, so I'm thinking that did not work19:09
jlkah indeed19:09
jlk"use_app=False"19:09
mordred2017-08-30 19:06:56,564 DEBUG zuul.GithubConnection: GitHub API rate limit remaining: 11991 reset: 150412125519:09
jlkthere are comments in there all about why19:09
mordredcool19:10
mordredjlk: another optimization I wonder if we could make - is to not do things with projects we're not configured to care about19:10
mordredI'm not sure a good way to get at that information from the webhook19:10
jlkyeah, well19:10
mordredbut if project not in the list of projects in main.yaml - there's really  no need to do anything further19:11
jlkthe webhook should just be getting enough info to send it through to the driver19:11
jlkthe driver then takes that info and examines it to see if it matches a pipeline19:11
jlkso it's not really at the webhook side, more at the driver side19:11
mordredyah - totally19:11
jlkoh hrm!19:12
jlkgoing to test a thing here19:12
jlkand then I'll put my brain meat in the same space you're thinking19:13
mordredfun19:14
jlkuh, is openstack-infra/zuul-jobs broken?19:15
mordredjlk: so, my brainmeat is thinking about the line above - "DEBUG zuul.GithubConnection: Got reviews for PR ansible/ansible#28833" -19:15
jlkextra keys not allowed @ data['release']19:15
mordredjlk: that's what it looks like when we get a broken config - looking19:15
mordredjlk: is that a new comment?19:15
mordredor from earlier today?19:15
jlkf8e746cb14646cc86885f9f7a0a817d9da864ac319:16
jlkI can't see what's wrong with it, but that's where the complaint is from19:17
mordredthat gets me to https://review.openstack.org/#/c/498903/19:17
mordredjlk: I feel we may be talking about slightly diffrent things ...19:18
jlkI might be missing something. But it complains about the "post" chunk there19:19
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Use app integration to get PR reviews  https://review.openstack.org/49926719:23
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Add role for adding launchpadlib credentials  https://review.openstack.org/49863319:26
mordredjlk: yah - I'm just confused by what you mean by f8e746cb14646cc86885f9f7a0a817d9da864ac3 and think I might not be looking at the right thing19:27
openstackgerritMerged openstack-infra/zuul-jobs master: Partially Revert "Add comment to top of zuul.yaml pointing to other files"  https://review.openstack.org/49916519:28
jlkmordred: oh well let me explain how I got there.19:30
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Add role for adding launchpadlib credentials  https://review.openstack.org/49863319:31
jeblairmordred: oh, we should not be adding project-templates to zuul-jobs19:31
jeblairmordred: that should be in openstack-zuul-jobs i think19:31
jlkmordred: I started my local zuul off of the topic branch. My tenant.yaml includes a reference to openstack-infra/zuul-jobs as untrusted-projects19:32
jeblair(it imposes pipeline requirements; and while installations could use include/exclude to filter those out, i think we decided that we should restrict that repo to jobs only to make it easier to use)19:33
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Fail early if people attempt to add zuul vars or secrets  https://review.openstack.org/48400019:33
jlkat start up, when zuul tries to process config for that repo, it chokes on the line I mentioned. I git logged the zuul.yaml file in that repo, foudn the commit that touched that area recently.19:33
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Revert "Make a docs-on-readthedocs project-template"  https://review.openstack.org/49927219:34
jeblairjlk, mordred: ^19:35
Shrewsmordred: i don't think there is a 'shred' module19:36
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Add roles for adding and removing launchpadlib credentials  https://review.openstack.org/49863319:36
mordredShrews: gah. that should be command shred19:37
mordredjeblair: ah. cool. gotcha (and makes sense)19:38
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Remove project stanza  https://review.openstack.org/49927819:38
pabelangerhttps://review.openstack.org/498621 and https://review.openstack.org/498267 are ready for review if people need a break from github. That is jobs for afs-docs19:40
jeblair19:40 < openstackgerrit> James E. Blair proposed openstack-infra/openstack-zuul-jobs master: Add docs-on-readthedocs project template  https://review.openstack.org/49927919:40
jeblairmordred: ^ there's the 2nd half of move19:40
jeblairpabelanger: what is afs.path?19:42
pabelanger /afs/.openstack.org/docs from our secret19:43
jeblairwhy is that part of the secret?19:43
pabelangerno reason, we did that for artifact publisher, so copypasta19:43
pabelangersite_logs for example19:44
mordredjeblair: +2 to all and +3 to some19:45
Shrewsjeblair: if the zuul-jobs project stanza is also defined in project-config, how does that work? were they merged? because the definitions are vastly different19:46
openstackgerritMerged openstack-infra/zuul-jobs master: Revert "Make a docs-on-readthedocs project-template"  https://review.openstack.org/49927219:46
mordredjeblair, pabelanger: I'm growing complex and conflicting feelings about our current pattern of bundling secret and non-secret data19:46
jeblairShrews: merged, in config loading order (so project-config is first)19:47
pabelangermordred: jeblair: ya, I'm happy to change it to something else if people would like19:47
mordredjeblair, pabelanger: on the one hand, it feels nice and encapsulated to say "add-filserver: site_logs" and have site_logs have the 4 parameters needed19:47
pabelangerRight, that is my feeling also. We could do that with 2 variables too19:48
mordredjeblair, pabelanger: on the otherhand itmeans we wind up with potentially the same private key multiple times when we want to use it for multiple purposes, when saying "add-fileserver: zuul_ssh_key, site_logs" would work too19:48
mordredyah19:48
kklimondais there some architecture docs about nodepool? I'm looking at creating windows images, and the best way (cloudbase based) requires a windows host. I'm reading through https://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-workers.html and it seems that the architecture would support custom builders, but I'm not sure where to look next.19:49
mordredjeblair, pabelanger: lemme propose a quick patch to something to see what y'all think (I don't want to bikeshed too much, but it's been bothering me a little bit recently)19:49
mordredkklimonda: hi! so - we don't have a good windows story yet - but when tobiash gets back from vacation he's planning on working on it19:50
pabelangermordred: wfm19:50
jlkhuh weird.19:50
mordredkklimonda: there are a couple of things that will be needed to get it done - but I don't think it's going to be a super long thing, just work that's needed19:50
jeblairmordred: i agree, i am conflicted.  however, bundling of *some* amount of data is the primary driver of the approach we chose, so i think it's worth exploring.  i think we haven't quite decided *what* one of these secrets is -- is it just access to a server, or is it the full package.  i think it's worth pushing the envelope as far as we can go in that direction, then maybe dialing it back if it's awkward.19:51
mordredkklimonda: which is mostly to say - I highly recommend syncing with tobiash when he's back (I think next week?) - he's got a much better sense of what's needed on the nodepool/zuul front19:51
jlkI made myself a test app and my API limits went down to 57 or so..19:52
mordredjeblair: ++ - quick sake-of-argument coming19:52
kklimondamordred: sure, is there anything I can read nodepool related that would give me a better overview of how it's working before then? This task just jumped a bit in my team's internal priority queue, and I'd like to take some time to investigate building blocks, so that I can actually talk with tobiash when he's back and not make a fool out of myself ;)19:53
mordredjlk: it seems like the webhook + user with oauth credentials will let you do auth'd things for all interactions - whereas we have to do unauth'd for some things becaue the api api is incomplete19:53
jlkmordred: yes, however, things that ARE authed as the app so it should be getting app level limits seem to be getting far less19:54
jlkmaybe a dev app gets a lot lower to start with?19:54
mordredkklimonda: https://docs.openstack.org/infra/nodepool/feature/zuulv3/ are the docs so far - leifmadsen is starting work on better getting started docs for nodepool19:55
mordredShrews: ^^ any thoughts on other things to point kklimonda at to read on nodepool architecture?19:56
Shrewskklimonda: which version of nodepool?19:56
mordredShrews: the interest is in windows support, and I was mentioning that tobiash was interested in workingon adding support for that when he got back19:56
Shrewskklimonda: are you using the version from the features/zuulv3 branch, or from master branch?19:56
mordredso I think we're talking v319:56
mordreds/I think//19:57
mordredwe will _definitely_ not be adding windows support to v2 :)19:57
jeblairkklimonda: if you want to read changes, https://review.openstack.org/468624 and its parent https://review.openstack.org/488384 are architecturally relevant.  also their git parents, already merged, continue the story.19:57
*** jkilpatr has quit IRC19:58
Shrewskklimonda: there is some stuff under https://git.openstack.org/cgit/openstack-infra/nodepool/tree/doc/source/devguide.rst19:58
Shrewsbut it's rather incomplete. i should probably update that19:58
*** weshay is now known as weshay_PTO19:58
jeblairkklimonda, Shrews: kklimonda pointed to the image build/upload spec, which is actually implemented in both branches.  however, the changes i just pointed to and their parents start to cause the implementation to diverge significantly between the two; all the more reason to only focus on the feature/zuulv3 branch.19:59
leifmadsenmordred: speaking of which :)20:00
leifmadsenwhen do you wanna get together and move to phase 2?20:00
kklimondaShrews: we are not running nodepool currently, I've actually been thinking that windows images could be our first step towards that (as we plan on using it at some point). We are currently running zuul from master branch, not v3.20:01
clarkbits possible you can just change the disk image builder invocation to the windows dib (assuming that works) run the whole lot on windows and be done20:04
clarkbbiggest thing is probably that the zookeeper lib runs on windows20:04
mordredclarkb: according to tobiash we need to plumb through information about username/password for remote connection withpowershell to work20:05
clarkbmordred: is that how windows dib works?20:05
jlkoh OH20:06
jlkhrm.20:06
jlkmay have found a big bug.20:06
mordredclarkb: I think so - like, I think he's using that by hand currently to create the user account, but the informatoin on how to use that user account needs to be communicated to zuul so that the inventory can be written out properly20:06
mordredclarkb: we also need to set a different connection-type in the inventory if it's windows too20:06
clarkboh I'm ignoring zuul for this thought experiment20:06
mordredjlk: yay!20:06
clarkbpurely just nodepool making an image and uploading it somewhere20:07
mordredclarkb: yah- same thing - you need the admin credentials to use the windows remote connect20:07
clarkbmordred: because windows doesn't have chroot so it must run a vm and connect to that?20:07
mordredwell - sure ,you could do that if all you wanted to do was upload it20:07
mordredclarkb: we're kind of at the limit of what I learned from tobiash20:07
clarkbmordred: well ya one step at a time20:07
jlkbug being I forgot to rebuild my container, so something was lost.20:08
clarkbmordred: step 0 is make image, step 1 is upload to cloud. I think that should mostly just work if you swap out the dib invocation command20:08
mordredclarkb: but the amount of work to add it properly actually doesn't seem too bad20:08
kklimondais windows dib available somewhere? the only reference I've found was an old and retired repo from stackforge20:08
clarkbya if its mostly just "this is how you connect to windows" that should be straighforward20:08
clarkbkklimonda: ya thats what I am not sure about. We have never used it20:09
jlkor not20:09
jlkhr .20:09
mordredclarkb: that seemed to be it- that and being able to mark a diskimage in nodepool config as being windows and not linux20:09
mordredso that that fact can be communicated to wherever that's necessary20:09
mordredkklimonda: tobiash is doing some amount of this locally by hand already - so he'll have the most info20:09
kklimondathanks, I'll just wait for him then :)20:10
clarkbmordred: and maybe rather than doing windows vs linux make it connection type. ssh, telnet, remote powershell20:10
clarkblooks like all of cloudbase's image building tools are snapshot based20:11
clarkb:/20:11
mordredclarkb: yah - biggest open question is whether there are also windows-specific boot params20:11
clarkbmordred: you mean to nova api (or similar)?20:12
mordredclarkb: which is an unknown for now waiting for tobiash to get back - if there aren't, then I agree, it should be connection type. if there are, it might need to be connection_type + os family - with os family == windows implying connection type == powershell20:12
mordredor something20:12
mordredclarkb: yah20:12
pabelangerclarkb: windows dib, crazy times20:13
clarkbpabelanger: it existed for a time but unsure if it is still a thing20:13
clarkbused powershell instead of  bash etc, but design of using elements was the same aiui20:13
*** jkilpatr has joined #zuul20:14
jlkah, pm != pem20:14
jlkokay, got it to work with my app now.20:19
jlkcan confirm that an app can get a list of the reviews on a PR20:19
* jlk out for lunch20:20
tobiashYes, I'll be back on monday20:23
tobiashAnd I finally got travel approvement for ptg :)20:24
tobiashSo will also be there20:24
*** hasharAway has quit IRC20:45
*** dkranz has quit IRC20:45
pabelangermordred: did you push up your secret changes? or did we want to keep iterating on https://review.openstack.org/498621/ and child20:50
clarkbtobiash: nice, don't forget to register nowish as price goes up on friday I think20:55
* clarkb looks20:55
clarkbya saturay morning ttx says price goes up20:56
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: WIP Split add-sshkey into two roles  https://review.openstack.org/49933820:58
tobiashclarkb: booked already everything :)20:58
mordredjeblair, pabelanger: sorry- https://review.openstack.org/499339 and https://review.openstack.org/49933821:00
mordredtobiash: woot!21:01
pabelangermordred: ya, 499339 is bascially how I see the 2 variable approach too21:02
pabelangermordred: only think I can think of an issue, is if we change the secret and forget to update other vars, or the other way around.  I mean, we know fast there is an issue and just do another commit to fix it21:03
mordredyah - I mostly just don't know if it's 'better' or not21:03
mordredpabelanger: I say we just move foward as is for now21:04
pabelangerya, no real preference either way for me. So will defer to what other people like :)21:04
pabelangermordred: danke21:05
mordredpabelanger: real quick - can you push in https://review.openstack.org/#/c/499277/ and https://review.openstack.org/#/c/499278/ and https://review.openstack.org/#/c/499279 ?21:07
pabelangerdone, done and done21:08
mordredpabelanger: and done on yours too21:08
mordredjlk, pabelanger, SpamapS: also - seems like we shoudl land https://review.openstack.org/#/c/490216/ before we forget about it  (it's had 2 +2s in the past already)21:11
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Use app integration to get PR reviews  https://review.openstack.org/49926721:17
* jlk back21:27
openstackgerritMonty Taylor proposed openstack-infra/nodepool feature/zuulv3: Remove the default argument to secure in nodepoolcmd  https://review.openstack.org/48031021:33
mordredtobiash: when you're back and ready to look at windows, there's 2 patches up https://review.openstack.org/#/q/topic:username+status:open that may have done part of what you need already21:35
jlkmordred: so, thinking about ignoring repos we don't care about, what would have to happen is a repo we don't care about would be configured to throw webhooks at us, signed by our webhook key (which is supposed to be private). I could see that happen in some corner situations21:36
mordredtobiash: I don't know if they'll be directly useful, but I thought i'd point them out21:36
jlk(like a repo that once installed the app we stopped caring but they keep sending)21:36
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Prevent execution of locally overridden core modules  https://review.openstack.org/49021621:36
mordredjlk: yah - or a repo that has installed the app but that we don't quite yet care abt21:36
jlkmaybe another scenario is finding a Depends-On: of a change we're handling that exists in a repo we don't care about. I'll look at the code for it.21:36
mordredjlk: it's an edge case to be sure - so if it's completely convoluted, I don't think we should lose too  much sleep over it21:37
jlkso we'd have to maybe scrape the tenant name out of the event URL, then see if the project exists in that tenant?21:40
jlkjeblair: there was something related to github driver yesterday you wanted me to look into, and we put it on pause because of a eureka moment. Do you recall what that was?21:42
jeblairjlk: oh i *think* it was just the branch lookup stuff, iirc21:44
jlkoh, getting the protected branches?21:45
jeblairjlk: no, getting the list of branches robustly and authenticated; so i think it's taken care of now21:46
jlkyeah21:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Remove comments questioning API capabilities  https://review.openstack.org/49935821:48
mordredjeblair: can project-templates have descriptions to?21:50
jeblairmordred: yep, they actually share an implementation with projects.21:50
mordredjeblair: neat21:50
jeblairmordred: i think we may have forgotten to add them with zuul-sphinx; easy enough to fix tho.21:50
jlkThere's one last call to a limited API, and that's searching for things that might have a Depends-On of a particular change.21:52
jlkcurrently we're caching that info when we get an event for a PR (and we refresh it for any subsequent events, and I don't think that's cachecontrol able)21:53
jlkI'm working through to see if we can delay fetching that info until it's actually going into a pipeline21:53
jlkyeah, I think I can21:55
jlkmaybe21:55
jeblairmordred: ohnoes zuul said i lied!21:56
mordredjeblair: ohnoes!21:56
jeblairmordred: i will add description to projects and project-templates now21:56
mordredjeblair: cool - it definitely seems useful for the templates21:57
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Allow description fields in projects and project templates  https://review.openstack.org/49936521:57
jlkmordred: jeblair: there is one change object attribute that we care about, that would trigger the search, and that's the needed_by_changes attribute. Would it make sense to turn that into a property (at least in the github version of the object), and when the property is accessed, that's when we do the expensive search?22:21
jlk'cause it should only happen when we're processing for a dependent pipeline22:21
jeblairjlk: unfortunately, that shifts network activity into the main (scheduler) thread; right now it's not slowing anything down22:22
jlkah, I see.22:23
jeblairjlk: however, there's some rework that we need to do in order to handle cross-source dependencies22:23
jlkyeah we gather it in the webhook thread, it's just that it costs us an API hit every time22:23
jeblairjlk: it's entirely possible that there's no way to do that without doing what you suggest22:24
jlkevery time we do a "refresh"22:24
jeblairjlk: so maybe we can revisit it as part of that22:24
jlkbut if we don't look at it when we do a refresh, our cache could become stale22:24
jlkbasically this will become our hard limit on how many webhooks we can respond to in a minute (30).22:26
jeblairjlk: depends on comes from the PR description right?22:27
jlkalthough in my testing it's showing 60 instead of 30, and it DOES appear that the search API call is cached.22:27
jeblairoh wait, this is needed by22:27
jlksame deal22:28
jlkWe're searching for PRs that would depend on the PR we're dealing with22:28
jeblairgotcha.22:28
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Move name from block to tasks in the block  https://review.openstack.org/49937522:30
jlkcouple things helping, looks like 60 a minute rather than 30 (or else it's giving me a 2 minute limit remainder), search is doing some caching somewhere, because a repeated search a few minutes later is not costing me an API limit22:35
jlkwhich is weird, because the cache isn't coming from cachecontrol.22:36
jlkanyway with the code changes made in the last couple days, and the logging changes, I'd like to see some logs and see if we're running close to API limit issues having just the ansible repo on there.22:38
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Add publish-openstack-python-docs to post pipeline  https://review.openstack.org/49884022:38
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Fix error in mirror-workspace-git-repos  https://review.openstack.org/49938222:53
jeblairmordred, pabelanger: ^22:53
pabelanger+222:54
jeblairmordred: when you have a minute, the console output on http://logs.openstack.org/99/497699/26/check/devstack-legacy-tempest-dsvm-neutron-full/29bfff5/job-output.txt.gz#_2017-08-30_22_39_11_159486 is lacking some info -- it doesn't include the error(s) within the loop, so it's very hard to tell what failed (only ara and the json have that)22:55
openstackgerritMerged openstack-infra/zuul-jobs master: Move name from block to tasks in the block  https://review.openstack.org/49937523:00
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Fix checkout in mirror-workspace-git-repos  https://review.openstack.org/49938423:00
jeblairpabelanger, jlk: want to look at that one too ^?23:05
pabelangerjeblair: is there an etherpad outlining the roles? I haven't really been following. And curious about delegate_to: localhost now23:08
jeblairpabelanger: no etherpad.  what's the question?23:09
openstackgerritMerged openstack-infra/zuul-jobs master: Fix error in mirror-workspace-git-repos  https://review.openstack.org/49938223:09
pabelangerjeblair: so, this is to use our local git repos in /opt/git? Or am I missunderstanding the role23:09
jeblairpabelanger: there are at least 2 roles involved -- one clones repos from /opt/git to /home/zuul (that's in project-config).  this one pushes commits from the executor to the repos in /home/zuul.23:11
pabelangerOkay, perfect23:11
pabelanger+323:11
pabelanger:)23:11
pabelangerthank you23:11
clarkbnote that git push can't create remote repos so you always need something to run first23:17
jeblairyep; the only reason those are 2 roles right now is i don't want to deal with getting our repo cache into golang style paths yet (which i think is required in order to generalize that role)23:18
jeblairwe can tackle that after ptg23:19
openstackgerritMerged openstack-infra/zuul-jobs master: Fix checkout in mirror-workspace-git-repos  https://review.openstack.org/49938423:20
mordredjeblair: I shall track down the issue with the LOOP (although it makes me sad that we have that issue)23:21
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add publish-openstack-python-docs to post pipeline  https://review.openstack.org/49884023:32
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Add roles for adding and removing launchpadlib credentials  https://review.openstack.org/49863323:53

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