Friday, 2019-02-01

openstackgerritMerged openstack-infra/zuul master: Fix context directories in image builds  https://review.openstack.org/63426600:00
*** shanemcd has quit IRC00:02
*** shanemcd has joined #zuul00:03
*** rlandy is now known as rlandy|afk00:09
*** sdake has quit IRC00:32
*** sdake has joined #zuul00:34
*** sdake has quit IRC00:36
dkehnclarkb, are there any examples for setting up fingergw in zuul/doc/source/admin/example zuul.conf and docker-compose.yaml?00:39
tristanCjhesketh: for zuul-runner instances lifecycle, i'm thinking we could use nodepool driver.handler.launch() with a special Node object that wouldn't require zookeeper...00:41
tristanCjhesketh: i know it sounds crazy, but with a user-provided nodepool.yaml, then zuul-runner should be able to use any type of labels (e.g. containers, instances, static-nodes, ...)00:42
*** rfolco has joined #zuul00:43
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: add /connections route  https://review.openstack.org/63170300:44
*** sdake has joined #zuul00:55
jheskethtristanC: what are you imaging would be in the user-provided nodepool.yaml? and what (if anything) would handle the launching?01:03
tristanCjhesketh: well i think we should retain the cli interface to provide node information, but the user could also provide a nodepool.yaml with labels associated with one or many providers01:04
tristanCjhesketh: perhaps using cloud-image for openstack if we don't want to bother with nodepool-builder01:05
tristanCjhesketh: then we could find a way to instantiate nodepool driver standalone and drive node creation/deletion from the zuul-runner cli01:06
openstackgerritMerged openstack-infra/zuul master: model: remove unused job's BranchMatcher procedures  https://review.openstack.org/63364301:07
jheskethright, I was kinda imaging a very similar thing, but I hadn't considered reusing nodepool to do it (basically I was thinking you'd just provide cloud creds and it'd launch nodes... I get that sounds like nodepool, but it wouldn't be keeping a pool)01:08
*** sdake has quit IRC01:08
jheskethI was also wondering if we should publish infra's built images and provide a way to grab those and push them to your own cloud.. but that'd be a high overhead01:08
tristanCjhesketh: that would work for cloud instance, but what about other type of instance like k8s pods?01:09
jheskethI had not considered that case tbh01:10
jheskethbasically a file that defines for each label what to do. eg: ssh to this static node here; launch a node on this cloud; here are the k8s creds01:11
*** dkehn has quit IRC01:11
jheskethwhich is basically what you're describing above, so I like that plan01:11
tristanCjhesketh: ok, i could look into that next week, as it seems like the main missing part for a complete zuul-runner experience01:13
tristanCthough i'm not convinced re-using nodepool driver code is the right way, it may be worth investigating, but the downside is that zuul-runner user would have to provide a nodepool.yaml configuration01:14
jheskethright, I'm not sure how much of it would be reusable.. We should probably find another term for our configuration like zuul-runner.yaml if we are only needing a subset of nodepool.yaml01:15
jheskethI'd also like to experiment with making the runner-launcher plugable, so we could have a local libvirt driver to run tests locally01:16
tristanCon the other hand, perhaps it would be a nice nodepool improvement if the drivers were usable standalone...01:16
tristanCjhesketh: well, if there was a libvirt driver in nodepool, then zuul-runner user would just map the label to it01:17
jheskethYep!01:20
tristanCactually, it would make testing/developping nodepool driver easier if they could be used standalone...01:31
*** sdake has joined #zuul01:34
*** dkehn has joined #zuul01:38
*** sdake has quit IRC01:49
*** sdake has joined #zuul02:23
*** sdake has quit IRC02:33
*** sdake has joined #zuul02:35
*** sdake has quit IRC02:37
*** sdake has joined #zuul02:40
*** sdake has quit IRC02:42
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [wip] add openstackci-mirrors element for centos/ubuntu testing  https://review.openstack.org/63436602:50
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [wip] add openstackci-mirrors element for centos/ubuntu testing  https://review.openstack.org/63436602:55
*** sdake has joined #zuul02:58
*** sdake has quit IRC03:17
*** sdake has joined #zuul03:19
*** sdake has quit IRC03:19
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [wip] add openstackci-mirrors element for centos/ubuntu testing  https://review.openstack.org/63436603:19
*** sdake has joined #zuul03:21
*** sdake has quit IRC03:22
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: add /connections route  https://review.openstack.org/63170303:24
*** bhavikdbavishi has joined #zuul03:36
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [wip] add openstackci-mirrors element for centos/ubuntu testing  https://review.openstack.org/63436603:41
*** sdake has joined #zuul03:44
*** rlandy|afk is now known as rlandy03:45
*** rlandy has quit IRC03:49
*** sdake has quit IRC04:39
*** spsurya has joined #zuul04:45
*** invincible has quit IRC04:58
*** chandan_kumar has joined #zuul04:59
*** chandan_kumar is now known as chkumar|ruck04:59
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [wip] add openstackci-mirrors element for centos/ubuntu testing  https://review.openstack.org/63436605:06
*** dkehn has quit IRC05:07
*** bhavikdbavishi1 has joined #zuul05:37
*** bhavikdbavishi has quit IRC05:37
*** bhavikdbavishi1 is now known as bhavikdbavishi05:37
*** pvinci has quit IRC06:05
*** bhavikdbavishi1 has joined #zuul06:13
*** bhavikdbavishi has quit IRC06:14
*** bhavikdbavishi1 is now known as bhavikdbavishi06:14
*** quique|rover|off is now known as quiquell|rover06:15
*** jesusaur has quit IRC06:47
*** jesusaur has joined #zuul06:52
*** pcaruana has joined #zuul07:19
*** saneax has joined #zuul07:46
quiquell|rovertristanC: o/07:48
quiquell|rovertristanC: Can I test https://review.openstack.org/#/q/topic:freeze_job  ?07:48
*** panda|off is now known as panda07:53
tristanCquiquell|rover: yes please07:56
quiquell|rovertristanC: How do I test it ?07:57
openstackgerritMerged openstack-infra/zuul-jobs master: Allow different filenames for Dockerfiles  https://review.openstack.org/63297907:58
tristanCquiquell|rover: apply the patch, and then you can run something like: zuul-runner -a http://localhost:9000/api/ --tenant local --pipeline check --project rdo-jobs --job tripleo-ci-centos-7-standalone execute08:00
tristanCquiquell|rover: atm node lifecycle management isn't implemented, so you have to give an ip address using --nodes ssh:zuul-worker:instance-ip:/home/zuul-worker08:01
tristanCquiquell|rover: the nodes list is coma separated, thus it should work for multinode jobs too08:01
*** gtema has joined #zuul08:01
quiquell|rovertristanC: ack08:05
*** gtema has quit IRC08:05
*** gtema has joined #zuul08:06
openstackgerritQuique Llorente proposed openstack-infra/zuul master: Escape jinja2 stuff from inventory  https://review.openstack.org/63393008:08
quiquell|rovertobiash, tristanC: The jinja2 thing https://review.openstack.org/#/c/63393008:09
quiquell|rovercorvus: ^08:09
*** rfolco has quit IRC08:41
*** rfolco has joined #zuul08:42
*** jpena|off is now known as jpena08:47
quiquell|rovertristanC: I have to apply just this ? https://review.openstack.org/#/c/631703/08:48
tristanCquiquell|rover: this + the rest of the topic08:51
tristanCquiquell|rover: at least 607078 and 607077 on server side08:52
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: Proposed spec: tenant-scoped admin web API  https://review.openstack.org/56232108:52
quiquell|rovertristanC: Looks like we zuul is using multi-stage Dockerfile to build09:12
quiquell|rovertristanC: Do you know if docker-ce is needed or buildha09:12
clarkbquiquell|rover: the zuul image builds use docker ce iirc09:23
quiquell|roverclarkb: so distro docker is old for that like docker at f28 and c709:24
quiquell|roverclarkb: thanks09:24
*** sdake has joined #zuul09:27
*** pcaruana has quit IRC09:30
*** pcaruana has joined #zuul09:42
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: Proposed spec: tenant-scoped admin web API  https://review.openstack.org/56232109:43
*** luizbag has joined #zuul09:54
*** bhavikdbavishi has quit IRC10:08
*** electrofelix has joined #zuul10:38
*** sdake has quit IRC10:51
*** sdake has joined #zuul10:51
tobias-urdinhow can i troubleshoot RETRY_LIMIT? I don't have any log storage right now, the zuul logs doesn't show anything and i'm trying to use finger but not sure how, fingergw is running11:06
tobias-urdini assume i can only finger while the jobs is running, but it's instances are killed pretty much instantly11:09
clarkbtobias-urdin: check the executor log if the job is running something it should show there11:12
clarkbif there isnt anything in the executor log then scheduler may say why it isnt getting that far11:13
*** bhavikdbavishi has joined #zuul11:13
tobias-urdinclarkb: i can see "2019-02-01 12:01:45,834 INFO zuul.AnsibleJob: [build: d73a9426ca934e38b4744481f5e17fde] Beginning job tox-py36-linters..."11:14
tobias-urdinafter that there's only "updating repo" and "checking out..." lines11:14
clarkbif you grep on that build id tou dont get other info?11:15
tobias-urdincat /var/log/zuul/*.log | grep d73a9426ca934e38b4744481f5e17fde11:15
tobias-urdin2019-02-01 12:01:49,769 INFO zuul.ExecutorClient: Build <gear.Job 0x7f2354394080 handle: b'H:::ffff:127.0.0.1:234' name: executor:execute unique: d73a9426ca934e38b4744481f5e17fde> complete, result RETRY_LIMIT, warnings []11:16
tobias-urdinis there anything stored on executor that could help me troubleshoot why?11:17
clarkbI wouldve expected logs from the ansible process too. Retry limit happens after a job fails in the pre run phase up to $limit attempts11:17
clarkbso would've expected ansible logs showing pre run fail11:18
*** bhavikdbavishi has quit IRC11:18
tobias-urdinhm i get zero indication on what is causing pre run to fail, no ansible output at all it seems11:20
clarkbany logs that match a grep for ansible-playbook? iirc zuul logs those command lines too11:25
clarkbif those are missing it may be failing before ansible runs11:26
tobias-urdingrep ansible-playbook /var/log/zuul/*.log11:26
tobias-urdinno match, does it log that by default or do i need to change some logging config?11:26
tobias-urdini'm testing a simple hello world now to see if it's something weird or my jobs/roles/playbooks causing it11:26
clarkbI dont know off the top of my head if debug level logging is default, but that is probably a good next item to check11:27
electrofelixWas there work done for zuulv3 for a generic mechanism to apply review comments to the change under test in gerrit/github?11:32
*** bhavikdbavishi has joined #zuul11:35
clarkbelectrofelix: there is the top level commenting that has always exosted and is configurable. But inline support for gerrit comments was added in v311:36
tobiashftr: https://zuul-ci.org/docs/zuul/user/jobs.html#leaving-file-comments11:37
tobiashbut it's currently only supported on gerrit11:37
electrofelixwas about to ask where to look, many thanks11:37
clarkbtobiash: maybe you know answer to tobias-urdin questions earlier?11:41
tobiashreading11:42
tobiashclarkb: you're awake at this time?11:42
clarkbIm in brussels for fosde.11:42
electrofelixtobiash: if it turns out that it's still only gerrit by the time we upgrade, that might be something I can look at11:42
tobiashclarkb: have fun11:43
tobiashtobias-urdin: the executor should have pretty detailed logs of ansible runs11:43
tobiashtobias-urdin: do you have the executor logs at hand (debug level)?11:44
tobias-urdintried with this http://paste.openstack.org/show/744368/ still fails on RETRY_LIMIT with no logs, need to fix logging config, think i just run with default and no custom logging config right now i.e only a zuul.conf11:44
tobias-urdinshould maybe note that i was on zuul 3.3.1 and caught this http://paste.openstack.org/show/744361/ so upgraded to 3.5.011:45
tobiashtobias-urdin: the reason for retry_limit can vary from unreachable node, auth problems to the node, failures in pre-playbooks11:45
openstackgerritSorin Sbarnea proposed openstack-infra/zuul-jobs master: Fix failure to add user to docker group on centos  https://review.openstack.org/63394811:46
openstackgerritSorin Sbarnea proposed openstack-infra/zuul-jobs master: Fix failure to add user to docker group on centos  https://review.openstack.org/63394811:46
tobiashtobias-urdin: but when I look at your job definition you don't have any pre-playbook so I'd assume a problem with communication problems to the node or auth problems11:46
tobias-urdinyeah i removed any pre/run playbooks and added that hello world to test11:47
tobias-urdingonna fix logging conf, reload then recheck that see if i can see anything11:47
tobiashk11:48
tobias-urdinjust need to figure out how first11:48
tobiashcorvus, clarkb: could it be possible that we have a memleak in the executor?11:48
tobiashI noticed that the rss of the executor process is higher every night without load11:49
tobiashthe weird thing is that during low load the baseline memory consumption looks constant but after high load during the day the low load consumption is higher by several hundred mb11:52
tobiashthan the day before11:52
*** EmilienM is now known as EvilienM11:58
tobias-urdinok so starting executor in cli did enable debug output, it's kind of obvious why it failed now haha http://paste.openstack.org/show/744369/12:00
tobias-urdinsorry for the noice12:01
tobiashthat explains something :)12:01
tobiashcorvus, clarkb: that's the rss of the executor container so basically rss of executor+ansible processes: https://paste.pics/a5a599d18aeb3aaaa3ad1218750febc912:03
tobias-urdinugh, does ansible "shell" invoke shell using python or a pure shell over ssh? maybe i could install python instead of carrying custom images to that cloud12:04
tobiashusing python12:04
tobiashyou can use a raw task for installing python however12:04
clarkbtobiash: ya openstack hasnoticed similar as well as swapping12:04
*** pcaruana has quit IRC12:05
tobiashclarkb: ok, thx so I'm not chasing a phantom12:05
tobias-urdintobiash: ack, thanks! one step closer to getting rid of the stupid jenkins stuff we have though :)12:05
tobiashtobias-urdin: but zuul does gather facts before running the job so python is probably required for this12:05
tobiashtobias-urdin: do you have python3 on your images?12:06
tobiashin that case you might be able to set the ansible_python_interpreter variable on the nodeset to /usr/bin/python312:06
tobiashwe may want a way in nodepool to define such variables in the future12:07
tobiashwe may want a way in nodepool to define such variables in the future12:08
tobias-urdinthanks :) seems like the image has py3.6 by default12:09
tobiashclarkb: that's interesting, a paused executor running no jobs anymore: http://paste.openstack.org/show/744371/12:10
tobiashit consumes much cpu and 3.5gb memory12:10
tobiashhrm, stack trace contains a job in pause state that is not in the system anymore12:17
*** pcaruana has joined #zuul12:19
*** pcaruana|afk| has joined #zuul12:25
*** pcaruana has quit IRC12:26
*** pcaruana|afk| is now known as pcaruana12:27
*** jpena is now known as jpena|lunch12:31
*** panda is now known as panda|lunch12:40
openstackgerritSorin Sbarnea proposed openstack-infra/zuul-jobs master: Make install-docker compatible with centos  https://review.openstack.org/63394812:43
*** sdake has quit IRC12:55
*** bhavikdbavishi has quit IRC13:08
tobias-urdintobiash: not sure where i should add ansible_python_interpreter doesn't seem like it reads it13:13
tobiashtobias-urdin: where did you try it?13:13
*** pcaruana has quit IRC13:13
tobias-urdintried as "vars" in parent job, "host-vars" on nodeset13:14
tobiashhrm, I could have sweared that the nodeset allows to add host or group vars, but it seems not: https://zuul-ci.org/docs/zuul/user/config.html#attr-nodeset13:14
tobiashtobias-urdin: I think pabelanger managed to use this by setting this as a site var in the executor config13:16
tobias-urdinmaybe it's even before my playbook is executed13:16
tobias-urdinhttp://paste.openstack.org/show/744390/13:16
tobiashtobias-urdin: https://zuul-ci.org/docs/zuul/admin/components.html#attr-executor.variables13:16
tobiashI think this should work13:16
tobiasheverything else is probably lower in the hierarchy to overwrite the variable zuul sets here: https://git.zuul-ci.org/cgit/zuul/tree/zuul/executor/server.py#n161413:17
*** rlandy has joined #zuul13:17
tobiashtobias-urdin: yes, the first thing zuul runs is a setup playbook that gethers and caches facts13:18
tobiashand that runs before any job defined playbooks13:18
tobias-urdinsince that is in zuul config it means i can't have per-project, nodeset, job etc specific py3 only13:19
tobias-urdinright?13:19
tobiashcorrect13:19
tobiashso this should probably changed ;)13:19
tobias-urdinor maybe extra-vars overrides it, haven't tried that13:20
tobias-urdinbut maybe it still doesn't override the hardcoded one13:20
tobias-urdinbut in normal ansible operations it prob would13:20
*** pcaruana has joined #zuul13:20
tobiashtobias-urdin: pabelanger already succeeded to override this and I think it was by the executor variables13:21
tobias-urdinack13:21
*** panda|lunch is now known as panda13:23
*** quiquell|rover is now known as quiquell|lunch13:23
*** jpena|lunch is now known as jpena13:37
sean-k-mooneyclarkb: corvus if ye have time later could ye take a look at https://review.openstack.org/#/c/633796/ and https://review.openstack.org/#/c/632452/13:37
sean-k-mooneyim hoping to start testing triggering builds form upstream gerrit over the weekend and if i depend on both those change my thrid party ci seams to work but it would be nice if i did not have to add the depens on lines.13:38
*** sdake has joined #zuul13:41
AJaegertobias-urdin: regarding https://review.openstack.org/633968 , please discuss this here. This looks like one of hte changes that need some discussion - probably with corvus involved.13:47
tobias-urdinwrong link right? you are thinking about the revoke-sudo i assume13:48
*** quiquell|lunch is now known as quiquell13:51
openstackgerritSorin Sbarnea proposed openstack-infra/zuul-jobs master: Make install-docker compatible with centos  https://review.openstack.org/63394814:05
*** sdake has quit IRC14:06
*** quiquell is now known as quiquell|rover14:07
*** quiquell|rover is now known as quique|roverish14:07
*** quique|roverish is now known as quiquell|rover14:08
*** sdake has joined #zuul14:17
AJaegertobias-urdin: yeah, that's it, sorry, wrong pasto. Was thinking about https://review.openstack.org/#/c/627534/ and the revoke-sudo.14:30
*** dkehn has joined #zuul14:39
quiquell|rovertristanC: Like the {% raw %} but I have to change all test now :-)14:41
openstackgerritQuique Llorente proposed openstack-infra/zuul master: Escape jinja2 stuff from inventory  https://review.openstack.org/63393014:42
*** quiquell|rover is now known as quiquell|off14:47
*** quiquell|off is now known as quique|rover|off14:48
openstackgerritSorin Sbarnea proposed openstack-infra/zuul-jobs master: Make install-docker compatible with centos  https://review.openstack.org/63394814:53
openstackgerritSorin Sbarnea proposed openstack-infra/zuul-jobs master: Make install-docker compatible with centos  https://review.openstack.org/63394815:17
*** panda is now known as panda|braindead15:42
dkehnclarkb: are there any examples for setting up fingergw in zuul/doc/source/admin/example zuul.conf and docker-compose.yaml?15:50
pabelangerIs there any way to see which semaphore zuul is currently holding? Trying to debug an issue if some semaphore jobs not running, and believe we may not have unlocked the semaphore currently15:55
tobiashpabelanger: not at the moment15:55
tobiashyou may have to dig in the logs15:56
pabelangerwe had a nodepool-launcher failure this morning, ran out of HDDs, and starting to think we had an exception lauching the semaphore job during that window15:56
pabelangernow, jobs are stuck15:56
corvusAJaeger, tobias-urdin: it looks like the puppetforge job uploads to puppetforge before fetching the artifact to the executor.  if we were to model on the pypi job, we would fetch them to the executor, then upload to puppetforge from the executor.  as it is, we're sending the credentials to the remote host, which means we're trusting any project that uses the job (which could be any project in the system).15:56
pabelangertobiash: k, thanks15:56
tobiashpabelanger: you could looks for the last job that locked it and see how that job finished15:57
tobiashpabelanger: that could possibly tell you the code path it took so we can find the broken one15:57
corvusAJaeger, tobias-urdin: so instead of changing the revoke-sudo, i'd suggest looking into what is required to upload to puppetforge from the executor.  we don't like to install much software on the executor (but we could probably install ruby itself, and then have the jobs install gems in the user's directory)15:58
*** luizbag has quit IRC15:58
*** pcaruana has quit IRC15:59
electrofelixhughsaunders: wonder if you've any idea what it would take for the nodepool agent plugin to support freestyle jobs?15:59
*** saneax has quit IRC16:00
corvustristanC, jhesketh: let's not expand the zuul-runner work to include nodepool yet.  let's just see if we can get something landed in zuul first.  :)  jhesketh, maybe you can review tristanC's updates to your changes first, and when they look good, i'll take a look?16:03
corvustristanC: it looks like https://review.openstack.org/630035 is almost ready to land, but either has a bug or needs a test update.16:04
AJaegerthanks, corvus for looking into this16:07
pabelangertobiash: okay, we had to restart zuul scheduler. jobs running again. So somehow we leaked semaphores, now comes the effort of trying to find where16:28
*** sdake has quit IRC16:32
pabelangertobiash: do you have syntax handy for reenqueue on github? trying to help nhicher with error we are getting, but I've never actually enqueued a github job before.16:38
*** sdake has joined #zuul16:39
tobiashpabelanger: same as gerrit but change as pr#,<sha of head>16:48
pabelangerack16:49
corvustobiash: oh, i didn't know you had started on the buildset registry idea months ago :)16:59
tobiashcorvus: yeah that was kind of the demo showcase for job pause ;)17:00
corvustobiash: should i continue with what i'm working on, then maybe later we can fold in some stuff from your role (eg, proxy)?17:02
tobiashye17:02
tobiashyes17:02
tobiashyour registry seems to be more sophisticated with certs and password17:03
corvustobiash: i'm not done yet, but you can see more of the system by searching for "topic: docker-registry" in gerrit17:03
corvusthere's 5 changes so far.17:03
tobiashah ok17:03
corvus(i haven't written the push/pull roles yet, that's the next big piece, but i stubbed out their location in 634347 so you can see the sequencing)17:04
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: Add a role to run a buildset registry  https://review.openstack.org/63431917:08
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: add role to use buildset registry  https://review.openstack.org/63434617:08
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432317:08
tobiashcorvus: looking at that topic I think you already have more than I had so I think I can just abandon my version of it17:08
corvustobiash: okay, don't let me forget proxies :)17:11
corvuscan anyone spot what i'm missing here?  http://logs.openstack.org/06/630406/14/check/system-config-run-review/5c71e91/ara-report/result/8db4b584-1ecf-44a7-ab2f-ea70c9edf529/17:13
corvusi expect that command to redirect stdout+stderr to a file, but the file is empty and ansible captures both17:14
corvusis that a bashism?  and is that not running bash?17:15
tobiashcorvus: is that a command or shell task?17:15
tobiasha command task won't interpret redirections17:15
corvusshell: http://logs.openstack.org/06/630406/14/check/system-config-run-review/5c71e91/ara-report/file/5b878655-15bb-4234-ade6-e8f9ab6b1f8e/#line-3117:16
corvusthat works as expected locally17:17
corvusbut my /bin/sh is bash17:18
corvusi'll just throw "executable: /bin/bash" at it :)17:19
tobiashcorvus: yepp, bashism: http://paste.openstack.org/show/744411/17:20
corvustobiash: thanks for the answer and for telling me about shellcheck :)17:20
tobiashshellcheck is awsome :)17:21
tobiashand it finds most of the bashisms :)17:21
tobiashit even has an online checker: https://www.shellcheck.net/17:21
*** jpena is now known as jpena|off17:37
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: Add a role to run a buildset registry  https://review.openstack.org/63431917:43
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: add role to use buildset registry  https://review.openstack.org/63434617:43
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432317:43
tobiashcorvus: I've just discovered a problem with job pause17:44
tobiashin case of an executor restart with a paused job, we currently restart that job17:45
tobiashhowever I think in this case we actually need to restart all child jobs of it too17:45
tobiashotherwise very unexpected and hard to debug symptoms can happen to the child jobs17:46
*** panda|braindead is now known as panda17:46
corvustobiash: yes, i think i agree17:47
*** dkehn has quit IRC17:49
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: Add a role to run a buildset registry  https://review.openstack.org/63431917:55
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: add role to use buildset registry  https://review.openstack.org/63434617:55
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432317:55
openstackgerritSorin Sbarnea proposed openstack-infra/zuul-jobs master: Make install-docker compatible with centos  https://review.openstack.org/63394817:56
*** gtema has quit IRC18:07
*** sdake has quit IRC18:08
*** sdake has joined #zuul18:09
*** electrofelix has quit IRC18:14
openstackgerritSorin Sbarnea proposed openstack-infra/zuul-jobs master: Make install-docker compatible with centos  https://review.openstack.org/63394818:21
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: Add a role to run a buildset registry  https://review.openstack.org/63431918:22
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: add role to use buildset registry  https://review.openstack.org/63434618:22
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432318:22
openstackgerritSorin Sbarnea proposed openstack-infra/zuul-jobs master: Make install-docker compatible with centos  https://review.openstack.org/63394818:33
*** fdegir has quit IRC18:38
*** sdake has quit IRC18:39
*** fdegir has joined #zuul18:40
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: add role to use buildset registry  https://review.openstack.org/63434618:40
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432318:40
*** sdake has joined #zuul18:40
*** panda is now known as panda|off18:47
*** pvinci has joined #zuul18:50
pvincicorvus: thank you for fixing my issue.18:51
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: add role to use buildset registry  https://review.openstack.org/63434619:13
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432319:13
SpamapScorvus: IIRC, there was talk of having a way to expose logs via zuul-web. Is there anywhere I can go to keep tabs on that idea?19:13
SpamapSI'm setting up an auth frontend for my logs right now and I'd really love to have a comment with "Once this lands we can remove this piece of the infrastructure" type of bread crumb.19:13
corvusSpamapS: not afaik; the latest artifact i know of is my email laying out the idea and the thread which follows: http://lists.zuul-ci.org/pipermail/zuul-discuss/2018-July/000501.html19:14
corvusSpamapS: i believe that tristanC has gotten some pre-requisite infrastructure in place for that (the build page fetches one file from the log server now), so ad-hoc progress is being made19:15
corvusSpamapS: but maybe if we turn that into a story with individual tasks we can get some more momentum on it19:15
SpamapScorvus: Indeed, I think it would be really great, then we can have a batteries-included log parser too.. I have so many ideas, but so little time. :-/19:17
corvusyeah.  it's about third down on my list right now.  but i think other folks could contribute.19:18
corvusand i'd rather wait until that's in place before moving opendev to swift logs (because without it, it's a UX regression, with it it's an improvement)19:19
SpamapSindeed, my s3 based logs are pretty awful right now19:21
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: add role to use buildset registry  https://review.openstack.org/63434619:23
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432319:23
corvuslemme etherpad up a task list and if it looks good i'll put it in storyboard19:24
SpamapSty, hopefully I can contribute some19:24
*** sdake has quit IRC19:28
*** sdake has joined #zuul19:29
*** sdake has quit IRC19:31
corvusSpamapS: how's that look? https://etherpad.openstack.org/p/mbAfaIpbWN19:32
corvus(actually, several hard things in the original email are done now -- not only fetching files, but artifact url return)19:32
corvusSpamapS: i went ahead and dumped it in storyboard: https://storyboard.openstack.org/#!/story/200492319:38
corvustristanC, mordred: ^19:39
*** dkehn has joined #zuul19:40
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: Add a role to run a buildset registry  https://review.openstack.org/63431919:43
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: WIP: add role to use buildset registry  https://review.openstack.org/63434619:43
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432319:43
dkehnis the a place one can look at how the docker zuul images where built for hub.docker.com? like fingergw user, because failing on zuul user19:50
corvusmordred, tobiash: http://logs.openstack.org/23/634323/14/check/test-buildset-registry/15d6904/job-output.txt.gz#_2019-02-01_19_46_38_350178 succeeded!  i think the first 2 roles in zuul-jobs are ready to land (run and use registry).  we're also ready to run the registry in opendev.  topic:docker-registry19:50
corvusmordred, tobiash: next i'll work on the pull/push roles, but we won't be able to really test them until we land provides/requires and have the opendev registry running19:51
corvusdkehn: yes it's just the Dockerfile in the zuul repo19:51
corvusdkehn: we should add fingergw to the zuul-quick-start19:51
dkehncorvus: yes try to do that now19:52
dkehncorvus: the only Dockerfile I see is logs-Dockerfile and node-Dockerfile, is that correct19:55
corvusdkehn: this one: http://git.zuul-ci.org/cgit/zuul/tree/Dockerfile19:55
tobiashcorvus: cool :)19:55
corvusdkehn: those are only used by the quickstart, and build images locally19:55
corvusdkehn: er, lemme clarify -- the logs and node dockerfiles are only used by the quickstart, to build local images for the quick-start's log server and worker node.  the dockerfile for all of the zuul service images is the one i linked.19:56
dkehncorvus: so what user is in the zuul/zuul-fingergw build, because its failing on: http://git.zuul-ci.org/cgit/zuul/tree/zuul/lib/streamer_utils.py#n105 using the zuul user19:59
corvusdkehn: oh, i think all the container images may run as root right now20:00
corvusdkehn: and yeah, looks like the default is zuul -- http://git.zuul-ci.org/cgit/zuul/tree/zuul/cmd/fingergw.py#n66 so we'll need to set the user in the config file to root20:01
corvussigh.  i think we should not have a default there20:02
corvus(because if there's no user set, we don't drop privs)20:03
corvusbut that's difficult to do if there's a default user20:03
corvusdkehn: try just setting "user="20:05
dkehncorvus: ack20:06
pabelangeris there a reason not to create zuul user inside dockerfile?20:06
pvinciIs it possible to run jobs on repo's without 'files' (.zuul.yaml)20:08
dkehncorvus: that seemed to work thanks, now dying on the socket file.20:08
pabelangerpvinci: yup, you can keep their job configuration in your config-project20:09
dkehncorvus: going to add the - /var/lib/zuul to the docker-compose,yaml20:10
pvincipabelanger: That's what I thought, but the scheduler wouldn't trigger until I added an empty .zuul.yaml to the repo.  I'll keep looking. thanks!20:11
tobiashcorvus: commented on 63431920:13
corvustobiash: oh thanks.  yeah, i'll update the docs, and... um, remove "WIP" from the commit message  :)20:13
tobiashcorvus: same doc issue applies to the 'use' role20:14
pabelangerpvinci: the projects tab on the UI should give you an idea of which jobs are attached to the projects. I am unsure why adding a .zuul.yaml is required, we have untrusted projects in ansible-network without any zuul configuration in them20:14
mordredcorvus: requires/provides lgtm - do you want me to hold off on +3 for anyone else to look at it?20:18
SpamapScorvus: that's great!20:23
pvincipabelanger: ok.  That helps. Thanks!20:23
corvusmordred: i reckon it's gtg; it's been out there a few days, plus had an email thread.20:23
tobiashcorvus: I've also commented on 63434620:28
tobiashcorvus: regarding proxy support I think we'll have to mess with systemd config. But that'll be more complicated and is definitely something for later when someone needs it.20:29
*** sdake has joined #zuul20:40
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Add a role to run a buildset registry  https://review.openstack.org/63431920:59
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Add role to use buildset registry  https://review.openstack.org/63434620:59
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432320:59
corvustobiash: thanks, that should address all the comments20:59
tobiashlgtm21:02
*** sdake has quit IRC21:03
mordredcorvus: the test job has sad21:08
mordredhttp://logs.openstack.org/23/634323/15/check/test-buildset-registry/2e8efb6/job-output.txt.gz#_2019-02-01_21_03_16_50191121:09
corvushrm.  so either there's a syntax error in the config, or we need to wait longer to log in?21:10
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432321:14
mordredcorvus: I'll be curious to see if that fixes it21:17
corvusi'm watching the stream, and i feel like it's not looping as much as i'd expect.21:19
corvusthe contents of that file look correct21:21
corvusoh!21:23
corvusi think i need to set restart true on the registry container21:23
*** sdake has joined #zuul21:23
corvusi'm going to leave that retry loop in there, just to avoid race conditions though21:25
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Add a role to run a buildset registry  https://review.openstack.org/63431921:26
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Add role to use buildset registry  https://review.openstack.org/63434621:26
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: DNM: test buildset registry  https://review.openstack.org/63432321:26
mordredcorvus: seems reasonable21:27
mordredcorvus: left a nit on 634346 - only matters if you wind up respinning again21:28
corvusmordred, tobiash: looks like the test is good now (and the retries weren't needed, but i still think it's good to leave there)21:36
*** dkehn has quit IRC21:42
mordredcorvus: woot!21:48
*** rlandy has quit IRC21:50

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