Wednesday, 2020-12-02

fungitristanC: if the question's what's wrong with reusing that branch for future 3.19.x point releases, it's that reno isn't designed to fold those back into a single-branch project and would need some significant logical rework to support that release model. on a side note, for a single-branch project i'm not entirely convinced reno and all its black magic are really a benefit to a single-branch project, when00:01
fungicompared with just committing updates to a news file or the like00:01
fungithe problems reno solves (branched release notes, collating multiple notes while avoiding merge conflicts) aren't that much of a challenge in a project like zuul00:03
fungiprobably the main benefit is reno's pbr-like behavior of deriving version numbers from git tags, so we neither need to predict the next version in advance nor need to merge a commit containing version information immediately before tagging00:05
*** wuchunyang has joined #zuul00:38
*** weshay|ruck is now known as weshay|pto00:41
*** wuchunyang has quit IRC00:42
*** wuchunyang has joined #zuul00:58
*** Goneri has quit IRC01:27
tristanCfungi: i see, thanks for the details. I guess my question was about if we should keep a stable branch around until the work on master is completed01:31
tristanCfor example we had to create a special 3.19.1-3 to include https://review.opendev.org/c/zuul/zuul/+/764069 for gerrit-3.x performance issue01:34
*** zenkuro has quit IRC02:14
*** rlandy has quit IRC02:15
*** ajitha has joined #zuul02:32
*** bhavikdbavishi has joined #zuul02:48
*** rfolcOUT has joined #zuul02:50
*** bhavikdbavishi1 has joined #zuul02:51
*** bhavikdbavishi has quit IRC02:53
*** bhavikdbavishi1 is now known as bhavikdbavishi02:53
*** iurygregory|pto has quit IRC03:01
*** rfolcOUT has quit IRC03:05
*** wuchunyang has quit IRC04:05
*** bhavikdbavishi has quit IRC04:22
*** bhavikdbavishi has joined #zuul04:22
*** ikhan has quit IRC04:38
*** vishalmanchanda has joined #zuul04:38
*** evrardjp has quit IRC05:33
*** evrardjp has joined #zuul05:33
*** wuchunyang has joined #zuul05:35
*** zbr has quit IRC06:13
*** zbr has joined #zuul06:14
*** y2kenny has quit IRC06:14
*** hamalq has quit IRC06:17
*** hamalq has joined #zuul06:18
*** jfoufas1 has joined #zuul06:25
*** bhavikdbavishi1 has joined #zuul06:27
*** bhavikdbavishi has quit IRC06:29
*** bhavikdbavishi1 is now known as bhavikdbavishi06:29
*** saneax has joined #zuul06:52
*** bhavikdbavishi has quit IRC06:53
*** mach1na has joined #zuul07:05
*** mach1na has quit IRC07:31
*** hashar has joined #zuul08:00
*** mach1na has joined #zuul08:01
*** mach1na has quit IRC08:04
*** hashar has quit IRC08:04
*** mach1na has joined #zuul08:04
*** hashar has joined #zuul08:04
*** jcapitao has joined #zuul08:12
*** rpittau|afk is now known as rpittau08:28
*** rishabhhpe has joined #zuul08:35
*** zbr has quit IRC08:44
*** zbr has joined #zuul08:45
*** zbr has quit IRC08:47
*** zbr has joined #zuul08:47
rishabhhpeHi .. did anyone facing issue with posting results of CI to upstream ? my gerrit is taking the events starting the job .. but after completion of job it is not able to post the result to community08:49
*** zbr has quit IRC08:49
*** zbr has joined #zuul08:49
openstackgerritFelix Edel proposed zuul/zuul master: WIP Switch to ZooKeeper backed result event queues  https://review.opendev.org/c/zuul/zuul/+/76434408:50
*** zbr has quit IRC08:52
*** zbr has joined #zuul08:52
*** jpena|off is now known as jpena08:57
*** rishabhhpe has quit IRC09:03
*** rishabhhpe has joined #zuul09:04
*** tosky has joined #zuul09:05
*** nils has joined #zuul09:16
*** sshnaidm is now known as sshnaidm|ruck09:34
*** bhavikdbavishi has joined #zuul09:54
*** sshnaidm|ruck has quit IRC10:01
*** sshnaidm has joined #zuul10:01
*** bhavikdbavishi has quit IRC10:07
*** wuchunyang has quit IRC10:07
*** nils has quit IRC10:30
*** hashar is now known as hasharLunch10:32
*** nils has joined #zuul10:35
*** wuchunyang has joined #zuul10:41
*** wuchunyang has quit IRC10:42
*** msuszko4 has joined #zuul10:53
*** msuszko4 is now known as msuszko10:54
*** sshnaidm is now known as sshnaidm|afk10:55
msuszkoDo you have recommendations on sampling profiler to watch zuul-scheduler on production?10:56
openstackgerritMatthieu Huin proposed zuul/zuul-client master: encrypt: fix bad indentation  https://review.opendev.org/c/zuul/zuul-client/+/76511211:01
msuszkoI'm observing Zuul pausing for some time (3-15 minutes) when there is > 80 jobs running. During this pause changes with success on all jobs are not finished, queued jobs are not started.11:01
msuszkoAnd I'm observing scheduler trigger queue steadily rising from few to sometimes over thousand events during this period11:03
avassrishabhhpe: maybe the scheduler doesn't have access or labels aren't configured correctly, does the logs say anything?11:04
msuszkothen trigger event queue suddenly drops, jobs are started, changes finished, and another cycle follows11:05
avassmsuszko: 3-15minutes sounds like a lot but I know bmw has been working on making reporting asynchronous https://review.opendev.org/c/zuul/zuul/+/69125311:06
avassmsuszko: looking at the commit message it sounds like it could stall the system if you have long merge times11:07
msuszkoavass: thanks, I'll take a look11:09
avasstobiash: probably has more information when he comes online :)11:11
msuszkoI'm already running with his change-queues changes integrated :-)11:13
*** rishabhhpe has quit IRC11:14
*** rishabhhpe has joined #zuul11:14
*** bhavikdbavishi has joined #zuul11:14
*** bhavikdbavishi1 has joined #zuul11:19
*** bhavikdbavishi has quit IRC11:21
*** bhavikdbavishi1 is now known as bhavikdbavishi11:21
*** rishabhhpe has quit IRC11:26
*** rishabhhpe has joined #zuul11:27
*** sshnaidm|afk is now known as sshnaidm|ruck11:39
tobiashmsuszko: we're running with async reporting since ~3 months in production11:41
tobiashmsuszko: which reporters are you using?11:41
tobiashwe observed different bottlenecks there in the past11:42
tobiashe.g. the sql db can be overloaded without https://review.opendev.org/c/zuul/zuul/+/758579 and many jobs with artifacts which can slow down sql reporting11:43
*** zenkuro has joined #zuul11:44
tobiashor if you report to gerrit it is crucual to have proper git gc settings there, otherwise this can cause very long pauses in reporting to gerrit on heavily used repos11:44
tobiashand not to forget, tenant reconfigurations (done after every merge of a zuul.yaml change) can also stall zuul (~3min for our largest tenant)11:46
tobiashrishabhhpe: you mean the opendev gerrit?11:47
openstackgerritSorin Sbârnea proposed zuul/zuul-jobs master: Enable ensure ansible to install local collection  https://review.opendev.org/c/zuul/zuul-jobs/+/76512511:50
msuszkotobiash: I have gerrit and postgres. PostgreSQL is an instance just for Zuul, and in looks unused on monitoring.11:52
tobiashmsuszko: you could add this to see in the logs if there are problems with reporting delays: https://review.opendev.org/c/zuul/zuul/+/75244311:54
msuszkochange thoughput is fairly low, less than 3 patchsets per minute11:55
msuszkotobiash: oh, I'd definitely add this change with reporting11:57
tobiashmsuszko: do you see larger jumps in the log timestamps?11:57
tobiashthat could possibly also hint towards a problem already without that change11:58
*** holser has joined #zuul11:59
rishabhhpetobiash: yes for openstack thirdparty CI gerrit i am talking11:59
msuszkoJuest need to wait till the evening, I have one particular repo with over 2000 branches and few million objects which makes zuul-scheduler more than 15 minutes to start (using 14 merger instances)11:59
tobiashrishabhhpe: since the gerrit update you need to switch to basic auch if you've not done that yet: https://zuul-ci.org/docs/zuul/reference/drivers/gerrit.html#attr-%3Cgerrit%20connection%3E.auth_type11:59
tobiash2000 branches on a gerrit repo? impressive :D12:00
msuszkotobiash: yes, there are certain types of log entries missing during pause, but events from gerrit are appearing for instance12:01
*** holser is now known as holser212:01
msuszko2000 after automated cleanup, I started with over 600012:01
tobiashyou want to filter out the events from gerrit since they're in a different thread12:01
*** holser2 is now known as holser12:01
msuszkothis is basically 400 man doing some kind of gitflow inspired freestyle on gerrit12:03
rishabhhpewell i tried with auth_type as basic and my zuul version is 3.1812:03
rishabhhpebut still the error persists12:03
*** iurygregory has joined #zuul12:03
tobiashrishabhhpe: can you post the error?12:04
*** mach1na has quit IRC12:05
openstackgerritSorin Sbârnea proposed zuul/zuul-jobs master: Enable ensure ansible to install local collection  https://review.opendev.org/c/zuul/zuul-jobs/+/76512512:06
*** jcapitao is now known as jcapitao_lunch12:06
rishabhhpetobiash: log is pasted here - https://paste.ubuntu.com/p/b6kfSYdVFY/12:06
*** rfolcOUT has joined #zuul12:06
*** rfolcOUT has quit IRC12:07
*** rfolco has joined #zuul12:07
tobiashrishabhhpe: so authentication failed. I guess this is a topic for #opendev then12:07
tobiashmaybe there is a problem with the account, but I'm no opendev code so can't help in that regard12:08
tobiashs/code/core/12:08
openstackgerritSorin Sbârnea proposed zuul/zuul-jobs master: Enable ensure ansible to install local collection  https://review.opendev.org/c/zuul/zuul-jobs/+/76512512:09
msuszkotenent reconfiguration is slow, but it is not common, and far quicker than pauses i'm investigating: Tenant reconfiguration complete (duration: 162.127 seconds)12:13
openstackgerritTobias Henkel proposed zuul/zuul master: Add logging and monitoring of reporting timings  https://review.opendev.org/c/zuul/zuul/+/75244312:16
rishabhhpetobiash: do u know how to pass proxy if we are behind firewall while changing the authtype to basic in zuul.conf ?12:21
*** jfoufas1 has quit IRC12:21
*** zenkuro has quit IRC12:21
tobiashrishabhhpe: I don't use a proxy towards gerrit, but zuul uses the requests library which should take care of this automatically if you set the http proxy env vars12:22
*** zenkuro has joined #zuul12:22
msuszkotobiash: Do you run on production Zuul with relation chain up to https://review.opendev.org/c/zuul/zuul/+/691253/33 applied?12:23
tobiashmsuszko: yes12:24
rishabhhpetobiash: or anybody out there can guide me on this a little because normal environmental proxy varibale are already imported but i am seeing the issue related to that12:25
msuszkoPerfect. I already have branche queues applied, which is zuul-enabler for this crazy branch repo I mentioned12:25
msuszkos/branche/branch/12:25
tobiashrishabhhpe: zuul has no specific way to enforce proxy usage other than http_proxy and https_proxy vars (maybe the https_proxy var is missing?)12:28
avassmsuszko: ooh git inspired freestyle is our speciality12:31
*** jpena is now known as jpena|lunch12:36
*** ikhan has joined #zuul12:50
openstackgerritJonas Sticha proposed zuul/nodepool master: WIP: aws: add support for uploading diskimages  https://review.opendev.org/c/zuul/nodepool/+/73521712:50
*** Goneri has joined #zuul12:55
*** rishabhhpe has quit IRC12:55
*** mach1na has joined #zuul12:56
*** jfoufas1 has joined #zuul13:00
*** hamalq has quit IRC13:01
*** jcapitao_lunch is now known as jcapitao13:03
*** hamalq has joined #zuul13:05
tobiashavass: did you see tristanC's comment on https://review.opendev.org/c/zuul/zuul/+/764584?13:06
*** rlandy has joined #zuul13:18
*** ikhan has quit IRC13:32
*** ikhan has joined #zuul13:35
avasstobiash: nope but I'll take a look at doing that instead13:36
*** bhavikdbavishi has quit IRC13:38
*** hasharLunch is now known as hashar13:43
openstackgerritAlbin Vass proposed zuul/zuul master: Throw a warning if the executors ssh-key can't be loaded  https://review.opendev.org/c/zuul/zuul/+/76458413:43
avasstobiash: how about logging a warning if it doesn't exist. That should make it a bit easier to debug13:43
*** manoj_kumar_kata has joined #zuul13:48
manoj_kumar_kataHello13:48
manoj_kumar_katawith the gerrit upgrade, we fixed zuul issue internally to launch the jobs.13:49
manoj_kumar_kataNow after execution, zuul is failing to report the jobs to reviews.13:49
manoj_kumar_katazuul.reporter.gerrit.Reporter is failing with exception :13:49
manoj_kumar_kata2020-12-02 12:13:44,731 ERROR zuul.source.Gerrit: Exception looking for ref refs/heads/master13:49
manoj_kumar_kataTraceback (most recent call last):13:49
manoj_kumar_kata  File "/usr/local/lib/python2.7/dist-packages/zuul/source/gerrit.py", line 49, in getRefSha13:49
manoj_kumar_kata    refs = self.connection.getInfoRefs(project)13:49
manoj_kumar_kata  File "/usr/local/lib/python2.7/dist-packages/zuul/connection/gerrit.py", line 399, in getInfoRefs13:49
manoj_kumar_kata    raise Exception("Gerrit repository does not support "13:49
manoj_kumar_kataException: Gerrit repository does not support git-upload-pack13:49
manoj_kumar_kata2020-12-02 12:13:44,873 ERROR zuul.IndependentPipelineManager: Exception while reporting:13:49
manoj_kumar_kataTraceback (most recent call last):13:49
manoj_kumar_kata  File "/usr/local/lib/python2.7/dist-packages/zuul/scheduler.py", line 1764, in _reportItem13:49
manoj_kumar_kata    ret = self.sendReport(actions, self.pipeline.source, item)13:49
manoj_kumar_kata  File "/usr/local/lib/python2.7/dist-packages/zuul/scheduler.py", line 1291, in sendReport13:49
manoj_kumar_kata    ret = reporter.report(source, self.pipeline, item)13:49
manoj_kumar_kata  File "/usr/local/lib/python2.7/dist-packages/zuul/reporter/gerrit.py", line 39, in report13:49
manoj_kumar_kata    message, self.reporter_config)13:49
manoj_kumar_kata  File "/usr/local/lib/python2.7/dist-packages/zuul/connection/gerrit.py", line 279, in review13:49
manoj_kumar_kata    out, err = self._ssh(cmd)13:49
manoj_kumar_kata  File "/usr/local/lib/python2.7/dist-packages/zuul/connection/gerrit.py", line 384, in _ssh13:49
manoj_kumar_kata    raise Exception("Gerrit error executing %s" % command)13:49
manoj_kumar_kataException: Gerrit error executing gerrit review --project openstack/cinder --message "Build13:49
manoj_kumar_katawould appreciate some help here.13:49
*** jpena|lunch is now known as jpena13:51
avassmanoj_kumar_kata: hi! please use a paste service like http://paste.openstack.org/ to post logs in the future13:53
*** sugaar has quit IRC14:02
manoj_kumar_kataavass: sure , will do it next time :)14:08
zbrout of curiosity, does zuul really need these huge UUIDS? can't we just use abridged versions like git at least for urls?14:20
fungizbr: that might be doable but would need a different kind of indexing in the database to efficiently perform substring lookups, i think? someone with a better grasp of mysql would need to confirm that though14:22
zbri suspect that there are concerns about clashing, but lets be realistic...even 6 chars should provide more than enough entropy for practical reasons.14:22
zbrshorter urls could improve display in several places, like the "build succeeded message".14:23
zbrhttps://sbarnea.com/ss/Screen-Shot-2020-12-02-14-23-59.75.png14:24
zbrnot sure why it is wrapped like this bug i suspect is a feature of wrapping long text to ~80 columns to make it easier to read.14:24
zbrin our particular case it works against its original intention14:24
corvuszbr: i don't think we should change zuul to accomodate that display issue in gerrit; instead we should update gerrit not to display urls as hyperlink titles14:26
zbrcorvus: that was one example, sharing links to builds, or even the links to logs are very long. i think fixing one does not rule out the other.14:27
zbri am sure that the short-uuid in zuul is not very easy to fix14:27
zbranother think that i find bit annoying is searching for a specific build by UI, many times i endup searching for it on the wrong tenant. I wonder if we could make it look on other tenants.14:29
corvuszbr: tenants are intentionally completely separate14:30
corvusnot only for scoping but for security/privacy reasons14:30
zbrstill, the web interface knows about all of them, so the react side could do some magic to help the user.14:31
fungiit's even set up so that deployments can require different authentication for accessing information about different tenants14:31
corvuszbr: my point is that's counter to the design so we aren't likely to do that14:32
corvuszbr: (opendev's deployment of the web ui is not the only way the system can be deployed; as fungi says, the web uis can be completely separate for tenants)14:32
fungiand the authentication may be done as an external mechanism based on url path, which react isn't going to even know exists, so could return results to which the user has no access thereby leaking some information14:32
avassbuild/buildset could be b/bs to make it shorter. like: /t/opendev/b/<uuid>14:34
zbrafaik, react is client only, which means it cannot expose stuff that user does not have access to, only a backend can do this kind of mistake.14:34
avassbut I can't say I've thought the url was too long14:34
corvuszbr: the web ui should also not mislead users into thinking that information is shared between tenants.  it's good that the ui reflects the actual system.14:37
avassalso it don't think I wanted to make the url build uuid shorten unless it's shorter everywhere else, I use that to take me to the correct build page pretty often14:38
zbrok, lets forget about combining results from multiple tenants in the UI, at least for now.14:39
avassthough I have to agree a multi-tenant dashboard would be nice to have14:41
*** bhavikdbavishi has joined #zuul14:45
*** bhavikdbavishi1 has joined #zuul14:48
*** bhavikdbavishi has quit IRC14:50
*** bhavikdbavishi1 is now known as bhavikdbavishi14:50
*** sanjayu_ has joined #zuul14:50
fungii also use it to get to other things, like build artifacts14:51
fungiyesterday i was testing a build of a container image for gerrit, and it was convenient to be able to just construct the url to it knowing the build id, without needing to go look up the artifact's url14:52
*** saneax has quit IRC14:52
fungifor reference, our test builds end up looking like insecure-ci-registry.opendev.org:5000/opendevorg/gerrit:5d927e040a1d4ffeb8baf17cad2acc16_3.214:54
fungiso just have to update the bit between the : and the _ with the build uuiid to get the new one i want to try for gerrit 3.214:55
fungiwhich means seeing the build result url posted on the change, i was able to set the correct image without ever needing to actually visit the zuul webui14:56
*** mach1na has quit IRC14:57
*** bhavikdbavishi has quit IRC14:59
*** mach1na has joined #zuul15:00
*** sugaar has joined #zuul15:03
*** hashar is now known as hasharAway15:05
*** bhavikdbavishi has joined #zuul15:17
*** bhavikdbavishi1 has joined #zuul15:20
*** bhavikdbavishi has quit IRC15:22
*** bhavikdbavishi1 is now known as bhavikdbavishi15:22
*** jfoufas1 has quit IRC15:22
corvustobiash: is https://review.opendev.org/752664 really required for mandatory sql?  the existing code was very deliberately written and well tested; i'd like to have a thorough conversation about changing it.15:27
corvusbolg: ^15:27
corvus(but i'd like to have that thorough conversation after v4 if possible)15:28
*** jfoufas1 has joined #zuul15:32
msuszkoThere is mqtt reporter. Does anyone have kafka reporter by any change?15:53
msuszkos/change/chance/15:53
pabelangermorning! IIRC, there was talk of zuul 4.0 soon, is that still the case?  I _think_ there was talk of this or next week?15:56
clarkbpabelanger: corvus was working on release notes stuff yesterday I think in preparation for that15:58
clarkbI'm not sure what else needs to be done though15:58
pabelangerokay, cool!15:59
pabelangerwe still need to enable SSL on zookeeper, so I guess now is the time to prepare15:59
corvusclarkb: that and we need the require-sql change and require-zk15:59
corvuspabelanger: yes!15:59
pabelangerthanks16:00
pabelangercould some one point me to Felix Edel?  I had a question about https://review.opendev.org/c/zuul/zuul/+/70913516:00
pabelangerspecifically, how aborts are setup in github16:00
corvuspabelanger: if you have zk+ssl enabled and reachable from all zuul components, along with a sql connection (which you can do now because it's optional), then upgrade should be painless16:00
corvuspabelanger: meet felixedel16:00
pabelangercorvus: will confirm16:01
pabelangerand thanks16:01
pabelangerfelixedel: can you point me to more info about custom aborts16:01
corvuspabelanger: i got the idea that it was automatic16:01
*** savihou has joined #zuul16:02
corvuspabelanger: ie, line 2053 in that change causes the abort action to be present on github's ui16:02
corvuspabelanger: so you'll get that automatically if you run master or the upcoming v4 release16:03
corvusat least, that's my understanding; haven't used it myself16:03
pabelangerah, I see. Zuul creates the abort button16:04
pabelangerokay, that explains it16:04
pabelangerdoes that mean anyone can click it, or only the PR owner?16:05
tobiashcorvus: no, that is not required for mandatory sql, no idea why it's in that order (this change was an attempt to improve reporting performance of the sql reporter)16:05
corvustobiash: cool, so maybe when you/bolg have a chance to refresh that, you could swap the order?16:05
tobiashon it16:05
fungimsuszko: i haven't seen any reporter implementation for apache kafka proposed, though it probably wouldn't be hard to add one based on the mqtt reporter if you wanted to try16:11
openstackgerritTobias Henkel proposed zuul/zuul master: Required SQL reporters  https://review.opendev.org/c/zuul/zuul/+/63047216:11
fungimsuszko: just be aware that runs as a reporter, so only emits events based on completion of all builds for a buildset, it's not a granular event stream16:12
tobiashpabelanger: I guess anyone with write access to the repo can click it16:13
pabelangertobiash: okay cool that is what I was hoping, write access was the acl16:13
pabelangertobiash: with that in mind, I also wonder if a new action for say 'auto-hold' could be setup via github actions16:13
tobiashpabelanger: I guess we could add any arbitrary type of action there16:15
tobiashclicking on the button would result in an according check_run event with the info we supply to the action16:15
pabelangerk, I'd have to look more into it. I think it would be neat, to expose some sort of 'auto-hold', which the check_run event exposed the person who clicked it, then injected their ssh keys, from github.com into the node.16:16
pabelangerFor that, I guess we'd need to some how map the check_run event, into running playbooks16:17
tobiashthat should be configurable though, I don't want an auto hold button where everyone of my users can click on ;)16:17
tobiashhm, that would be difficult, each event is change related16:17
msuszkofungi: Writing kafka reporter is indeed easy, far easier than tests for it.16:18
tobiashso you could only add autoholds for changes16:18
pabelangertobiash: yah, that is right16:18
tobiashor you add an autohold button for each job :D16:18
pabelangerotherwise, it would be using SpamapS idea of adding your ssh key into the PR16:18
*** jfoufas1 has quit IRC16:19
pabelangerwith some sort of 2 hour busy-loop16:19
tobiashthat's our default way for on node debugging16:19
pabelangerfeels so dirty16:19
fungimsuszko: an alternative might also be an mqtt broker acting as a kafka proxy, so publish zuul reports into it and then convert them on the fly to kafka events, as a stand-alone daemon/service16:19
SpamapSpabelanger: I always hoped we might build in something to make it more web-based. ;)16:19
msuszkofungi: I settled with https://github.com/nodefluent/mqtt-to-kafka-bridge16:20
fungimsuszko: aha, so it already exists. i thought it might16:20
corvusSpamapS, pabelanger, tobiash: i think mhu has WIP on that (using zuul-web authn)16:20
corvusso the button would be in zuul's ui, not github's16:20
tobiashwhich would be the better more generic solution16:21
msuszkoi was asking, because last time I've made upload-logs-s3 role just to find it in zuul-jobs few weeks later16:22
pabelangercorvus: k, I haven't looked into zuul webui actions yet. Need to better understand how auth for it works16:22
corvuspabelanger: it's incomplete; i think the backend api is there but not the frontend yet16:23
pabelangerdo you know if it is expect to work with SSO, say from github?16:24
pabelangerperhaps I should sync with mhu more16:24
mhuOHAI16:24
avassnow might be a good time to tell everyone that upload-logs-s3 is broken: https://review.opendev.org/c/zuul/zuul-jobs/+/76447816:25
avassmsuszko: ^16:25
*** mach1na has quit IRC16:26
avassI think I made that fix in only upload-logs-s3 before the roles were merged so it got left out16:26
corvusavass: any idea why that [apparently] works as written for the others?16:26
avassI guess they specify a read length16:26
mhupabelanger, I wanted to revisit the scoped admin ui after the migration to patternfly was done, then I got into zuul-client16:26
pabelangermhu: so, zuul web auth, can you use github as source for user credentials?16:27
corvusavass: that gets passed to a boto class which uses it?16:27
avasscorvus: yeah, it crashes when boto calls read()16:27
corvusavass: makes sense; clarkb, tobiash: can one of you look at 764478 ?16:27
clarkbI can take a look16:28
corvusclarkb: (and parent)16:28
avassalso I'm using that fix at https://zuul.vassast.org so I know it works :)16:28
clarkbavass: do you know why the gzip thing broke? that is vendored code only minimally modified to handle python2 and python3 and its worked for us as far as I can tell?16:29
corvusthis is the second personal/private zuul instance i've seen; i feel like we may be starting to round the curve on "zuul is hard to install/run" :)16:29
avasswell it's easy when you know how to do it :)16:29
tobiashavass: is that your personal home-zuul?16:30
avassclarkb: I guess the other role that uses it calls read() with and argument and doesn't read until EOF16:30
avasstobiash: yeah16:30
tobiashawesome :)16:30
avassrunning in k8s in digitalocean16:30
clarkbavass: well the current api there requires you always pass an argument?16:30
avassyep16:30
clarkb(I mean I don't think the chagne is necessarily wrong, I just don't see how it could've worked before without passing in -1 already)16:31
msuszkocorvus: hardly anything to curve, docker-compose is a breeze16:31
mhupabelanger, not sure if github uses OIDC or old oauth16:31
avassclarkb: I think I fixed it when I copy pasted it to upload-logs-s3 but not in swift :)16:31
mhupabelanger, there was a doc I wrote for google auth: https://review.opendev.org/c/zuul/zuul/+/734082/14/doc/source/howtos/openid-with-google.rst16:31
tobiashoh and I broke it during consolidation?16:31
avassbut then it broke when it got merged into upload-logs-base and the tests didn't run since the file: attribute wasn't updated16:31
avassyeah16:32
tobiashsorry16:32
mhupabelanger, worst case scenario, you can configure zuul with keycloak, and have keycloak authenticate users on github16:32
avassnp we didn't start using it anyway16:32
avassbut are gonna do that soonish probably16:32
mhupabelanger, https://review.opendev.org/c/zuul/zuul/+/734082/14/doc/source/howtos/openid-with-keycloak.rst16:32
avasscorvus: also, I'm gonna push the helm charts we use at volvo to zuul-helm whenever I find time. It automates zookeeper tls, whitelabeling, separates config per components so only relevant components gets restarted16:34
avassuuh and uses a prestop hook to gracefully shut down executors for roling updates16:34
avassprobably something else :)16:34
pabelangermhu: okay, thanks. Are you running the web-ui bits in rdo zuul? or some other sf install16:35
pabelangerI'd love to look at it16:35
mhucorvus, tobiash do you think you'd have time in the coming weeks to review the scoped admin web UI changes if I refresh them?16:35
clarkbavass: looking at the code in that file all the read()s are specifying a size from what I see16:35
msuszkoavass: do you have gracefull shutdown of executors?16:35
clarkbavass: do you know where the short read call was being made?16:35
mhupabelanger, not yet, besides these UI patches probably need a refresh - I can set up a demo some time soon if you'd like16:36
tobiashmhu: I think so16:36
mhuI use keycloak as the SSO16:36
pabelangermhu: yah, demo would be cool16:37
clarkbI'm wary of approving that change since I don't understand why it should be necessary. At the same time I'm reasonably convinced it would be ok since we pass a length everywhere else? corvus tobiash I'll defer to you on that I think16:37
avassclarkb: botocore or boto3 somewhere16:38
mhupabelanger, what's your TZ these days?16:38
msuszkospeaking of helm, current charts are restarting scheduler on tenant config change16:38
avassmsuszko: there's `zuul-executor graceful` but I think it's just a stub on 3.1916:38
avassmsuszko: oh we set the updatestrategy to OnDelete for the scheduler16:38
tobiashclarkb: that's the base class: https://docs.python.org/3/library/io.html#io.RawIOBase.read16:39
pabelangermhu: UTC-516:39
tobiashdocs say that size defaults to -1 so the change looks correct to me16:39
msuszkoI'm using curl -sSn https://gerrit/a/plugins/gitiles/zuul-setup/+archive/refs/heads/master/tenants.tar.gz | tar xzf - -O as tenant_config_script16:39
tobiashalthough we may even rename length to size to accomodate for the interface16:40
avassclarkb, tobiash: yeah the current GZip implementation is incompatible to the superclass16:40
clarkbtobiash: right, the problem is more that when we call GZIPCompressedStream.read() previously length was always required. So we should never get a short read as you were forced to apss that argument16:40
avasstobiash: true16:40
fungicould that vary by python version?16:40
clarkboh I see what the issue is now, compat with parent interface16:40
tobiashfungi: 3.5 has the same interface16:41
msuszkoavass: great!16:41
tobiashyes16:41
clarkbhttps://docs.python.org/2.7/library/io.html#io.RawIOBase.read 2.7 calls it n16:42
clarkbI think we go for 3 compat here and if 2.7 is a problem due to named args we firgure that out when it becomse a problem?16:42
tobiashat least the default is the same since 2.716:43
clarkbyup so only a problem if using a named arg16:43
tobiashso do we want to rename that arg as well or just set the default?16:43
avassrenaming it probably avoids a future headache :)16:44
clarkbIf the goal is parent interface compat we should rename the arg imo16:44
tobiashprobably :D16:44
clarkband maybe add a note about it to the vendored code comment16:44
clarkbso that we can track our delta from the upstream more easily16:44
openstackgerritMerged zuul/zuul-jobs master: upload-logs-s3: fix test-jobs files: attribute  https://review.opendev.org/c/zuul/zuul-jobs/+/76447616:45
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: GZIPCompressedStream default read length to -1  https://review.opendev.org/c/zuul/zuul-jobs/+/76447816:52
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: GZIPCompressedStream default read size to -1  https://review.opendev.org/c/zuul/zuul-jobs/+/76447816:53
avasshow about that ^16:53
avasstobiash: too quick :)16:54
tobiashyeah...16:54
clarkbthats great thank you. I +2'd but didn't approve in case corvus wants to rereview16:54
clarkbbut if it isn't approved in a half an hour I think we can just approve it?16:55
tobiash++16:55
avassalso s3 doesn't redirect to index.html so only the cors logs work. but if you report the log_url to point at the index.html logs the cors logs breaks..16:59
avassnot sure if there's a good way to fix that16:59
avassyou can see it here: https://zuul.vassast.org/build/2ec604b42feb4f769cb8aebe8b61e007/logs17:00
*** bhavikdbavishi has quit IRC17:01
*** rpittau is now known as rpittau|afk17:04
*** bhavikdbavishi has joined #zuul17:07
corvusavass: yeah, gcs has the same problem; i think we need some flag to link to '/index.html' in the web page17:09
*** manoj_kumar_kata has quit IRC17:14
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: ensure-podman: Use official podman repos for ubuntu  https://review.opendev.org/c/zuul/zuul-jobs/+/76517717:18
*** manoj_kumar_kata has joined #zuul17:27
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: ensure-podman: Use official podman repos for ubuntu  https://review.opendev.org/c/zuul/zuul-jobs/+/76517717:38
*** sshnaidm|ruck is now known as sshnaidm|afk17:47
avasscorvus: yep17:47
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: ensure-podman: Use official podman repos for ubuntu  https://review.opendev.org/c/zuul/zuul-jobs/+/76517717:48
*** polls45 has joined #zuul17:49
*** jcapitao has quit IRC17:54
*** jpena is now known as jpena|off18:02
*** wuchunyang has joined #zuul18:02
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: ensure-podman: Use official podman repos for ubuntu  https://review.opendev.org/c/zuul/zuul-jobs/+/76517718:04
*** wuchunyang has quit IRC18:07
*** bhavikdbavishi has quit IRC18:08
*** hasharAway is now known as hashar18:15
*** nils has quit IRC18:18
avasscorvus: if you have a second to approve https://review.opendev.org/c/zuul/zuul-jobs/+/76447818:21
msuszkowhile profiling zuul-scheduler found out it spent 30% time in chardet18:23
msuszkoi guess it is requests calling gerrit18:23
*** manoj_kumar_kata has quit IRC18:39
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: ensure-podman: Use official podman repos for ubuntu  https://review.opendev.org/c/zuul/zuul-jobs/+/76517718:43
mnasertalking out loud -- i'm trying to look at replacing terraform cloud by zuul, however, a use case that i'm finding a bit harder is the 'retry' story18:48
mnaserinside terraform clouds ui, you can go back and 'queue' a run if it failed18:48
mnaseri cant think of any simple way of doing that within zuul other than making an empty change to retrigger it18:49
openstackgerritMerged zuul/zuul-jobs master: GZIPCompressedStream default read size to -1  https://review.opendev.org/c/zuul/zuul-jobs/+/76447818:49
corvusmnaser: we should be able to handle that with a direct-enqueue via api; combined with mhu's authenticated ui work, could be a button on a the build result page.18:49
mnasercorvus: has the auth'd ui work itself landed (i.e. would the work needed essentially be enqueue on the build result page or more?)18:51
corvusmnaser: no; only the backend api part18:51
pabelangermnaser: you are using github?18:52
mnaseri think something that might be tricky in my case is uh, auth for api per tenant18:52
mnaserpabelanger: yes18:52
pabelangerwon't the re-run button in check runs work for this?18:52
corvusmnaser: api auth is per-tenant18:52
mnaserpabelanger: hmm, maybe?  i wonder if you can ask to rerun the post jobs in this case18:53
mnasercorvus: ok, so that's really interesting then.. i should play with that code a bit more18:53
corvusmnaser: the cli should support it; so you should be able to get an auth token and use the cli to demo18:53
corvusmnaser: zuul-client18:54
mnaserhrm, got it18:54
mnaseri might write up something if i end up coming up with a full terraform pipeline for this18:55
pabelangerwhat we came up with was 1hr periodic pipeline, if we needed something to re-run18:56
pabelangerthen, re-enqueue with CLI if we need faster18:56
mnasergot it18:57
corvusthat's pretty much the opendev strategy too18:58
*** vishalmanchanda has quit IRC18:58
fungialmost exactly, in fact18:58
mnaserto be honest, the only concern i have a little bit right now is running this on our existing shared zuul or dedicating one for this use case18:58
mnaserone side says "dogfood" the other says "risk-mitigating" :)18:59
fungithe biggest logistical challenge we face is triggering deployments by changes landing in related repositories18:59
fungiso we still rely on hourly deploys for that sort of stuff too18:59
*** polls45 has quit IRC19:00
mnaserhmm19:01
mnaseri wonder if i can have multiple zuuls talking to the same nodepool instance19:01
mnaser:p19:01
corvusmnaser: theoretically yes; i don't think it's well tested19:02
corvus(it definitely was a design intent)19:03
mnaseri guess i could technically run a seperate zuul that uses the same nodepool19:04
*** reiterative has quit IRC19:06
*** reiterative has joined #zuul19:07
corvusfungi, clarkb, pabelanger: stack at https://review.opendev.org/765023 is ready for review; that's the first blocker for v419:16
*** sugaar has quit IRC19:17
*** manoj_kumar_kata has joined #zuul19:22
*** iurygregory has quit IRC19:29
*** msuszko has quit IRC19:53
fungicorvus: thanks for the reminder! looking at it now19:54
*** reiterative has quit IRC19:57
*** reiterative has joined #zuul19:57
fungiunrelated, but has anyone started looking into the nodepool-zuul-functional build timeouts? i haven't been following closely if so19:58
*** hashar has quit IRC20:23
openstackgerritMatthieu Huin proposed zuul/zuul-client master: API, CLI: Allow use of tenant-scoped API URLs  https://review.opendev.org/c/zuul/zuul-client/+/76520320:33
openstackgerritMerged zuul/zuul master: Temporarily remove pending release notes in order to merge 3.19.1  https://review.opendev.org/c/zuul/zuul/+/76502321:00
openstackgerritMerged zuul/zuul master: Merge tag '3.19.1'  https://review.opendev.org/c/zuul/zuul/+/76502421:02
*** rfolco has quit IRC21:20
*** iurygregory has joined #zuul21:28
openstackgerritMerged zuul/zuul master: Re-add pending release notes  https://review.opendev.org/c/zuul/zuul/+/76502522:09
*** ajitha has quit IRC22:35
fungicorvus: ^ okay those blockers are in, thanks for working through the last of that!23:03
* fungi missed that merging by nearly an hour23:03
*** rlandy has quit IRC23:23
*** holser_ has joined #zuul23:48
*** Goneri has quit IRC23:50
*** holser has quit IRC23:51
*** sanjayu_ has quit IRC23:52

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