Wednesday, 2019-11-20

*** tjgresha has quit IRC00:09
*** rlandy|rover has quit IRC00:44
*** rfolco has quit IRC00:52
*** sgw has quit IRC01:01
*** armstrongs has joined #zuul01:04
*** armstrongs has quit IRC01:13
*** sgw has joined #zuul01:18
*** adso78 has quit IRC01:27
*** jamesmcarthur has joined #zuul02:06
*** michael-beaver has quit IRC02:12
*** igordc has quit IRC02:18
*** bhavikdbavishi has joined #zuul02:35
*** bhavikdbavishi1 has joined #zuul03:18
*** bhavikdbavishi has quit IRC03:20
*** bhavikdbavishi1 is now known as bhavikdbavishi03:20
*** bjackman has joined #zuul03:34
openstackgerritIan Wienand proposed zuul/zuul-jobs master: use-buildset-registry: Vendor pytoml and remarshal  https://review.opendev.org/69505004:46
*** threestrands has joined #zuul05:18
*** pcaruana has joined #zuul05:25
openstackgerritIan Wienand proposed zuul/nodepool master: Dockerfile: add DEBUG environment flag  https://review.opendev.org/69484505:32
openstackgerritIan Wienand proposed zuul/nodepool master: [wip] move openstack testing to use containerised daemon  https://review.opendev.org/69346405:32
*** themroc has joined #zuul07:23
*** bjackman has quit IRC07:32
*** tosky has joined #zuul07:35
*** threestrands has quit IRC07:58
*** avass has joined #zuul08:23
*** jpena|off is now known as jpena08:49
avassI'm not sure if I'm blind because I'm tired or something else is going on here but this: http://paste.openstack.org/show/786386/ is producing a strange error for the weekly pipeline.08:57
avassWith this error: http://paste.openstack.org/show/786388/08:57
avasswhich is strange because I can't find an reference to a 'weekly-pass-release-configuration-parse' in any of our repos08:58
avassthe check/gate jobs are working perfectly fine08:59
avassany suggestions on how to proceed?09:04
*** rfolco has joined #zuul09:05
*** jamesmcarthur has quit IRC09:07
*** rfolco has quit IRC09:09
*** saneax has joined #zuul09:12
*** tosky has quit IRC09:13
*** tosky has joined #zuul09:14
*** jamesmcarthur has joined #zuul09:15
*** themr0c has joined #zuul09:56
*** themroc has quit IRC09:58
*** NBorg has joined #zuul10:18
*** mhu has joined #zuul10:27
*** bhavikdbavishi has quit IRC10:28
NBorgHello. We want to run ansible-lint through tox. Is there a package we can require for the linter to not throw an error when we use zuul_return in our playbooks/roles?10:31
*** mhu has quit IRC10:34
*** mhu has joined #zuul10:43
*** bhavikdbavishi has joined #zuul10:50
*** swest has joined #zuul10:54
*** bhavikdbavishi1 has joined #zuul10:57
*** bhavikdbavishi has quit IRC10:58
*** bhavikdbavishi1 is now known as bhavikdbavishi10:58
*** swest has quit IRC11:03
*** swest has joined #zuul11:04
*** PrinzElvis has quit IRC11:08
NBorgNever mind. It was just zuul. Ee had an old path to ansible action plugins.11:42
NBorgWe*11:42
*** rlandy has joined #zuul11:55
*** rlandy is now known as rlandy|rover11:55
*** NBorg has quit IRC12:03
*** PrinzElvis has joined #zuul12:15
*** pcaruana has quit IRC12:24
*** jpena is now known as jpena|lunch12:29
*** swest has quit IRC12:31
*** pcaruana has joined #zuul12:50
fungiavass: unless there's a dependency declared from weekly-test-pass-release-configuration-verify or one of its parent jobs on a weekly-pass-release-configuration-parse job on some branch of some repository (whether or not that's defined) then the only other guess would be it used to exist and a zuul bug causing it to cling to outdated configuration for some reason12:56
fungihave you tried exploring the relevant jobs with the jobs interface in the zuul web dashboard?12:56
*** avass has quit IRC13:19
*** jpena|lunch is now known as jpena13:36
*** AJaeger has quit IRC13:58
*** AJaeger has joined #zuul14:06
*** saneax has quit IRC14:11
*** PrinzElvis has quit IRC14:38
*** jamesmcarthur has quit IRC14:49
*** avass has joined #zuul14:52
avassfungi: I'm getting the 'Something went wrong.' screen for taht job in the dashboard14:54
avasseven after doing a full-reconfigure14:55
corvusavass: were there any lines before  http://paste.openstack.org/show/786388/ in the log?  it may have indicated whether it was going to run that job or not.  also, is that logging at debug level?14:56
corvusavass: another thing to check is that there may be a files matcher or something on test-pass-release-configuration-parse which is the parent of the job that's not being run.  it could also cause it not to run.14:57
*** jamesmcarthur has joined #zuul14:57
avasscorvus: I'll check14:58
avasscorvus: but I saw a discussion about jobs in timed pipelines not triggering if they have any files specified a couple of days ago so that's why they are separated14:59
corvusavass: ah yeah, then presumably that one shouldn't.  the other thing to check would be branches then.15:00
avassah yeah, it's also because of the branches. we're still running zuul2 on master but working on zuul3 on that feature branch15:01
corvusavass: that'll do it.  every job in the inheritance hierarchy will need a variant on the feature/zuul3 branch in order for the job to run.  so probably just adding a 1-line job def for "name: test-pass-release-configuration-parse" with "branches: feature/zuul3" would do it.15:04
corvusavass: er, strike that15:04
avass:)15:05
corvusavass: just add "branches: [master, feature/zuul3]" to the existing def of test-pass-release-configuration-parse"15:05
avassah, but we want to run the weekly on master but the check/gate jobs on the branch. that's why they look like that15:05
avasslooks like I got a different error from the scheduler after running full-reconfigure actually so that could be it.15:07
corvusavass: is that config snippet you sent from .zuul.yaml in the feature/zuul3 branch of an untrusted project?15:10
avassit's from master in an untrusted project15:12
corvusavass: it also has a feature/zuul3 branch?15:13
avassyep15:13
avassfixed the new error and the old one is back15:13
corvusavass: here's a suggestion: http://paste.openstack.org/show/786423/15:14
corvuser, 1 sec.15:15
corvusavass: http://paste.openstack.org/show/786424/15:15
corvusthis is a little tricky since you're wanting to avoid check/gate on master.  that turns of implied branch matchers, so that all the job definitions apply to every branch you use them.  then on the feature/zuul3 branch, we add the check/gate jobs.  then in the config project we set up the weekly jobs to run on master.15:16
corvusavass: let me explore one more idea15:17
corvus(since now i know you're okay with putting zuul config in the master branch)15:17
avassyeah, as long as we don't have anything trigger by changes to master really15:18
corvusavass: this should do the same with no config-project: http://paste.openstack.org/show/786428/15:20
corvusavass: you can also switch the branches like this: http://paste.openstack.org/show/786426/15:21
corvusdepending on whichever is more convenient15:21
corvusthen, when you're ready to engage gating on master, copy the job defs to the other branch, then drop the "pragma".15:21
corvusthe "project" stanzas, when they appear in an untrusted-project, always apply only to the branch they appear in.  i think that's the clearest way of saying "do this on this branch".  you just check the project stanza in the .zuul.yaml on the branch in question, and you'll see what's running on that branch.15:24
corvus(the pragma that turns off implied-branch-matchers just means that it no longer matters which branch the jobs are defined in, they will run the same way on every branch and only need to be defined once.  it's useful in this case since you don't need branch variants, but once you start having zuul manage more branches, it'll probably get in the way and you should go back to the normal case of per-branch job15:26
corvusvariants)15:26
corvushttps://zuul-ci.org/docs/zuul/user/config.html#attr-pragma.implied-branch-matchers15:26
avasswait, so does job 'A' on branch feature/1 with 'branches: master' even though the job itself is not on master?15:28
avassbecause I just found that missing job and it's on the feature branch.15:29
corvusavass: can you clarify the question?15:29
corvus(that question was missing at least one important word :)15:30
avassjob 'A' trigger.. :)15:30
AJaegercorvus: see also https://opendev.org/openstack/glance/src/branch/stable/train/.zuul.yaml#L291-L304 - this is a problem, isn't it?15:30
AJaegerSo, that needs some education with the glance folks...15:30
avassso the job 'weekly-test-pass-release-configuration-verify' exists on feature/zuul3 with 'branches: master', 'depedencies: [weekly-pass-release-configuration-parse]' (which is wrongly configured)15:32
corvusAJaeger: that may actually be the right thing to do in that case -- assuming there's a copy of that on the master branch, that will all match there, but it won't match anywhere else, therefore, things only run on master.15:33
AJaegercorvus: it's on all branches. So, I wonder: IF they remove a job from master branch but it's still on stable/train - will it run?15:34
corvusavass: yes, if you set explicit branch matchers, they override anything else.  so you can have a job on feature/zuul3 that matches the master branch (but you couldn't cause it to run on the master branch except by adding it to a project stanza on master, but if you did that, it would).15:34
corvusAJaeger: it will not, because the project stanza on train won't match master.15:34
AJaegerah15:35
AJaegerthanks, corvus15:35
corvusAJaeger: (basically, just like jobs have a "branches" matcher, project stanzas do as well, but you can't change it, it's always simply the branch where the project stanza is defined)15:35
avasscorvus: that's probably what happened then because the jobs have the same name but different dependencies, one of them being wrongly configured.15:35
corvusAJaeger: (except in config projects, where there are no branch matchers on project stanzas)15:36
corvusAJaeger: (so a project stanza in a config project matches all branches -- to do branch selection, you would then have to put branch matchers on the jobs themselves in the project-pipeline config)15:36
AJaegercorvus: the config-project I understand, the others is the fun part ;)15:37
corvusAJaeger: it sounds complex when i write it out, but it's usually pretty intuitive: probably the most intuitive part: if you want to see what jobs run on a given branch, just look at the "project" stanza in that branch.  :)15:39
avasscorvus: gotta go soon so I'll have to take a closer look at your suggestions tomorrow. thanks!15:39
corvussorry about that sentence, i'm still jetlagged, but you get the idea.15:39
corvusavass: hope it helps! let me know if you have more questions.15:40
avasscorvus: anyway, there's gertty, boartty and presentty. any plan on a zuultty? :)15:40
AJaegercorvus: ;)15:40
corvusavass: :) my favorite interface to zuul is gerrit itself... but i think someone actually did write a tool that renders the status page in the console15:41
fungi"czuul" was it?15:41
funginot sure if it kept up pace with v3 development though15:41
corvusfungi: yeah that's it.  it's probably not far out of date, the status page didn't change much15:41
corvushttps://github.com/harlowja/gerrit_view/blob/master/scripts/czuul15:42
fungiyou beat me to that link by seconds! ;)15:42
avassnice, I'll take a look at it :)15:44
avassI'm gonna have a quck demo of zuul3 here at Volvo Cars for a couple of people using presentty. Just thought that it was a bit strange that there wasn't a tty for zuul itself ;)15:47
fungiwell, there's always `wget -Qo- ... | flamel -`15:48
avasshaha15:48
corvusczuul is what introduced me to urwid (the toolkit that gertty/presentty use)15:48
fungispeaking of which, i thank SpamapS in my head daily for flamel15:48
fungii should thank him more out loud too15:48
fungiSpamapS: thanks again for making flamel!15:48
dmsimardflamel ?15:48
SpamapSfungi: 🙇 (bow)15:49
dmsimardSpamapS, fungi: link ? curious :)15:49
SpamapSpip install flamel15:49
SpamapSI use it daily. :)15:49
fungime too15:50
fungihttps://github.com/SpamapS/flamel15:50
SpamapSpatches accepted: https://github.com/SpamapS/flamel15:50
SpamapSI should add a cheeky README15:50
*** rlandy|rover is now known as rlandy|rover|mtg15:50
fungisomething something alchemy something15:50
SpamapSThe name is a play on words with YAML and Nicholas Flamel, who claimed to be able to turn lead in to gold via alchemy. ;)15:50
dmsimardnot exactly clear what it does at first glance -- loads stdin and pretty prints it ?15:50
corvusdmsimard: the project description says:15:51
corvusFlamel flips yaml to json and vice versa15:51
fungitranslates back and forth between json and yaml15:51
dmsimardohhhh15:51
fungithe implementation is fairly simple, but also very useful15:51
dmsimardneat15:51
avassgotta go, I'll check in later tonight to update my change in zuul-jobs15:52
avass(please have a look at it if you have time)15:52
*** avass has quit IRC15:53
SpamapSfungi: and many thanks to mordred for making the mapping keys appear in the same order as they appear in the input.15:54
fungiahh, yep15:59
fungithough in python3.7+ that may happen by default anyway16:00
*** rlandy|rover|mtg is now known as rlandy|rover16:01
SpamapSfungi: I'm not so sure, that would require the json and YAML modules to keep the order in what they produce, which is the magic that mordred did.16:08
SpamapSBut yeah probably. :)16:09
SpamapSanyway, thanks for the bump, I added a README. :)16:09
fungiright, i'm surmising they they both internally use python dicts and so would inherit the change to deterministic dict ordering anyway16:10
fungimy primary use is (per above) to grab unreadable rest api json vomit and shove it through stdin on a pipe to get pretty yaml out the other end16:12
fungiso the autodetection is especially useful there16:12
SpamapSsame16:13
SpamapSalso I use it to pipe yaml into jq sometimes. :)16:13
fungioh, yep, that can also be handy. done that a few times myself16:13
fungialso, great readme!16:14
AJaegercorvus: in the context of jobs and branch matches, there's also http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010990.html - hope my initial email was correct16:18
*** gmann has joined #zuul16:21
corvusAJaeger: your advice looks good to me16:23
AJaegerthanks for confirming16:27
mordredSpamapS: my pleasure - but also, I second the thankfulness to you for having created it in the first place. I use the crap out of it16:32
corvusshould i make a build-podman-image role to mirror build-docker-image, or add a flag to build-docker-image to tell it to use podman commands (and then maybe start working to rename the roles)?16:51
corvusactually, maybe i should create 'build-container-image' and have it take a parameter, then later add upload- and promote-container-image, also with a parameter for the command system as well as target registry16:55
*** tjgresha has joined #zuul17:08
*** michael-beaver has joined #zuul17:25
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: WIP: use-buildset-registry: add podman support  https://review.opendev.org/69505117:35
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add build-container-image role  https://review.opendev.org/69525117:35
fungibuild-container-image sounds wonderfully generic, as long as "container images" are standardized (whether ietf or merely de facto)17:46
*** igordc has joined #zuul18:00
*** jpena is now known as jpena|off18:00
*** mattw4 has joined #zuul18:19
*** tosky has quit IRC18:55
*** bhavikdbavishi has quit IRC18:55
*** jamesmcarthur has quit IRC19:14
*** avass has joined #zuul19:15
*** jamesmcarthur has joined #zuul19:27
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Adds go jobs and roles.  https://review.opendev.org/69111419:28
*** jamesmcarthur has quit IRC20:20
*** jamesmcarthur has joined #zuul20:23
*** jamesmcarthur has quit IRC20:24
*** jamesmcarthur has joined #zuul20:26
*** michael-beaver has quit IRC20:45
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: WIP: use-buildset-registry: add podman support  https://review.opendev.org/69505120:54
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: WIP: use-buildset-registry: add podman support  https://review.opendev.org/69505121:22
*** tosky has joined #zuul21:41
*** pcaruana has quit IRC21:42
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: WIP: use-buildset-registry: add podman support  https://review.opendev.org/69505121:47
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: WIP: use-buildset-registry: add podman support  https://review.opendev.org/69505122:04
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: WIP: use-buildset-registry: add podman support  https://review.opendev.org/69505122:18
corvusmordred, tristanC: i don't understand this error; it works locally: https://zuul.opendev.org/t/zuul/build/bb0eae37627c43e18ea8108a96e88ead/log/job-output.txt#966-98122:41
corvusoh, it's not stdlib, i thought it was22:45
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: use-buildset-registry: Vendor pytoml and remarshal  https://review.opendev.org/69505022:48
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add build-container-image role  https://review.opendev.org/69525122:48
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: WIP: use-buildset-registry: add podman support  https://review.opendev.org/69505122:48
corvusi don't think it's used in that code path, so i excised it22:48
*** jamesmcarthur has quit IRC22:57
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: use-buildset-registry: Vendor pytoml and remarshal  https://review.opendev.org/69505023:05
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add build-container-image role  https://review.opendev.org/69525123:05
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: WIP: use-buildset-registry: add podman support  https://review.opendev.org/69505123:05
*** rlandy|rover is now known as rlandy|rover|bbl23:13
ianwhrm, this is annoying ... it seems that dib when running in a container with nodepool in debug mode never exits23:56
ianwhttps://zuul.opendev.org/t/zuul/build/b5ab8b39657f41a68951fc0aa7a967ec/log/nodepool/builds/test-image-0000000002.log#786923:56
ianwit's stuck on a "wait" ... I don't think this happens in non-debug mode23:57
ianwi suspect something to do with open file descriptors ... ?  anyone seen anything like that23:57
ianwit's a bit odd not running it in daemon mode (in container) ... perhaps nobody has tried this combo23:58
clarkbianw: do you maybe need to do docker run -t for a tty?23:58
ianwyeah, i mean i wouldn't think so ... but maybe :/23:59
*** mattw4 has quit IRC23:59

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