Monday, 2019-06-17

*** bhavikdbavishi has joined #zuul01:45
*** bhavikdbavishi has quit IRC01:52
*** ianychoi has quit IRC02:25
*** ianychoi has joined #zuul02:26
*** homeski_ has joined #zuul03:38
*** homeski_ is now known as homeski03:41
homeskiI installed zuul from source, and everything works now except the builds API ...03:49
homeskiI can `curl myhost.com/api/tenant/my-tenant/info` and get a JSON response back03:50
homeskibut `curl myhost.com/api/tenant/my-tenant/builds` returns a 40403:50
homeski`404: Tenant homero does not exist`03:51
homeski** sorry `404: Tenant my-tenant does not exist`03:51
homeski`curl myhost.com/api/tenant/my-tenant/jobs` returns successfully03:52
homeskiI've tried creating multiple tenants, changing names ... but for whatever reason `.../builds` always returns a 404 and "tenant does not exist"03:53
homeskiany ideas on what is going wrong?03:53
homeskieverything seems to work (labels, jobs, console-stream, info, etc) besides`/builds`03:56
tristanChomeski: iirc the builds api is only available when there is an sql connection, did you configured one?03:58
homeskinope...03:59
homeskiI don't see anything in docs specifically about that04:00
homeskiany tips on setting that up?04:00
homeskijust setup a `[connection sql]` in zuul.conf, then restart services?04:02
tristanChomeski: yes, such as: https://opendev.org/zuul/zuul/src/branch/master/doc/source/admin/examples/etc_zuul/zuul.conf#L2804:04
homeskidoes a reporter need to be configured as well? as talked about here: https://zuul-ci.org/docs/zuul/admin/drivers/sql.html04:05
tristanChomeski: yes, zuul doesn't store build data automatically, pipelines need the sql connection in succes/failure reporters list04:07
tristanCsuch as: https://opendev.org/zuul/zuul/src/branch/master/doc/source/admin/examples/zuul-config/zuul.d/pipelines.yaml#L2004:08
homeskiI see now. Thanks for the info04:09
tristanChomeski: you're welcome :)04:09
*** bhavikdbavishi has joined #zuul04:26
*** sshnaidm|off has quit IRC05:01
openstackgerritJoshua Hesketh proposed zuul/zuul master: Expose date time as facts  https://review.opendev.org/66467405:26
openstackgerritJoshua Hesketh proposed zuul/zuul master: Expose date time as facts  https://review.opendev.org/66467406:10
*** saneax has joined #zuul06:18
*** gtema has joined #zuul06:56
*** jpena|off is now known as jpena07:52
openstackgerritFabien Boucher proposed zuul/zuul master: Pagure driver - https://pagure.io/pagure/  https://review.opendev.org/60440407:58
*** sshnaidm has joined #zuul08:08
*** hashar has joined #zuul08:11
*** sshnaidm has quit IRC08:14
*** sshnaidm has joined #zuul08:17
*** flepied has joined #zuul08:47
*** pcaruana has joined #zuul08:52
*** sileht has joined #zuul09:24
tobias-urdinthere is a 3.8.2 release on pypi but can't see a 3.8.2 git tag?09:42
*** gtema has quit IRC10:19
*** gtema has joined #zuul10:19
openstackgerritGuillaume Vincent proposed zuul/zuul master: Return store object instead of a function  https://review.opendev.org/66564210:59
*** jpena is now known as jpena|lunch11:15
*** panda is now known as panda|lunch11:23
*** hashar has quit IRC11:27
fungitobias-urdin: where do you see a 3.8.2 release on pypi?11:49
fungihttps://pypi.org/project/zuul/ says zuul 3.8.111:50
fungi(which corresponds with the most recent tag)11:50
tobias-urdinah sry, missed pre-release so it's probably from master11:53
fungiyeah, those are auto-numbered dev snapshots of the master branch state12:00
*** rfolco has joined #zuul12:01
*** rlandy has joined #zuul12:14
*** rlandy is now known as rlandy|ruck12:15
*** panda|lunch is now known as panda12:25
*** rlandy|ruck is now known as rlandy|ruck|mtg12:29
*** hashar has joined #zuul12:38
*** lennyb has quit IRC12:40
*** jpena|lunch is now known as jpena12:49
*** rlandy|ruck|mtg is now known as rlandy|ruck12:54
*** armstrongs has joined #zuul12:58
armstrongshi im trying to setup ara 1.0.1 with zuul but it doesn't seem that ara-wsgi-sqlite binary is packaged with it. Is it not ready to use with ara-wsgi-sqlite?13:00
armstrongsI had it working on 0.16.413:00
*** gtema has quit IRC13:09
fungiarmstrongs: we've also pinned our installation to the last release before 1.0.0, as far as i know there's no middleware or static deployment method for ara 1.x13:10
fungiat least not yet, but i think dmsimard was working on something13:10
armstrongsah ok thanks for the info13:10
*** lennyb has joined #zuul13:13
*** pcaruana has quit IRC13:26
*** pcaruana|afk| has joined #zuul13:26
*** bhavikdbavishi has quit IRC13:33
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213413:40
*** pcaruana has joined #zuul13:48
*** pcaruana|afk| has quit IRC13:51
dmsimardarmstrongs: we have a WIP patch for implementing a similar sqlite middleware for 1.013:59
dmsimardso it's in progress :)14:01
*** hashar_ has joined #zuul14:03
*** hashar_ has quit IRC14:03
armstrongsdismard: sounds great looking forward to it :)14:07
openstackgerritGuillaume Vincent proposed zuul/zuul master: Return store object instead of a function  https://review.opendev.org/66564214:28
*** hashar has quit IRC14:29
*** jamesmcarthur has joined #zuul14:44
*** pcaruana has quit IRC14:47
*** saneax has quit IRC14:56
pabelangerdoes autohold work with regex? didn't see anything in docs, figured I ask before diving into code14:57
pabelangerdoesn't look like it for job name15:02
pabelangertobiash: I look a quick look at reviews last night, looks pretty sane to me. I'm not sure how to best test this however, have any ideas?15:07
pabelangerI was thinking we could run a zuul-test instance setup to github, with new github app maybe on gtest org that opendev has15:08
corvuspabelanger: the unit test coverage gives me enough confidence to restart the opendev system with it.  but perhaps tobiash has already run it on his?15:11
Shrewspabelanger: i don't think there is any regex support on any of the autohold fields15:11
fbocorvus: Hi, should we retry a W+1 on the Pagure Driver patch https://review.opendev.org/604404/ ?15:12
pabelangercorvus: okay, cool. That works for me, if you are good :)15:12
pabelangerShrews: I _think_ refs can15:12
*** hashar has joined #zuul15:13
Shrewspabelanger: oh, you're right. there is a re.match() on ref15:13
pabelangercorvus: tobiash: just checking moring ERRORs in scheduler, noticed http://paste.openstack.org/show/753097/ for the first time.15:14
pabelangerI also noticed 2019-06-17 14:57:14,834 ERROR zuul.GithubEventConnector: [delivery: d9af4484-910e-11e9-985f-7d61fe3bb106] Failed handling status event; remote said retry after None,will retry attempt 5/5 in 60.0 seconds :( still not long enough wait time15:16
corvuspabelanger: was that in a sytem running with parallel support?15:18
pabelangercorvus: no, just the retry patch15:20
*** jamesmcarthur_ has joined #zuul15:21
*** jamesmcarthur has quit IRC15:25
tobiashcorvus: I'm not running this yet because I first need to reimplement the parallel thing on top of it15:32
tobiashBut I extensivly tested it using the github debug tooling that creates a standalone githubconnection object15:32
corvustobiash: should we wait until you're done with that to land changes and test?15:38
*** pcaruana has joined #zuul15:40
Shrewsmhu: sorry for misspelling your name in that email  :)15:42
mhuShrews, no worries, my girlfriend is american and that's how her side of the family calls me :)15:43
openstackgerritMerged zuul/nodepool master: static: enable using a single host with different user or port  https://review.opendev.org/65920915:45
tobiashcorvus: I think it should work and I can wait with my next update until I implemented it. So it's your choice. I think it will have quite some benefit for upstream given the current problems15:46
*** ianychoi_ has joined #zuul15:48
corvusfbo: done! :)15:50
*** ianychoi has quit IRC15:52
*** gtema has joined #zuul15:55
corvusclarkb, fungi: https://review.opendev.org/657102 may not be on your radar but could use a look16:01
fungithanks for the heads up, checking it out now16:02
*** mattw4 has joined #zuul16:03
fungithat looks quite useful, agreed!16:08
fbocorvus: thanks hopefuly it will pass the gate this time :)16:10
*** michael-beaver has joined #zuul16:22
*** panda is now known as panda|off16:30
*** igordc has joined #zuul16:44
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213416:45
*** zbr|ooo has quit IRC17:04
*** zbr has joined #zuul17:05
*** zbr is now known as zbr|ruck17:06
*** hashar has quit IRC17:13
*** jpena is now known as jpena|off17:14
pabelangertobiash: so, maybe terrible idea, but it would be neat if zuul could some how figure out the diff when a PR was created, to when zuul got the event, then emit that into statsd.  There is some sort of outage going on at https://www.githubstatus.com/, and figure tracking that in grafana might be helpful to our users17:17
pabelangerright now, events look to be 1hr delayed17:17
fungipabelanger: could it be the gh event processing queue in zuul which is backed up?17:21
pabelangerfungi: no, it is basically zero right now17:23
pabelangerevents from GH just delayed today17:23
*** sshnaidm is now known as sshnaidm|afk17:28
fungiahh17:31
fungiso something queuing on the gh end of things17:31
*** chandankumar is now known as raukadah17:33
*** gtema has quit IRC17:37
pabelangeryah, some sort of backup today17:43
mgoddardhello17:46
corvusthat github queues events like that is interesting and useful knowledge17:46
mgoddardhaving an issue with some zuul config, trying to skip a job on a branch17:46
mgoddardhttps://opendev.org/openstack/kolla/src/branch/master/.zuul.d/centos.yaml#L3817:46
mgoddardI've seen that pattern used elsewhere, but that periodic job still seems to run on stable/ocata17:47
mgoddardhttp://zuul.openstack.org/builds?job_name=kolla-publish-centos-source&branch=stable%2Focata17:47
fungimgoddard: could it be because of https://opendev.org/openstack/kolla/src/branch/stable/ocata/.zuul.yaml#L4917:50
mgoddardfungi: good question17:51
fungigenerally you should either control jobs in branched zuul configuration or only in master, but having them defined in both places gets confusing17:51
fungii can't remember whether explicit vs implicit branch filters take precedence17:52
corvusneither, they both win :)17:52
fungiaha. so as long as at least one of them says it runs, then it runs17:52
corvusyep17:52
corvusbetween the two, i'd recommend controlling things like that in the branches themselves rather than master17:53
corvusso i'd drop https://opendev.org/openstack/kolla/src/branch/master/.zuul.d/centos.yaml#L35-L40 as well as https://opendev.org/openstack/kolla/src/branch/stable/ocata/.zuul.yaml#L4417:54
mgoddardso I could remove the filter from master and add it to stable/ocata17:54
corvusnothing says "don't run this job" like not having anything that says "run this job" :)17:54
corvusmgoddard: no need for a filter on stable/ocata17:54
corvusmgoddard: as long as nothing on stable/ocata says to run the job, then it won't run17:54
*** hashar has joined #zuul17:56
mgoddardI think my mental model of zuul config is incomplete17:56
*** jamesmcarthur_ has quit IRC17:57
mgoddardwe do want to run periodic jobs for pike,queens,rocky,stein,master17:57
corvusmgoddard: i'd recommend adding the jobs you want to .zuul.yaml (or equivalent) on each of those branches17:57
mgoddardideally we'd not touch the zuul config when we branch, but is that going to be a problem?17:57
funginormally it's designed so that when you branch your old branches keep running what they were running at the time they were branched, unless you update the branch17:58
mgoddardright17:58
fungiso in theory the kolla-publish-centos-source job was running for master when stable/ocata was branched from it17:58
mgoddardcorvus: you said to remove https://opendev.org/openstack/kolla/src/branch/master/.zuul.d/centos.yaml#L35-L40 Is that not going to break our periodic jobs?17:59
fungiif you want stable/ocata to stop running kolla-publish-centos-source in its periodic pipeline after branching, then you would edit the .zuul.yaml file in the stable/ocata branch removing the kolla-publish-centos-source job from its periodic pipeline definition17:59
mgoddardok. I'll give that a shot18:00
mgoddardand maybe read the zuul docs again :)18:00
corvusmgoddard: since stable/pike still has the job listed (just like stable/ocata), it will continue running the job18:00
fungibut for stable/pike of course18:00
corvusright18:00
mgoddardgreat, thanks for the help18:01
fungithe branch the job should operate on is inferred from the zuul config if that branch has zuul configuration, otherwise the configuration on the master branch is used. jobs defined on a branch assume they are scoped to that branch unless you override that via further configuration18:01
corvusmgoddard: this is probably the most relevant bit of docs if you want that refresher: https://zuul-ci.org/docs/zuul/user/config.html#attr-job.branches18:02
*** rlandy|ruck is now known as rlandy|roverish18:02
corvus(especially the part at the end)18:02
mgoddardthat makes sense now you say it. I think there was a mention of branchless config at some point that confused me, but google suggests thats more for projects without branches (of course)18:03
mgoddardthat does look helpful, I'll give it a read. Thanks18:03
*** mattw4 has quit IRC18:07
*** mattw4 has joined #zuul18:07
*** mattw4 has quit IRC18:12
*** gtema has joined #zuul18:36
*** gtema has quit IRC18:42
*** pcaruana has quit IRC18:44
*** jamesmcarthur has joined #zuul18:51
*** hashar has quit IRC18:53
*** pcaruana has joined #zuul19:17
*** pcaruana has quit IRC19:27
*** rlandy|roverish is now known as rlandy|roverish|19:28
*** rlandy|roverish| is now known as rlandy|rover|brb19:29
*** jamesmcarthur has quit IRC19:42
*** armstrongs has quit IRC19:44
*** rlandy|rover|brb is now known as rlandy|rover19:50
*** mattw4 has joined #zuul19:50
*** jamesmcarthur has joined #zuul20:15
corvustobiash: question on 66550520:28
*** jamesmcarthur has quit IRC20:28
tobiashcorvus: responded20:33
tobiashI guess I should just remove that comment20:33
corvustobiash: okay, if 403 always has the needed header i agree it's okay, and it's only a confusing comment :)20:34
corvustobiash: probably worth removing the comment though, considering how confusing it could be20:35
tobiashyeah, I'll remove it20:35
tobiashjust a sec20:35
corvustobiash: that whole stack looks great :)20:36
tobiashthanks :)20:36
*** jamesmcarthur has joined #zuul20:37
tobiashshall I push the header removal as followup or change 665505?20:37
corvustobiash: change 505, i'll re+220:37
tobiashk20:37
*** hashar has joined #zuul20:38
openstackgerritTobias Henkel proposed zuul/zuul master: Rework GitHub rate limit handling  https://review.opendev.org/66550520:39
openstackgerritTobias Henkel proposed zuul/zuul master: Switch getPullBySha to using the search api  https://review.opendev.org/66546920:40
openstackgerritTobias Henkel proposed zuul/zuul master: Add central retry handling for github requests  https://review.opendev.org/66550620:40
openstackgerritTobias Henkel proposed zuul/zuul master: Cleanup specialized retry in _process_event  https://review.opendev.org/66550720:40
openstackgerritTobias Henkel proposed zuul/zuul master: Eliminate two github requests per _updateChange  https://review.opendev.org/66551120:40
*** hashar has quit IRC20:40
*** hashar has joined #zuul20:40
fungiaprice just noticed this in her twitter feed: https://twitter.com/gchenuet/status/114071976934947635420:40
fungiguilhermesp: that's really amazing!!!20:41
*** jamesmcarthur has quit IRC20:41
corvusnice :)20:42
*** jamesmcarthur has joined #zuul20:42
fungiguilhermesp: er, sorry, tab completion failed me20:42
tobiashcool :)20:42
fungi>4k pipelines and >40k virtual machines?20:44
fungino idea what size deployments the rest of you have, but that's waaay beyond the size of the one i help run ;)20:45
fungii wonder if they've seen our scheduler memory leak20:45
*** jamesmcarthur has quit IRC21:01
*** mattw4 has quit IRC21:04
*** mattw4 has joined #zuul21:04
*** jamesmcarthur has joined #zuul21:15
*** rfolco has quit IRC21:16
openstackgerritJames E. Blair proposed zuul/zuul master: Pagure driver - https://pagure.io/pagure/  https://review.opendev.org/60440421:18
openstackgerritJames E. Blair proposed zuul/zuul master: Make git repo leak check advisory in TestExecutor  https://review.opendev.org/66576421:18
*** mattw4 has quit IRC21:22
*** mattw4 has joined #zuul21:22
openstackgerritMerged zuul/zuul master: Show retry attempts in UI  https://review.opendev.org/66096021:30
*** hashar has quit IRC21:45
*** sgw has joined #zuul22:07
*** ChanServ has quit IRC22:09
openstackgerritMerged zuul/zuul master: Report job depedencies via MQTT reporter  https://review.opendev.org/66094022:09
*** ChanServ has joined #zuul22:14
*** niven.freenode.net sets mode: +o ChanServ22:14
*** shachar has quit IRC22:17
*** shachar has joined #zuul22:20
*** jamesmcarthur has quit IRC22:22
*** jamesmcarthur has joined #zuul22:22
clarkbfungi ours does 20k jobs ish on 20kish VMs22:34
clarkbso we run more jobs on fewer machines22:35
fungiyeah, they didn't say how many jobs (unless that's what they meant by "pipelines")22:35
clarkbyes its 4k pipeline jobs as I read it22:36
clarkbnot 4k pipelines22:36
fungii took "4k+ pipelines" to mean they had configured >4k different actual pipelines in zuul22:36
fungiso maybe i just assumed a more accurate phrasing than they meant22:36
clarkb its "4k pipelines jobs" in the tweet22:36
fungioh, so it is. i guess it's just a plurality error in their phrasing22:37
fungii read it as "4k+ pipelines, jobs ran on 40k+ vms"22:38
fungiso thought that was 4k pipeline configurations and they had enough quota to run 40k virtual machines concurrently22:39
fungii guess that's the problem with trying to cram information into sms22:40
corvusit's still big whether it's 1/2 opendev or 2x opendev :)22:40
clarkbYa just wanted to point out our number is similarly large?22:41
clarkber :)22:41
corvusalso, tomorrow we should see if we can find someone to tweet about how *small* their zuul is :)22:41
openstackgerritMerged zuul/zuul master: Add more test coverage on using python-path  https://review.opendev.org/65981222:42
corvus(so we don't get typecast as "ci for really big projects")22:43
corvusthe nuance i'd like to convey is, "ci that will grow with your project"22:44
clarkb++22:46
fungii'm tempted to set up my own zuul for a very small project of mine... but it's equally tempting to just move it into opendev22:50
SpamapScorvus:my zuul is pretty medium/small22:53
corvusSpamapS: :)22:59
*** gfhellma has joined #zuul23:03
*** tjgresha has quit IRC23:09
SpamapSBy what measure do we size Zuul's?23:13
SpamapSWe run about 100 jobs per day, and have a pool of 24 AWS EC2 nodes of varying sizes that we spin up on demand.23:14
corvusreally good question -- total projects, total jobs, change rate, build rate, total workers, worker rate are all reasonable things i've seen.23:15
*** gfhellma has quit IRC23:21
*** rlandy|rover has quit IRC23:22
fungisounds like it's time for SpamapS to write a blog post ;)23:29
dmsimardclarkb: 20k jobs or 20k patchsets ? Last time I looked (albeit it was a while ago) there was around ~300k job results per sql reporter23:32
dmsimard(per month)23:33
corvusthe number of jobs launched is greater than the number of jobs reported too23:34
dmsimardBecause of retries ?23:34
corvusmostly speculation23:34

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