Monday, 2019-01-14

*** _KaszpiR_ has left #zuul00:01
openstackgerritRui Chen proposed openstack-infra/zuul master: Avoid using list branches with protected=1 in github driver  https://review.openstack.org/63003802:57
*** remi_ness has quit IRC03:01
*** remi_ness has joined #zuul03:15
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: config: add playbooks to job.toDict()  https://review.openstack.org/62134303:20
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: WIP: Add API endpoint to get frozen jobs  https://review.openstack.org/60707703:20
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: WIP: Get executor job params  https://review.openstack.org/60707803:20
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: WIP: Separate out executor server from runner  https://review.openstack.org/60707903:20
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: tests: improve test_web to only provision events when needed  https://review.openstack.org/63057503:20
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [wip] Use bindep for devstack jobs  https://review.openstack.org/62606803:22
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: tests: improve test_web to only provision events when needed  https://review.openstack.org/63057503:49
tristanCjhesketh: is there a reason why https://review.openstack.org/607081 isn't part of https://review.openstack.org/607080 ? It seems like it would better if those 2 were squashed04:45
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: tests: improve test_web to only provision events when needed  https://review.openstack.org/63057505:19
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: config: add playbooks to job.toDict()  https://review.openstack.org/62134305:19
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: WIP: Add API endpoint to get frozen jobs  https://review.openstack.org/60707705:19
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: WIP: Get executor job params  https://review.openstack.org/60707805:19
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: WIP: Separate out executor server from runner  https://review.openstack.org/60707905:19
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: WIP: Move common AnsibleJob prep tasks into a base class  https://review.openstack.org/60708005:19
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: WIP: Implement a local zuul-runner  https://review.openstack.org/60708205:19
openstackgerritRui Chen proposed openstack-infra/zuul master: Avoid using list branches with protected=1 in github driver  https://review.openstack.org/63003806:33
*** remi_ness has quit IRC06:51
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [wip] Use bindep for devstack jobs  https://review.openstack.org/62606807:08
*** pcaruana has joined #zuul07:11
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: WIP: Move common AnsibleJob prep tasks into a base class  https://review.openstack.org/60708007:31
openstackgerritRui Chen proposed openstack-infra/zuul master: Avoid using list branches with protected=1 in github driver  https://review.openstack.org/63003807:58
*** themroc has joined #zuul08:11
*** avass has joined #zuul08:13
openstackgerritFelix Schmidt proposed openstack-infra/zuul master: Add action to task result in zuul_json callback  https://review.openstack.org/63062208:28
*** gtema has joined #zuul08:47
*** avass has quit IRC08:49
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [wip] Use bindep for devstack jobs  https://review.openstack.org/62606808:51
quiquellhello08:53
quiquellis possible to hold a node on "success" with a openstack nodepool provider ?08:53
*** ssbarnea|rover has joined #zuul08:54
openstackgerritFelix Schmidt proposed openstack-infra/zuul master: Add action to task result in zuul_json callback  https://review.openstack.org/63062208:54
quiquellOk I see it's not possible https://github.com/openstack-infra/zuul/blob/2fd688352f5e220fda0dfc72b164144910670d95/zuul/scheduler.py#L124908:55
quiquellcorvus: ^ It make sense if I put in place a review to be able to hold without filtering result if it's propertly configured ?08:58
quiquellcorvus:  in the scheduler config08:58
*** jpena|off is now known as jpena08:58
quiquellclarkb: ^08:58
*** panda|off is now known as panda09:12
*** avass has joined #zuul09:14
*** hashar has joined #zuul09:20
*** chandan_kumar is now known as chandankumar09:21
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Add dogpile.cache master to the -src tests  https://review.openstack.org/62545709:27
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: WIP: Implement a local zuul-runner  https://review.openstack.org/60708209:40
tristanCjhesketh: just got "zuul-runner prep-workspace" command working :-)09:40
tristanCjhesketh: i'll work on the "execute" sub-command tomorrow09:46
*** sshnaidm|off is now known as sshnaidm10:27
jheskethtristanC: that's awesome, thanks so much!10:39
jheskethI'm traveling for the next couple of weeks so I won't be able to do much upstream stuff, but I'm looking forward to taking a closer look as soon as I can :-)10:40
tristanCjhesketh: you're welcome, thanks for putting the fondation10:40
jheskethre the order of the patches, they were kept like that because of the way I was working through the problem in my head. I knew some of them should be more logically grouped and it was my intention to reorder and squash etc down the line, so that's fine :-)10:40
quiquelltristanC: hello, I was trying to figure out how to do autohold on success jobs10:44
quiquelltristanC: Does it make sense to put in place a review to configure that per tenant at tenant_configuration ?10:44
tristanCquiquell: perhaps an auto-hold option to force hold even on success?10:45
*** electrofelix has joined #zuul10:45
quiquelltristanC: Looks like job results are harcoded at scheduler https://github.com/openstack-infra/zuul/blob/2fd688352f5e220fda0dfc72b164144910670d95/zuul/scheduler.py#L124910:46
quiquelltristanC: Humm wait I see it now kwno to do it10:47
quiquelltristanC: We get the autohold tuple key, we can also put there the job results we are interested in :-)10:48
quiquelltristanC: Changing the zuul client acording to that, is that it ?10:48
tristanCquiquell: maybe? not sure why the hold command was removed from nodepool in the first place10:49
quiquelltristanC: what do you mean ? do we have an unfiltered autohold at nodepool before ?10:49
quiquelltristanC: I am very new to all this10:49
tristanCquiquell: yes, it was named nodepool hold10:51
quiquelltristanC: do we have a nodepool command too at launchers ?10:51
quiquellyep just checked it10:52
jktin the openstack's zuul config, am I correct in assuming that https://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/main.yaml is the place which lists all projects that Zuul cares about?10:53
jkthow is that file distributed to the scheduler?10:53
jktI'm asking because the quick tutorial (with a prebuild Docker image) apparently has a hard-coded list of projects in a file /etc/zuul/main.yaml which looks like being provisioned out-of-band10:55
quiquelljkt: you have the scheduler config pointing to this file directly, with tenant_config10:55
quiquelljkt: in the zuul.cfg file10:55
jktquiquell: so in case of openstack's CI, is the openstack-infra/project-config managed out-of-band via, e.g., Puppet/cron/soomething?10:58
quiquelljkt: Could be that zuul.cfg is generated10:59
quiquelljkt: maybe at #openstack-infra they know better10:59
* quiquell remember reading about it but has forgot11:00
jktquiquell: let me rephrase, I'm being confused because in case of that CI, there's a git repo which contains both the top-level tenant definition with a list of projects etc, and that same git repo is also being "included" into zuul from that same tenant config11:05
jktso I wonder how this got bootstrapped11:05
quiquelljkt: For example you can clone it start zuul and with this config and commit changes to this it will be hot reconfigured11:07
quiquelljkt: and if you restart you have to be sure that you are refreshing the cloned repo11:07
quiquelljkt: out of my mind, don't know how the real deal is done11:07
jktokay, thanks, I'll wait for the admins to respond, I know they are here as well11:08
*** gtema has quit IRC11:09
jktquiquell: it seems like it's provisioned out-of-band for the tenant config, https://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/site.pp#n86211:13
quiquelljkt: so they just clone and push changes later on11:14
jktquiquell: perhaps it's the cron+puppet for content of the tenant file (which is https://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/main.yaml ), and then zuul's builtin stuff for https://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul.d11:16
openstackgerritSagi Shnaidman proposed openstack-infra/nodepool master: Support userdata for instances in openstack  https://review.openstack.org/63064911:19
quiquellsshnaidm: ^ needed for the cloud-init + zuul ?11:20
sshnaidmquiquell, yep11:21
quiquellsshnaidm: cool cool11:22
quiquellsshnaidm: so at the end is not an image issue ?11:22
sshnaidmquiquell, there is no other way to inject key for non-default user except using userdata :(11:23
sshnaidmquiquell, and I don't know if we want to go this way tbh..11:23
quiquellsshnaidm: let's talk about this this afternoon meeting11:23
sshnaidmquiquell, yeah11:24
sshnaidmbut still nice to have this functionality in nodepool, seems like very trivial change11:24
openstackgerritTobias Urdin proposed openstack-infra/zuul-jobs master: Add upload-puppetforge role  https://review.openstack.org/62755311:30
quiquellsshnaidm: Can you put the possible options at the taiga thingy for the meeting ?11:34
*** gtema has joined #zuul11:35
*** rfolco has joined #zuul11:38
sshnaidmquiquell, yeah, doing..11:39
avasszuul encryption keys seem to be changing every time the containers are restarted. any way to make them static?11:42
avasskeys for zuul secrets i mean11:42
tobiashavass: you need to mount a volume (/var/lib/zuul) by default into the container11:46
jktI wonder how sane it would be to use https://softwarefactory-project.io/docs/zuul/admin/components.html#attr-scheduler.tenant_config_script to fetch the main config file from Gerrit :)11:46
avasstobiash: into the scheduler?11:53
avasstobiash: looks like it's already doing that in the docker-compose file11:54
tristanCjkt: you still need to reload the scheduler procedure when the file change, so you might as well drop the new version before doing that11:54
tristanCjkt: but it's sounds sane to me to fetch the config dynamically through config_script, but put some retry logic in case gerrit is slow, not available11:55
*** dkehn has quit IRC12:25
*** jpena is now known as jpena|lunch12:27
tobiashavass: yes, into the scheduler. It by default stores its keys in /var/lib/zuul/keys12:31
*** quiquell is now known as quiquell|lunch12:48
*** rlandy has joined #zuul12:58
*** needssleep is now known as TheJulia13:02
avasstobiash: strange, it's mounted and the keys exist but they change when the containers are restarted.13:02
*** quiquell|lunch is now known as quiquell13:05
avasstobiash: looks like it's creating a new volume every time it's restarted13:14
jkttristanC: thanks (...or one could always rely on systemd to restart this if the initial attempt fails, I guess)13:23
jktit seems that I will have to always restart the scheduler when I add/register/... more projects, right?13:23
*** dkehn has joined #zuul13:31
*** jpena|lunch is now known as jpena13:31
tobiashjkt: no, you can update the main.yaml and then trigger a reconfiguration13:33
tobiashhttps://zuul-ci.org/docs/zuul/admin/components.html?highlight=reconfigure#operation13:33
tristanCjkt: no need to restart the process, you can use "zuul-scheduler -d full-reconfigure" as ExecReload=13:34
jktthanks, that's nice, I must have been a bit overwhelmed by the combination of docs *and* the openstack-specific operation cookbooks13:57
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Document default values of runtime arguments  https://review.openstack.org/63067913:59
Shrewsianw: re: your suggestion to my nodepool build timeout change, do you know how dib handles stderr if you use the --logfile option?14:16
*** gtema has quit IRC14:18
tobiashShrews: shouldn't dib isolate concurrent image builds?14:30
tobiashI just switched nodepool to do 2 image builds in parallel and now the builds fail with this: E: Could not get lock /var/cache/apt/archives/lock - open (11: Resource temporarily unavailable)14:31
Shrewstobiash: i don't know14:31
openstackgerritQuique Llorente proposed openstack-infra/zuul-jobs master: WIP: Default private_ipv4 to use public_ipv4 address when null  https://review.openstack.org/62329414:36
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add a timeout for the image build  https://review.openstack.org/62992314:42
*** pabelanger has joined #zuul14:43
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add a timeout for the image build  https://review.openstack.org/62992314:44
quiquelltobiash: Do you know if it's easy to have the seam console stream we have at  zuul web for jobs but at command line ?14:51
quiquelltobiash: like piping it with a command14:52
quiquellI suppose it involes using websockets and all14:52
Shrewsquiquell: finger UUID@zuul.openstack.org    where UUID is the running job uuid (can pull this from the web interface path)14:55
quiquellShrews: thanks15:03
corvusjkt: your assumption about how openstack-infra sets up main.yaml is correct: out-of-band ansible/puppet15:07
corvustristanC: 'nodepool hold' was removed because it doesn't work with the nodepool locking system.15:08
avasszuul_return doesn't seem to work on windows nodes15:08
corvusavass: that's unexpected; do you know why?15:09
corvusavass: oh wait15:10
corvusavass: zuul_return has to run on the executor15:10
avassone second I'll try to reproduce it. It works with delegate_to: localhost but throws an exception otherwise15:10
corvusavass: so yes, delegate_to: localhost is the right way to use it15:10
corvuswe should, erm, probably document that.15:11
avassalright, but then the variables seem to be undefined in the child job15:11
avasshaha15:11
corvusokay, we did "document" it, in that we mentioned it in a sentence, and then proceeded to omit the localhost part from every example.  i'll make a patch15:12
avassah, I see it now15:13
corvusavass: oh, what was the issue?15:13
avassI mean the documentation :)15:13
corvusavass: oh, so the vars in child job is still an issue?  can you pastebin the task that uses zuul_return so i can look at it?15:14
jktcorvus: thanks; I saw some initial (?) work for auto-restarting scheduler upon changes to the tenant config, but it appears to be disabled15:15
jktcorvus: is that a manual step now?15:16
avasshttp://paste.openstack.org/show/742309/15:17
corvusjkt: i don't recall that -- we've needed a reconfiguration (which is much less disruptive than a restart) to reload main.yaml since 3.0.  the main.yaml basically bootstraps the system to tell zuul where all the git repos are so it can find the rest of the configuration.15:18
tobiashcorvus, avass: there is a change in review that converts zuul_return into a plugin: https://review.openstack.org/59116815:19
tobiashthis way we won't have to delegate it to localhost15:19
corvusthat'll be nice :)15:19
jktcorvus: https://git.openstack.org/cgit/openstack-infra/system-config/tree/playbooks/zuul_reconfigure.yaml looks like a stub15:19
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Include "delegate_to: localhost" in zuul_return examples  https://review.openstack.org/63070015:20
corvusjkt: ah, yes, that -- sorry, i thought you meant in zuul itself.  yes, that should, eventually, be part of a post-merge job in openstack's zuul to reload zuul's configuration when changes land to that file.  it's waiting on us to move more of our config management to ansible.15:21
tobiashcorvus: what do you think about adding run: once to this too? ^15:21
corvustobiash: probably a good idea15:21
pabelangeravass: corvus: https://review.openstack.org/591168/ makes zuul_return more user friendly for playbooks, but still need to address tobiash comments15:21
pabelangerah, just seen tobiash pointing to it15:22
jktcorvus: and all projects to "handle" via zuul must be defined in a per-tenant manner via its main config file, right? (and only activated by that reconfig op)15:23
corvusjkt: exactly15:23
corvusavass: there were some yaml errors in that (colon on line 2, indentation on lines 4-6); it should look like http://paste.openstack.org/show/742310/15:24
jktthanks, I hope this is all from me for now :)15:24
corvusavass: wait15:24
corvusavass: sorry, like this: http://paste.openstack.org/show/742311/15:24
corvusjkt: you're welcome :)15:25
avasscorvus: yeah, that makes sense15:26
avasscorvus: but it doens't seem like it fixed it15:29
corvusavass: do you have the inventory file from the child job?15:29
avasscorvus: http://paste.openstack.org/show/742313/15:32
corvusavass: i mean like this: http://logs.openstack.org/68/630468/8/check/system-config-build-image-gerrit/ca32dee/zuul-info/inventory.yaml   (we have our base job set up to save the inventory file on the log server)15:33
avasscorvus: oh, I'm not using the default base job15:37
corvusavass: if you add https://zuul-ci.org/docs/zuul-jobs/roles.html#role-log-inventory  to your base job, you'll get the inventory saved too; it can be very useful in debugging.15:38
corvusavass: if you want to continue debugging without that change, you can run 'zuul-executor keep' on an executor node, and it will not delete the build directory when it's finished a job.  you can then look at the logs to see what the full path is (should be like: /var/lib/zuul/builds/<uuid>/...) and look in there to see the inventory file15:39
corvusavass: that might give us a clue if we see the variable showing up someplace unexepected in that file, or not at all.15:39
corvusavass: ('zuul-executor unkeep' turns deletion back on again when you're done)15:40
corvusavass: also, can you pastebin the project-pipeline configuration where these jobs are running?15:41
avasscorvus: not sure if I'm allowed to do that to be honest15:43
avasscorvus: post the pipeline that is15:44
corvusavass: no problem; i mostly wanted to see what the "dependencies" configuration between the jobs was15:45
avasscorvus: oh, it's independent15:46
corvusavass: i assume it looks like this?  http://paste.openstack.org/show/742314/15:46
corvus(since i haven't fixed that bug where dependencies are ignored if they aren't in the project-pipeline config; that's on my list this week)15:47
avassorvus: oh, no. the job is inheriting from the base job that fetches information and tries to return to jobs inheriting from it15:47
corvusavass: ah there's our problem; i think it's one of terminology.  zuul_return is used to pass information from one job to a second (dependent) job, which runs after the first.15:49
avasscorvus: ah15:49
*** hashar has quit IRC15:50
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add a timeout for the image build  https://review.openstack.org/62992315:50
corvusavass: i'm guessing you have two playbooks, one in a parent job, and one in a child job which inherits from the parent.  and when the child job runs, both playbooks are run, and you want to pass data from the parent's playbook to the child's.15:50
avasscorvus: exactly15:51
corvusavass: i'd probably recommend using plain ansible to share that data... maybe via json files...15:51
corvusavass: maybe write a json file with the "copy" module, and then use "include_vars" to load it15:52
avasscorvus: yeah, that will probably do it.15:53
corvusavass: the nice thing about that is it's testable outside of zuul15:53
*** avass has quit IRC16:05
*** hashar has joined #zuul16:11
openstackgerritMerged openstack-infra/zuul master: Add governance document  https://review.openstack.org/62243916:12
* fungi spies https://zuul-ci.org/docs/zuul/governance.html16:19
*** pcaruana has quit IRC16:20
corvustobiash: i'm worried about 630472 landing too early (mordred has +2d it already).  i'd like to wait until we've actually landed the spec before we starting doing big changes like that.  i'm going to put an administrative -2 on it for now, ok?16:24
mordredcorvus: reading scrollback - we could make zuul_return into an action plugin instead of a normal module so that it always runs on the executor regardless of the playbook ... which I now see tobiash has linked to a patch doing16:27
fungicould it depends-on the spec change?16:27
tobiashcorvus: fine for me16:27
pabelangermordred: Yup, do you have thoughts on path there?16:30
pabelangerI can push up a patch to get it landed16:30
*** chandankumar is now known as codemonster16:31
mordredpabelanger: well - if we keep it, we should definitely do the path validation on the value ... I don't see anywhere that we're passing path - but it has been part of the argspec for the module version, so removing it would probably need a deprecation period16:34
tobiashmordred: the path argument is completely undocumented16:35
tobiashI even wasn't aware of it until I reviewed pabelanger's change16:35
mordredtobiash: hrm. good point16:36
mordredcorvus: do you have an opinion?16:36
corvusmordred: i think it's probably okay to drop; i added it in case it was useful, but i don't think a use has come up in the past year16:37
mordredcool. yeah - it also doesn't seem useful to me16:37
*** rfolco is now known as rfolco|brb16:37
*** corvus is now known as thecount16:38
*** thecount is now known as corvus16:38
*** zxiiro is now known as zxiiro-away16:40
*** themroc has quit IRC16:46
*** codemonster is now known as chkumar|out16:49
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Convert zuul_return into action plugin  https://review.openstack.org/59116816:54
pabelangercorvus: mordred: tobiash: i believe ^ should address safe_path comment16:54
pabelangerI can also send on ML post about removing it, just to be safe16:54
tobiashpabelanger: commented16:59
pabelangertobiash: ah, thanks17:02
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Convert zuul_return into action plugin  https://review.openstack.org/59116817:03
pabelangertobiash: I didn't run remote tests, lets see what zuul.o.o says now17:04
corvusif it's an action plugin, is it okay to still have delegate_to: localhost?17:04
corvus(will that just be ignored?)17:05
pabelangerbelieve it is ignored17:06
pabelangerwe can add test for that too17:06
tobiashcorvus: yes, that should be ok17:08
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Convert zuul_return into action plugin  https://review.openstack.org/59116817:09
pabelangerand test to confirm17:09
tobiashcorvus: further docs to action plugins: https://docs.ansible.com/ansible/latest/plugins/action.html17:11
tobiashSo in our case we actually just skip the actual module17:11
*** gtema has joined #zuul17:14
*** pcaruana has joined #zuul17:15
openstackgerritMerged openstack-infra/zuul-jobs master: Add upload-puppetforge role  https://review.openstack.org/62755317:17
pabelangerhas anybody thought about submitting a talk for open infra summit in Denver? I know CFP is still open, but haven't found the motivation to write up anything yet17:22
clarkbpabelanger: I haven't, but was thinking a good talk could be a bit more in depth presentation about how to run zuul (and in general CI) at scale17:28
clarkbthings like the fair scheduling, distributed mergers and executors, multiple clouds (or other nodepool providers etc17:28
pabelangerI'd attend :)17:29
pabelangerwould be good to also give numbers to people17:29
pabelangerwas thinking of submitting one about migrating from jenkins to zuul17:29
clarkbI don't know that I'll be able to do that myself or at least by myself considering I'll be prepping for PTG and other infra tasks17:29
pabelangeror how to CD an openstack cloud from zuul, for the purpose of using it for testing resources17:29
*** gtema has quit IRC17:38
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Convert zuul_return into action plugin  https://review.openstack.org/59116817:39
*** hashar has quit IRC17:42
*** hashar has joined #zuul17:42
*** hashar_ has joined #zuul17:45
*** hashar has quit IRC17:46
*** hashar_ has quit IRC17:47
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add a timeout for the image build  https://review.openstack.org/62992317:52
*** electrofelix has quit IRC17:57
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add a timeout for the image build  https://review.openstack.org/62992318:06
pabelangertobiash: corvus: mordred: https://review.openstack.org/591168/ is ready for review again18:08
pabelangerI guess, maybe we should add a reno note about the change18:08
*** panda is now known as panda|off18:12
*** jpena is now known as jpena|off18:12
tobiashI think reno makes sense18:14
*** rfolco|brb is now known as rfolco18:14
corvusyeah, maybe just to let folks know they don't need 'delegate_to' anymore18:35
*** remi_ness has joined #zuul18:47
*** remi_ness has quit IRC18:54
*** pcaruana has quit IRC19:08
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Add release note for zuul_return action plugin update  https://review.openstack.org/63076019:09
corvuspabelanger: can you squash that?19:09
pabelangersure, was trying to keep tobiash review19:09
corvusif the only change is a reno, i'm sure the re-review will be easy :)19:10
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Convert zuul_return into action plugin  https://review.openstack.org/59116819:11
pabelangerdoh19:11
pabelangerOh, that is right.19:11
openstackgerritMerged openstack-infra/zuul master: sql: add buildset uuid column  https://review.openstack.org/63003419:13
*** remi_ness has joined #zuul19:25
pabelangercorvus: Shrews: do you think we'll have a nodepool release this week too? The 1/2 of code for zuul-executor zones is still unreleased.19:32
corvusShrews: ^? :)19:54
clarkbopenstack is running up to date launchers and builders. I dont think there are problems other than the dib build timeout fix19:55
clarkbmay want to get that in or do a releasethen quickly get timeout released after19:56
pabelangerwfm19:59
*** remi_ness has quit IRC20:05
corvuswhat's the urgency for the dib timeout fix?20:08
pabelangerI just realized, we don't actually install encrypt_secret if you pip install zuul. Think we should maybe update that to zuul-encrypt(-secrets) and add entrypoint20:08
clarkbcorvus: openstack found that dib builds were hanging blocking the image build queues twice in two months. Probably low overall20:08
corvuspabelanger: well, it's not really intended to be run on zuul servers; it's intended to be run by anyone, via wget.  we *could* do that, but then i feel like we're undercutting the message that "you don't need to install zuul to run this"20:09
corvusclarkb: okay, so there isn't some new change in the landscape that we urgently need to respond to (obviously getting the fix in asap is good, but it doesn't need to supercede normal process)20:10
clarkbcorrect20:10
corvusShrews, pabelanger, clarkb: so it sounds like we could tag master now, then do a new release once the timeout stuff has settled20:10
clarkbyes I think so20:11
pabelangercorvus: sure, I don't have a strong view on it. I needed it on a remote server, and defaulted to pip install zuul, and noticed it wasn't there.  I then proceeded to git clone the repo for it.20:11
pabelangerwget would have worked, just didn't think to do it.20:11
corvusclarkb: we've restarted with the config parsing changes?20:11
clarkbcorvus: let me find where I noted the sha120:12
clarkbf8bf6afd08bcdcee06b377fda71ad543a63f2ffc was what i restarted on20:13
clarkbthat does not include config parsing changes20:13
corvuspabelanger: in this case, it sounds like a win, since you've now realized that you don't need to install zuul just to get the tool; the main thing that could be improved is finding a way for you to have realized that before installing it.  :)20:14
pabelangeragree20:14
corvusclarkb: ok.  nothing user-visible depends on the config changes, so i think we can release that sha (but i wouldn't want to release later without testing in case we missed an edge case in config loading)20:15
pabelangerokay, I need to #dadops here for a bit, will be back online in a few hours. any version of nodepool works for me, if openstack isn't running master20:15
corvusclarkb, pabelanger, Shrews: i think we can tag nodepool f8bf6afd08bcdcee06b377fda71ad543a63f2ffc as 3.4.0.  sound good?20:15
clarkb++ there was at least one feature added (the metadata support in openstack driver)20:16
clarkbso commit and tag lgtm20:16
tobiashcorvus, clarkb: that will miss this fix for static winrm nodes: bcaa264 - Default host_keys to empty list in static driver20:30
tobiashbut I think the one who had this problem (I forgot the name) doesn't depend on a release20:31
corvusdrat, sorry i missed that20:32
corvusbut it sounds like we can still go ahead and release f8bf, and that will end up in the timeout fix which will probably follow shortly20:32
Shrewscorvus: yeah. changing the dib timeout stuff for ian is proving a bit problematic atm20:33
tobiashok, ++ for f8bf20:33
tobiashbtw, think we should land 613261 and do another zuul release soon (maybe next week)20:34
tobiashwithout this the skip child jobs feature is unusable and can even wedge zuul20:35
corvusShrews: any reason that's a CLI argument and not a config file entry?20:35
Shrewscorvus: no, only following the pattern for the num uploaders/builders. we don't have any "count" of things in the config for builder, atm20:36
corvusShrews: ok, i'm going to suggest the other way with more words on the review20:37
Shrewscorvus: that's fine, thx20:37
Shrewsi don't know how my most recent change to the fake dib command "fixed" the nodepool-zuul-functional job. that's a puzzler20:40
Shrews*sigh*20:40
Shrewscorvus: clarkb: tobiash: can we please get a consensus on whether the timeout should be per-image or global? folks keep suggesting either way and i'd like to get that settled20:43
clarkbShrews: the ideal would be to be per image20:43
tobiashShrews: I'm ok with either20:44
clarkbShrews: that way you don't have to set all iamges to a ~12 hour timeout if you are tobiash. That said I think it is ok to do a global timeout value if it is siginificantly simpler to implement20:44
Shrewsso, i hear "either" again. corvus, final vote?20:45
tobiashShrews: you can rrad my 'either' as take the choice of less effort ;)20:46
ShrewsI'll make the executive decision then... i'll just do the per-image route, even though it's more code.20:49
ShrewsDisagreeing voices may show their disapproval with a patch set of their own.  :)20:50
corvusShrews: that wfm.  we can always upgrade it to "both" later.  :)20:51
*** hashar has joined #zuul21:03
dmsimardThis isn't the first time I see something like this when trying to see the console recently: https://i.imgur.com/zZ3j3rl.png .. I noticed that when it happens, the progress bar on zuul web doesn't seem to actually progress.21:09
clarkbdmsimard: it means the jobs hasn't actually started aiui21:09
clarkbbut there is a node allocated for the job21:10
dmsimardclarkb: right, but the "end of stream" loop ?21:10
clarkbprobably due to the governor in the executors21:10
clarkbdmsimard: the web client is trying to connect to the stream ina  loop21:10
dmsimardthe end of stream loop is new to me21:10
clarkbeventually it should connect once the job starts running21:10
dmsimardoh, is it, huh21:10
dmsimardhttp://zuul.openstack.org/stream/4324b9b7d7ed45278a9ec8e75595d115?logfile=console.log has been looping for a while now ...21:11
*** maxamillion has quit IRC21:11
clarkbdmsimard: http://grafana.openstack.org/d/T6vSHcSik/zuul-status?orgId=1 zero accepting executors21:12
clarkbfor about half an hour, that seems long21:12
dmsimardok, we can move to -infra21:12
dmsimardeh, of course now it starts21:13
dmsimardso should we wait until an executor has picked up the nodeset before making the console available ?21:17
dmsimardotherwise the UX is not awesome21:17
corvusdmsimard: theoretically that would mean waiting for the build to have reported 'start'; i'm not sure what the trigger is for that atm.21:19
dmsimardclarkb: I was looking at the ram sensor http://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/executor/sensors/ram.py21:37
dmsimardIt doesn't take swap into account... should it ?21:37
dmsimardThey're two different things from the perspective of psutils21:37
dmsimardex: http://paste.openstack.org/show/742354/21:37
clarkbdmsimard: possibly? or maybe it should be a different sensor21:38
clarkbdmsimard: however in this case it would just result in us not running any more jobs21:38
clarkbreally what we need to figure out is how to reduce the memory overhead of the zuul executor (I think)21:38
dmsimardBrowsing through upstream Ansible issues to see if there's anything obvious standing out... Unless mistaken, Zuul is currently running Ansible 2.5.14 which contains some significant memory usage improvements that landed either in 2.4 or early on in 2.521:45
dmsimardThey're up to 2.6.11 and 2.7.5 now but the issues I found were fixed before then21:50
fungithe osf newsletter editors want to run a spotlight piece on zuul for this week's edition, so i've been trying to put together some notes at https://etherpad.openstack.org/p/a5OnSIreGH and would appreciate links anyone has handy for proposed changes or design discussions about adding gitlab or bitbucket connection drivers to zuul, and a gce provider driver to nodepool (did i perhaps imagine one or more of21:51
fungithose?)21:51
clarkbdmsimard: manageLoad which determines if the governor should kick is is run after grabbing a job handle but before executing it21:55
clarkbdmsimard: this explains your time gap in the log21:55
clarkb(I think)21:55
clarkbcomment says this is done to make unittesting easier21:57
clarkbwe might be able to turn that into a test only behavior21:57
pabelangercorvus: f8bf6a wfm22:02
*** hashar has quit IRC22:13
fungigrepping the mailing list archives turns up no mention of gce, only a note that someone at ansiblefest had requested bitbucket, and no mention of gitlab since november 28 (though that thread is probably at least notable enough to link for it)22:38
fungihrm, or not, it's more about aggregating changes under test22:41
fungiaha, found some irc conversation for bitbucket22:42
fungifound people in the channel log talking about the possibility they might write drivers for bitbucket and gitlab, but no firm commitments22:46
fungiand none in the past 6 months at any rate22:47
fungiamd last real gce driver mention in channel was last april22:47
fungiso i'll just take those out22:47
mordredfungi: yah - I don't think those have made much traction22:50
fungii don't suppose tristanC's vmware driver has garnered much interest either? https://review.openstack.org/55446322:51
fungi maybe mentioning and linking to it will at least encourage someone to help finish it22:57
ianwShrews: stderr & stdout shoudl be caught by dib's --logfile output22:59
ianwtobiash: dib in parallel probably isn't as isolated as you'd hope.  certainly we have a few lockfiles and points where we deal with concurrency, but it's not very well tested23:01
mordredfungi: fbo has made good progress on the pagure driver: https://review.openstack.org/#/c/604404/23:03
fungii saw! included a mention/link for it in the writeup already23:04
mordredfungi: which, incidentally, has led to improvements to pague in a good virtuous circle23:04
mordredyay!23:04
fungiexcellent23:04
ianwShrews: the capturing is based on what devstack does redirects via a backgrounded python process.  it's been working fairly well in unit tests where builds are now split out for easier tracing of issues, e.g. http://logs.openstack.org/20/619120/18/gate/dib-functests-xenial-python3/a9d9b45/logs/23:05
*** rlandy has quit IRC23:25
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Add dogpile.cache master to the -src tests  https://review.openstack.org/62545723:33
*** dkehn has left #zuul23:33
*** dkehn has joined #zuul23:37
pabelangerfungi: one of the human interested in gitlab has sadly moved on from the original company, they are no longer doing zuul23:41
fungi:(23:43
fungisad for us anyway23:43
fungiperhaps it's happy for them though23:43
clarkbhttps://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/models/project_services/ci_service.rb looks like the starting point of adding such support to gitlab for zuul23:43
clarkb(you can also do more restricted webhooks(23:43
tristanCfungi: thanks for putting the list together, i'm not aware of any wip for the vmware driver23:44
fungiwell, at least there's work someone can build on for it23:44
*** rfolco has quit IRC23:45
clarkbfungi: oh well thats just their generic ci service base class in gitlab23:45
clarkbunsure of any specific zuul work23:45
fungiclarkb: sorry, i was responding to tristanC with that ;)23:45
*** rfolco has joined #zuul23:45
corvuspabelanger: oh, then maybe we should put out a call for interest on the mailing list, since i think some folks were waiting on that work to start; maybe there's enough interest to put a group together?23:47
pabelanger+123:48
pabelangerwe in ansible-network are likely still interested in it, just haven't discussed it much on our side recently23:49
tristanCperhaps i should abandon those untested driver that are starting to rot, and replace them with a "how to write a driver" documentation23:49
tristanCShrews: do you think we can mark the current drivers api as stable (e.g. version=1) ?23:51
fungimmm, if you're planning to abandon the vmware and azure drivers, maybe i shouldn't mention them in the article23:52

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