Friday, 2020-06-19

*** rlandy|ruck2 has quit IRC00:01
corvusmordred: oh, we use buildx for nodepool -- looks like we have more cleanup to do: https://zuul.opendev.org/t/zuul/build/a370356fb916463ebdac72b0698a70ed00:05
*** rfolco has quit IRC00:28
*** wuchunyang has joined #zuul01:01
*** Goneri has quit IRC01:07
openstackgerritGuillaume Chauvel proposed zuul/zuul master: [DNM] TEST zuul_stream+callback test using multinode jobs  https://review.opendev.org/73548301:09
openstackgerritGuillaume Chauvel proposed zuul/zuul master: Add 'uuid' to 'src_dir' in order to allow parallel jobs for a static node  https://review.opendev.org/73598101:09
openstackgerritGuillaume Chauvel proposed zuul/zuul master: [DNM] TEST 'uuid' in 'src_dir': 1 node, 4 parallel jobs  https://review.opendev.org/73557601:09
*** wuchunyang has quit IRC01:20
*** wuchunyang has joined #zuul01:43
*** wuchunyang has quit IRC01:47
*** swest has quit IRC01:49
*** jamesmcarthur has joined #zuul02:02
*** swest has joined #zuul02:04
*** jamesmcarthur has quit IRC02:08
*** jamesmcarthur has joined #zuul02:08
*** jamesmcarthur has quit IRC02:15
*** jamesmcarthur has joined #zuul02:24
*** jamesmcarthur has quit IRC02:37
*** jamesmcarthur has joined #zuul02:38
*** wuchunyang has joined #zuul02:38
*** sgw has quit IRC02:42
*** jamesmcarthur has quit IRC02:43
*** bhavikdbavishi has joined #zuul02:44
*** sgw has joined #zuul03:00
*** wuchunyang has quit IRC03:04
*** bhavikdbavishi1 has joined #zuul03:05
*** bhavikdbavishi has quit IRC03:07
*** bhavikdbavishi1 is now known as bhavikdbavishi03:07
*** jamesmcarthur has joined #zuul03:19
*** jamesmcarthur has quit IRC03:22
*** jamesmcarthur has joined #zuul03:23
*** harrymichal has quit IRC03:35
*** wuchunyang has joined #zuul03:37
*** jamesmcarthur has quit IRC03:58
*** wuchunyang has quit IRC03:58
*** jamesmcarthur has joined #zuul03:58
*** wuchunyang has joined #zuul04:01
*** jamesmcarthur has quit IRC04:04
*** ysandeep|away is now known as ysandeep04:05
*** wuchunyang has quit IRC04:06
*** sgw has quit IRC04:08
*** sgw has joined #zuul04:09
*** sgw1 has quit IRC04:09
*** evrardjp has quit IRC04:33
*** evrardjp has joined #zuul04:33
*** wuchunyang has joined #zuul04:39
*** jamesmcarthur has joined #zuul04:40
*** jamesmcarthur has quit IRC04:44
*** jamesmcarthur has joined #zuul04:45
*** wuchunyang has quit IRC04:47
*** sgw has quit IRC05:03
*** jamesmcarthur has quit IRC05:09
*** jamesmcarthur has joined #zuul05:09
*** sgw has joined #zuul05:10
*** sgw1 has joined #zuul05:10
*** jamesmcarthur has quit IRC05:15
*** bhavikdbavishi has quit IRC05:37
*** armstrongs has joined #zuul05:51
*** jamesmcarthur has joined #zuul05:52
*** bhavikdbavishi has joined #zuul05:55
*** armstrongs has quit IRC06:01
*** bhavikdbavishi1 has joined #zuul06:04
*** bhavikdbavishi has quit IRC06:06
*** bhavikdbavishi1 is now known as bhavikdbavishi06:06
*** jamesmcarthur has quit IRC06:06
*** armstrongs has joined #zuul06:28
*** tosky has joined #zuul06:30
*** harrymichal has joined #zuul06:36
*** armstrongs has quit IRC06:36
*** rpittau|afk is now known as rpittau06:44
*** harrymichal has quit IRC07:01
*** harrymichal has joined #zuul07:01
*** bhavikdbavishi has quit IRC07:05
openstackgerritMatthieu Huin proposed zuul/zuul master: web UI: allow a privileged user to dequeue a change  https://review.opendev.org/73485007:08
openstackgerritMatthieu Huin proposed zuul/zuul master: web UI: allow a privileged user to re-enqueue a change  https://review.opendev.org/73677207:09
openstackgerritMatthieu Huin proposed zuul/zuul master: web UI: allow a privileged user to re-enqueue a change  https://review.opendev.org/73677207:11
mhucan someone explain to me what the promote subcommand of the CLI does exactly? My understanding is that it moves a change at the top of pipeline queue, to be built in priority. Is that correct?07:13
mhuAlso does it apply only to dependent pipelines like gate?07:13
openstackgerritMatthieu Huin proposed zuul/zuul master: Builds: add "held" attribute  https://review.opendev.org/72899407:14
openstackgerritMatthieu Huin proposed zuul/zuul master: Web UI: add checkbox filters to TableFilters component, filter builds by held status  https://review.opendev.org/72926507:15
*** bhavikdbavishi has joined #zuul07:19
*** jcapitao has joined #zuul07:22
openstackgerritFelix Edel proposed zuul/zuul master: WIP: Introduce Patternfly 4  https://review.opendev.org/73622507:23
*** hashar has joined #zuul07:30
*** bhagyashris|away is now known as bhagyashris07:39
*** felixedel has joined #zuul07:43
fricklerthe stage-output role claims to "Copies contents into {{ zuul_output_dir }}" but actually uses "stage_dir" as variable. Is just the comment in the readme wrong or should the variable be changed?07:45
frickleralso maybe someone wants to build a test for https://review.opendev.org/73671407:47
*** michael-beaver has quit IRC07:52
sshnaidm|offplease review/merge https://review.opendev.org/#/c/730360/ - zuul roles for working with ansible collections07:55
*** jpena|off is now known as jpena07:57
*** nils has joined #zuul08:01
*** wuchunyang has joined #zuul08:04
*** felixedel has quit IRC08:23
openstackgerritMatthieu Huin proposed zuul/zuul master: REST API: improve tenant scoping of autohold, authorizations  https://review.opendev.org/72811808:30
avassToday's the day for eating herring, drinking schnapps and dancing around a maypole. Happy midsummer everybody!08:40
mhuskol !08:41
mhu(altough it might be a bit early)08:41
avassskål!08:46
*** mugsie has quit IRC08:48
*** mugsie has joined #zuul08:48
*** jamesmcarthur has joined #zuul09:21
*** clarkb has quit IRC09:23
*** jamesmcarthur has quit IRC09:27
*** clarkb has joined #zuul09:28
*** ysandeep is now known as ysandeep|brb09:29
openstackgerritMatthieu Huin proposed zuul/zuul master: REST API, Web UI: add pipelines' manager, triggers data in status  https://review.opendev.org/73696810:07
*** bhavikdbavishi has quit IRC10:08
*** rpittau is now known as rpittau|bbl10:22
openstackgerritMatthieu Huin proposed zuul/zuul master: REST API, Web UI: add pipelines' manager, triggers data in status  https://review.opendev.org/73696810:23
*** wuchunyang has quit IRC10:29
*** vishalmanchanda has joined #zuul10:34
*** bhavikdbavishi has joined #zuul10:35
*** jcapitao is now known as jcapitao_lunch10:47
*** harrymichal has quit IRC10:51
*** harrymichal has joined #zuul10:52
*** jamesmcarthur has joined #zuul11:24
*** wuchunyang has joined #zuul11:28
*** jamesmcarthur has quit IRC11:31
*** harrymichal has quit IRC11:32
*** harrymichal has joined #zuul11:32
*** wuchunyang has quit IRC11:33
vishalmanchandaHi all11:40
vishalmanchandaDue to recent changes in zuul horizon node gate job  is failing.11:41
*** jpena is now known as jpena|lunch11:41
vishalmanchandaI am not sure but it happened after this patch https://review.opendev.org/#/c/736330 is merged.11:41
vishalmanchandaCan Someone take a look...11:41
vishalmanchandathanks11:41
*** bhavikdbavishi has quit IRC11:53
*** bhavikdbavishi has joined #zuul11:53
*** rlandy has joined #zuul11:56
*** rlandy is now known as rlandy|ruck11:57
*** bhavikdbavishi has quit IRC11:57
openstackgerritFelix Edel proposed zuul/zuul master: WIP: Introduce Patternfly 4  https://review.opendev.org/73622512:08
*** ysandeep|brb is now known as ysandeep12:11
*** rfolco has joined #zuul12:12
openstackgerritBenjamin Schanzel proposed zuul/nodepool master: Kubernetes Driver: Allow cpu/mem resource limits  https://review.opendev.org/73698412:17
*** rpittau|bbl is now known as rpittau12:19
*** jcapitao_lunch is now known as jcapitao12:20
openstackgerritFelix Edel proposed zuul/zuul master: Introduce Patternfly 4  https://review.opendev.org/73622512:23
AJaegervishalmanchanda: do you have a link to a failed job?12:27
vishalmanchandaAJaeger: https://zuul.opendev.org/t/openstack/build/00049c2aff4742ce8a2b96dbc0be4708/log/job-output.txt#3652-369312:28
AJaegertox not found, I see...12:30
AJaegervishalmanchanda:  in horizon's package.json this fails: "postinstall": "if [ ! -d .tox/npm ]; then tox -e npm --notest; fi",12:33
AJaegervishalmanchanda: the job is not installing tox, let's add that to a pre-run for your job, you need ensure-tox role there12:34
AJaegervishalmanchanda: can you do that or shall I send a patch and let you take over?12:34
vishalmanchandaAJaeger: I think we have to add a role here https://github.com/openstack/horizon/blob/master/playbooks/npm-test-xstatic-master/pre.yaml12:35
AJaegervishalmanchanda: not for horizon-nodejs10-run-test12:36
openstackgerritBenjamin Schanzel proposed zuul/nodepool master: Kubernetes Driver: Allow cpu/mem resource limits  https://review.opendev.org/73698412:36
AJaegervishalmanchanda: let me send a first patch12:37
vishalmanchandaAJaeger: I am not so familiar with this part.12:37
vishalmanchandaAJaeger: Could you push a patch for adding the 'ensure-tox role' and let' see..12:38
openstackgerritGuillaume Chauvel proposed zuul/nodepool master: Initial change to rename zuul-quick-start to zuul-tutorial-quick-start  https://review.opendev.org/72826212:39
AJaegervishalmanchanda: on my way...12:39
vishalmanchandaAJaeger: thanks for looking into it.12:39
AJaegervishalmanchanda: let's see whether https://review.opendev.org/736992 fixes  it12:41
vishalmanchandaAJaeger: +1.12:41
*** jpena|lunch is now known as jpena12:43
openstackgerritGuillaume Chauvel proposed zuul/zuul master: Fix zuul_run_command ret when command is not found  https://review.opendev.org/73547512:45
openstackgerritGuillaume Chauvel proposed zuul/zuul master: zuul_stream: close streamer when task is skipped  https://review.opendev.org/73547612:45
openstackgerritGuillaume Chauvel proposed zuul/zuul master: Add 'uuid' to 'src_dir' in order to allow parallel jobs for a static node  https://review.opendev.org/73598112:45
*** harrymichal has quit IRC12:52
*** harrymichal has joined #zuul12:53
ttxHi all, was wondering if semaphores could be used to avoid the errors when parallel mirroring operations occur in https://zuul.opendev.org/t/openstack/builds?job_name=openstack-upload-github-mirror#12:53
ttxideally it would be a per-repo semaphore, but since semaphores need to be pre-declared we could settle with a global github-mirroring semaphore12:54
ttxalso what's a "resource" in the context of job.semaphore.resources-first ?12:56
ttxThe glossary does not tell12:56
AJaegerttx, a semaphore could declare that only 1 (or whatever you configure) jobs run in parallel, so it would serialize everything if you set it to 112:57
ttxright12:57
ttxthat would allow to serialize that job but not anything else in the post pipeline12:57
*** harrymichal has quit IRC12:57
AJaegercorrect12:57
AJaegerWE use a semaphore for translations - but limit to 10; our translation server cannot handle a higher load...12:58
*** harrymichal has joined #zuul12:58
ttxhere it's more to avoid two updates on the same repo at the same time, It would avoid two updates at the same time, period. Which is a bit too much, but acceptable if there is no backlog forming. Which is why I was curious about resources-first12:59
AJaegerttx, this runs in post - corvus, don't we "merge" multiple jobs in post anymore? Or is that only in promote?12:59
openstackgerritBenjamin Schanzel proposed zuul/nodepool master: Kubernetes Driver: Allow cpu/mem resource limits  https://review.opendev.org/73698413:00
ttxAJaeger: post is supercedent, which does merge but only for same project-ref13:01
ttxhere it's two project-refs (one updating stable/train and the other on master for example)13:01
AJaegerI see13:02
ttx(or pushing two different commits in master)13:03
*** jamesmcarthur has joined #zuul13:26
*** Goneri has joined #zuul13:36
AJaegerttx, sorry, coming back now to your question: AFAIK: with resources-first: We ask for a node, acquire the semaphore; with resources-first: false, first acqure the semaphore, then request the node. So, if you have 50 post jobs: With resources-first, you would start 50 nodes, and then one runs after the other - with false, it's get semaphore, get node, get semaphore, get node; Since post pipeline has13:44
AJaegerhighest priority, I would go with "false" and see how that works13:44
openstackgerritGuillaume Chauvel proposed zuul/zuul master: [DNM] TEST run zuul tutorials to test 'uuid' in 'src_dir'  https://review.opendev.org/73557613:50
openstackgerritGuillaume Chauvel proposed zuul/zuul master: [DNM] TEST run zuul tutorials to test stream+callback (+ zuul-jobs change)  https://review.opendev.org/73547713:50
openstackgerritGuillaume Chauvel proposed zuul/zuul master: [DNM] TEST run zuul tutorials to test stream+callback and multiple nodes  https://review.opendev.org/73548313:50
*** rpittau is now known as rpittau|brb13:54
fungimhu: doesn't look like anyone else has answered you here yet, your impressions are correct. promote is only really relevant for reordering change queues in dependent pipelines (say you have 10 items queued and one of the most recently enqueued items is urgent but you're concerned there's a risk one of the changes ahead of it may fail, perhaps it's a fix for a nondeterministic failure case which you're afraid a13:57
fungichange ahead of it may hit), then you can promote that change to the head of the queue and restart testing of all the other items behind it13:57
mhufungi, thanks! Do you mind if I take this and add it to the doc? So next time I forget about it, I can just refer to the manual13:58
ttxAJaeger: since most of that job runtime is around setting up resources, I fear that would create a backlog. I'd rather try resources-first:true13:59
*** rpittau|brb is now known as rpittau|afk14:00
fungimhu: please do14:02
fungittx: this is specifically for the release notes jobs which are essentially branchless? if so, maybe the ideal is for zuul to get a new pipeline manager which is like supercedent but also ignores branch differences when deciding what to dequeue14:03
ttxfungi: no I ws trying to serialize the github mirroring14:05
ttxbut yes that would also solve it14:05
fungioh, yep14:05
fungialternatively, if the job only pushed the branch or tag which triggered it, that would avoid collissions14:05
ttxBut I was thinking it would still fail14:05
ttxlike the branch-agnostic-supercedent pipeline manager would kill previously-enqueued jobs and only run the latest right14:06
ttxbut I could see how that killing could intervene after the start of the mirror for job 214:08
fungiright now supercedent enqueues up to one item behind the running item for the same project+branch, and if there is a change already queued when another is eneuqued, the newly-enqueued one replaced the one waiting in the queue14:08
*** tosky has quit IRC14:08
fungibut it only runs at most one at a time14:08
ttxwhat happens if the first job is already running?14:09
ttxLike you have job 1 started, and job 2 arrives14:09
fungithe queued item waits for all builds for the running item to finish14:09
fungiso it should not run two concurrently (for the same project+branch at the moment)14:09
fungiif we had a version of that algorithm which only took the project into account, then say you have a build running for master and one queued for a stable/stein commit which merged, then a stable/train commit merges for the same project, the stable/stein one would be dequeued without ever running14:10
ttxOK so a supercedent-but-at-repo-level would work... just a bit costly as you;d have to define a separate post pipeline for that14:11
fungiright. well, i mean, pipelines aren't *really* that costly, they're a few lines in a file14:11
fungibut the semaphore solution would likely also work since it's just one job you're concerned about14:12
fungithough i can't recall if you'd need a separate semaphore per project for that solution14:12
ttxfungi: but a semaphore would also work (locking a bit too much), as would a change that would limit what is actually mirrored14:12
ttxwould be a github-semaphore, which would lock more than necessary14:13
ttx(there is no way apparently to create one semaphore per project)14:13
fungiyeah, if there was one semaphore for all runs of the same job, and the job is used by multiple repos, you'd never push more than one repo at a time14:13
fungiwhich could get fairly backlogged14:13
*** ysandeep is now known as ysandeep|away14:14
ttxmaybe adding an implicit semaphore for each project would be a better approach14:14
fungiwould also like to pick others' brains once they wake up... there are likely other solutions i'm just not thinking of14:15
ttx(limiting the github_mirror script to the affected branch would not work for things like tags, which would need to be pushed from all branches14:15
ttxso we'd still get conflicts14:15
fungiwouldn't you mirror tags to github only when tags get pushed to gerrit?14:16
ttxyou want the job to be idempotent14:16
fungilike, if you limited to just replicating the ref which triggered the build, then you could use push rather than mirror14:17
ttxlike if that tag does not get pushed for whatever reason, you want another future run to make it eventually consistent14:17
fungithough maybe you could special-case tags and push all tags to github each time a tag ref triggers the job14:17
AJaegerand if it fails, we would need to re-enqueue. Right now, it's self-healing with the next merge...14:18
ttxI'll send an email to discuss the various options14:18
fungisince git knows about all the local tags, the job could just `git push --tags` and then any which do not exist in github will be pushed to it14:18
ttxright. tags being infrequent that would mean slow reconciliation14:19
fungithat's true14:19
ttxeach solution has drawbacks :)14:19
fungiadd a daily periodic to fill in the gaps? ;)14:19
fungiof course your supercedent pipeline could also race/collide with periodic builds, so that's also not ideal14:20
ttxI think implicit repo-specific semaphores is the most elegant solution personally14:20
ttxbut I'll describe them all in an email, as this discussion will be hard to follow14:21
fungisounds good14:22
*** hashar has quit IRC14:27
mnaserhas zuul by any chance changed behaviour around 'dynamically' including a role from the repo it lives in?14:28
mnaserhttps://opendev.org/vexxhost/ansible-role-base-server/src/branch/master/.zuul.yaml shows a simple job with https://opendev.org/vexxhost/ansible-role-base-server/src/branch/master/examples/playbook.yml -- no weird includes or symlinks14:28
mnaserwhereas noonedeadpunk has been trying to do the same here https://review.opendev.org/#/c/736331/11 but without a symlink it doesn't end up working?14:29
mnaseraahhhhhh wait i notice it14:30
mnasernoonedeadpunk: we had to use 'frrouting' only and not 'ansible-role-frrouting' woops14:30
* mnaser tries to push edit and see14:30
noonedeadpunkhm14:36
noonedeadpunkI eventually also tried https://review.opendev.org/#/c/736331/10/meta/main.yml but it didn't work14:37
mnasernoonedeadpunk: i think what was missing is using 'ansible-role-frrouting', all good thoguh14:37
ttxfungi. corvus, AJaeger: posted http://lists.zuul-ci.org/pipermail/zuul-discuss/2020-June/001265.html14:38
noonedeadpunkoh, so just zuul just drops ansible-role with itself?14:38
noonedeadpunkthat's interesting14:39
mnasernoonedeadpunk: yeah because, the standard naming procedure for ansible roles is 'ansible-role-XXX' where 'XXX' is the role name14:40
mnaserso i'm not sure if zuul or ansible drops it, but something does :)14:40
*** chandankumar is now known as raukadah14:45
mordredmnaser: I think this is an area where adding colllection support to zuul may be helpful14:52
mnaser++14:53
*** sgw has quit IRC15:06
*** sgw has joined #zuul15:08
clarkbmordred: corvus: I think the foundation is hoping for slide content by the end of today for the community update. Are we happy with the etherpad's contents at this point? I think allison said she could transcode to slide format when ready15:10
openstackgerritMatthieu Huin proposed zuul/zuul master: CLI: add documentation on promote  https://review.opendev.org/73702715:13
mordredclarkb: I lost my tab - link me to it again?15:14
clarkbmordred https://etherpad.opendev.org/p/zuul-update-2020-0615:15
corvusclarkb: i think so15:16
mordredcorvus: what's the talking point on Improved support for managing release jobs in-tree. ?15:18
clarkbmordred: I think thats the thing where zuul tries to match tags to branches and lookup jobs from that branch config15:19
fungiyes, that ^15:19
clarkbthe old behavior was tags existed completely separate of branches so it didn't know what version of jobs to use when running under a tag15:19
fungitag refs are now backtracked to the best match branch for identifying configuration15:20
corvusyep that15:20
corvusmordred: https://review.opendev.org/578557 this change15:20
corvusit's not really groundbreaking info for that audience, it's sort of filler.  if we wanted to bump something in favor of something else, that would be the one to change :)15:21
corvusdid we have a gce driver for nodepool the last time one of these happened?15:22
*** bhavikdbavishi has joined #zuul15:22
corvus(even if we did, do we want to mention it again?15:22
corvuswe could also say something about ongoing progress with gitlab15:22
corvusi put those on the etherpad, feel free to drop anything15:23
clarkbI think we talked about gce last time.15:23
clarkbgitlab progress would be good15:23
mordredcorvus: ah - awesome, thatnks15:26
mordredcorvus: and yes, I thnk those are good additions15:26
mordredcorvus: oh - also - have we landed avass' nodepool-builder ec2 support?15:27
*** bhavikdbavishi has quit IRC15:28
*** harrymichal has quit IRC15:29
corvusmordred: no that's wip https://review.opendev.org/73521715:29
mordredcorvus: k. that'll be good fodder for next time then15:30
corvusya15:31
*** sgw has quit IRC15:32
*** Goneri has quit IRC15:32
*** reiterative has quit IRC15:32
*** sgw has joined #zuul15:32
*** Goneri has joined #zuul15:32
*** reiterative has joined #zuul15:32
*** masterpe has quit IRC15:35
*** tosky has joined #zuul15:50
*** jamesmcarthur has quit IRC15:53
*** jamesmcarthur has joined #zuul15:55
*** jcapitao has quit IRC16:01
*** rlandy|ruck is now known as rlandy|ruck|brb16:09
dmsimardWow zuul v4 and v5 :)16:12
dmsimardv3 took so long haha16:12
fungiyeah, but now that we have v3 to gate zuul changes, v4 and v5 can be quick! ;)16:12
dmsimard\o/16:12
fungireally though, zuul 3.0.0 is over two years old now16:13
fungiso v4 hasn't really happened terribly quickly (v5 likely will though)16:14
*** jamesmcarthur has quit IRC16:20
*** bhavikdbavishi has joined #zuul16:32
*** rlandy|ruck|brb is now known as rlandy|ruck16:37
*** nils has quit IRC16:40
*** jamesmcarthur has joined #zuul16:41
*** Goneri has quit IRC16:43
*** hamalq has joined #zuul16:47
hamalqhi am facing a problem trying to get zuul to work in https://zuul.opendev.org/t/openstack/build/8da2f74869744629a223ae03b698bb1e i get the error designate-tempest-plugin requires Python '>=3.6' but the running Python is 2.7.17 for stein designate16:49
*** ChanServ has quit IRC16:59
fungihamalq: this is probably a topic for the #openstack-infra channel, but i can tell you that's almost certainly due to running with a version of pip which is too old17:02
hamalqfungi: thanks i will check on that17:03
*** jamesmcarthur has quit IRC17:04
*** jpena is now known as jpena|off17:04
fungihamalq: oh, or possibly using the wrong constraints list17:04
hamalqfungi: because it should use https://github.com/openstack/designate-tempest-plugin/blob/0.7.0/setup.cfg 0.7.0 is there a way to specify that on zuul.yaml17:06
hamalqin here https://github.com/openstack/designate/blob/stable/stein/.zuul.yaml17:06
fungihamalq: let's discuss in #openstack-infra, this isn't a zuul problem, it's an openstack job problem17:07
hamalqok will do17:07
*** gmann is now known as gmann_afk17:13
*** bhavikdbavishi has quit IRC17:31
*** ChanServ has joined #zuul17:37
*** tepper.freenode.net sets mode: +o ChanServ17:37
*** jamesmcarthur has joined #zuul17:37
*** Goneri has joined #zuul17:37
*** harrymichal has joined #zuul17:52
*** jamesmcarthur has quit IRC18:09
*** jamesmcarthur has joined #zuul18:10
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Fix and test multiarch docker builds in a release pipeline  https://review.opendev.org/73705918:27
corvusavass: ^ using your new test :)18:27
openstackgerritSergii Golovatiuk proposed zuul/zuul-jobs master: Install source Python for supported OSes  https://review.opendev.org/73706018:27
*** holser has joined #zuul18:27
AJaegercorvus: that one breaks VEXXHOST CI - mnaser could you update your CI for 737059, please?18:30
*** jamesmcarthur has quit IRC18:40
*** jamesmcarthur has joined #zuul18:41
*** armstrongs has joined #zuul18:43
corvusAJaeger, mnaser: i'm a little confused; vexxhost reported okay on the parent18:44
corvusAJaeger, mnaser: i don't think vexxhost should be reading the zuul-tests.d -- that's intended for opendev18:45
holserAJaeger let me fix python-devel patch really quick18:47
armstrongsQuick question I have a common config project on multiple tenants. This however has a zuul file with dependencies on other projects that aren't included in those projects so it gives config issues. Is there any way to avoid these config issues without adding all projects to every tenant?18:48
clarkbarmstrongs: what opendev has done is try and get our base config to avoid external deps as much as possible. Because ya, zuul wants to resolve those deps if they exist18:49
*** armstrongs has quit IRC18:53
corvusdid armstrongs leave?18:54
clarkblooks lke it18:54
corvusif they come back; i would add to that that the extra-config-paths option may be useful in that case18:55
corvushttps://zuul-ci.org/docs/zuul/reference/tenants.html#attr-tenant.untrusted-projects.%3Cproject%3E.extra-config-paths18:56
corvusyou might be able to separate config into different files/dirs for use in different tenants.  so if you need some extra stuff in, say, a main tenant that manages that config-project, and then only need a subset in the rest of the repos that use it, you could put the extra stuff in its own dir18:57
*** jamesmcarthur_ has joined #zuul18:57
corvusmay or may not be appropriate depending on circumstances18:57
*** jamesmca_ has joined #zuul18:58
*** jamesmc__ has joined #zuul18:59
*** jamesmcarthur has quit IRC19:00
*** jamesmc__ has quit IRC19:00
*** jamesmcarthur_ has quit IRC19:02
*** jamesmca_ has quit IRC19:03
*** armstrongs has joined #zuul19:04
armstrongsSorry got disconnected there19:05
clarkbarmstrongs: let me get you a link to the logs of what corvus said after you left19:06
clarkbarmstrongs: http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2020-06-19.log.html#t2020-06-19T18:55:5619:06
armstrongsYeah so I could use the extra config option on the base common tenant and then it wont be read on the other tenants. That would work thank you.19:07
avasscorvus: cool, if there's no rush I'll take a look at it tomorrow. :)19:07
avassotherwise you can just bypass that for now19:07
*** armstrongs has quit IRC19:13
*** jamesmcarthur has joined #zuul19:14
*** jamesmcarthur has quit IRC19:20
*** jamesmcarthur has joined #zuul19:22
mnasercorvus, AJaeger: ok, i think we may have made the mistake of actually loading zuul-tests.d19:28
mnaseri think the idea was 'we can run more downstream tests' initially19:29
*** jamesmcarthur has quit IRC19:32
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Fix zuul-jobs-test-ensure-python-pyenv files  https://review.opendev.org/73706819:32
*** jamesmcarthur has joined #zuul19:32
AJaegermnaser: that would explain it. I agree with corvus, please update your CI to ignore zuul-tests.d19:34
mnaseryep, already done, it's shipping :)19:34
AJaegerzuul-jobs maintainers, please review 737068, I noticed that we did not run tests when we should19:34
AJaegermnaser: Great!19:34
AJaegermnaser: not working yet, see https://review.opendev.org/#/c/737059/ - I just rechecked and get the same failure19:36
mnaserAJaeger: yes, sorry, should have clarified, it's in flight19:36
mnaserour cd takes 5-10 minutes to pick it up and reload19:36
mnaserwe have to restart all of our zuul for this, i never got around finishing the inotify patch :(19:37
mnaserso no smart-reconfigure19:37
AJaegermnaser: ah, please recheck when done to double check that it works19:38
AJaegermnaser: also, why are there no logfiles from your CI in https://review.opendev.org/#/c/737060/1 - https://zuul.vexxhost.dev/t/opendev/build/1bbfebba5fb4498aa5cdfb9116260d8e  shows the Zuul UI and a "404" ;(19:39
mnaserAJaeger: because the tenant is mid reload right now19:39
mnaser:P19:39
mnaserzuul is starting up19:39
mnaserso everything 404s https://zuul.vexxhost.dev/t/opendev19:39
AJaegermnaser: Got it, thanks19:39
* AJaeger wishes everybody a great weekend and waves good night19:40
mnaserAJaeger: good night and have a good weekend19:40
corvushuh, that failed the original version of avass's test... i wonder if something external changed19:40
corvusAJaeger: good night!19:41
AJaegerthanks19:41
*** yolanda has quit IRC19:41
mnasercorvus: 737059 is fixed and running at https://zuul.vexxhost.dev/t/opendev/status -- thank you for pinging me about that19:43
corvusmnaser: woot, thanks :)19:43
*** sanjayu_ has quit IRC19:53
*** saneax has joined #zuul19:54
*** jamesmcarthur_ has joined #zuul20:12
*** jamesmcarthur has quit IRC20:15
*** gmann_afk is now known as gmann20:15
*** jamesmcarthur_ has quit IRC20:26
*** jamesmcarthur has joined #zuul20:27
*** vishalmanchanda has quit IRC20:40
*** jamesmcarthur has quit IRC20:48
*** hashar has joined #zuul20:54
*** rfolco has quit IRC20:54
*** y2kenny has joined #zuul20:56
y2kennydoes the console stream to the web-ui come from the executor?21:06
fungiy2kenny: indirectly, yes21:08
clarkby2kenny: it comes from the zuul-fingergw which then talks to the executors iirc21:08
y2kennyok.  The stream stopped working all of a sudden and I am wondering where to start doing the debugging21:08
fungiy2kenny: we've seen that if an out-of-memory event on the executor causes the kernel to sacrifice the log streaming process21:09
fungirestarting the executor daemon generally fixes that21:11
*** sgw1 has quit IRC21:11
y2kennyfungi: I tried that but didn't seem to work.  I just restarted the web UI server and see if that fixes it...21:11
corvuser actually the fingergw is not involved in the web console stream; zuul-web talks to the executor directly21:12
corvusso it's: browser -> zuul-web -> zuul-executor21:13
clarkbcorvus: TIL21:13
clarkbfor some reason I thought it went throught the fingergw too21:13
clarkbsince fingergw knows which executor to talk to but I guess web knows too?21:13
corvusthe fingergw is just for "finger @"21:13
corvusyep21:13
fungiyeah, zuul-fingergw is in case someone wants to use finger protocol to stream the log without access to the finger port on the executor (or having to know which executor) right?21:13
corvusthey're basically doing the same thing for both protocols21:13
clarkbgot it21:13
corvusy2kenny: as an admin, you can also telnet or finger to the zuul-executor finger port to debug this21:15
corvusi think something like this should work:  echo SHA | nc executor.example.com -p 790021:16
corvusthat would get you a console stream talking directly to the executor.  whether that works or fails should help narrow down what's broken.21:17
y2kennycorvus: I see... are there more documentation around this?  is this along the line of what's describe here: https://zuul-ci.org/docs/zuul/howtos/troubleshooting.html21:17
corvusecho 21bee08ebf1f4c90881040f4a2ee91d7 | nc localhost 790021:18
corvussorry i got the cmdline wrong; that ^ is a working example21:18
y2kennySHA being the job id?21:18
corvusy2kenny: yes the build id21:18
y2kennyok21:18
corvusy2kenny: and yeah, i don't think we documented this troubleshooting technique21:18
corvusavass: wow, docker really did just update the registry:2 image and 'htpasswd' is no longer in it21:21
corvusavass: however, we have a bunch of code to set up the registry for the intermediate registry tests and it doesn't rely on that, so i'm going to modify your change to use that approach21:22
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add tests for upload-docker-image  https://review.opendev.org/73540221:29
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Fix and test multiarch docker builds in a release pipeline  https://review.opendev.org/73705921:29
*** sgw1 has joined #zuul21:31
*** saneax has quit IRC21:47
*** hashar has quit IRC21:54
*** harrymichal has quit IRC21:56
*** weshay|ruck is now known as weshay_pto22:00
*** jamesmcarthur has joined #zuul22:48
*** rlandy|ruck has quit IRC22:59
*** jamesmcarthur has quit IRC23:07
*** jamesmcarthur has joined #zuul23:09
*** hamalq has quit IRC23:11
*** tosky has quit IRC23:45
mnasercorvus: is there someone playing around with adding patternfly 4 to the zuul ui?23:49
mnaseri was looking to see if we can get it into horizon but figured the zuul web ui might be a good hit to get to know what im dealing with first23:49
corvusmnaser: i think so, 1 sec23:53
corvusmnaser: https://review.opendev.org/73622523:53
mnaseroh awesome23:54
corvusthat's a good chunk of work done23:54
corvusi'm having some problems navigating around a bit23:56
corvusin the preview site23:56
corvusi'm not sure if that's something that would happen for a real deployment, or something specific to the preview23:56
corvusall the liks go to the 'undefined' tenant23:56
corvuslinks23:57
corvusmnaser: anyway, there's enough there to see what it looks like, and enough left to do to warrant playing around with it :)23:57
mnasercorvus: yeah i noticed those too, but looks like some awesome progress, i'll dive int if there's any work left later as i see some good effort by felix starting it :)23:58
corvusmnaser: i really like PF's tables, but some of the more complex structures like trees, etc, are lacking23:59
corvusmnaser: but i think horizon is pretty table heavy and not so much into trees, so probably a good fit :)23:59
mnasercorvus: yeah i agree, i dont think there is a good replacement to our need for the trees, but i think we should certainly look at moving at using the tables for buildsets/nodes/etc23:59
mnaserbut yes, agreed on the horizon thing too23:59

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