Tuesday, 2020-11-17

*** tosky has quit IRC00:06
*** rfolco has quit IRC00:12
*** rlandy|rover|bbl is now known as rlandy|rover00:28
*** Goneri has quit IRC01:01
*** iurygregory has quit IRC01:32
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: Use --password-stdin for upload-container-image  https://review.opendev.org/76293901:46
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: Use --password-stdin for upload-container-image  https://review.opendev.org/76293901:47
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: Use --password-stdin for upload-container-image  https://review.opendev.org/76293902:00
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: Use --password-stdin for upload-container-image  https://review.opendev.org/76293902:05
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: Use --password-stdin for upload-container-image  https://review.opendev.org/76293902:09
*** zenkuro has quit IRC02:31
*** bhavikdbavishi has joined #zuul02:40
*** bhavikdbavishi1 has joined #zuul02:42
*** bhavikdbavishi has quit IRC02:44
*** bhavikdbavishi1 is now known as bhavikdbavishi02:44
*** rlandy|rover has quit IRC02:52
*** bhavikdbavishi has quit IRC03:21
*** bhavikdbavishi has joined #zuul03:22
*** bhavikdbavishi has quit IRC03:29
*** bhavikdbavishi has joined #zuul03:31
*** vishalmanchanda has joined #zuul03:52
*** donnyd has quit IRC04:07
*** donnyd has joined #zuul04:08
*** ChrisShort has quit IRC04:16
*** ChrisShort has joined #zuul04:16
*** bhavikdbavishi has quit IRC04:19
*** bhavikdbavishi has joined #zuul04:19
*** bhavikdbavishi has quit IRC04:34
*** bhavikdbavishi has joined #zuul04:37
*** johnsom has quit IRC04:46
*** johnsom has joined #zuul04:49
*** bhavikdbavishi has quit IRC04:52
*** johnsom has quit IRC05:18
*** johnsom has joined #zuul05:19
*** aprice has quit IRC05:27
*** aprice has joined #zuul05:27
*** evrardjp has quit IRC05:33
*** evrardjp has joined #zuul05:33
*** johnsom has quit IRC06:27
*** johnsom has joined #zuul06:27
*** bhavikdbavishi has joined #zuul06:53
*** bhavikdbavishi1 has joined #zuul06:56
*** bhavikdbavishi has quit IRC06:58
*** bhavikdbavishi1 is now known as bhavikdbavishi06:58
*** bhavikdbavishi has quit IRC07:24
*** bhavikdbavishi has joined #zuul07:25
*** mach1na has joined #zuul07:25
*** CraigR has joined #zuul07:29
*** bhavikdbavishi has quit IRC07:29
*** mach1na has quit IRC07:33
*** jcapitao has joined #zuul08:03
*** rpittau|afk is now known as rpittau08:05
*** bhavikdbavishi has joined #zuul08:08
*** jpena|off is now known as jpena08:09
*** hashar has joined #zuul08:11
*** jfoufas1 has joined #zuul08:11
*** sugaar has quit IRC08:12
*** sugaar has joined #zuul08:12
*** guillaumec has quit IRC08:14
*** guillaumec has joined #zuul08:15
*** tobiash has quit IRC08:15
*** bhavikdbavishi1 has joined #zuul08:15
*** bhavikdbavishi has quit IRC08:16
*** bhavikdbavishi1 is now known as bhavikdbavishi08:16
*** tobiash has joined #zuul08:16
*** guillaumec has quit IRC08:23
*** guillaumec has joined #zuul08:24
*** slaweq has joined #zuul08:51
slaweqhi zuul experts :)08:51
slaweqI'm trying to fix Neutron ovn multinode jobs08:52
*** iurygregory has joined #zuul08:52
slaweqthe problem is that in those jobs we are installing ovn and ovs from source during devstack installation08:52
slaweqand that breaks tunnel created by multi-node-bridge role08:52
slaweqso I tried to do something like https://review.opendev.org/#/c/762650/ to workaround it08:53
slaweqbut it seems for me that this jinja2 template isn't rendered correctly08:53
slaweqsee https://b18b498c87a70760171a-55be5aa52ff9f3c19ea7817c824a7dd8.ssl.cf5.rackcdn.com/762654/5/check/neutron-ovn-tempest-slow/d4cc10a/job-output.txt08:53
slaweqcan You help me with that maybe?08:53
*** tosky has joined #zuul08:56
*** sean-k-mooney has quit IRC09:27
*** sean-k-mooney has joined #zuul09:27
*** zenkuro has joined #zuul09:46
*** odyssey4me has quit IRC09:50
*** odyssey4me has joined #zuul09:50
*** felixedel has quit IRC09:56
*** felixedel has joined #zuul09:57
openstackgerritTobias Henkel proposed zuul/zuul master: WIP: Report max 50 file comments to github  https://review.opendev.org/76286909:57
*** nils has joined #zuul10:01
*** bhavikdbavishi has quit IRC10:15
*** wuchunyang has joined #zuul10:18
*** CraigR has quit IRC10:20
*** mach1na has joined #zuul10:20
*** wuchunyang has quit IRC10:22
*** mach1na has quit IRC10:54
*** wuchunyang has joined #zuul11:05
*** bhavikdbavishi has joined #zuul11:13
*** migi has joined #zuul11:29
*** mach1na has joined #zuul11:33
*** mach1na has quit IRC11:36
*** mach1na has joined #zuul11:36
*** jcapitao is now known as jcapitao_lunch11:55
*** slaweq has quit IRC11:56
*** slaweq has joined #zuul11:57
*** mach1na has quit IRC12:09
*** ianychoi_ has quit IRC12:10
*** wuchunyang has quit IRC12:11
*** rfolco has joined #zuul12:26
*** rfolco has quit IRC12:28
*** jpena is now known as jpena|lunch12:36
*** bhavikdbavishi has quit IRC12:48
*** bhavikdbavishi has joined #zuul12:48
*** jcapitao_lunch is now known as jcapitao12:55
*** rlandy has joined #zuul12:55
*** rlandy is now known as rlandy|rover12:56
*** mach1na has joined #zuul12:57
*** mach1na has quit IRC12:58
*** mach1na has joined #zuul12:58
*** jpena|lunch is now known as jpena13:24
*** Goneri has joined #zuul13:40
tobiashslaweq: could the delegate_to be an issue there?13:43
slaweqtobiash: tbh I don't know13:43
slaweqI'm not zuul and ansible expert13:43
slaweqbut should delegate_to simply create this file on the delegated node?13:44
tobiashslaweq: I think the delegated task uses the hostvars of the original node13:44
tobiashI don't know if that's an issue there since I don't know the details of that role13:44
slaweqtobiash: my modification is "just" doing script using variables which were already used in that job, also in task which was delegate_to13:45
slaweqIMO there is some issue with rendering jinja template - probably I'm doing something wrong in that template :/13:46
tobiashat least I don't see any obvious typo at first glance13:47
slaweqtobiash: I try to use this new script here https://review.opendev.org/#/c/762654/13:50
tobiashslaweq: http://paste.openstack.org/show/800094/13:50
slaweqtobiash: exactly13:50
tobiashlooking at that it looks like there is an unintended line break in there13:50
slaweqthat's my understanding too13:50
slaweqbut there is no this line break in the template :/13:50
slaweqand I don't know why it's like that13:51
tobiashmaybe the {{ switch_ip }} variable has one13:51
tobiashyes, after each of that ip address there is a line break in that file13:51
slaweqtobiash: ha13:52
slaweqYou are genius :)13:52
slaweqthx a lot13:52
tobiashno problem :)13:52
openstackgerritSlawek Kaplonski proposed zuul/zuul-jobs master: [multi-node-bridge] Add script to configure connectivity  https://review.opendev.org/76265014:00
slaweqtobiash: ^^ lets see if that will help :)14:01
*** zenkuro has quit IRC14:04
*** zenkuro has joined #zuul14:05
*** bhavikdbavishi has quit IRC14:08
*** bhavikdbavishi has joined #zuul14:56
*** lliu82 has joined #zuul14:58
*** CraigR has joined #zuul14:58
lliu82Hi, I find it a little hard to understand zuul.child_jobs What kind of jobs will show in the list?14:59
*** mach1na has quit IRC15:01
*** lliu82 has quit IRC15:02
*** LLIU82 has joined #zuul15:04
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: replace react-ansi component with re-ansi  https://review.opendev.org/76275915:08
*** CraigR has quit IRC15:15
*** mach1na has joined #zuul15:16
*** jfoufas1 has quit IRC16:14
*** mach1na has quit IRC16:26
*** iurygregory has quit IRC16:29
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: replace react-ansi component with re-ansi  https://review.opendev.org/76275916:37
corvusLLIU82: jobs that set 'dependencies' on the parent job16:45
*** LLIU82 has quit IRC16:48
*** hamalq has quit IRC16:56
*** hamalq has joined #zuul16:57
*** jpena is now known as jpena|off17:01
*** jcapitao has quit IRC17:19
*** iurygregory has joined #zuul17:19
*** rpittau is now known as rpittau|afk17:27
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: DNM: generate ansi log for benchmark purpose  https://review.opendev.org/76305417:40
openstackgerritJeremy Stanley proposed zuul/zuul-jobs master: validate-host: Options to require v4 and v6 routes  https://review.opendev.org/76306518:01
fungiclarkb: frickler: ^ i should probably work out how to include a test for that18:02
clarkbfungi: we might rely on base-test, not sure18:02
fungiwell, i meant a test for those new vars in the battery of zuul-jobs testing18:03
clarkbfungi: gotcha. Also I think continuing to support the default behavior would be good. Maybe we can use a single var: require_network_connectivty then default to 'either' but handle ipv6, ipv4, and both as values?18:04
fungiisn't it still supporting the prior behavior? i merely inverted how the passed flag was being toggled18:06
fungioh... i see18:06
*** y2kenny has joined #zuul18:06
corvusfungi: also see inline comments18:06
fungii just made it a no-op when neither is required, yup18:06
clarkbya18:06
fungithat was not intentional ;)18:06
fungii started with separate flags and then thought i could condense them to simplify the logic, but nope. fixing18:07
*** nirmoy has joined #zuul18:07
tristanCzbr: corvus: i shared ansi code rendering benchmark in https://review.opendev.org/76275918:10
nirmoyHi did any one faced:18:10
nirmoy2020-11-17 17:41:05.478390 | buildpod | MODULE FAILURE:18:10
nirmoy2020-11-17 17:41:05.478603 | buildpod | Traceback (most recent call last):18:10
nirmoy2020-11-17 17:41:05.478636 | buildpod |   File "<stdin>", line 102, in <module>18:10
nirmoy2020-11-17 17:41:05.478661 | buildpod |   File "<stdin>", line 94, in _ansiballz_main18:10
nirmoy2020-11-17 17:41:05.478683 | buildpod |   File "<stdin>", line 40, in invoke_module18:10
nirmoy2020-11-17 17:41:05.478706 | buildpod |   File "/usr/lib64/python3.9/runpy.py", line 210, in run_module18:10
nirmoy2020-11-17 17:41:05.478728 | buildpod |     return _run_module_code(code, init_globals, run_name, mod_spec)18:10
nirmoy2020-11-17 17:41:05.478750 | buildpod |   File "/usr/lib64/python3.9/runpy.py", line 97, in _run_module_code18:11
nirmoy2020-11-17 17:41:05.478771 | buildpod |     _run_code(code, mod_globals, init_globals,18:11
nirmoy2020-11-17 17:41:05.478793 | buildpod |   File "/usr/lib64/python3.9/runpy.py", line 87, in _run_code18:11
nirmoy2020-11-17 17:41:05.478815 | buildpod |     exec(code, run_globals)18:11
nirmoy2020-11-17 17:41:05.478836 | buildpod |   File "/tmp/ansible_command_payload_tajemifl/ansible_command_payload.zip/ansible/modules/command.py", line 675, in <module>18:11
nirmoy2020-11-17 17:41:05.478860 | buildpod |   File "/tmp/ansible_command_payload_tajemifl/ansible_command_payload.zip/ansible/modules/command.py", line 651, in main18:11
nirmoy2020-11-17 17:41:05.478882 | buildpod |   File "/tmp/ansible_command_payload_tajemifl/ansible_command_payload.zip/ansible/modules/command.py", line 498, in zuul_run_command18:11
nirmoy2020-11-17 17:41:05.478904 | buildpod | AttributeError: 'Thread' object has no attribute 'isAlive'18:11
nirmoy2020-11-17 17:41:05.478925 | buildpod | command terminated with exit code 118:11
nirmoy2020-11-17 17:41:05.478959 | buildpod | changed: All items complete18:11
clarkbnirmoy: please use a paste service in the future as it is more readable and doesn't flood the channel wit hmessages. And yes people have hit that, there is a discussion on the mialing list18:11
clarkblet me get a link18:11
clarkbhttp://lists.zuul-ci.org/pipermail/zuul-discuss/2020-November/001389.html the discussion starts there18:12
corvustristanC: thanks; my other question is whether we can use it in the logs tab18:12
nirmoyclarkb: sorry about that18:12
tristanCcorvus: for sure, i designed re-ansi so that it integrates transparently in zuul ui component18:13
corvustristanC: iirc, the logs tab is a little unusual in that it operates line-by-line to support line numbers and syntax highlighting of error messages18:13
clarkbnirmoy: if you run the head of master the issue is fixed, but the latest reelase doesn't have it yet. YOu can also have zuul run under an older python version on the remote (while still testing under 3.9)18:14
y2kennyclarkb: head of master for the executor?18:15
clarkby2kenny: yes18:15
tristanCcorvus: well i'd be happy to improve the logs tab too, but i think the main advantage of re-ansi is provided by bucklescript, and i'd like to benefit from the compiler optimizations18:15
y2kennyclarkb: (nirmoy is my colleague)18:16
clarkbI broght up the idea of doing a 3.9.2 release in that mailing list thread but not sure how much interest there is in that currently18:16
clarkb(the existing goal was to release 4.0 with the new zk required stuff)18:16
corvustristanC: i don't understand your answer18:16
clarkbcorvus: ^ not sure if you saw that thread18:16
nirmoyclarkb: thanks for your quick reply :)18:16
y2kennyclarkb: are the the dockerhub images are always tip of master18:16
corvusclarkb: it took about a week of work last time to do a point release; is someone willing to do that?  (i don't have time)18:17
clarkby2kenny: oh wait sorry I misread your question, no it is the python version that ansible runs under on the remote18:17
corvusclarkb: i'm happy to help push the buttons if someone else wants to do the prep.  and make sure we don't end up with crazy release notes again.18:17
clarkby2kenny: you can avoid that by running the latest executor code18:17
clarkbcorvus: I don't have time this week at least18:17
y2kennyclarkb: ok.18:17
clarkby2kenny: and yes the latest docker image should be up to date18:18
clarkby2kenny: basically 3.9.1 executor sends code to the remote node that can't run under 3.9. Latest sends code that can.18:18
tristanCcorvus: we could use re-ansi here: https://opendev.org/zuul/zuul/src/branch/master/web/src/containers/logfile/LogFile.jsx#L22118:19
corvustristanC: want to try that out and see if it scales to 10k lines?18:19
tristanCcorvus: but i think we could also benefit from bucklescript optimization if the whole logfile container was written in reason, similarly to re-ansi18:19
zbrtristanC: i am not sure if a benchmark done between incomplete ansi implementations would be correct.18:20
y2kennyclarkb: understood.  thanks18:20
openstackgerritJeremy Stanley proposed zuul/zuul-jobs master: validate-host: Options to require v4 and v6 routes  https://review.opendev.org/76306518:20
tristanCzbr: well react-ansi is also incomplete, as far as i understand it only adds color18:22
zbrtristanC: i am not saying is bad but I would first collect some real ANSI examples of stuff we naturally find on build logs. combine them and benchmark on them. also checking that it works fine.18:23
zbrimho, performance matters when feature level is relatively equal. it did not observe any performance issues myself with current one.18:24
zbron the other hand, I have the impression that I will get more attention if I make a PR towards your re-ansi repo instead of of current react-ansi18:25
zbrthe author does not seem to be very active18:25
zbrtristanC: did you cc the patterfly feature request? it would be awesome to get this into pf itself.18:27
tristanCzbr: i would be happy to review your changes. We are using ReasonML to write react component, which i find a better fit for web (and native) development than es6, thus i'd be also happy to do some onboarding too.18:32
tristanCzbr: i'm not sure why patternfly would provide such specific component18:33
*** cloudnull is now known as kecarter18:36
*** kecarter is now known as cloudnull18:36
*** nirmoy has quit IRC18:39
tobiashclarkb, corvus: what do you think about getting the 4.0 release done instead? I think we'd need mostly the first few changes of the zk preparation stack plus the mandatory sql?19:03
tobiashMandatory sql got broken due to rebases but I could fix that by tomorrow probably19:05
clarkbI'm not opposed, though currently distracted by all the gerrit upgrade planning and next week is a big holiday19:06
tobiashWe could target 4.0 maybe the week after the gerrit upgrade?19:08
tobiashI guess that work would collide with 3.9.2 as well?19:08
clarkbit conflicts with USA thanksgiving so mayn of us likely won't be around tohelp19:08
clarkbweek after I expect things to be more normal for me19:08
tobiashThe other question is can/should we extend reno such that it supports our use case of branching and releasing from older releases19:10
clarkbI want to say that openstack already does that, but I can't seem to keep the related issues paged in19:11
tobiashAt least the 3.9.1 caused a lot of trouble19:11
tobiashThe problem I think was we have one page im the docs with all releases which was not possible with simple branching and tagging19:12
pabelangeranyone up for a review: https://review.opendev.org/762939/ that switches to --password-stdin for container-upload-role, in an effort to remove no_log: true task19:13
tobiashpabelanger: won't the copy task have the pw in the json log?19:14
pabelangershouldn't19:15
pabelangerI don't believe content is rendered19:15
pabelangerhttps://6fe79164c1899b3f89c6-6113b1a0d951f28e43a544861377cc1f.ssl.cf1.rackcdn.com/762939/5/check/zuul-jobs-test-build-container-image-release/93189f0/job-output.json19:16
pabelangertestpassword only shows up, because we use set_fact19:17
*** y2kenny has quit IRC19:17
pabelangerover security stanza19:17
fungiclarkb: the only openstack reno examples i could find was branched release notes (the releases on stable branches aren't mixed back into the master branch document)19:17
clarkbfungi: gotcha the issue is the shred doc which is what tobiash thoughti t was19:17
clarkbseems like that use case woudl be one reno should support since release notes tend to be a single large doc19:18
corvusi think 4.0.0 would be preferable to 3.9.2; i don't think we should target it until 1st week of december though due to holidays/upgrade19:19
fungiyeah, i can't say for certain the problem is solveable... right now the way it works out how to include notes in a release goes by the point at which the tag appears in the branch history, so if we merge 3.9.2 back into master and delete the temporary stable branch for it, basically all release notes merged in master before 3.9.2 got merged in would get listed as belonging to 3.9.219:20
fungione workaround we talked about was merging a change to delete all new release notes, merging the tag in, then reverting the deletion, but that's exceptionally messy and not great for bisecting/pickaxe19:21
clarkbfungi: reno could create a single combined doc from scans of ever branch?19:21
fungithen the branch would need to be kept indefinitely19:22
clarkbbasically aggregate all the release notes found in /tmp or wherever and build from there rather than only building off of a branch19:22
tobiashsomething like a --all-releases option might make sense19:22
tobiashaka current branch plus all tags19:22
fungioh, mmm maybe iterating over tags yeah19:22
fungiand then doing a version sort on the tag names, and deduplicating release notes associating them with the first release (according to version sort order) they're contained in19:23
tobiashcorvus: so we could target in 3-4 weeks?19:23
fungithat would be a pretty big modification to reno, but it might work19:23
corvustobiash: sounds reasonable19:24
tobiashgreat :)19:24
corvusi honestly don't see us being able to do 3.9.2 any earlier19:24
*** bhavikdbavishi has quit IRC19:41
openstackgerritGuillaume Chauvel proposed zuul/zuul master: Fix gerrit merge commit change with zuul configuration  https://review.opendev.org/76288619:47
openstackgerritGuillaume Chauvel proposed zuul/zuul master: Fix gerrit amended merge commit change with zuul configuration  https://review.opendev.org/76288719:47
avassI got a quick review if anyone has time: https://review.opendev.org/#/c/762767/20:17
avassit adds the job node to the graph over the components, we've had a lot of users that thinks the 'executors' are the nodes the tests run on20:18
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: replace react-ansi component with re-ansi  https://review.opendev.org/76275920:18
avassI think it would be a simple way to make that a bit clearer20:18
openstackgerritGuillaume Chauvel proposed zuul/zuul master: Fix gerrit merge commit change with zuul configuration  https://review.opendev.org/76288620:22
openstackgerritGuillaume Chauvel proposed zuul/zuul master: Fix gerrit amended merge commit change with zuul configuration  https://review.opendev.org/76288720:22
avasspabelanger: re 76293920:25
avasspabelanger: oh you already got that question and answered it :)20:26
avasstobiash, pabelanger: content shows up as 'content: null' so I'm unsure if that's intentional or not. it seems like it's an unecessary risk to not use no_log there20:28
pabelangeryah, using copy / content will be safe, and it is a pattern we already use in roles20:28
pabelangersign-artifact for example20:28
pabelangeradd-sshkey20:29
avassthere's a no log for it so I guess it's fine: https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/copy.py#L50820:32
pabelangerright20:33
fungicorvus: are you still -1 on 761621 if combined with 762588?20:45
corvusfungi: i think so; i think the disappearing search icon is just plain not the way to do a hyperlink.20:47
fungiyeah, i'm not terribly keen on the icon business either. clickable text is preferable, so long as making it clickable doesn't also cause it to no longer be highlightable so the text can be copied to the clipboard20:51
openstackgerritMerged zuul/zuul-jobs master: Use --password-stdin for upload-container-image  https://review.opendev.org/76293920:53
funginot sure if this is a case of fighting the framework, and whether designers assume ~nobody copies page content from their browsers these days20:53
pabelangercorvus: do you think we can tag zuul-registry for pypi release?20:54
corvusfungi: no, i don't think so.  i think the original state of having the result be the link is perfectly feasible.  i believe this was an attempted improvement and it hasn't worked out.20:54
pabelangercorvus: actually, we'd need pypi jobs it looks like20:55
pabelangerI can work on that now20:55
corvusi believe it's okay to try things like this out, but when they don't work we should be willing to roll back.  so i'd like to see us just go back to the result being a link.  but if that was hard to discover, i have no objection to making the job also be a link.20:57
openstackgerritPaul Belanger proposed zuul/zuul-registry master: Begin publishing to pypi  https://review.opendev.org/76308620:59
*** hashar has quit IRC21:06
*** hashar_ has joined #zuul21:06
*** hashar_ is now known as hashar21:20
pabelangeris anyone aware of build-python-release job being broken?  https://zuul.opendev.org/t/zuul/build/225b52058c8e454ea4152f9008a0b5a321:24
pabelangeror a change to setuptools missing on nodes?21:24
pabelangerbefore I start down the path of fixing21:25
pabelangeractually, let me move that into #opendev21:25
clarkbI think fungi just updated those jobs?21:25
clarkbthat could be fallout21:25
clarkb?21:25
fungipabelanger: we merged https://review.opendev.org/762699 earlier today, could it be fallout from that? we stopped running ensure-tox and bindep roles21:27
fungiwe do still include ensure-pip, so i would expect we'd still have setuptools21:28
clarkbfungi: I just checked and I think these jobs are in zuul-jobs and not affected by openstack21:28
clarkbI think I know what it is21:28
clarkbpython2 is being used and not python3?21:28
*** nils has quit IRC21:29
clarkbpabelanger: ^ check zuul and nodepool release jobs they may set python3 explicitly and that may be the fix you need21:29
pabelangeroh, you might be right21:29
fungiyeah, so probably unrelated as i only altered pti-python-tarball and python-branch-tarball playbooks in openstack/project-config21:29
pabelangeryah, that looks to be it21:29
openstackgerritPaul Belanger proposed zuul/zuul-registry master: Begin publishing to pypi  https://review.opendev.org/76308621:30
pabelangerclarkb: thanks for the pointer21:30
*** holser has quit IRC21:52
pabelangerclarkb: corvus: https://review.opendev.org/763086 is passing now (release jobs)21:57
pabelangerfor zuul-registry21:57
*** y2kenny has joined #zuul22:03
y2kennyhas anyone run into "Executing local code is prohibited" when using prepare-workspace-openshift recently?22:03
y2kennyhttp://paste.openstack.org/show/800125/22:04
clarkby2kenny: the raeson for that is going to be that the role does command or shell on localhost and zuul restricts that to trusted playbooks only22:04
clarkby2kenny: the likely fix in your case is to move that role into a bse job in a trusted repo or similar22:05
*** y2kenny58 has joined #zuul22:05
*** y2kenny58 has quit IRC22:05
*** y2kenny1 has joined #zuul22:06
*** y2kenny1 has quit IRC22:06
*** y2kenny64 has joined #zuul22:07
*** y2kenny has quit IRC22:08
*** y2kenny64 has quit IRC22:09
*** y2kenny has joined #zuul22:09
y2kennyit has been working for me without problem.  The only thing I just changed is upgrading the executor (which I didn't think it's an issue.)22:10
clarkby2kenny: depending on which version you upgraded from that may be it. There was a security hole plugged around this22:10
y2kennyclarkb: ok... I am guessing prepare-workspace-openshift needs to be run by trusted project all the time?  (like it can't be included by untrusted project?)22:12
fungiyes, older versions of the executor didn't realize they were supposed to forbid that22:12
fungiit can be in a parent job inherited by jobs in an untrusted project22:12
fungibut the playbook calling prepare-workspace-openshift should be in a job defined in a trusted repo22:13
y2kennyum... Ok...  it needs to be inherited at the job level... ok22:13
clarkbthe reason for that is the trusted repo's code will only be used in a merged state not a pre merge state22:13
clarkbhaving this check in place ensures that people have checked any code changes and merged them before they are used when they can be used in sensitive areas22:14
y2kennyright... I probably wasn't quite clear about the security model at the time and thought I understood the model since things work22:14
y2kennythis actually answered a question I have for awhile... when to use job inheritance and when to just include_role22:15
y2kennythanks folks.22:15
y2kennyclarkb: although this bring up another issue I ran into awhile back (I am not sure if it's fixed now.)  Is it still true that I cannot modify the inventory across play?22:16
clarkby2kenny: you cannot across playbooks, but each playbook can load in extra inventory stuff iirc22:18
fungiy2kenny: announcement was here: http://lists.zuul-ci.org/pipermail/zuul-announce/2020-July/000078.html22:18
fungifor the executor security fix22:19
y2kennyfungi: thanks22:19
y2kennyclarkb: um... is there a recommended way to pass information across playbook?22:20
clarkbI think zuul return maybe available between playbooks. corvus is that true?22:21
y2kennyactually... may be this still work... I just need to be more creative I guess.  What I have is a role that launches a pod in a received k8s namespace resources and add the pod into the inventory.22:21
y2kennyand then run prepare-workspace-openshift22:21
clarkbtristanC and tobiash may have ideas too as they use k8s a bit more than I do22:22
y2kennythis role was included in the playbook such that the pod  in the inventory is available within the same playbook.  But now that the security hole is fixed, the prepare-workspace-openshift no longer works.22:23
y2kennyIdeally I should have the pod launching in a pre- playbook in some base job but then I need to figure out how to pass the pod info across the playbook22:24
clarkbI think another option is you can write into the build dir then read that info back in later22:24
y2kennyI think tristanC or someone else may have a patch that allow inventory modification but I don't think that was merged.22:25
clarkbso make pod, prepare-workspace, write details to the build dir, in next playbook read those details and add host to inventory22:25
*** holser has joined #zuul22:25
y2kennyclarkb: ah... I can give that a try22:25
*** hashar has quit IRC22:26
tristanCclarkb: iiuc, zuul return passes variables accross jobs, and using the special set_facts `cacheable: true` may makes a fact variable available for the next playbook22:30
tristanCy2kenny: the change to enable a playbook to update the inventory for the other playbook is https://review.opendev.org/590092 , and that can be emulated by dumping host info the executor work_dir, and then reloading in the next playbook22:31
clarkboh right you can set facts and cache them22:32
clarkbthat is probably the easiest option here22:32
y2kennyawesome.  I will play around with this.  Thanks clarkb, tristanC22:33
tristanCy2kenny: and this is how software-factory setup container native job, using the emulation trick here: https://softwarefactory-project.io/cgit/software-factory/sf-config/tree/ansible/roles/sf-repos/files/config/playbooks/openshift/deploy-project.yaml#n6322:33
tristanCy2kenny: in the run phase, you can load the pods.yaml file and use add_host22:33
y2kennynice.22:34
tristanCi think that's what `cacheable: true` does, but i find the explicit dump less magic22:35
tristanCy2kenny: here is how the load works from the integration job: https://softwarefactory-project.io/cgit/software-factory/sf-ci/tree/roles/health-check/openshift/tasks/demo_project_zuul_configuration.yml#n4022:37
y2kennyok, got it.22:38
corvusthere are a number of jobs in zuul-jobs that use cacheable:true to pass facts from one playbook to the next23:07
corvusy2kenny: it's a good pattern for passing information23:07
*** armstrongs has joined #zuul23:12
*** slaweq has quit IRC23:21
*** armstrongs has quit IRC23:22
pabelangerI'm seeing missing dependency when running nodepool config-validate23:26
pabelangermsrestazure23:26
pabelangerhttp://paste.openstack.org/show/800137/23:27
pabelangerlooks like azure driver?23:27
pabelangerah23:31
pabelangerhttps://review.opendev.org/752724/23:31
pabelangerclarkb: corvus: do you think we can have a new nodepool release to pull in^23:32
*** zbr has quit IRC23:57
*** zbr4 has joined #zuul23:57
*** tosky has quit IRC23:58

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!