Tuesday, 2019-06-11

*** jamesmcarthur has joined #zuul00:01
mordredclarkb: nope. I lost the session and wasn't running it in screen because FAIL00:03
mordredclarkb: oh - that was after the time I ran in to duplicate key issues because the first mttest image didn't get deleted :)00:03
mordredclarkb: trying once more00:03
clarkbya they leak :)00:04
clarkbnote I did not delete mttest as part of my leak cleanups00:04
*** michael-beaver has quit IRC00:09
fungii've got tests.unit.test_scheduler.TestScheduler.test_head_is_dequeued_once failing with MismatchError: 14 != 1500:24
fungiis that a known instability in the unit tests?00:25
fungifailed on py35 but not py3600:25
fungihttp://logs.openstack.org/70/662870/8/check/tox-py35/9aabd57/00:25
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Add sanity checks  https://review.opendev.org/66447100:48
*** jamesmcarthur has quit IRC00:52
*** igordc has quit IRC00:56
*** mattw4 has quit IRC00:57
*** threestrands_ has joined #zuul01:11
*** swest has quit IRC01:12
*** threestrands has quit IRC01:14
*** threestrands_ has quit IRC01:21
*** swest has joined #zuul01:27
*** sshnaidm has quit IRC01:33
*** sshnaidm has joined #zuul01:35
*** jamesmcarthur has joined #zuul01:35
*** jamesmcarthur has quit IRC01:37
*** bhavikdbavishi has joined #zuul02:05
*** bhavikdbavishi has quit IRC02:09
*** michael-beaver has joined #zuul02:12
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Update the readme for new role options  https://review.opendev.org/66448402:14
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Add variable to set the docker download url  https://review.opendev.org/66448502:22
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Update the readme for new role options  https://review.opendev.org/66448402:49
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Add variable to set the docker download url  https://review.opendev.org/66448502:49
*** bhavikdbavishi has joined #zuul02:56
*** bhavikdbavishi1 has joined #zuul02:59
*** bhavikdbavishi has quit IRC03:01
*** bhavikdbavishi1 is now known as bhavikdbavishi03:01
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Update the readme for new role options  https://review.opendev.org/66448403:12
*** bhavikdbavishi1 has joined #zuul03:18
*** bhavikdbavishi has quit IRC03:20
*** bhavikdbavishi1 is now known as bhavikdbavishi03:20
*** swest has quit IRC04:33
*** bjackman_ has joined #zuul04:36
*** michael-beaver has quit IRC05:02
*** saneax has joined #zuul05:03
*** saneax has quit IRC05:07
*** swest has joined #zuul05:16
*** swest has quit IRC05:18
*** bhavikdbavishi1 has joined #zuul05:19
*** bhavikdbavishi has quit IRC05:19
*** bhavikdbavishi1 is now known as bhavikdbavishi05:19
*** swest has joined #zuul05:19
*** bhavikdbavishi has quit IRC05:23
*** bhavikdbavishi has joined #zuul05:41
openstackgerritTristan Cacqueray proposed zuul/nodepool master: static: enable using a single host with different user or port  https://review.opendev.org/65920905:47
*** saneax has joined #zuul05:48
openstackgerritMerged zuul/zuul master: Annotate logs around build states  https://review.opendev.org/66148905:51
*** threestrands has joined #zuul05:52
*** threestrands has quit IRC05:53
*** pcg has joined #zuul05:54
*** pcg has left #zuul05:54
openstackgerritTristan Cacqueray proposed zuul/nodepool master: static: document multiple labels shortcomming  https://review.opendev.org/66295405:55
openstackgerritMerged zuul/zuul master: Annotate logs around reporting  https://review.opendev.org/66149006:12
openstackgerritMerged zuul/zuul master: Annotate logs around finished builds  https://review.opendev.org/66149106:33
*** pcaruana has joined #zuul06:55
*** badboy has joined #zuul07:13
*** saneax has quit IRC07:17
*** flepied has quit IRC07:20
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213407:22
*** gtema has joined #zuul07:24
*** bjackman_ has quit IRC07:42
*** hashar has joined #zuul07:45
*** jpena|off is now known as jpena07:46
*** flepied has joined #zuul07:54
*** saneax has joined #zuul07:58
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213408:07
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213408:35
openstackgerritTobias Henkel proposed zuul/zuul master: Parallelize github event processing  https://review.opendev.org/66281808:39
openstackgerritTobias Henkel proposed zuul/zuul master: Allow to select the merge method in Github  https://review.opendev.org/61794908:52
openstackgerritTobias Henkel proposed zuul/zuul master: Support squash merge in Github  https://review.opendev.org/66109608:52
*** tobberydberg has quit IRC09:22
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213409:25
*** tobberydberg has joined #zuul09:31
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213409:45
*** gtema has quit IRC09:47
*** panda has quit IRC09:47
*** panda has joined #zuul09:49
*** gtema has joined #zuul09:58
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213409:59
openstackgerritTobias Henkel proposed zuul/zuul master: Allow to select the merge method in Github  https://review.opendev.org/61794910:08
openstackgerritTobias Henkel proposed zuul/zuul master: Support squash merge in Github  https://review.opendev.org/66109610:08
openstackgerritFabien Boucher proposed zuul/zuul master: Disable gc in test_scheduler.TestExecutor  https://review.opendev.org/66131610:13
openstackgerritFabien Boucher proposed zuul/zuul master: Disable gc in test_scheduler.TestExecutor  https://review.opendev.org/66131610:14
openstackgerritFabien Boucher proposed zuul/zuul master: Pagure driver - https://pagure.io/pagure/  https://review.opendev.org/60440410:14
fbocorvus: hi, thanks for the review on the Pagure driver, I've fixed gc patch https://review.opendev.org/661316 according to your request.10:17
*** pcaruana has quit IRC10:19
*** gtema has quit IRC10:28
*** gtema has joined #zuul10:28
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213410:31
*** bhavikdbavishi has quit IRC10:39
*** pcaruana has joined #zuul11:09
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213411:31
*** jpena is now known as jpena|lunch11:38
*** bhavikdbavishi has joined #zuul11:45
*** rlandy has joined #zuul11:58
*** rlandy is now known as rlandy|ruck11:59
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213412:02
*** badboy has quit IRC12:13
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Add variable to set the docker download url  https://review.opendev.org/66448512:24
*** jpena|lunch is now known as jpena12:43
*** zbr|ruck is now known as zbr|rover12:44
zbr|roverdoes anyone knows if is legal to add extra text after URL on Depens-On or Needed-By:?12:51
*** jamesmcarthur has joined #zuul12:51
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Adds tox-molecule job  https://review.opendev.org/66423012:54
fungifor needed-by it doesn't matter because that's not a zuul feature. i do not know if it will confuse zuul on depends-on, but it's probably easy to try12:55
fungijust remember that git considers footers to be one thing per line, so at least don't go adding comments so long that you need to wrap them onto additional lines12:56
fungi(granted, git commit footers are merely a convention, but some applications do expect to interpret them one per line)12:57
zbr|roverfungi: i asked because on more complex changes where you have 2-3 depends-on, it makes code easier to read if you mention repo-name after the URL.12:57
zbr|roveri think i already did this in the past and apparently it does not break anything, but I wanted to ask, just in case.12:58
fungizbr|rover: makes sense. if it helps, when we upgrade to current gerrit you'll get that by default (change numbers are scoped to projects in notedb, so the project names appear in the change urls)12:58
zbr|roverfungi: super cool!12:59
zbr|roveri used https://review.gerrithub.io/ in the past and loved the UI, i am sure others may not share the same love of it :)13:00
*** jamesmcarthur has quit IRC13:02
openstackgerritTobias Henkel proposed zuul/zuul master: Evaluate CODEOWNERS settings during canMerge check  https://review.opendev.org/64455713:10
tobiashcorvus: btw, this is getting battle tested since three weeks here in production ^13:25
tobiashso we're shaking out most bugs on this atm ;)13:26
*** jamesmcarthur has joined #zuul13:26
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213413:28
*** armstrongs has joined #zuul13:33
*** bhavikdbavishi has quit IRC13:33
armstrongshi guys, i am trying to execute a playbook from a required projects workspace using the run: with a full relative path of the dependent project but it isn't working. Is this possible to do?13:34
pabelangerarmstrongs: no, playbooks need to live next to zuul.yaml file13:35
pabelangeryou cannot get them from cross projects13:35
pabelangeryou're best to move the logic into a role, they create a smaller wrapper playbook13:36
armstrongscool so to call cross project i could have a playbook that calls the dependant one13:36
armstrongsas long as original playbook lives in the same repo as zuul.yaml13:36
pabelangeryup13:38
pabelangeror, move the playbook into a share repo13:38
pabelangerand update both jobs to then use it13:38
armstrongsso theres no way shadow jobs could allow this at all13:38
armstrongsi have the scenario where we have a standard set of playbooks to deploy apps, teams have config repos to provide inputs to self-serve against them. So really the use case is each team needs to use the playbooks in the central repo and provide the supplimentary self-service repo to give inputs13:40
armstrongsif that makes sense the self-service repos are just var files for each app13:40
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213413:42
mordredclarkb, fungi, corvus, Shrews: patch up in sdk https://review.opendev.org/#/c/664585/ to fix the nodepool regression. I predict you're going to "love" the patch13:44
*** electrofelix has joined #zuul13:44
mordredI particularly enjoy that we got a raw 400 error back with no error message on a "this field wants a string and you passed a boolean" issue13:46
pabelangerarmstrongs: yes, you can create new child jobs, which setup vars to the parent and that will work too13:47
fungiright, jobs and roles can be reused between projects (with some limitations around secrets in untrusted repositories), you just can't refer to playbooks in other projects as far as i know13:49
fungiand you can certainly derive new jobs by parenting them to jobs in other repos, or create "variants" of jobs in other repos if you just need to override some parameters in them13:50
*** hashar has quit IRC13:58
*** pcaruana has quit IRC14:04
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213414:10
*** michael-beaver has joined #zuul14:10
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213414:11
*** jpena is now known as jpena|afk14:14
*** chandankumar is now known as raukadah14:23
zbr|roverfungi: clarkb mordred pabelanger : i think I implemented all comments on tox-molecule job at https://review.opendev.org/#/c/664230/14:29
*** pcaruana has joined #zuul14:30
pabelanger+214:30
*** pcaruana has quit IRC14:31
*** pcaruana has joined #zuul14:31
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213414:32
corvusevrardjp, clarkb, pabelanger: i'm trying to think of alternate approaches to https://review.opendev.org/662828 -- i'm frustrated that the date/time is not available to an untrusted zero-node job.  that seems like it would be generally very useful.  perhaps we should consider modifying zuul to stick that into the executor's fact cache?  or, add a new zuul. variable?14:32
evrardjpso... Yeah I tried to have this facts gathered selectively, but as you could guess, the whole setup, even filtered, was not allowed.14:33
evrardjpso to think of alternative approaches, I think what I would like was to freeze by sha14:34
evrardjpthat could work, as the lookup('url' would be allowed.14:34
evrardjpbut then the build and publish would become quite ugly14:34
evrardjpcorvus: not sure what you mean by adding a new zuul variable14:35
evrardjpI mean I am not sure what this technically involves14:35
corvusevrardjp: like "{{ zuul.executor.datetime }}"14:35
evrardjpyeah got that part :)14:35
clarkbcorvus: may even be worth adding to ansible as a var that isnt a fact14:35
clarkbsince it can lookup time too14:35
corvusevrardjp: both of my suggestions are small code changes to the executor source code14:36
corvusclarkb: yeah, i think if we're automatically adding variables which aren't facts, we should stick it in the zuul. hierarchy to avoid collisions14:36
evrardjpdoes the executor now the target state of the repo for which the change is made?14:36
evrardjp(sorry I am thinking outside the box here)14:37
corvusevrardjp: yes, but i don't think we set that as a variable for changes (only for ref-updates)14:38
evrardjpcorvus: could you remind me why the change_<changeid> was added in the past, and not make the final tag part of the upload?14:38
evrardjpcorvus: ok on that14:38
evrardjpI suppose the change_<change number> question is because we only want the tag applied post-merge14:39
pabelangerI wonder what facts are gathered with gather_subset=!all'14:39
pabelangerwill have to test that out locally14:39
corvusevrardjp: because when we upload an image, we don't know yet if the change for it will actually land, so promote is responsible for finding the changes which actually did land and retagging them with the 'real' tags.14:39
evrardjppabelanger: I think in this case, it's the setup module that wouldn't be allowed to run in promote pipeline, so it doesn't really matter14:40
corvusclarkb: but i figured it would be okay to "shadow" a known ansible fact with an equivalent value.  it would make more things work out of the box with less zuul-specific knowledge.14:41
pabelangerevrardjp: I was thinking more of https://opendev.org/zuul/zuul/src/branch/master/zuul/executor/server.py#L206214:41
evrardjpcorvus: well that could as well be a post job14:41
pabelangerall jobs run that today14:41
pabelangerexecpt localhost14:41
fungiit's unclear to me how a static timestamp is especially useful... or is there some way for it to be the actual time and not just the time at which the variable was resolved and stored for that build?14:41
pabelangerbut cannot remember what facts it gather14:41
corvusevrardjp: it's not actually the pipeline that restricts it, but rather that the playbook is in an untrusted repo (zuul-jobs)14:42
evrardjpcorvus: thanks for improving my knowledge there :)14:42
fungiit the timestamp was stored in a fact, then it's frozen at the point at which fact gathering happened, right?14:42
corvusfungi: evrardjp is going for an approximate date, so the slight error/race isn't too important14:42
fungiahh14:43
corvusbasically a "one-per-day" archive14:43
fungiand having the timestamp be static throughout the build is also acceptable i guess14:43
corvusyeah, if we were to define it as a zuul var, i'd describe it as the "start time" for the build14:43
evrardjpfungi: yeah I don't even mind if the day is different when it starts and when it ends14:44
fungiseems like it would be especially flexible as an ansible feature where the value was expanded at the moment of execution rather than compilation14:44
evrardjpit's just better than not freezing it _at all_14:44
corvusfungi: that could be done as a lookup plugin or module14:44
corvus(ideally lookup plugin)14:44
fungiyeah, i suppose if one existed we could whitelist it fairly easily14:44
fungiespecially if that's all it did14:44
evrardjpit looks better to have a lookup plugin for date to whitelist, than whitelist setup14:45
fungibut sure, build start time as a zuul var also makes fine sense14:45
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213414:45
evrardjpI think build start time would be cleaner though14:45
fungii can see both approaches being useful for different things, and not necessarily exclusive of one another14:45
evrardjpI have the impression it's more work long term to have a lookup and whitelist it14:46
evrardjpthan expose the current build start time14:46
evrardjpbut I might be wrong14:46
corvusyeah, i think it would be weird to have a zuul-specific lookup plugin which does that (though we certainly could) -- that would make more sense to me as something to add to upstream ansible.  so that's not short-term :)14:47
*** kklimonda has quit IRC14:47
evrardjppabelanger: not really sure where this runAnsibleSetup is involved and would be able to expose more data14:47
fungiif a plugin is tightly scoped and poses no breakout risk, whitelisting it in zuul for use on an executor is fairly trivial14:47
*** kklimonda has joined #zuul14:47
*** kklimonda has left #zuul14:48
evrardjpI guess the real question is... does this really need to be in zuul, or can this be in the role14:48
evrardjp(for my case)14:48
fungiand certainly a plugin of this nature could be as simple as a few lines to call and return a single python stdlib function14:48
evrardjpyup14:48
evrardjpfungi: https://review.opendev.org/#/c/662828/1/roles/promote-docker-image/tasks/promote-retag-inner.yaml L12 -- something like that I suppose14:49
fungibut i agree that ideally would go into the ansible source tree as a community plugin14:49
pabelangerevrardjp: we use it before every job starts to confirm the network is up and working as expect, so we prime all nodes (minus executor) with some facts14:49
evrardjpit's unlikely to happen there, as setup covers the same thing14:49
pabelangereg: http://paste.openstack.org/show/752749/14:49
evrardjppabelanger: so you propose the executor to also have this but not expose it?14:50
evrardjpor expose it partially?14:50
pabelangerwe could update that to filter that output for facts we consider safe, and add them to localhost fact cache14:50
pabelangerbut that is a change in out we gather facts for localhost14:50
fungievrardjp: is the ansible community opposed to a proliferation of simple and tightly-scoped lookup plugins? seems like there's a definite use case for deployments deciding which plugins are safe and blacklisting the rest (we have at least one such use case)14:51
evrardjpI don't have enough view on how best it would be maintained, this is why I am looking for help :)14:51
*** jpena|afk is now known as jpena14:51
fungikitchen sink plugins like setup are likely not to meet that use case14:52
evrardjpfungi: I guess you could run lookup shell for the same results, so I see a reason to not carry code14:52
evrardjpwhich would be an opposite reason to what we want to do (i.e.: NOT run shell)14:52
fungiright, hence my question about use cases involving only allowing certain plugins for safety reasons14:53
corvusthe thing i would suggest would be useful upstream is a plugin which gets the *current* time like fungi was suggesting (not the playbook start time as the current setup/fact does).  it would help people with issues like this: https://stackoverflow.com/questions/31323604/ansible-date-variable14:53
corvusand https://gist.github.com/halberom/b452df40828839fecabf14:53
fungiright, could be as simple as just returning the result of time.time()14:54
corvusor as complicated as accepting all the arguments to datetime + timedelta :)14:54
fungithat can always be postprocessed14:54
fungibut sure14:54
evrardjpcorvus: I should have started by the fact I have strict deadlines14:55
evrardjphahaha14:55
fungianyway, i do still think a build start timestamp as a zuul variable is also a good idea14:55
evrardjpso the summary, is ... do everything? :p14:55
fungii think the summary is tackle whichever one you're keen to work on14:56
corvusevrardjp: yeah, upstream isn't going to be an immediate answer, if we do it, we should do it out of generosity with a view to improving things in the future, but still do something else now :)14:56
evrardjpI am worried about converting timestamp to dates for my use case, as it mean I would also need to "run something" :D14:56
corvuslet's see what pabelanger comes up with in exploring what facts get collected with !all14:56
dmsimardfwiw I've been experimenting with a lookup plugin to the new ARA API so you can query the API during the the execution of the playbook itself https://review.opendev.org/#/c/663968/1/tests/integration/lookups.yaml14:57
corvusif we can extend the fact gathering of the executor itself, then that would be the simplest, nicest way to go14:57
*** saneax has quit IRC14:57
evrardjpI would prefer that tbh14:57
fungifacts incorporate a timestamp for when they were gathered, i guess?14:58
corvusif we can't then i think our best options are to shadow ansible_date_time in the executor, or create zuul.build_start_time14:58
evrardjpbut I am not really sure where to start debugging this14:58
evrardjpwhat do you mean by "shadow ansible_date_time" ?14:59
corvusfungi: one of the facts is "ansible_date_time" which you can see here: https://ttl255.com/ansible-getting-date-and-timestamp/14:59
evrardjpsorry for asking so many questions :)14:59
*** hashar has joined #zuul14:59
fungigot it14:59
fungiso basically if we *can't* safely gather facts, then have zuul somehow inject a fact with the appropriate data type?15:00
corvusevrardjp: we can put our own "facts" in without getting ansible involved: https://opendev.org/zuul/zuul/src/branch/master/zuul/executor/server.py#L41115:00
corvusfungi: right15:00
evrardjpcorvus: haha exactly what I thought doing :p15:01
fungii suppose that keeps it somewhat ansibleish15:01
evrardjpseed the facts there15:01
fungiso you don't need zuul-specific roles when you're consumnig it15:01
evrardjpI can do a patch to keep that content, have the same structure as ansible_date_time15:01
corvusoptions: A) pabelanger says it's safe to gather more facts on the executor; B) have the executor write an ansible_date_time fact; C) have the executor add a zuul.build_start_time variable15:01
evrardjpwe can still call it ansible_date_time too15:01
pabelangerI think it would be helpful, at least for me, what is considered a safe fact from executor POV. ansible_date_time seems good, but is there others we need / want?15:01
evrardjpI will ansible setup locally real quick15:02
corvusi will eat breakfast15:03
evrardjpcorvus: sounds great!15:03
evrardjppabelanger: hostname maybe?15:04
evrardjpthe rest sound very sensitive15:04
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Add multi-distro support to install-docker  https://review.opendev.org/66445515:05
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Add variable to set the docker download url  https://review.opendev.org/66448515:05
pabelangerevrardjp: okay, I'll work up a test to see if my hunch is correct15:07
evrardjppabelanger: that would be awesome. So basically approach A said by corvus. I will propose approach B in parallel.15:07
pabelangerwfm15:07
evrardjpif you could ping me, that would be amazing, as I would 1) learn 2) review15:07
evrardjppabelanger: gather_subset="date_time" would also be interesting btw15:08
evrardjpoh wait15:09
evrardjpnevermind15:09
*** pcaruana has quit IRC15:17
*** bhavikdbavishi has joined #zuul15:21
openstackgerritPaul Belanger proposed zuul/zuul master: WIP: Remove fact cache restriction for localhost (zuul-executor)  https://review.opendev.org/66462015:24
pabelangerevrardjp: ^ is what I am thinking we could do, however left some questions in commit message15:24
pabelangeralso, we'll need to add various tests to validate we are not leaking info15:24
evrardjpoh I see, simple as that. I thought we had some extra validation. I feel dumb now to not have proposed that15:29
pabelangerevrardjp: I think the safest approve, would be 2nd setup task just for localhost (running it first), then we can only place filters on that host15:33
pabelangervs across all hosts15:34
evrardjppabelanger: I thought of that :)15:37
evrardjpwell my implementation for B could be close to that tbh15:38
evrardjpfinishing my series of meetings then will take a crack at it15:38
*** pcaruana has joined #zuul15:43
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: download-artifacts: only consider the most recent build  https://review.opendev.org/66462415:44
*** igordc has joined #zuul15:44
corvusfungi, clarkb, tobiash: ^ that's the next thing needed to fix the tarball promote jobs15:45
*** pcaruana has quit IRC15:55
*** flepied has quit IRC15:59
zbr|roverclarkb: can we wf tox-molecule now? https://review.opendev.org/#/c/664230/16:13
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Add variable to set the docker download url  https://review.opendev.org/66448516:13
openstackgerritMerged zuul/zuul-jobs master: download-artifacts: only consider the most recent build  https://review.opendev.org/66462416:14
*** gtema has quit IRC16:22
pabelangerI've raised an item on zuul-discuss about an issue we are having with the github driver, to humans that are intersted16:23
clarkbzbr|rover: one small thing then I think it is ready16:24
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Adds tox-molecule job  https://review.opendev.org/66423016:25
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Adds tox-molecule job  https://review.opendev.org/66423016:25
clarkbzbr|rover: looks great now. pabelanger if you want to rereview ^16:26
pabelanger+316:29
*** kklimonda has joined #zuul16:32
*** jamesmcarthur has quit IRC16:32
clarkbpabelanger: your email thread honestly seems like one better suited for github and vexxhost support :/16:35
pabelangerclarkb: yah, expect that to be true.16:35
pabelangerWanted to get it out there, to spark some discussion. Because I imagine us being the only one who has the isssue16:36
pabelangerclarkb: I looked at zuul.o.o last week, and also seem the same tracebacks16:36
corvuswell, if two systems in different cloud providers have the same issue, it's not a network problem in one cloud provider16:37
pabelangerlet me look again at logs on zuul.o.o for signs it is happening today16:37
clarkbI did quickly double check there are no AAAA records for github in dns still (there aren't any) as ipv6 has been flaky in $clouds16:38
clarkbalso they report no errors on their status site16:38
clarkbthey being github16:38
*** hashar has quit IRC16:39
pabelangerhttp://paste.openstack.org/show/752758/16:39
pabelangeryah, I can see 55 errors just from today on zuul.o.o16:39
corvuspabelanger: all read timeouts?16:40
pabelangercorvus: yah16:41
pabelangerlet me figure out if they are in the same time period16:41
corvusgood idea16:42
pabelangerI can also ask sf.io to check their logs16:42
corvuspabelanger: does the system get events for ansible/ansible ?16:43
*** [GNU] has quit IRC16:43
pabelangercorvus: now yes16:43
pabelangerwe enabled it maybe 3 weeks ago16:43
corvuspabelanger: if they are for the same time period, it may be worth checking if they are for the same events16:44
pabelangerkk16:44
corvusie, is it a really big query against the ansible repo or something16:44
corvuspabelanger: i replied to the ml, but also if you wanted to expirement with a longer read timeout, i think this is how you would do it: https://paste.ubuntu.com/p/FYxyzXHxfQ/16:44
pabelangerack16:44
pabelangerthanks16:45
fungiwell, also github probably has all manner of global load distribution, so just because we saw timeouts from one place on the internet doesn't mean someone else did as they could be hitting entirely different github systems16:48
fungiso a failure correlating these sorts of things doesn't mean it wasn't still broken16:48
*** pcaruana has joined #zuul16:49
pabelangerzuul.a.c: http://paste.openstack.org/show/752762/16:50
pabelangerzuul.o.o: http://paste.openstack.org/show/752763/16:51
pabelangerboth start having failures around the same time16:51
pabelangerin fact the same event a45aa186-8c16-11e9-9e52-4a6f1ad9106116:51
corvuspabelanger: you could have github resend that event and see if it happens again16:51
pabelangercorvus: okay, let me figure out how to find it16:52
pabelangerlet me do a more recently failure16:55
pabelangerthere doesn't seem to be any pagenation here16:55
pabelangerokay, f63ca21a-8c61-11e9-9dc1-c61cd291984c16:56
corvusmhu: i did a quick scan of the jwt stack and it looks good; i think the only thing missing is docs16:58
mhucorvus: great! Yeah I was waiting for validation before adding the docs. I'll add some based on the spec17:00
mhucorvus, I'm also revisiting my docker-compose PoC so that folks can experiment easily, I'll push something this evening17:01
*** gtema has joined #zuul17:01
mhuthe hardest part so far is configuring gerrit with oidc, it makes it harder to setup admin and zuul accounts, but this could be skipped17:02
openstackgerritMerged zuul/zuul-jobs master: Adds tox-molecule job  https://review.opendev.org/66423017:03
*** jamesmcarthur has joined #zuul17:10
zbr|roverpabelanger: clarkb: thanks. I guess next one is the openstack one https://review.opendev.org/#/c/663599/17:15
*** jpena is now known as jpena|off17:17
*** bhavikdbavishi has quit IRC17:22
*** jamesmcarthur has quit IRC17:26
*** jamesmcarthur has joined #zuul17:26
*** electrofelix has quit IRC17:27
tobiashcorvus: pagure driver lgtm, do you want mor eyes on it?17:57
corvustobiash: mordred reviewed an earlier version; my guess is he'd be happy with the current PS but he can speak up now if he wants to review again... let's ask SpamapS if he's interested since he's been diving in on bitbucket.... otherwise, unless someone jumps up and says "me!" i think we're good.18:00
pabelangercorvus: retrigger worked this time: http://paste.openstack.org/show/752771/18:01
pabelangercorvus: but did notice a 20min delay on processing it18:01
pabelangersorry, 10min18:01
corvuspabelanger: so it was more likely a transient issue on the github side before18:02
pabelangeragree18:02
clarkbpabelanger: re the delay check your github event queue processing lengths18:03
clarkbpabelanger: ansible/ansible in particular is quite susceptible to those delays due to long queues due to its post merge testing18:03
pabelangerclarkb: okay, let me check logs18:03
corvusthat's about to get better -- https://review.opendev.org/66281818:04
clarkbya I need to rereview that apparently18:04
pabelangeroh, neat18:04
tobiashyeah, needed a rebase because of log stack18:05
pabelangerjlk: do you happen to know when the next release of github3.py will be happening?18:05
*** armstrongs has quit IRC18:10
pabelangercorvus: re: pastebin for default_read_timeout, docs seem to say the following: https://github3.readthedocs.io/en/master/api-reference/github.html#githubsession-object18:13
clarkbI've approved the github multiprocessing change18:13
clarkbpabelanger: ^ so you should be able to update to that and see if it is happier soon18:13
pabelangerclarkb: great, thanks18:14
fungiat least it looks like the session timeout parameters are configurable18:14
corvuspabelanger: er yes, do that.  :)18:16
corvuspabelanger: you can skip the connect timeout if it's not a problem.18:16
pabelanger+118:16
*** [GNU] has joined #zuul18:17
pabelangercorvus: should we expose that value as a config setting? Or 300 for all?18:18
corvuspabelanger: i think you should pick a value and see if it makes things better, and if it does, we'll hardcode it18:19
pabelangerunderstood18:20
corvusno one should have to set that on their own18:20
tobiashfyi, I'll roll out the mitogen change to production tomorrow morning and try it with some jobs18:21
* tobiash is looking forward to see if it improves things18:22
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Add caching of autohold requests  https://review.opendev.org/66341218:23
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Add autohold-info CLI command  https://review.opendev.org/66248718:23
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Record held node IDs with autohold request  https://review.opendev.org/66249818:23
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Auto-delete expired autohold requests  https://review.opendev.org/66376218:23
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Mark nodes as USED when deleting autohold  https://review.opendev.org/66406018:23
jlkit's not a scheduled event, one of us will decide that enough has changed to need a release, or somebody asks really nicely.18:27
jlkpabelanger: ^^18:28
tobiashjlk: I guess pabelanger chooses to ask really nicely ;)18:28
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Auto-delete expired autohold requests  https://review.opendev.org/66376218:30
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Mark nodes as USED when deleting autohold  https://review.opendev.org/66406018:30
fungirecent problem with the zuul-stream-functional-2.5 job?18:30
fungiE: Failed to fetch http://mirror.dfw.rax.opendev.org/ubuntu/dists/xenial-updates/main/binary-amd64/Packages.gz  Hash Sum mismatch18:31
fungiahh, must have been a problem with opendev's mirrors18:31
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Auto-delete expired autohold requests  https://review.opendev.org/66376218:36
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Mark nodes as USED when deleting autohold  https://review.opendev.org/66406018:36
*** gtema has quit IRC18:38
openstackgerritTobias Henkel proposed zuul/zuul master: Add spec for enhanced regional executor distribution  https://review.opendev.org/66341318:38
pabelangerjlk: tobiash: a release would be nice, if able :)18:38
*** pcaruana has quit IRC18:39
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Auto-delete expired autohold requests  https://review.opendev.org/66376218:39
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Mark nodes as USED when deleting autohold  https://review.opendev.org/66406018:39
ShrewsFrankie says "Relax. This time for sure"18:40
*** jamesmcarthur has quit IRC18:40
jlkpabelanger: it's been a while since I've done a release. I'll try to remember how to do it.18:40
pabelangertyty18:44
jlkpabelanger: this is to fix the issue w/ pull reviews?18:44
pabelangerjlk: yah18:45
openstackgerritSean McGinnis proposed zuul/zuul master: Fix minor typos in Nodepool OpenStack instructions  https://review.opendev.org/66466518:49
openstackgerritPaul Belanger proposed zuul/zuul master: Bump default_read_timeout for github driver to 300  https://review.opendev.org/66466718:52
openstackgerritPaul Belanger proposed zuul/zuul master: WIP: Bump default_read_timeout for github driver to 300  https://review.opendev.org/66466718:52
*** jamesmcarthur has joined #zuul18:59
*** jamesmcarthur has quit IRC19:01
*** jamesmcarthur has joined #zuul19:03
*** jamesmcarthur has quit IRC19:05
*** jamesmcarthur has joined #zuul19:07
openstackgerritJean-Philippe Evrard proposed zuul/zuul master: Expose date time as facts  https://review.opendev.org/66467419:09
openstackgerritMerged zuul/zuul master: Parallelize github event processing  https://review.opendev.org/66281819:14
*** jamesmcarthur has quit IRC19:15
*** hashar has joined #zuul19:23
*** igordc has quit IRC19:26
*** jamesmcarthur has joined #zuul19:34
*** armstrongs has joined #zuul19:44
*** armstrongs has quit IRC19:58
*** jamesmcarthur has quit IRC20:03
fungithe most recent recheck of 662870 hit a TimeoutException in TestAnsible28.test_plugins at 260s in the py35 job... the change sets wait_timeout=270 though so not sure why it bailed 10s early. regardless, should i be upping it even further?20:06
openstackgerritSean McGinnis proposed zuul/zuul master: Limit jobs runs with standard set of irrelevant files  https://review.opendev.org/66468020:07
openstackgerritEvgeniy L proposed zuul/nodepool master: Add `floating-ip-pool` option to specify custom pool name  https://review.opendev.org/66468120:11
openstackgerritSean McGinnis proposed zuul/zuul master: Limit jobs runs with standard set of irrelevant files  https://review.opendev.org/66468020:15
*** jamesmcarthur has joined #zuul20:25
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: download-artifacts: correct build selection  https://review.opendev.org/66468520:28
corvusclarkb, fungi: ^ sorry about that20:28
*** jamesmcarthur has quit IRC20:28
fungioops, i didn't even consider stack vs queue20:30
*** jamesmcarthur has joined #zuul20:53
*** jamesmcarthur has quit IRC21:04
openstackgerritMerged zuul/zuul-jobs master: download-artifacts: correct build selection  https://review.opendev.org/66468521:12
clarkbcorvus: sorry just got back from lunch21:14
fungii ended up taking a ~30-minute break to solder longer leads onto a replacement cpu fan and then tear down my workstation and replace its fan (for some reason the replacement fans i found come with leads just a few mm too short and rerouting them causes the case to press them into the fan housing distorting it until the fins rub against the inside, slowing it down measurably and making my cpu not cool off so21:21
fungiwell)21:21
fungihere's to less thermal throttling and not having to press f1 to ignore fan errors at boot21:21
*** igordc has joined #zuul21:31
*** hashar has quit IRC21:37
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Enhance upstream installation mode  https://review.opendev.org/66471122:06
openstackgerritKevin Carter (cloudnull) proposed zuul/zuul-jobs master: Isolate installation mode  https://review.opendev.org/66471122:29
SpamapS$ git describe22:55
SpamapS3.8.1-138-g1fab39cc22:55
SpamapSAnything I can do to help get a 3.9 out? (I assume we'd go 3.9 since there are at least 2 new minor features)22:55
SpamapSI'm about to deploy 3.8.1-138-xxxx but was thinking it would be nice if this was 3.9.0 instead. ;)22:56
clarkbwe did just redeploy opendev's zuul and haven't had problems with it though we know there is a memory leak hiding somewhere22:57
clarkbthat restart did not include the github multi processing though22:57
pabelangermulti processing would be nice22:58
SpamapSIf there's a leak, mine doesn't seem to be showing it. Mine is also super tiny.22:58
clarkbSpamapS: it shows up "randomly" after a few weeks of running. So opendev's last restart included the repl change to aid in debugging22:58
SpamapSI'm at 40 days with my 3.8.0 install22:59
pabelangerI've done some basic testing of ansible 2.8, and it seems to work22:59
SpamapShttp://paste.openstack.org/show/752782/23:00
pabelangerwe just did a reset to apply https://review.opendev.org/664667/23:01
pabelangerhoping that 'fixes' github23:01
clarkbSpamapS: http://cacti.openstack.org/cacti/graph.php?action=zoom&local_graph_id=64792&rra_id=3&view_type=&graph_start=1557615695&graph_end=1560294095 you can see it hit us there23:02
*** rlandy|ruck has quit IRC23:14
SpamapSyeah I suspect my activity is too low to notice it23:26
SpamapSBTW, I just experienced something unexpected. Two PR's, one to a branch (prod), one to master. They both got approved in a short time, and the second one is showing as dependent on the first in the Zuul UI.23:27
SpamapSI'd have thought different branches would mean different queues.23:27
fungibranches all share the queue because you might do upgrade testing or similar branch-dependent things23:28
fungiso a change to one branch could influence the result of jobs run for a change on another branch23:28
clarkband it isn't a strict dependency. If the parent fails jobs reschedule for the child without the parent23:29
fungii think we had at one point talked about some way to make that configurable23:29
clarkbwhich is different than proper git or depends-on deps23:29
fungi(configurable branch-independent queuing i mean)23:29
fungibut yeah, they're not "dependent" they're merely "sequenced"23:30
fungiin the same way that multiple projects sharing the same change queue would be23:30
SpamapSclarkb:ah, I wonder if we could make that show up as a dotted line in the UI or something.23:31
fungiwell, you might wind up with changes a,b,c in a queue where c depends on a but b got approved between them23:32
fungiso using different line styles wouldn't cut it23:32
fungithe graph of dependencies and the graph of sequencing would be hard to effectively overlay23:34
fungithough that might be a really useful alternative status view... ability to switch between queue and deptree views23:35
*** ianychoi has quit IRC23:48
*** ianychoi has joined #zuul23:48
SpamapSto quote the great Avril Levine: Why'd you have to go and make things so complicated?23:48
*** jamesmcarthur has joined #zuul23:58

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