Thursday, 2020-04-02

*** armstrongs has joined #zuul00:02
*** armstrongs has quit IRC00:11
*** rfolco has quit IRC00:43
*** y2kenny has quit IRC00:48
*** cdearborn has quit IRC01:13
*** weshay|ruck is now known as weshay01:31
*** swest has quit IRC01:34
*** swest has joined #zuul01:49
*** Goneri has quit IRC01:50
*** ysandeep|away is now known as ysandeep|rover01:57
*** zxiiro has quit IRC02:15
*** ysandeep|rover is now known as ysandeep|rover|b03:26
*** bhavikdbavishi has joined #zuul03:39
*** igordc has quit IRC03:42
*** bhavikdbavishi has quit IRC03:48
*** bhavikdbavishi has joined #zuul03:56
*** bhavikdbavishi1 has joined #zuul04:11
*** bhavikdbavishi has quit IRC04:13
*** bhavikdbavishi1 is now known as bhavikdbavishi04:13
*** ysandeep|rover|b is now known as ysandeep|rover04:19
*** evrardjp has quit IRC04:36
*** evrardjp has joined #zuul04:37
*** swest has quit IRC04:55
*** swest has joined #zuul04:55
*** hashar has joined #zuul04:58
*** threestrands has joined #zuul05:06
*** mnasiadka has quit IRC06:21
*** mnasiadka has joined #zuul06:22
*** avass has joined #zuul06:50
*** sugaar has joined #zuul06:53
*** frickler_ is now known as frickler07:05
*** hashar has quit IRC07:06
*** jcapitao has joined #zuul07:13
*** rpittau|afk is now known as rpittau07:17
openstackgerritJan Kubovy proposed zuul/zuul master: Connect fingergw to Zookeeper  https://review.opendev.org/71687507:27
*** masterpe has quit IRC07:29
openstackgerritJan Kubovy proposed zuul/zuul master: Connect fingergw to Zookeeper  https://review.opendev.org/71687507:30
openstackgerritSimon Westphahl proposed zuul/zuul master: Render buildset progress bar correctly  https://review.opendev.org/71687807:32
openstackgerritJan Kubovy proposed zuul/zuul master: Connect fingergw to Zookeeper  https://review.opendev.org/71687507:40
*** bhavikdbavishi has quit IRC07:40
*** ysandeep|rover is now known as ysandeep|rover|l07:43
*** jpena|off is now known as jpena07:54
*** masterpe has joined #zuul07:58
openstackgerritSimon Westphahl proposed zuul/zuul master: Render buildset progress bar correctly  https://review.opendev.org/71687808:00
*** threestrands has quit IRC08:01
*** tosky has joined #zuul08:02
AJaegerI now have a memory error on pep8: https://zuul.opendev.org/t/openstack/build/23286cf5ecc54fccb8d87172ecc5476808:17
*** bhavikdbavishi has joined #zuul08:17
AJaegerThe flake8wrap script looked in .tox etc ;( now fixed ^08:28
*** ysandeep|rover|l is now known as ysandeep|rover08:33
*** hashar has joined #zuul08:35
openstackgerritAntoine Musso proposed zuul/zuul master: Enhance some logging messages  https://review.opendev.org/70433108:45
openstackgerritAntoine Musso proposed zuul/zuul master: Add details to waitUntilSettled() debug log  https://review.opendev.org/70438008:48
openstackgerritAntoine Musso proposed zuul/zuul master: tests: throttle after all builds have reported  https://review.opendev.org/70438108:49
openstackgerritAntoine Musso proposed zuul/zuul master: tox: rename pep8 to linters  https://review.opendev.org/70363508:58
openstackgerritAntoine Musso proposed zuul/zuul master: tox: do not install bindep for linters  https://review.opendev.org/70363608:59
*** sshnaidm|afk is now known as sshnaidm09:25
openstackgerritTobias Henkel proposed zuul/zuul master: Ensure correct cleanup on repo update and reset  https://review.opendev.org/70153110:05
*** rpittau is now known as rpittau|bbl10:14
*** hashar is now known as hasharLunch10:17
openstackgerritTobias Henkel proposed zuul/zuul master: Ensure correct cleanup on repo update and reset  https://review.opendev.org/70153110:18
*** gtema has joined #zuul10:21
gtemaI'm trying to finally enable gating for github, where I want zuul to merge PR from feature branch into master. Current failure I get is "No base commit found ...". What can I do?10:23
openstackgerritMerged zuul/zuul-jobs master: Do not end host if correct go version is installed  https://review.opendev.org/71660710:24
openstackgerritMerged zuul/zuul-jobs master: go-jobs: improve testing  https://review.opendev.org/71666810:24
*** ysandeep|rover is now known as ysandeep|brb10:34
*** rfolco has joined #zuul11:01
*** jcapitao is now known as jcapitao_lunch11:03
*** bhavikdbavishi has quit IRC11:13
openstackgerritTobias Henkel proposed zuul/zuul master: Ensure correct cleanup on repo update and reset  https://review.opendev.org/70153111:19
tobiashgtema: that sounds lie the feature branch is disconnected from the master11:22
tobiashs/lie/like11:22
gtemait's not, since the github itself can merge it without problems11:22
gtemaand this whole branch is like 'git checkout -b FEATURE && git add .zuul.yaml && git push origin FEATURE11:23
gtemaso really a single commit11:23
tobiashgtema: in this case a log would help to see where in the workflow this happens11:23
gtemathe scheduler fails with message about cross-repo conflict (which it is not), but I see this is anyway a default error11:23
gtemalog: this is exactly weird - there are lot's of those "can not find base" debug messages, then it still checks out everything in the tenant, starts some playbooks and there is no real "failure" in the executor log (no separate merger)11:24
*** ysandeep|brb is now known as ysandeep|rover11:25
gtemaI mean a really lot output11:25
gtemathose merger messages were already hard to find11:25
gtemaand no ansible failed plays11:26
gtemaI still have a feeling that it tries to do something with other repo (as a cross-dep, which should not be the case). Otherwise I can't understand why it tries to start jobs from totally independent projects11:27
*** jpena is now known as jpena|lunch11:36
gtematobiash - found it. Very epic and weird: on github master branch policy required linear history (without merge commits)12:08
gtema1) before scheduler restart I didn't see that in logs, that it was forbidden12:09
gtema2) github itself is still allows admin to merge it, so I was never actually noticing that12:09
*** hasharLunch is now known as hashar12:11
*** bhavikdbavishi has joined #zuul12:12
*** rpittau|bbl is now known as rpittau12:12
*** rlandy has joined #zuul12:20
*** bhavikdbavishi1 has joined #zuul12:25
*** bhavikdbavishi has quit IRC12:26
*** bhavikdbavishi1 is now known as bhavikdbavishi12:26
*** jcapitao_lunch is now known as jcapitao12:27
*** sgw has quit IRC12:35
*** jpena|lunch is now known as jpena12:43
fungithat sounds like a pitfall we might want to caution about in the github connection driver docs12:44
mordredgtema: it's possible you may want to configure https://zuul-ci.org/docs/zuul/reference/project_def.html?highlight=merge%20mode#attr-project.merge-mode in this case? I also wonder if there is additional support we could do in the github driver in this case (I don't know what's available in the API)12:48
mordredthat failure certainly doesn't sound very informative at the least12:49
*** bhavikdbavishi has quit IRC12:53
gtemamordred: but for github they all map to "merge", so there is no other thing to try out with merge-mode13:03
gtemait just seems to me that GH bypasses own sec limitations from UI13:05
mordredgtema: of course it does13:09
gtemalike everything :D13:09
mordredgtema: incidentally, when openstac moved to git 9 years ago, one of the two reasons we did not move to github was that there was no way to remove normal push/merge ability from the admins of a project13:10
gtemayeah, I wanted gerrit, but it changes the flow so "dramatically", that not every developer is ok with that (don't throw stones into me)13:11
gtemaand GH is for everybody a regular way of devel13:11
* fungi is glad not to be a part of "everybody" in that case13:13
mordredgtema: I hear you. the early days of openstack involved much fighting about gh vs not-github ... and the unfortunate part is much of the argument in favor of gh at that time did not take the form of technical arguments and was instead a bunch of "but I would personally prefer using gh"13:13
gtemasure, I mean everybody outside of openstack :D13:13
mordred(which makes for an unpleasant argument, because then it's just personal)13:13
avassgtema: you could try squash-merge except that it doesn't delete branches13:13
gtemaavass: actually default one didn't delete branch as well13:14
avassI think that's a setting in github, let me check13:15
gtemayeah, there is an option for that in settings13:17
gtema"automatically delete head branches"13:17
*** ianychoi_ has joined #zuul13:17
avassgteme: yeah found it, that's what I mean13:17
avassI'm still trying to get my friends to let me host a gerrit instance for us instead of using github13:20
*** ianychoi has quit IRC13:20
*** ianychoi_ is now known as ianychoi13:23
corvusavass: did you want to send a message to zuul-discuss about the renames?13:36
AJaegerthere are a few more changes for the linting work, anybody else wants to review the stack starting at https://review.opendev.org/716263 for sphinx?13:38
corvusAJaeger: was just doing that...13:38
AJaegergreat13:39
corvusAJaeger, tobiash: i'm thinking there's enough different spellings of sphinx in there that we might want to respin that :)13:39
corvusi count at least two, zero of them correct.  it's enough that it might be confusing for future maintenance ('grep -i sphinx' returns no results...)13:40
zbri would like to reopen the subject of filters in zuul roles, like the one we used at https://review.opendev.org/#/c/705623/18/filter_plugins/flatten_nested_dict.py13:41
zbrwhat kind of workaround can we do to make it work?13:42
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Support multiple matchers when parsing tox output  https://review.opendev.org/71626313:42
corvusAJaeger, tobiash ^ fixed :)13:42
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Don't silently ignore exceptions when parsing tox output  https://review.opendev.org/71676613:43
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Strip source dir from file comments  https://review.opendev.org/71626413:43
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: DNM: Debug sphinx message  https://review.opendev.org/71672213:43
corvusrebased13:43
corvuszbr: where was the previous discussion?13:44
zbrcorvus: i think arxcruz asked about that yesterday?13:45
corvuszbr: i don't think i was around for that.  can you point me to it?13:45
AJaegercorvus: thanks!13:45
arxcruzzbr: corvus yeah, i spoke with AJaeger13:45
arxcruzhere13:45
arxcruzbasically, a test i'm doing with include role is failing because we have a python filter in our role13:45
arxcruzand it's not possible to use filter outside the trusted jobs13:46
fungii somehow missed arxcruz mentioning it yesterday. we normally discuss each filter we whitelist, and identify any ways it might be able to write to arbitrary file locations or execute arbitrary code so we can shadow those bits13:46
zbrif i understood corectly, we cannot use custom filters in zuul roles due to security issues.13:46
corvusmaybe we could find an eavesdrop link?13:46
corvusso i can catch up?13:46
zbrthat is a very simple filter, i guess a workaround would be to make it part of zuul?13:46
corvusit's not in anyone's interest to just type what they typed yesterday again13:46
corvusarxcruz: is this it?  http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2020-04-01.log.html#t2020-04-01T11:53:1413:47
AJaegercorvus: it was no real discussion, we can recap. I asked him to come back again ;)13:47
AJaegercorvus: yeah, time looks ok - there was a link to a failure that is relevant13:48
arxcruzAJaeger: corvus yeah, i just wondering why was failing,  asked here, and AJaeger point me that i'm using a filter that is blocked by zuul due secure reasons13:48
arxcruzi ping zbr since he was the one who implement the filter in our collect-logs role13:49
zbrbasically is a filter that transforms a nested dict into a list, so ansible can loop over it. i ended up writing it after wasting two days trying to do the same in jinja213:54
corvusokay, i think i'm caught up.  zbr, arxcruz: zuul doesn't allow untrusted projects to run arbitrary code on its executors, and any kind of ansible plugin can run arbitrary code.  i'm not sure there's a good workaround here.  putting on my opendev hat, we can't make that a trusted repo.  i don't think we want to add arbitrary ansible plugins to zuul.13:55
*** weshay is now known as weshay|ruck13:55
corvusyou could write an ansible module to do that; it'd run on the remote host, which is probably excessive, but should work13:56
zbrcorvus: i am having a bit of a laugh as I know what ansible 2.10 is cooking regarding all those modules moved from core into community.general collection :D13:56
zbrbut i guess that zuul will pre-install community.general collection.13:57
*** avass has quit IRC13:57
mordredzbr: I believe zuul will install ACD13:57
*** avass has joined #zuul13:57
mordredwhich should have the same effect13:57
zbryep13:58
zbrnow, back at our use-case. what can we do?13:58
avasscorvus: yeah I'll do it in a moment13:58
zbrmordred: i could run a shell python command that does the transformation, return json, load json with ansible. ugly like s*** but it should work14:00
corvuszbr: or you could write an ansible module to do that; it'd run on the remote host, which is probably excessive, but should work14:01
zbrthe irony is that it will not be safer in any way, once you run shell/python on the localhost, you still get same security issues.14:01
*** Goneri has joined #zuul14:01
corvuszbr: it won't run on localhost14:01
corvuszbr: are you able to receive messages from me?14:01
corvuszbr: as i mentioned, twice, it will run on the *remote* host14:02
fungizuul doesn't allow you to run arbitrary shell or python on executors14:02
zbraha, i did not know that.14:02
fungiat least not from untrusted repos14:02
zbrso basically this protection breaks any filters, because by design filters run on controller, but does not break modules.14:03
zbrno problem, I know how to make it a module.14:03
zbrin fact it was originally a module: p14:03
mordredzbr: then it should be quite easy to make a module :)14:03
zbrthanks everyone on this. lesson learn: ansible filters can be tricky with zuul.14:04
corvuszbr: yes -- and it's actually any kind of plugin (not just filters)14:04
*** jpena is now known as jpena|off14:10
*** jpena|off is now known as jpena14:12
*** y2kenny has joined #zuul14:16
y2kennyI have a few questions about nodepool.  What are the images that the builder build?  Do those images apply generally to all driver or just openstack?  (I am not fmiliar with dib images.)14:17
tristanCy2kenny: it's currently only building image for openstack14:18
tristanC(building and uploading)14:18
avasscorvus: alright, I sent something. Anyway, three of those changes are still getting "depends on a change with invalid configuration"14:20
avassnot sure if I'm missing something or if the error could be what you suggested yesterday14:21
y2kennyI see.  Thanks tristanC.  Second question: Is there any facility to hook into the lifecycle of nodepool like clean up and tear down?  For example, nodepool automatically create namespaces in the k8s (and I assume openshift.)  is it possible for nodepool to prepopulate the namespace outside of any job or does the pre and post have to be part of14:21
y2kennyspecific jobs?14:21
funginodepool doesn't really know anything about jobs. the nodepool launcher gets node requests from the zuul scheduler and then fulfils them, and later removes them once zuul releases its lock on them14:22
corvusy2kenny: it has to be part of a job, but you can make a parent job to do that, and have all jobs that you want to use that behavior inherit from that parent job14:22
corvusy2kenny: job inheritance playbook ordering is like an onion, so parent job pre-playbooks run before children, and parent post-playbooks run after children.14:24
y2kennyok.  What I am thinking is more of a time optimization thing.  Having bring up and tear down outside of the job that is general to all jobs can make the CI appear to be more responsible even though the actual work done is the same14:25
*** sshnaidm is now known as sshnaidm|afk14:25
corvusy2kenny: understood.  that is a drawback of this.  the advantage, however, is that we only have to maintain one system for running remote code on nodepool nodes, not two.  :)14:25
*** ysandeep|rover is now known as ysandeep|away14:26
y2kennyok.  Third question: are there facility in nodepool to allow for automatic registration of nodes?  or does all nodes have to start with a definition at nodepool (be it static or other kind of provider?)14:28
y2kenny(actually... does nodepool have some kind of rest API?.... I didn't realize to check... let me see...)14:29
corvusy2kenny: no; has to be through a provider.14:29
corvusy2kenny: the idea is that nodepool isn't supposed to be a cloud system, but should interface with them.  so if there's some other system that handles registration (like ironic for bare metal?) then we should write a provider to interface with it14:30
tristanCy2kenny: it doesn't have a rest API to push configuration, but it does read and load its configuration file change automatically, so you could scp configuration update to push provider configuration automatically14:32
AJaegertobiash, corvus, 716766 still shows "Job tox-py37: unable to map line for file comments: etc."14:34
y2kennycorvus: ok, so it's not there by design.  baremetal is certainly a use case (I haven't figured out what to do with that just yet.  So far I am just using Cobbler to bring up baremtal nodes.  I have looked into Ironic may be 3~4 years ago.  And now there's metal3, which is based on Ironic.)14:34
AJaegermordred: ^14:34
mnaserAJaeger: we can probably do testing now on that stuff14:39
y2kennytristanC: that's good to know, thanks.  I am still trying to figure out the performance side of things because having local on disk code cache is something we have done for our existing infrastructure.  I might need to do a lot of pre-provisioning of nodes and having something more dynamic to augment the static provider would be useful.14:40
tobiashcorvus: thanks for fixing my stupid typos :)14:41
corvusy2kenny: we do a lot of caching too, and that's definitely something we want to support in nodepool.  we have the diskimage builder for use with vm clouds (openstack only now, but could be extended for others).  we could also use diskimage builder for bare metal images.  k8s i'd probably just build container images in zuul.14:42
tobiashcorvus: shall we merge those or shall I add test cases first?14:42
corvustobiash: maybe at this point adding some testing to the end of the stack would be good14:45
tobiashk14:45
tobiashthen I'll -2 the stack until tests are there to prevent accidental merge14:45
AJaegertobiash: any idea where the warnings on 716766 come from?14:47
tobiashAJaeger: weird, that should have been filtered by the fix yesterday14:49
tobiashAJaeger: oh, it's matching a real 'line comment': /usr/local/lib/python3.6/dist-packages/tox/config/__init__.py:595: UserWarning: conflicting basepython version (set 3.6, should be 3.7) for env 'py37';resolve conflict or set ignore_basepython_conflict14:50
tobiashI think I we should ignore all absolute paths that are left after https://review.opendev.org/71626414:51
AJaegergood idea14:51
y2kennycorvus: is there something more 'light weight' than diskimage I wonder.  I don't really have a solution just yet but what I was thinking initially is to have some kind of standard path on the physical nodes to store ccache or git bare repos.  I don't necessarily need the cache to be synced across all nodes.  Just something being there to speed14:53
y2kennythings up opportunistically.14:53
tristanCy2kenny: couldn't you use a periodic zuul jobs to refresh your cache on the node directly?14:54
corvusy2kenny: regarding somethign more lightweight than dib: what's your target platform?  openstack or something else?   regarding the cache -- yes, that's exactly how we handle it in opendev, and there are roles in zuul-jobs that can utilize cached repos.. i'll get some links14:55
y2kennytristanC: I can definitely do that.  I think what I am missing is something that persist across jobs.  I think AFS or NFS is what was suggested in the past.14:56
corvusy2kenny: here's our diskimage element that we use to cache git repos on our openstack cloud vm images: https://opendev.org/openstack/project-config/src/branch/master/nodepool/elements/openstack-repos14:56
y2kennybut if I have AFS then I don't really need to do periodic sync.  I guess I am looking for disk local cache without a network file system.14:57
openstackgerritTobias Henkel proposed zuul/zuul-jobs master: Ignore absolute paths after stripping work dir  https://review.opendev.org/71704214:58
corvusy2kenny: then https://zuul-ci.org/docs/zuul-jobs/general-roles.html#role-prepare-workspace-git uses the cache in /opt/git14:58
y2kennycorvus: thanks.  I will take a look.  Right now I am building on top of k8s (that's why I have been asking a lot of question about the namespace, etc.)14:58
corvusy2kenny: if you're using k8s, then i would look at building container images (inside of zuul) with git repos cached in /opt/git14:58
corvusthen have nodepool use those container images14:59
y2kennycorvus: I think that's a possible solution.  But I will probably have to experiment a bit (first thing that pops into my mind is the possibility of blowing up /var/lib/docker but perhaps the union fs would be able to deal with the incremental addition to the cache quite well.)15:03
*** dmellado has quit IRC15:14
*** sshnaidm|afk is now known as sshnaidm15:15
*** ysandeep|away is now known as ysandeep15:18
avasscorvus, mordred: looks like there are callbacks that can only be configured by environment variables: https://docs.ansible.com/ansible/latest/plugins/callback/jabber.html15:20
mordredavass: "neat"15:22
avass:)15:23
*** gtema has quit IRC15:28
*** dmellado has joined #zuul15:30
corvusavass: wow.  well, if we need/want to support those, we should be able to add env variables to zuul.conf and set them when calling ansible15:37
avasscorvus: I would guess that there could be custom callbacks that for some reason support both15:39
avasss/support/require15:39
*** bhavikdbavishi has joined #zuul15:40
fungior propose fixes upstream for those callbacks15:40
avassyeah15:40
*** bhavikdbavishi1 has joined #zuul15:43
*** bhavikdbavishi has quit IRC15:44
*** bhavikdbavishi1 is now known as bhavikdbavishi15:44
avasshere's a quick draft what it could look like if we don't want to support environment variables: http://paste.openstack.org/show/791546/15:46
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Add support for RedHat platforms on install-podman  https://review.opendev.org/71657815:48
tristanCavass: lgtm, isn't callback_name equivalent to the [ansible_callback "name"] ?15:49
avasstristanC: not sure, but what I've seen so far yes15:49
corvusavass: ++15:50
*** smcginnis has left #zuul15:53
*** jamesmcarthur has joined #zuul15:55
avasstristanC: oh wait, mixed that up with the callback_config_section. Yeah it should probably do that15:55
*** rpittau is now known as rpittau|afk15:56
avasstristanC: but I'm imitating the connection configuration15:56
corvusto be fair, i'm not sure which of [connection "foo"] and name="foo" do what anymore, so if you don't need both, i would recommend not doing both :)15:58
corvus(we should probably figure that out and clean it up for connections)15:59
avasshuh, corvus: yeah I was just looking at that15:59
avasscorvus: name=foo isn't documented but it's in the example zuul.conf15:59
corvusmaybe name=foo doesn't even really exist16:00
avasssince the config section needs to be unique anyway i guess [ansible_callback "foo"] is the way to go16:00
corvusyeah, that sounds preferable16:00
corvustristanC: can we abandon https://review.opendev.org/707908 ?16:07
*** jamesmcarthur has quit IRC16:11
*** jamesmcarthur has joined #zuul16:12
corvusavass: let me know if my comment on https://review.opendev.org/706248 sounds correct16:15
*** jamesmcarthur has quit IRC16:16
avasscorvus: I think the idea was something like defaulting to "revoke_sudo: {{ nodepool.attributes.revoke_sudo }}"16:17
*** jamesmcarthur has joined #zuul16:18
avassso it does the same thing, only setting the variable somewhere else16:19
*** jamesmcarthur has quit IRC16:21
avassbut I guess the role could do when: "{{ nodepool.attributes.revoke_sudo }}" instead16:26
*** ysandeep is now known as ysandeep|away16:31
*** jamesmcarthur has joined #zuul16:34
*** evrardjp has quit IRC16:36
*** evrardjp has joined #zuul16:36
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Add support for RedHat platforms on install-podman  https://review.opendev.org/71657816:54
*** bhavikdbavishi has quit IRC16:54
corvusavass: yeah, i think if we do the second thing, then it means that a site admin can still force revoke sudo on test jobs16:57
corvusavass: because if we allow jobs to turn it off, someone will while we aren't looking :)16:57
*** hashar is now known as hasharAway17:28
*** jamesmcarthur has quit IRC17:28
*** jamesmcarthur has joined #zuul17:29
*** jpena is now known as jpena|off17:41
*** ironfoot has quit IRC17:43
*** ironfoot has joined #zuul17:43
avasscorvus: we can do that, I'm just not sure how the node-attributes work yet, since they're only documented on the openstack driver in nodepool17:44
avasshttps://zuul-ci.org/docs/nodepool/configuration.html#attr-providers.[openstack].pools.node-attributes17:44
avassand I'm not sure if they end up in the jobs yet17:45
avassaccording to: https://zuul-ci.org/docs/nodepool/releasenotes.html?highlight=node%20attributes#relnotes-3-4-0-new-features they're stored with the node data in zookeeper. But I don't know what the usecase if for that17:46
*** zxiiro has joined #zuul17:47
*** jamesmcarthur has quit IRC17:54
*** jamesmcarthur has joined #zuul17:55
*** jcapitao has quit IRC17:59
tobiashmnaser: the test case for tox is gonna be a bit trickier because of the existing file check :/18:02
Shrewsavass: https://review.opendev.org/#/q/status:open+project:zuul/nodepool+branch:master+topic:node-attr should fix the doc part. Right now, it's only used for zoning executors.18:06
Shrewsre: node-attributes, that is18:06
corvusavass, Shrews: yeah, if it isn't passed through all the way to the job, i think we should be able to add that18:16
corvusat least, i can't think of a reason not to right now18:16
avassShrews: ah nice18:16
*** gtema has joined #zuul18:17
ShrewsIf anyone wants to take those two changes over for me, feel free. One needs a merge fix, but they should be ready to go otherwise, IMO18:23
*** jamesmcarthur has quit IRC18:24
*** sshnaidm is now known as sshnaidm|afk18:24
*** jamesmcarthur has joined #zuul18:25
corvusShrews: that first one lgtm; the merge conflict on the second one looks real easy to fix18:25
corvuswe can probably just merge the first, then rebase the second18:26
*** jamesmcarthur has quit IRC18:26
*** jamesmcarthur has joined #zuul18:26
corvustristanC, tobiash: maybe you'd be interested in looking over https://review.opendev.org/714672 ?18:30
tobiashcorvus: that was actually on my list but I forgot about that18:33
corvusi'm going to try to get some gce tests soon too18:35
*** gtema has quit IRC18:50
mnasertobiash: oh that's interesting, maybe the yaml file can be extended to include something like 'files'18:55
mnasertobiash: actually, that's way more tricky18:55
* mnaser mindset is somewhere else but can try and help later18:55
corvusShrews: aws has a nice "moto" library for emulating; gcloud doesn't have that, so i think i'll have to make my own emulator like we did for openstack19:02
corvusi might be able to base it on the test from the azure driver19:04
*** hasharAway is now known as hashar19:14
*** jamesmcarthur has quit IRC19:15
*** jamesmcarthur has joined #zuul19:16
*** jamesmcarthur has quit IRC19:16
*** jamesmcarthur has joined #zuul19:16
openstackgerritMerged zuul/nodepool master: Support node-attributes in static driver  https://review.opendev.org/71467219:21
openstackgerritJames E. Blair proposed zuul/nodepool master: Update tests for node-attributes  https://review.opendev.org/71473819:40
corvusShrews: rebased ^19:40
Shrewscorvus: ++19:40
Shrewsthx19:40
*** jamesmcarthur has quit IRC20:02
*** jamesmcarthur has joined #zuul20:02
*** jamesmcarthur has quit IRC20:19
*** saneax has quit IRC20:21
*** jamesmcarthur has joined #zuul20:26
tobiashmnaser: I think I found a way but will finish it probably tomorrow20:36
*** weshay|ruck is now known as weshay20:57
*** jamesmcarthur has quit IRC21:03
*** jamesmcarthur has joined #zuul21:03
*** igordc has joined #zuul21:05
*** jamesmcarthur has quit IRC21:08
*** dpawlik has quit IRC21:12
*** rlandy is now known as rlandy|brb21:21
*** jamesmcarthur has joined #zuul21:26
*** jamesmcarthur has quit IRC21:26
*** jamesmcarthur has joined #zuul21:26
mnasertobiash: cool, look forward for that :)21:32
*** armstrongs has joined #zuul21:37
*** armstrongs has quit IRC21:48
*** hashar has quit IRC21:49
openstackgerritJames E. Blair proposed zuul/nodepool master: Add GCE driver tests  https://review.opendev.org/71713322:02
openstackgerritJames E. Blair proposed zuul/nodepool master: Fix shutdown ordering  https://review.opendev.org/71713422:02
corvusShrews: ^ there's my penance :)22:02
*** rlandy|brb is now known as rlandy22:17
*** openstackstatus has quit IRC22:56
*** openstack has joined #zuul23:00
*** ChanServ sets mode: +o openstack23:00
*** tosky has quit IRC23:00
*** rlandy has quit IRC23:11
*** zxiiro has quit IRC23:24

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