Wednesday, 2019-06-19

sgwevening folks, I am trying the Zuul tutorial and running into an issue with the git review / push to gerrit.  I get the follow message which seems to indicate it's pushing to the wrong branch (not sure why):00:02
sgw ! [remote rejected] HEAD -> refs/publish/master (prohibited by Gerrit: not permitted: create)00:02
*** mattw4 has joined #zuul00:02
sgwif I push by hand to refs/for/master it seems to work, I use :git-review regularly with opendev.org with no issues, just seems to be a problem with the local tutorial gerrit.00:03
*** gfhellma_ has joined #zuul00:07
*** gfhellma_ has quit IRC00:09
fungisgw: you need a newer git-review release00:10
fungiwhat version are you running?00:10
fungithe version of gerrit in the tutorial is much newer than what review.opendev.org runs00:11
fungilast gerrit release dropped support for the publish refs path, and recent git-review releases are updated to adapt00:11
* fungi figures out the minimum gr version you need, just a sec00:12
fungihttps://review.openstack.org/584607 is the change which fixed it, included in the 1.27.0 release00:14
sgwfungi: 1.26.0, will a newer version be problematic for review.opendev.org?00:14
funginewer version works just fine00:14
fungii use it daily00:14
fungiyou can install latest from pypi (1.28.0) and it'll be fine with opendev's gerrit00:14
sgwfungi: BTW, I also had to make sure I was using pip3 for the initial installation of the tutorial, otherwise I got an error, you might call that out in your tutorial docs00:15
fungigood idea. which step gave you the error?00:15
sgwThe docker-compuse up needed a new version that what was installed by default packages (Ubuntu)00:16
fungithis is the "quickstart" tutorial?00:16
sgwyes, is there a different tutorial I should work through?00:16
funginope, just making sure you weren't talking about the "zuul from scratch" tutorial00:17
fungiso it was the docker-compose up in the third quote block of https://zuul-ci.org/docs/zuul/admin/quick-start.html#start-zuul-containers00:18
sgwUltimately I want to learn about using a docker container to build packages in a check job00:19
sgwyes that quote block00:19
fungisource code is here: https://opendev.org/zuul/zuul/blame/branch/master/doc/source/admin/quick-start.rst#L6600:21
fungiwhat did you end up needing to do to specify python 3?00:22
fungier, pip300:22
sgwyes, I ran pip3 install docker-compose00:23
fungiinteresting. https://opendev.org/zuul/zuul/blame/branch/master/doc/source/admin/quick-start.rst#L44 had you install docker-compose from ubuntu's packages00:24
fungibut that was too old i guess?00:24
funginow i'm starting to understand i think00:25
fungiwhat sort of error did the older (ubuntu packaged) docker-compose give you? do you happen to have it handy?00:25
sgwRight that exactly what happened first a ubuntu package install and then I did the pip3 install.00:26
sgwRight at the top of my scroll back with all the other logging going on!00:27
sgwTypeError: build() got an unexpected keyword argument 'stream'00:27
sgwGoogle was able to help me figure it out.00:27
fungiwe try to test the quick-start steps in our ci, and install docker-compose from distro packages it seems https://opendev.org/zuul/zuul/src/branch/master/playbooks/quick-start/run.yaml#L10-L1500:28
fungithe job definition is at https://opendev.org/zuul/zuul/src/branch/master/.zuul.yaml#L85-L96 and doesn't specify a nodeset, so is presumably running on ubuntu-bionic (18.04 lts, opendev's default nodeset)00:30
fungiwhat ubuntu release are you running on?00:30
*** mattw4 has quit IRC00:32
sgw18.04.2 LTS00:32
fungiokay, that's what we're testing it on00:32
fungii wonder why we don't hit it there00:32
sgwno idea, but I did hit it and the package was older.00:34
sgwI might hit you up with more questions tomorrow if that's OK, I am off to tear up an old deck00:34
fungidocker-compose 1.17.1 is what's currently in bionic anyway00:34
fungiokay, great! have fun with the deck00:35
mnaserso trying to rotate credentials here https://review.opendev.org/#/c/665917/ -- it seems like zuul is unhappy because it doesn't match the secret in the other branches00:48
mnasernow ideally we would want to change it everywhere..00:48
mnaserand it isn't really a branch-specific secret either, so i'm not sure if maybe this should live in openstack/project-config ... i dunno00:49
fungii wonder if zuul should simply ignore secrets defined on a stable branch if they're also defined in master?00:51
fungithere's presumably some reason we added that safety catch though00:51
fungideleting the copies from the stable branches should work, but obviously that makes for more work after future branching events00:52
mnaseryeah, in the future i assume this will just happen again on the next branch i guess00:52
mnaseri could go and drop them from all stable branches but just trying to future-proof this from a zuul perspective00:53
fungicode comments here lend some explanation: https://opendev.org/zuul/zuul/src/branch/master/zuul/model.py#L3610-L362800:56
fungilooks like it's similarly picky about divergent nodeset definitions on different branches00:56
mnaseryeah that explains the exact behaviour here, hmm00:57
mnaseri guess this was a conscious decision00:57
fungiit may be we were just being overly cautious, and didn't consider the implications on replacing those values in branched projects00:57
fungihttps://review.openstack.org/535501 is the change which added that logic00:59
fungithere's a fairly extensive commit message with it00:59
clarkb01:00
clarkboops01:00
mnaserfungi: the commit message contains a clear "We do not support different values for the same secret name on different branches."01:00
mnaserso i guess we should clean that up01:00
fungiyeah, so prior to that change we didn't support defining the same secret on multiple branches at all01:01
fungithat change made it possible to branch projects with secrets in them, because it became obvious that was a workflow people had01:01
fungiit may be a defensible position that zuul should allow (and ignore) divergent secret definitions from what's on master and still ignore the non-master copies01:03
mnaseryeah, but i think this seems reasonable now to avoid huge amonuts of confusion01:03
mnaserhttps://review.opendev.org/#/c/665917/ is now ok with a depends-on the stable branch that has the secret defined01:04
fungithough worth thinking about what happens when you have secret-using jobs on branches master, foo and bar and where all three differ and then you remove the secret from master01:04
mnaserwhich means things are working as planned(tm)01:04
*** igordc has quit IRC01:16
*** mattw4 has joined #zuul03:00
*** bhavikdbavishi has joined #zuul03:13
*** bhavikdbavishi1 has joined #zuul03:18
*** bhavikdbavishi has quit IRC03:20
*** bhavikdbavishi1 is now known as bhavikdbavishi03:20
*** bhavikdbavishi has quit IRC04:24
*** raukadah is now known as chandankumar04:31
*** bhavikdbavishi has joined #zuul04:37
openstackgerritTobias Henkel proposed zuul/zuul master: Evaluate CODEOWNERS settings during canMerge check  https://review.opendev.org/64455704:54
openstackgerritTobias Henkel proposed zuul/zuul master: Optionally support mitogen for job execution  https://review.opendev.org/65702405:06
*** irclogbot_1 has quit IRC05:30
*** mgoddard has quit IRC05:31
*** irclogbot_3 has joined #zuul05:32
*** mgoddard has joined #zuul05:33
*** spsurya has joined #zuul06:16
*** threestrands has joined #zuul06:27
*** gtema has joined #zuul06:29
*** themroc has joined #zuul07:04
*** igordc has joined #zuul07:05
*** igordc has quit IRC07:10
*** hashar has joined #zuul07:26
*** saneax has joined #zuul07:38
*** jpena|off is now known as jpena07:43
*** threestrands has quit IRC07:59
*** themroc has quit IRC08:10
*** themroc has joined #zuul08:11
*** pcaruana has quit IRC08:27
*** pcaruana has joined #zuul08:45
*** arxcruz is now known as arxcruz|brb08:47
*** mattw4 has quit IRC08:59
*** hashar has quit IRC09:23
*** hashar has joined #zuul09:24
*** hashar has quit IRC09:27
fbocorvus: Pagure driver merged \o/ thanks :) !09:30
*** igordc has joined #zuul09:37
*** yolanda has quit IRC09:41
badboyguys, is it possible to show IP or hostname in the Nodes tabs of static-vms?09:43
*** electrofelix has joined #zuul10:03
*** electrofelix has quit IRC10:03
*** electrofelix has joined #zuul10:09
openstackgerritMatthieu Huin proposed zuul/zuul master: Dequeue a change by its buildset UUID  https://review.opendev.org/66625810:12
*** gtema has quit IRC10:14
*** gtema has joined #zuul10:15
openstackgerritMatthieu Huin proposed zuul/zuul master: Dequeue a change by its buildset UUID  https://review.opendev.org/66625810:21
*** sshnaidm is now known as sshnaidm|afk10:24
*** saneax has quit IRC10:26
*** saneax has joined #zuul10:26
*** sanjayu_ has joined #zuul10:34
*** sanjayu_ has quit IRC10:34
*** sanjayu_ has joined #zuul10:35
*** saneax has quit IRC10:35
*** sanjayu__ has joined #zuul10:37
*** sanjayu_ has quit IRC10:40
Shrewsbadboy: No reason that info can't be added (it's stored in zookeeper, where that data comes from). That info probably isn't as useful for the openstack driver (which is probably why it isn't there). But for the static driver, that info makes sense to have.10:53
badboyShrews: I only have static-vms at the moment and that's why I'm asking about it :)10:54
* Shrews reads email about dynamic nodesets based on user location... scratches his head11:03
openstackgerritMatthieu Huin proposed zuul/zuul master: Dequeue a change by its buildset UUID  https://review.opendev.org/66625811:06
*** yolanda has joined #zuul11:17
*** jpena is now known as jpena|lunch11:19
openstackgerritJean-Philippe Evrard proposed zuul/zuul master: Expose ansible_date_time instead of date_time  https://review.opendev.org/66626811:25
openstackgerritJean-Philippe Evrard proposed zuul/zuul master: Expose ansible_date_time instead of date_time  https://review.opendev.org/66626811:30
*** arxcruz|brb is now known as arxcruz11:53
*** rfolco has joined #zuul11:54
*** gtema has quit IRC12:00
tobiashwe never had user based things in jobs and I'm not really sure if that's desirable12:06
openstackgerritMatthieu Huin proposed zuul/zuul master: web: add tenant and project scoped, JWT-protected actions  https://review.opendev.org/57690712:16
openstackgerritMatthieu Huin proposed zuul/zuul master: Dequeue a change by its buildset UUID  https://review.opendev.org/66625812:18
*** gtema has joined #zuul12:21
openstackgerritMatthieu Huin proposed zuul/zuul master: Allow operator to generate auth tokens through the CLI  https://review.opendev.org/63619712:21
*** rlandy has joined #zuul12:27
openstackgerritMatthieu Huin proposed zuul/zuul master: Zuul CLI: allow access via REST  https://review.opendev.org/63631512:28
*** sshnaidm|afk is now known as sshnaidm12:29
mnaseri have a bit of a generic question.  is there a workflow that's recommended when using zuul for a periodic task that's not necessarily tied to a specific repo?12:29
*** jpena|lunch is now known as jpena12:29
mnaserfor example: we need to run a periodic task that does mirroring of docker images.. it isn't tied to a code.. or commit or anything12:30
openstackgerritMatthieu Huin proposed zuul/zuul master: Add Authorization Rules configuration  https://review.opendev.org/63985512:32
openstackgerritMatthieu Huin proposed zuul/zuul master: Web: plug the authorization engine  https://review.opendev.org/64088412:35
openstackgerritMatthieu Huin proposed zuul/zuul master: Zuul Web: add /api/user/authorizations endpoint  https://review.opendev.org/64109912:36
openstackgerritMatthieu Huin proposed zuul/zuul master: authentication config: add optional token_expiry  https://review.opendev.org/64240812:36
openstackgerritMatthieu Huin proposed zuul/zuul master: [WIP] admin REST API: zuul-web integration  https://review.opendev.org/64353612:41
fungimnaser: perhaps a glib answer, but the configuration which defines that task needs to live in a git repository, so couldn't you say the task is tied to it?12:46
mnaserfungi: i guess that's what i ended up concluding too as well, i think that's the path i'll do, the odd thing is how to self-test that change when its meant to be a periodic job (but i guess thats why zuul enqueue is a thing)12:46
fungiwith enough abstraction you could run that in the check/gate pipelines in an incomplete way, maybe "mirroring" the images to /dev/null12:48
mnaseryeah.. or actually have a mirror target of a locally deployed registry too12:48
fungior to a local directory which then gets scooped up during log collection so that you can confirm it got the right things12:48
mnaserinstead of dockerhub in my case12:48
fungisure, fake image repository. we already have roles to make those too12:49
mnaseryep, that sounds like my path to success12:49
fungiwell, not even fake. actual image repository just not one which sticks around past the end of the buildset12:49
fungithough https://review.opendev.org/663119 will make that role slightly safer12:50
mnaseroh its nice there's an actual password12:51
mnaserbecause id liek to simulate the login too12:51
mnaserthis is aesome12:51
fungiyep12:51
mnaseris there any sample jobs i can eye (a project should be enough to point me to)12:52
fungithere are indeed. zuul's image build jobs are using this already12:53
mnasercool, ill look at zuul/zuul then :>12:53
fungi(for building our zuul docker images)12:53
fungilmk if you have any questions and i'll try to answer them, though some of this is still slightly voodoo to me12:54
fungijust because i haven't spent enough time digging into the docker protocols12:54
openstackgerritMatthieu Huin proposed zuul/zuul master: Dequeue a change by its buildset UUID  https://review.opendev.org/66625812:56
*** yolanda has quit IRC13:13
*** yolanda has joined #zuul13:17
mnaserok i've ben struggling with this for way too long..13:20
mnaserERROR! the role 'add-build-sshkey' was not found13:20
mnaseri do have roles: - zuul: zuul/zuul-jobs in there though13:20
mnaser(and i have zuul/zuul-jobs defined as an untrusted job)13:22
pabelangermnaser: have you added the role to your (base) job?13:24
mnaserpabelanger: not to the base (tbh i am still using zuul-base-jobs right now) but i added it to the job that im running13:24
pabelangermnaser: eg: https://github.com/ansible/project-config/blob/master/zuul.d/jobs.yaml#L3313:25
pabelangerI am guessing you are missing that13:25
mnaseroh i have that but without opendev.org/13:25
pabelangermnaser: is the job you are using it trusted or untrusted?13:25
mnaseri think that might be it13:25
mnaserits an untrusted job13:25
pabelangermnaser: no, opendev.org is option, that is just the connection name I have13:25
mnaserah okay13:25
pabelanger(I use full path, to help users know where it is)13:25
mnaserhttp://paste.openstack.org/show/753187/ is the job13:26
pabelangermnaser: an you have a connection to opendev.org?13:26
mnaserand i can see zuul/zuul-jobs listed under projects in the ui (with connection=opendev and type=untrusted)13:26
pabelangerokay, that should be okay13:26
pabelangerwhere is add-build-sshkey done?13:27
pabelangerwhich playbook (zuul job)13:27
mnaserim assuming the zuul-base-job is doing it13:27
mnaserbut im guessing maybe thats the issue13:27
pabelangeryou need to make sure the roles is define before or at that playbook13:27
mnaseri guess you cant just 'use' zuul/zuul-base-jobs even in some form of testing?13:27
mnaserlet me get some base jobs going13:28
mnaserand attach those roles to the base jobs13:28
pabelangermnaser: if add-build-sshkey is in base, yah the role also needs to be defined next to it13:31
openstackgerritJames E. Blair proposed zuul/nodepool master: WIP: new devstack-based functional job  https://review.opendev.org/66502313:33
openstackgerritTobias Henkel proposed zuul/zuul master: Add repl server for debug purposes  https://review.opendev.org/57996213:36
tobiashcorvus: I have to debug a weird memleak we have on web and executor so I thought it would be a good idea to finalize this ^13:37
corvustobiash: awesome, thx!13:37
tobiashwe currently have the problem that our executors show the same memleak we have also for zuul-web which renders filesystem caches useless after one day13:39
corvustobiash: cool, i like that as a first step.  i think leaving it undocumented is fine for now.  also, i was thinking we might want to do "zuul-executor enable-repl"13:39
tobiashleading to job preparation times of up to an hour :/13:39
tobiashcorvus: that is a great idea :)13:39
*** bhavikdbavishi has quit IRC13:45
tobiashcorvus: should we instead make it available only through the command socket?13:46
corvustobiash: i do think that would be preferable13:47
tobiashk, I'll change that13:47
openstackgerritMatthieu Huin proposed zuul/zuul master: URLTrigger driver time based  https://review.opendev.org/63556713:47
openstackgerritFabien Boucher proposed zuul/zuul master: A reporter for Elasticsearch  https://review.opendev.org/64492713:48
flaper87tobiash: hey, did you get the web console to work on your k8s based deployment? Mind sharing how you configured it? :)13:55
*** sanjayu__ has quit IRC13:55
*** jamesmcarthur has joined #zuul14:05
openstackgerritMatthieu Huin proposed zuul/zuul master: Get executor job params  https://review.opendev.org/60707814:12
tobiashflaper87: what kind of problem do you have?14:13
flaper87tobiash: basically, the executor is reporting its hostname but the web can't resolve it (its hostname is basically the pod name). I may be missing one config step here. I'm not setting the executor.hostname option14:29
flaper87The hostname the web service receives is correct but it can't resolve it 'cause it's not a service, it's the pod name14:29
openstackgerritJames E. Blair proposed zuul/nodepool master: WIP: new devstack-based functional job  https://review.opendev.org/66502314:30
tobiashflaper87: I'm running the executors as statefulset combined with a headless service which makes them resolvable14:31
tobiashthen the hostnames should work14:31
tobiashheadless service == Type clusterip AND clusterip==None14:32
openstackgerritTobias Henkel proposed zuul/zuul master: Add repl server for debug purposes  https://review.opendev.org/57996214:33
openstackgerritTobias Henkel proposed zuul/zuul master: Add command processor to zuul-web  https://review.opendev.org/66630714:33
tobiashcorvus: now with commandsocket ^14:33
tobiash(had to add it first to zuul-web)14:33
openstackgerritTobias Henkel proposed zuul/zuul master: Add command processor to zuul-web  https://review.opendev.org/66630714:34
openstackgerritTobias Henkel proposed zuul/zuul master: Add repl server for debug purposes  https://review.opendev.org/57996214:34
flaper87tobiash: oh, mmh, lemme try something like that.14:34
flaper87tobiash: any reason why you went with statefulset instead of deployment ?14:35
tobiashexactly because of this14:35
tobiashhaving individual pods resolvable is only possible with statefulsets14:35
flaper87lol, good!14:36
flaper87In that case, lemme change14:36
flaper87it14:36
*** gfhellma has joined #zuul14:45
openstackgerritTobias Henkel proposed zuul/zuul master: Add repl server for debug purposes  https://review.opendev.org/57996214:57
*** michael-beaver has joined #zuul15:05
*** mattw4 has joined #zuul15:11
tobiashcorvus: did you see my comment on 666177?15:13
tobiashhow urgent is this?15:13
*** themroc has quit IRC15:18
openstackgerritJean-Philippe Evrard proposed zuul/zuul master: Expose ansible_date_time instead of date_time  https://review.opendev.org/66626815:25
openstackgerritMatthieu Huin proposed zuul/zuul master: Dequeue a change by its buildset UUID  https://review.opendev.org/66625815:39
*** gfhellma has quit IRC15:40
mhuhey jhesketh I think I broke your patch by attempting a rebase: https://review.opendev.org/#/c/607078/ my apologies!15:42
corvustobiash: yes; that solution sounds okay, though we should sit down and see about addressing your underlying problems at some point :)15:43
corvustobiash: it's not urgent15:43
tobiashcorvus: yes, what I meant was it would be good if I could get a few days to address my underlying problems with that15:44
tobiashthe easiest would be a config option in the diskimage that specifies the diskimage builder executable to be used15:44
corvustobiash: yes, i think that's okay (but not ideal -- the software depends on DIB, not on "something that implements a DIB interface" -- when DIB is python-importable, we have every intention of switching to that, which would break your hack)15:46
corvustobiash: which is why i say that at some point we should figure out how to make DIB serve your needs better15:46
tobiashI don't think dib can be changed to fit our windows needs15:46
pabelangertobiash: I think that would be a great idea, we are use case for virt-customize for network appliances15:47
pabelanger(not to side track)15:47
corvustobiash: sure, which probably means you need a different builder for windows15:47
*** mattw4 has quit IRC15:47
corvustobiash: nodepool is designed to support multiple builders15:47
*** mattw4 has joined #zuul15:47
tobiashthat would be the other option15:48
tobiashwe use a custom ansible based builder that imitates the diskimage-builder cli interface15:48
corvuswe shouldn't try to shoe-horn everything into the DIB builder15:48
corvuswe should have an ansible builder :)15:48
pabelangerYES15:48
pabelangerPlease :D15:48
corvusyou don't have to ask me15:49
corvusjust do it15:49
pabelanger(TM)15:49
tobiashthat sounds good15:49
corvusthis design even pre-dates zuulv3...15:49
tobiashwe currently drive a similar way like dib (we treat a list of playbooks like the elements)15:50
pabelangerIt is on the list of things to do, so far we are relying on https://github.com/ansible-network/network-image-builder/ for network image builds.  Would be fantastic to have nodepool-builder call that directly15:50
corvusnodepool v2 had a multi-builder design.  the fact that there wasn't a second builder merely reflects the fact that openstack hasn't needed a second builder15:50
pabelangerYah15:50
corvusor, i should say, nodepool v015:50
tobiashI'll think about how we could integrate something like this that fits our needs15:50
tobiashour second use case is that we do a git-pull on our custom elements before building to make our continuous delivery easier15:52
tobiashotherwise we would need to rebuild/restart nodepool to update the elements15:52
tobiashI guess this could be solved by some pre-execution step15:52
pabelangerwhy do you need to restart?15:53
tobiashthe elements can be either baked into the container or loaded on startup in the container15:54
pabelangerah15:54
tobiashboth involve a restart of the builder to update the elements15:54
pabelangercould you place them into volume?15:54
pabelangeror is there a downside to that?15:54
tobiashon the fly updating from outside is too racy15:55
tobiashso our solution was a wrapper that updates then executes the build15:55
tobiashthat is simple and race free15:55
*** mattw4 has quit IRC15:55
* Shrews wants to come to BMW to see tobiash's zuul setup15:56
Shrewsand get a free car15:56
tobiashand could be easily replaced by a pre-buikd step15:56
* tobiash doesn't have a free car ;)15:56
tobiashShrews: but I'd happy to show you my zuul setup when we meet next at some conference :)15:57
*** mattw4 has joined #zuul15:59
tobiashso a plan could be 1) add diskimage-builder executable setting (optional, depending how important the venv change is), 2) create an ansible builder (might need a spec), 3) add pre-build step to facilitate preparation like in-place updates of elements before build16:00
openstackgerritTobias Henkel proposed zuul/zuul master: Add command processor to zuul-web  https://review.opendev.org/66630716:08
*** spsurya has quit IRC16:18
*** chandankumar is now known as raukadah16:21
*** rfolco has quit IRC16:25
*** rfolco has joined #zuul16:26
*** mattw4 has quit IRC16:37
*** mattw4 has joined #zuul16:37
*** mattw4 has quit IRC16:42
*** gfhellma has joined #zuul16:44
*** bjackman has quit IRC16:45
*** jpena is now known as jpena|off16:45
*** gfhellma_ has joined #zuul16:50
*** gfhellma has quit IRC16:53
openstackgerritJames E. Blair proposed zuul/nodepool master: WIP: new devstack-based functional job  https://review.opendev.org/66502316:56
*** mgoddard has quit IRC17:25
*** mgoddard has joined #zuul17:27
*** migi has joined #zuul17:29
migiHi. I am getting some issue defining zuul job that includes role from external project. External project has a role which has include_tasks as defined here https://github.com/rhos-infra/patch-components/blob/master/roles/patch_rpm/tasks/main.yml#L9617:31
miginow when I add the top level repo to the job definition via roles.zuul then it complains this particular line can not be found: Could not find or access [stripped] tasks/patch_opendaylight.yml' on the Ansible Controller.17:33
migieverything works fine if the project which is included does not contain the include_tasks, is this some bug in zuul or my misuse ?17:33
pabelangermigi: do you have an example of the failure? When you say roles.zuul, are you referring to jobs.role setting in your zuul.yaml file?17:36
*** mattw4 has joined #zuul17:36
corvusmigi: relative paths in ansible can be pretty confusing; i think that include is going to be relative to the current task list, so you might need to drop "roles/patch_rpm/tasks" from it since that file is already in that directory17:36
corvusmigi: so maybe it should just say "include_tasks: patch_component.yml" ?17:37
migipabelanger: here is what I am defining http://paste.openstack.org/show/753198/17:39
pabelangerI think the issue is, https://github.com/rhos-infra/patch-components/ isn't an ansible role17:39
pabelangerso, zuul isn't adding it to your role path17:40
pabelangerit is a group of roles, which I am not sure zuul supports17:40
openstackgerritJames E. Blair proposed zuul/nodepool master: WIP: new devstack-based functional job  https://review.opendev.org/66502317:40
corvuspabelanger: zuul totally supports groups of roles17:40
migipabelanger: similarly the https://github.com/redhat-openstack/octario/ is added and used as multiple roles which works ok17:41
pabelangerokay, then ignore me :)17:41
migipabelanger: the only difference between those two projects and the way it's being used is this include_tasks17:41
corvuspabelanger: https://zuul-ci.org/docs/zuul/user/config.html#attr-job.roles  fourth paragraph "contained role"17:41
pabelangercorvus: thanks!17:42
migicorvus: ok will try that, thanks for the hint17:44
migicorvus: or to make it backwards compatible will try to loop over two paths, one current and one without roles/patch_rpm/tasks17:45
corvusmigi: if omitting it works, it may be backwards compatible too17:46
corvusmigi: (ansible often has a series of locations it searches for things, so using the "closest" path may work in both situations)17:47
corvusmigi: you may be able to verify that with depends-on patches17:48
migicorvus: it's non-production version of zuul so I am fine submitting atm many changes without breaking anyone17:49
migicorvus: but yes depends-on is best here, thanks !17:49
*** hashar has joined #zuul17:50
*** gtema has quit IRC17:54
*** gtema has joined #zuul17:59
*** gfhellma__ has joined #zuul18:03
*** gfhellma_ has quit IRC18:06
*** electrofelix has quit IRC18:08
openstackgerritMatthieu Huin proposed zuul/zuul master: Dequeue a change by its buildset UUID  https://review.opendev.org/66625818:10
*** pcaruana has quit IRC18:11
*** jamesmcarthur has quit IRC18:40
*** jamesmcarthur has joined #zuul18:41
openstackgerritJames E. Blair proposed zuul/nodepool master: WIP: new devstack-based functional job  https://review.opendev.org/66502318:45
*** jamesmcarthur has quit IRC18:46
*** jamesmcarthur has joined #zuul19:04
migicorvus: removing worked, thanks a lot !19:09
*** jamesmcarthur has quit IRC19:10
*** jamesmcarthur has joined #zuul19:23
*** gtema has quit IRC19:50
*** gfhellma__ has quit IRC20:07
openstackgerritJames E. Blair proposed zuul/nodepool master: WIP: new devstack-based functional job  https://review.opendev.org/66502320:09
*** jamesmcarthur has quit IRC20:13
*** jamesmcarthur has joined #zuul20:15
*** jamesmcarthur has quit IRC20:23
corvus3.7.0 https://opendev.org/zuul/nodepool/commit/3412764a985b511cdc6b70dc801ffdb357ec02c220:41
corvus3.9.0 https://opendev.org/zuul/zuul/commit/217dea00251a51b23fe3d2083f965482eb71af8b20:41
corvuspabelanger, fungi, tobiash, mordred: ^ how's that look?20:42
tobiashlgtm20:44
pabelanger+120:44
fungi90 commits for zuul between 3.8.1 and the proposed 3.9.0 at least some of which look like more than a patch level increase, so that seems reasonable20:45
fungionly 16 for nodepool between 3.6.0 and the proposed 3.7.0 but at least some stuff (at least the openshift pod provider) warrants the minor version increase20:47
fungiyeah, lgtm corvus!20:47
corvusthat whole gpg agent thing that broke our ability to edit password files on bridge has also broken my ability to sign tags.  so this'll be a minute.20:47
SpamapS\o/20:52
SpamapSrelease day20:52
corvusokay both have been pushed20:52
*** hashar has quit IRC20:53
corvusSpamapS: fyi we're trying to keep the github changes to a mininum in this release, and then in the next, we're planning on having pabelanger and tobiash's work on retries, additional efficency, and (some) parallelization20:54
corvus(master is already slightly ahead of both of these releases)20:55
SpamapScorvus:cool. We don't have any problems with github at the moment, but we are about to migrate from github.com -> internal GHE20:56
SpamapSMeanwhile.. one struggle I'm really having is files matchers and the monorepo approach.21:02
SpamapSUsing files matchers basically renders zuul enqueue/enqueue-ref unusable.21:03
SpamapSeven if all I do is say  irrelevant-files: '.*\.md$'21:04
SpamapSthat matcher will never match on a CLI enqueue21:04
corvusSpamapS: i may have something for you, lemme dig it up21:04
SpamapSI wonder if we can figure something else out21:04
SpamapSRight now al I can do is go dig out the github webhook event and resend it.21:05
corvusSpamapS: https://review.opendev.org/66085621:06
corvusSpamapS: making sure that case is handled is more or less the reason for my -1 on that.  but i think it can be handled in a fairly straightforward way, so i expect we can merge a revision of that soon21:07
corvusSpamapS: (there is a workaround described in the first comment there -- which, briefly, is "don't add file matchers to job definitions, only add them when attaching jobs to pipelines".  it's not as elegant as fixing zuul to match our mental models, but that's something you might consider doing (depending on how complex that would be) until we can revise and merge that change.21:09
SpamapSI only have files matchers on the project attachments. :-/21:10
SpamapSBecause I attach this job in 2 projects.21:10
SpamapSStill can't enqueue it.21:11
corvusSpamapS: oops, i may not understand then21:11
SpamapSThe problem is that the files list comes from the trigger.21:11
SpamapSand the files list is empty when you trigger with the zuul CLI21:11
corvusSpamapS: are you enqueing a change or a ref?21:12
SpamapSchange21:12
SpamapSalso before we go much further.. I just found a bug in my files matchers, so it's possible the change I enqueued missed for that.. and I'm cray.. and you can stand down.21:12
SpamapScorvus: ok ya, files matcher was missing an entry. So that might be leftover PTSD from when I was using refs.21:15
corvusSpamapS: i *think* that Change objects which arrive to be enqueued that have incomplete file information are supposed to cause the mergers to go fetch their files, so in principle that case should be handled.  but enqueing from the cli is slightly different than normal triggers, so there may be an oversight there....21:15
corvusSpamapS: \o/21:15
corvusSpamapS: at any rate, let's proceed under the assumption that (once the obvious error is corrected) your setup should work as you expect21:16
SpamapScorvus: yep, it's winding through the tubes now21:16
corvusand if it doesn't, there's a bug (but not a mis-design)21:16
SpamapSI really wish there was some way to test promote jobs more thorougly locally. I find myself iterating a lot by pushing PR's into master and bugging folks for approvals whenever I'm in this situation.21:17
SpamapSHave landed like 5 "oops forgot a -" and "need to widen file matcher" commits today. :-P21:17
corvusSpamapS: yeah, i tried a thing recently where i stuck a promote job in the gate pipeline so it would self-test, but there's a nuance with how zuul caches artifact queries that renders that dangerous, so i wouldn't recommend it yet (we might be able to make zuul more robust in that situation)21:18
SpamapScorvus:yeah, in my case, it's the zuul config itself that I keep getting slightly wrong. vars, matchers, etc.21:19
SpamapSI like the idea of having a gate job for testing it, but stops short of mutating anything.21:20
SpamapSLike "if we WERE going to deploy this... would it work up to the actual deploy poart?"21:20
*** rfolco is now known as rfolco_off21:26
corvusreleases are published and announcement emails sent21:30
SpamapSwoot21:33
*** jamesmcarthur has joined #zuul21:40
*** jamesmcarthur has quit IRC21:51
*** sgw has quit IRC22:17
*** zbr|ruck has quit IRC22:17
*** rlandy is now known as rlandy|bbl22:24
openstackgerritJames E. Blair proposed zuul/nodepool master: WIP: new devstack-based functional job  https://review.opendev.org/66502322:29
*** sgw has joined #zuul22:37
*** rfolco_off has quit IRC22:56
*** dmsimard has quit IRC23:08
*** dmsimard0 has joined #zuul23:08
SpamapShm, confusing log messages today..23:30
SpamapShttp://paste.openstack.org/show/753206/23:30
SpamapSSo I have a project, GoodMoney/funnel-cake, and it has a zuul config. But zuul never runs any jobs, not even noops, on it.23:31
SpamapS"not in pipeline check"23:31
SpamapSderp23:32
SpamapSjust figured it out23:32
SpamapSno branch protection23:32

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