Monday, 2018-10-01

*** nilashishc has joined #zuul03:10
*** nilashishc has quit IRC03:15
*** nilashishc has joined #zuul03:17
*** nilashishc has quit IRC03:49
*** nilashishc has joined #zuul03:56
*** pcaruana has joined #zuul04:06
*** pcaruana has quit IRC04:23
*** nilashishc has quit IRC04:32
*** nilashishc has joined #zuul04:57
*** nilashishc has quit IRC05:41
*** jimi|ansible has joined #zuul05:42
*** pcaruana has joined #zuul05:51
*** nilashishc has joined #zuul05:54
*** jpena|off is now known as jpena07:40
*** zigo has joined #zuul07:47
*** electrofelix has joined #zuul08:30
*** nilashishc has quit IRC10:27
*** nilashishc has joined #zuul10:28
*** jpena is now known as jpena|lunch11:30
*** rfolco has joined #zuul12:21
*** jpena|lunch is now known as jpena12:31
*** nilashishc has quit IRC13:18
*** _ari_ has joined #zuul13:44
*** nilashishc has joined #zuul13:48
*** samccann has joined #zuul13:49
*** nilashishc has quit IRC13:52
*** nilashishc has joined #zuul13:58
pabelangerSpamapS: tobiash: do you happen to use unlabel property in (check) pipelines? For example, on start unlabel the 'gate' label used to enqueue into gate pipeline. To force a review again by the user.14:42
*** jimi|ansible has quit IRC14:50
corvustristanC: i chatted with mordred in person at ansiblefest and we agree https://review.openstack.org/606740 is a good solution.  left some comments.  we should also actually document that we publish that tarball.  :)14:53
tobiashpabelanger: no, didn't use it yet14:59
pabelangertobiash: k, you are gating both on code review approval, and some label for github?15:00
pabelangerThe issue i am trying to figure out, is if a new patchset is uploaded, to remove the 'gate' label when the PR is back in check, to avoid somebody pushing up a new patch and keeping the 'gate' label15:01
pabelangerunlabel works, however if because we also use /recheck to add something into check, zuul will run unlabel there too. Removing 'gate' label15:02
pabelangers/if because/if15:02
tobiashpabelanger: yes, we gate on code review and the 'merge15:05
tobiash label15:05
pabelangertobiash: okay, we've dropped code review for now due to single user on repo issue15:05
tobiashpabelanger: but unlabel on gate start sounds good15:06
pabelangerI want to add it back, but can't get past the need 2 github accounts15:06
tobiashyes, github doesn't support self-review15:06
tobiashwhen I asked about this the answer was: 'self review doesn't make sense so we don't support it'15:07
pabelangeryah15:07
jlkpabelanger: I think we didn't use labels to control that15:07
jlkbut yeah you're running into the self review thing :/15:07
tobiashjlk: any chance that self-review will be possible/allowable somewhere in the future?15:08
jlkhonestly I don't know.15:09
jlkNothing is going to get changed there right now, but after Universe I might be able to bend some ears on this15:09
jlkalthough the answer just may be "use labels"15:10
jlkpabelanger: we should probably walk through the label strategy and see where it's inadequate.15:12
pabelangerjlk: agree, would like that also15:17
*** pcaruana has quit IRC15:30
fungianother zuul case study just got posted on superuser: http://superuser.openstack.org/articles/zuul-case-study-packet-host/15:46
dmsimardsweet!15:48
SpamapSpabelanger: yes I do use it15:52
SpamapSpabelanger: I have a specific pipeline just for unlabeling things that are 'approved'15:53
corvuswhen nicole sends blurbs for the pending user stories, i'll update the website page to add them15:53
SpamapShttp://paste.openstack.org/show/731181/15:54
SpamapStobiash: ^^15:54
*** bhavikdbavishi has joined #zuul15:55
SpamapSI have that templated into all my projects now15:55
pabelangerSpamapS: thank you! I'll test that this morning, also for your check pipeline, you still trigger on pull_request, event opened / changed / reopened + recheck?15:56
SpamapSpabelanger: correct16:02
SpamapSOn the self-review thing.. honestly.. the labels workflow is pretty easy to grok and you can use my little hack to tack labels on when somebody approves something via review.16:03
SpamapSOne thing I haven't managed to circle back to is triggering things to happen on negative/dismissed reviews.16:04
pabelangerSpamapS: yah, I also was looking into branch protection things, which seem to also be able to setup number of approvals for a project.16:05
Shrewsfungi: neat. it'd be nice if the article's nodepool doc link pointed to actual nodepool docs though16:16
fungiShrews: i'll admit, i only saw someone mention the article, i'm still behind enough this morning i haven't read it yet16:17
fungioh, lookie there, it's not even morning here now :/16:17
Shrewswhen you're behind, it can still be morning  :)16:17
fungii expect it's going to be morning all day. maybe all week16:18
SpamapSpabelanger: note that if you have zuul as a required check status in branch protection then dependent pipelines won't pass the "is this mergable" check until that status is set to OK16:20
corvusShrews: good catch, i'll ask nicole to update it16:21
tobiashSpamapS: so you'r running a noop job in unlabel-on-push?16:22
*** samccann is now known as away16:24
SpamapStobiash: yep, on every project16:24
*** away is now known as Guest6268316:24
SpamapSI actually would love to have a way to basically hide these16:24
*** Guest62683 is now known as samccann16:25
tobiashSpamapS: so your mergers don't have to be afraid of being jobless ;)16:25
SpamapSI have no dedicated mergers16:26
SpamapS3 executors, they seem to get the job done.16:26
corvusSpamapS: by hide -- do you mean don't include the job result message when reporting to gh?16:27
tobiashSpamapS: I guess you mean to hide the noop job from the pipeline of every job?16:29
tobiashSpamapS: if yes, there is a way: regex project matching in a trusted repo16:29
corvushrm, 'comment' should do what i said: https://zuul-ci.org/docs/zuul/admin/drivers/github.html#attr-pipeline.%3Creporter%3E.%3Cgithub%20source%3E.comment16:29
SpamapScorvus: don't show in the UI, and don't even require a noop job to be specified in the template. It's not really a pipeline. It's just a little zuul magic.16:31
SpamapSI do have a regex that attaches it.16:31
SpamapSI just find that a bit silly16:31
pabelangerSpamapS: okay, thanks! I was able to get unlabel-on-push pipeline to work.  I guess you have a global project-template where you add unlabel-on-push: jobs: -noop to all projects, right?16:51
SpamapSpabelanger: yeah16:51
pabelangerSpamapS: great, thanks again!16:52
*** pcaruana has joined #zuul16:56
*** jpena is now known as jpena|off17:11
*** nilashishc has quit IRC17:16
*** electrofelix has quit IRC17:16
*** nilashishc has joined #zuul17:55
*** nilashishc is now known as nilashish17:55
*** nilashish has quit IRC18:06
*** jimi|ansible has joined #zuul18:08
*** nilashishc has joined #zuul18:10
*** bhavikdbavishi has quit IRC18:14
*** gundalow has quit IRC18:14
*** gundalow has joined #zuul18:14
Shrewsmordred: the install-docker role uses an 'ansible_user' variable (assumes this is defined). but when i use that role, i do not have it defined (and doesn't appear to be a fact var).18:24
Shrewsmordred: do we need to mention this as a required var in the README.rst?18:24
corvuspabelanger: can you look at http://logs.openstack.org/34/589634/5/check/openstack-zuul-jobs-linters/a6b5435/job-output.txt.gz ? i can't figure out why the skip tag isn't working18:25
Shrewsor is it *suppose* to reference a fact var18:25
Shrewsmordred: i'm also assuming you wrote that role. maybe i should check...18:26
Shrewsyep18:26
pabelangercorvus: sure18:31
pabelangercorvus: looking at project-config, it looks like we are not adding zuul_return into the ANSIBLE_LIBRARY path: http://git.openstack.org/cgit/openstack-infra/project-config/tree/tox.ini#n14 which means, we need to also add zuul as a dependency. http://git.openstack.org/cgit/openstack-infra/project-config/tree/tox.ini#n3018:47
pabelangerdoing that locally made syntax-check work as expected18:47
pabelangeryour code for tags is correct18:48
corvuspabelanger: i shouldn't skip_ansible_list have worked anyway?18:49
pabelangercorvus: in this case no, this is ansible-playbook that is raising the error, not ansible-lint18:50
corvuspabelanger: http://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/upload-logs/tasks/main.yaml#n53 is a zuul_returnn18:51
pabelangercorvus: yah, we must not be running a playbook now that invokes upload-logs in zuul-jobs repo.  I think in this case, it is the playbooks/tox/ playbooks that is getting loaded with --syntax-check18:52
pabelangerhttp://paste.openstack.org/show/731201/ was the playbooks it found for me locally (I've modified tox.ini to strip flake / ansible-lint)18:53
pabelangerthis must be the first time we are trying to load zuul_return with it18:54
corvuspabelanger: oh, so it's running the syntax check on all playbooks in the repo, and since there's a job+playbook in repo that uses the role, it's hitting that18:55
corvuspabelanger: okay, then, yeah, i think we want to do as you suggest18:56
pabelangeryes, exactly right18:56
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Extract pep8 messages for inline comments  https://review.openstack.org/58963419:04
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Add zuul to the linters tox env  https://review.openstack.org/60702619:04
corvuspabelanger: think that'll do it? ^19:07
pabelangercorvus: +219:07
*** nilashishc has quit IRC19:37
*** nilashishc has joined #zuul19:39
*** nilashishc has quit IRC19:48
*** nilashishc has joined #zuul19:49
*** nilashishc has quit IRC19:56
Shrewsmordred: oh, nm. i see where that comes from now19:56
dmsimardThere is a Zuul session at the AnsibleFest contributor summit bound to be starting any minute now -- it's hosted in #ansible-network and there should also be a bluejeans20:02
Shrewsdmsimard: hrm, bluejeans link?20:06
Shrewsdmsimard: nm, found it20:07
*** jimi|ansible has quit IRC20:16
*** pcaruana has quit IRC20:43
*** samccann has quit IRC21:05
clarkbwhat is/was subject of conversation? using zuul for ansible or making ansible better for zuul or?21:16
clarkbI just landed in austin21:16
Shrewscorvus: tristanC: fwiw, I'm having problems getting minikube running with the --vm-driver=none option. And I'm not sure I understand completely why we can't use virtualization there. May need tristanC or someone more k8s experienced to help me out.21:23
corvusclarkb: bit of both; etherpad https://etherpad.openstack.org/p/ansible-summit-october-2018-zuul there will be irc and bluejeans recordings21:24
*** caphrim007 has joined #zuul21:35
*** caphrim007 has quit IRC22:00
corvushttps://meetbot.fedoraproject.org/ansible-network/2018-10-01/ansiblefest_austin:_contributors_summit_-_zuul.2018-10-01-20.05.log.html22:01
*** ianw is now known as ianw_pto22:17
*** threestrands has joined #zuul22:42
gouthamrhi, i'm having an issue getting the "logs" directory copied over as part of the Zuul post-run - http://logs.openstack.org/29/604929/3/check/manila-tempest-dsvm-mysql-generic/9328255/ (https://review.openstack.org/#/c/604929/)23:27
gouthamrI'm changing the nodeset that the jobs use, and per clarkb's suggestion, i added a definition for the nodeset and set the groups to tempest23:27
gouthamrnodeset definition: ^ https://review.openstack.org/#/c/605810/23:28
gouthamr!! wow :P i named the node "controller" and post.yaml on my jobs is expected to copy "logs" from a non-existent "primary"23:44
openstackgouthamr: Error: "!" is not a valid command.23:44
gouthamropenstack: it should be :)23:44

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