Thursday, 2020-04-23

*** cdearborn has quit IRC00:47
*** rlandy|brb has quit IRC00:51
*** bhavikdbavishi has joined #zuul01:04
*** bhavikdbavishi1 has joined #zuul01:06
*** bhavikdbavishi has quit IRC01:08
*** bhavikdbavishi1 is now known as bhavikdbavishi01:08
*** swest has quit IRC01:09
*** swest has joined #zuul01:23
*** rfolco has quit IRC01:24
*** rfolco has joined #zuul01:25
*** Goneri has quit IRC01:43
*** rf0lc0 has joined #zuul02:03
*** bhavikdbavishi has quit IRC02:04
*** rfolco has quit IRC02:04
*** bhavikdbavishi has joined #zuul02:28
*** threestrands has joined #zuul02:33
*** mordred has quit IRC02:43
*** mordred has joined #zuul02:45
*** zxiiro has quit IRC03:30
*** wxy-xiyuan has quit IRC03:47
*** bhavikdbavishi has quit IRC03:47
*** wxy has joined #zuul03:49
*** zxiiro has joined #zuul04:08
*** bhavikdbavishi has joined #zuul04:23
*** evrardjp has quit IRC04:35
*** evrardjp has joined #zuul04:35
openstackgerritIan Wienand proposed zuul/zuul master: [wip] intermediate jobs  https://review.opendev.org/72220005:29
*** reiterative has quit IRC05:36
*** reiterative has joined #zuul05:36
*** sgw has quit IRC05:55
*** dpawlik has joined #zuul06:01
openstackgerritIan Wienand proposed zuul/zuul master: [wip] intermediate jobs  https://review.opendev.org/72220006:07
openstackgerritIan Wienand proposed zuul/zuul master: [wip] intermediate jobs  https://review.opendev.org/72220006:08
*** ysandeep is now known as ysandeep|afk06:28
openstackgerritMerged zuul/nodepool master: Actually install extras from nodepool_base  https://review.opendev.org/72213506:28
AJaegermordred: the config-errors for the openstack tenant come from a retirement, we need to remove a couple of requireed-projects from old branches. noonedeadpunk has patches up for those06:30
avassmordred: oh, too bad, I thought it was just the tests that was failing, at least the build was green ;)06:39
openstackgerritIan Wienand proposed zuul/zuul master: [wip] intermediate jobs  https://review.opendev.org/72220006:42
*** jcapitao has joined #zuul07:07
*** ysandeep|afk is now known as ysandeep07:10
*** bhavikdbavishi has quit IRC07:20
*** tosky has joined #zuul07:24
*** yolanda has joined #zuul07:24
*** rpittau|afk is now known as rpittau07:39
avasswhat happens if you have reporters for two different gerrit instances in the same pipeline? would that produce an error or does zuul only report to the instance relevant to the change?07:50
*** bhavikdbavishi has joined #zuul07:50
avasswondering if we're going to need separate pipelines for each gerrit instance in that case, we have repos that are dependent on eachother between them07:51
avassor if we should just migrate that repo over to the other gerrit instance :)07:55
*** jpena|off is now known as jpena07:57
*** igordc has quit IRC08:13
openstackgerritIan Wienand proposed zuul/zuul master: [wip] intermediate jobs  https://review.opendev.org/72220008:14
*** threestrands has quit IRC08:33
*** zxiiro has quit IRC08:40
tobiashavass: zuul will only report to the source gerrit of the change08:41
*** ysandeep is now known as ysandeep|lunch08:44
avasstobiash: nice, thanks!08:45
tobiashavass: it's handled by this: https://opendev.org/zuul/zuul/src/branch/master/zuul/driver/gerrit/gerritreporter.py#L5208:47
avasstobiash: I guess the 'require:' is separate as well then, because it won't be able to be open and current patachset in both gerrits :)08:49
tobiashyes08:49
tobiashwe also have pipelines wich work on both github and a gerrit simultaneously08:50
avassnice08:51
avasstobiash: we're probably going to need to do something like that as well soon, nice to know it works08:54
*** sshnaidm|afk has quit IRC08:55
avasstobiash: re 722058, so soft dependency works like, if the dependency is not in the buildset the job will run, but if it is but was skipped the job will not run and not produce an error?08:56
avasstobiash: so the current do should be 'will be ignored if the dependent job is not in the buildset/not configured to run in the pipeline'08:58
avasss/do/doc08:59
tobiasha soft dependency will still produce an error if the dependent job had an error08:59
tobiashbut not entirely sure what happens if the dependent job has been skipped09:00
tobiashI think it will still run it in this case09:01
avassI actually meant failed and not skipped. But I should probably investigate this a bit to be sure how it works. The docs could probably be a bit clearer on this09:02
tobiashif the parent job fails it will be skipped regardless of the type of dependency09:03
tobiasha soft dependency just doesn't require that the parent job ran at all09:03
avassright, I'm probably just confused09:04
avasssince it says 'run'.09:07
avassanyway09:15
openstackgerritAlbin Vass proposed zuul/zuul master: doc fix: containes -> contains  https://review.opendev.org/72223709:17
avass:)09:17
*** ysandeep|lunch is now known as ysandeep09:33
openstackgerritJan Kubovy proposed zuul/zuul master: Connect merger to Zookeeper  https://review.opendev.org/71622110:07
*** sshnaidm has joined #zuul10:14
jktdo I have a way of finding out the reason behind "Merge Failed." when I don't have access to mnaser's hosted Zuul logs?10:18
jktI have a change that I uploaded: https://review.gerrithub.io/c/Telecominfraproject/oopt-gnpy/+/488748/4, its git parent is one behind current tip of the target branch10:18
jktthe tip of the target branch has modified repo's top level README.md, the change in question modified some unrelated Python code10:19
jktif I upload another change with the same parent, this time adding an unrelated file, Zuul doesn't complain10:19
*** rpittau is now known as rpittau|bbl10:21
jkthmm, and now that I've left a "recheck" comment, the builds have started. Perhaps it was a transient failure in the merger?10:22
openstackgerritJan Kubovy proposed zuul/zuul master: Connect executor to Zookeeper  https://review.opendev.org/71626210:24
openstackgerritTobias Henkel proposed zuul/zuul master: Tune automatic garbage collection of git repos  https://review.opendev.org/72227210:45
tobiashzuul-maint: this contains the stuff I learned about automatic garbage collection in git ^10:46
*** jcapitao is now known as jcapitao_lunch10:47
*** bhavikdbavishi has quit IRC10:58
openstackgerritMerged zuul/zuul master: doc fix: containes -> contains  https://review.opendev.org/72223710:59
avasstobiash: cool, this looks like it could be useful for us as well11:13
openstackgerritJan Kubovy proposed zuul/zuul master: Connect fingergw to Zookeeper  https://review.opendev.org/71687511:16
*** jpena is now known as jpena|lunch11:34
tristanCcorvus: rootless podman needs userns and centos requires a sysctl to enable unprivileged userns with : echo 10000 > /proc/sys/user/max_user_namespaces11:47
tristanCcorvus: otherwise running podman as root works out of the box11:47
*** rlandy has joined #zuul12:00
*** bhavikdbavishi has joined #zuul12:02
*** rpittau|bbl is now known as rpittau12:02
*** bhavikdbavishi1 has joined #zuul12:09
*** bhavikdbavishi has quit IRC12:11
*** bhavikdbavishi1 is now known as bhavikdbavishi12:11
*** mhu has joined #zuul12:12
mordredAJaeger: yah - actually though, the config errors are helpful right now, as they're showing an unexplained flaw in a zuul dashboard patch12:28
*** jcapitao_lunch is now known as jcapitao12:29
*** jpena|lunch is now known as jpena12:39
openstackgerritTristan Cacqueray proposed zuul/zuul master: merger: replace custom message logger  https://review.opendev.org/72026612:43
openstackgerritPaul Albertella proposed zuul/zuul-jobs master: Add Bazel build and ensure roles  https://review.opendev.org/69351312:51
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Add testing of fetch-sphinx-tarball role  https://review.opendev.org/71502812:53
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Improve linters execution  https://review.opendev.org/72230712:59
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Improve linters execution  https://review.opendev.org/72230713:01
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: hlint: add haskell source code suggestions jobs  https://review.opendev.org/72230913:02
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Switch remaining tests to fedora-31  https://review.opendev.org/72231013:06
*** igordc has joined #zuul13:07
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: hlint: add haskell source code suggestions job  https://review.opendev.org/72230913:14
*** Goneri has joined #zuul13:15
*** zxiiro has joined #zuul13:16
*** bhavikdbavishi has quit IRC13:17
AJaegerzbr, looking at 722310, I would expect our jobs to fail - why do they pass?13:25
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: hlint: add haskell source code suggestions job  https://review.opendev.org/72230913:26
zbrAJaeger: why to fail? my only worry is that migration happened by missing these, not sure why.13:31
*** ysandeep is now known as ysandeep|away13:38
*** panda is now known as panda|babysit13:43
AJaegerzbr: asked differently why does https://review.opendev.org/722310 not update zuul-tests.d/container-roles-jobs.yaml ?13:44
AJaegerzbr: changes look fine, I'll review later again, just way puzzled by it and had no time to dig further13:45
openstackgerritMerged zuul/zuul master: Tune automatic garbage collection of git repos  https://review.opendev.org/72227213:47
AJaegerzbr: ah, it does not handle node changes...13:47
zbras long we merge it, we should be fine.13:47
*** sgw has joined #zuul13:54
tobiashcorvus: I've responded on 72045813:59
AJaegerzbr: yep13:59
*** sshnaidm has quit IRC14:01
corvustobiash: ok.  i was hoping we'd get a test case out of it, since it seems like something we'd like to avoid regressing in the future (it's really tempting for us to want to "simplify" the git processing code, and without regression tests, we'd reintroduce stuff like that)14:01
AJaegerzuul-jobs reviewer, please have a look at https://review.opendev.org/722307 https://review.opendev.org/722310 https://review.opendev.org/715028 https://review.opendev.org/721796 https://review.opendev.org/#/c/721248/  - all smaller fixes14:02
corvustobiash: but if we just can't figure out how repos get in that state, not much we can do :)14:02
tobiashcorvus: I know, but so far I had no luck with a direct reproducer :/14:02
AJaegerzbr: want to abandon https://review.opendev.org/#/c/721571/ ?14:02
*** sshnaidm has joined #zuul14:02
zbrAJaeger: probably. but that change undelined several problem we still need to address.14:10
*** sassyn has joined #zuul14:39
sassynHi Amazing Group14:39
sassynI wanted to let you know we started zuul in our production!14:40
sassynthe team~400 developers are happy!14:40
sassynBut I still have one issue to take care of14:40
sassynMy Question: User X commit a patch to the gerrit repo A. User Y and Z also commit patches to repo A.14:41
sassynso we have PatchX, PatchY and PatchZ in that order14:41
sassynall pacthes were triggered by zuul and got +1 verified!14:42
sassynUser BOSS go to gerrit and mark patchX and PatchZ as +2 while patchX as -2.14:42
AJaegersassyn: glad to hear the team is happy!14:42
corvussassyn: wait i don't understand 14:42 < sassyn> User BOSS go to gerrit and mark patchX and PatchZ as +2 while patchX as -2.14:43
corvussassyn: was one of those patchX supposed to be a patchY ?14:43
sassynAJaeger thank u14:43
sassyncorvus no. patch x is by user x and patch y is by user y14:43
corvussassyn: did boss mark patchX both +2 and -2?14:44
AJaegersassyn: I guess you wanted to say: "User BOSS go to gerrit and mark patchX and PatchY as +2 while patchZ as -2." instead of having X twice in there...14:44
sassynno14:44
sassyni'm saying user Boss mark patchX as +2 and patch Z +2 but didn't touch patch Y14:45
sassynmy mistake14:45
sassynI hope now it is more clear14:45
corvusokay, got it, please continue :)14:45
AJaegerok, now the question ;)14:45
sassynZuul firing a jpb for patchX, and that't it14:45
sassynonly if I do +2 on Y14:46
sassynthen zuul will put Y and Z14:46
avassAJaeger: reviewed the ones I could :)14:46
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: WIP Support multi-arch image builds with docker buildx  https://review.opendev.org/72233914:46
openstackgerritMerged zuul/zuul-jobs master: Switch remaining tests to fedora-31  https://review.opendev.org/72231014:46
AJaegerthanks, avass !14:46
tobiashsassyn: are those patches stacked onto each other or independent from each other?14:47
avassjust went for a run so I'm gonna take a shower, but I'll do a bunch of reviews when I'm back14:47
sassyntobiash: let me check14:47
*** cdearborn has joined #zuul14:49
*** cdearborn has quit IRC14:53
*** cdearborn has joined #zuul14:53
openstackgerritMerged zuul/zuul-jobs master: Improve linters execution  https://review.opendev.org/72230714:55
sassyntobiash: I don't know how to answer this14:57
sassynthe patches are for the same repo X14:57
openstackgerritJan Kubovy proposed zuul/zuul master: Connect merger to Zookeeper  https://review.opendev.org/71622114:57
openstackgerritJan Kubovy proposed zuul/zuul master: Connect executor to Zookeeper  https://review.opendev.org/71626214:57
openstackgerritJan Kubovy proposed zuul/zuul master: Connect fingergw to Zookeeper  https://review.opendev.org/71687514:57
tobiashsassyn: if Z is stacked on Y it has a hard dependency defined by git so Z can only enter the gate if Y is approved as well14:58
tobiashsassyn: you can see that when you checkout Z and look at the git history if Y is part of the history14:59
sassynI run form my machine  echo File1 >> File1 ; git add File1; git commit -m "file1";   git push origin HEAD:refs/for/master15:00
openstackgerritMerged zuul/zuul-jobs master: Add testing of fetch-sphinx-tarball role  https://review.opendev.org/71502815:00
sassynand then I run form my machine  echo File2 >> File2 ; git add File2; git commit -m "file2";   git push origin HEAD:refs/for/master15:00
sassynand then I run form my machine  echo File3 >> File3 ; git add File3; git commit -m "file3";   git push origin HEAD:refs/for/master15:00
sassynconsider file1, file2 and file3 as PatchA, patchB, patchC15:01
AJaegersassyn: so, those are are on on the same branch stacked on top of each other15:01
corvussassyn: in that case those commits are 'stacked'15:01
AJaegersassyn: you can showcase using our sandbox repository ...15:01
sassynwhat do u mean shocase?15:02
AJaegersassyn: opendev/sandbox - in case you want to show us how it looks like so that we can explain a life example15:02
sassynAJaeger, so what is the way to work?15:02
corvussassyn: if they aren't related to each other, and you want to be able to merge them independently of each other, then you can make each commit on a new branch, and after making each commit, checkout the master branch again15:02
sassynmy repo is set as fast forward only15:02
AJaegerhttps://docs.opendev.org/opendev/infra-manual/latest/developers.html#starting-a-change15:03
corvussassyn: oh, then that won't work15:03
corvussassyn: the main reason to use ff-only is if you never want that to work.  most people do want to be able to write independent changes, so ff-only is usually not the right choice for projects with multiple people working on them.15:05
AJaegersassyn: you really serialize the work of your team ;(15:05
avassfungi: thanks for the tip yesterday, we found out that running an mqtt message broker could solve more problems so that's what we're going for now ;)15:06
sassynThank you all15:06
*** panda|babysit is now known as panda|ruck15:08
avassfungi: doesn't look like the mqtt driver includes the commit id though, but I guess that shouldn't be hard to add or workaround worst case15:11
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Update ensure-javascript-packages README  https://review.opendev.org/72235415:19
*** sshnaidm has quit IRC15:22
*** bhavikdbavishi has joined #zuul15:34
*** bhavikdbavishi1 has joined #zuul15:37
*** bhavikdbavishi has quit IRC15:39
*** bhavikdbavishi1 is now known as bhavikdbavishi15:39
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Add testing of fetch-sphinx-tarball role  https://review.opendev.org/72158415:42
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Add testing of fetch-sphinx-tarball role  https://review.opendev.org/72158415:43
tristanChttps://review.opendev.org/#/q/topic:haskell-jobs adds two new zuul-jobs, could you please have a look when you have spare time? Thank you in advance!15:47
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: tox: allow tox to be upgraded  https://review.opendev.org/69005715:48
*** sshnaidm has joined #zuul15:55
openstackgerritTristan Cacqueray proposed zuul/zuul master: merger: replace custom message logger  https://review.opendev.org/72026615:59
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: bindep: Add missing virtualenv and fixed repo install  https://review.opendev.org/69363716:15
fungisassyn: catching up, but this is precisely the problem i tried to explain last week or the week before that you would encounter if you continue to insist on configuring gerrit to require ff-only for your repositories. you basically give up a lot of zuul's efficiencies. you're also going to see that you need to rebase changes any time an unrelated change you've stacked your change on can't merge for some reason16:24
fungi(starts failing a job or whatever)16:24
avasstristanC: taking a quick look, but I'll go through it a bit later as well16:24
fungisassyn: you'll need to switch to merge-if-needed or cherry-pick if you want to allow changes to land in the same repository independently of one another16:25
fungizuul expects to manage the order in which changes merge, and can't do that if gerrit is controlling the order16:26
*** avass has quit IRC16:29
*** evrardjp has quit IRC16:35
*** evrardjp has joined #zuul16:35
*** avass has joined #zuul16:36
tristanCavass: thanks! I'm using forked version, but i think it would be good if zuul could test more languages16:38
bolgdoes someone know why ZK is not able to read certificate in https://zuul.opendev.org/t/zuul/build/d2601858cf2e4af385f6cf42273d30b2/log/container_logs/zk.log while here (https://zuul.opendev.org/t/zuul/build/2bf3734c628b4712919015d564000974/log/container_logs/zk.log) it does?16:38
mordredavass: yeah - honestly, making the mqtt driver better seems like a good general idea - I'm glad it turned out to be a good solution for you!16:40
tristanCbolg: perhaps a race condition on cert permission?16:41
bolgtristanC: so recheck till it works?16:42
tristanCbolg: the permission issue is odd, it seems like it happens when zookeeper access the file between L7 and L6 of https://opendev.org/zuul/zuul/src/branch/master/doc/source/examples/playbooks/setup.yaml . which seems rather unlikely16:45
tristanCbolg: there are successfull connection happening after the failure, are you sure the build failure is caused by this zk permission failure?16:47
tristanCbolg: e.g., there are `AttributeError: 'MergeJob' object has no attribute 'updated'` in https://zuul.opendev.org/t/zuul/build/d2601858cf2e4af385f6cf42273d30b2/log/container_logs/scheduler.log#12516:48
avassmordred: yeah, and it seemed like a good way to let people subscribe to a lot of events from zuul or anything else we publish there16:48
*** rpittau is now known as rpittau|afk16:49
bolgtristanC: will check, thanks for the hint16:50
bolgtristanC: I think it is connected to the ZK, the change makes executor use zk. At 15:31:22 executor tries to connect to it (https://zuul.opendev.org/t/zuul/build/d2601858cf2e4af385f6cf42273d30b2/log/container_logs/executor.log). About the same time ZK cannot access the cert (https://zuul.opendev.org/t/zuul/build/d2601858cf2e4af385f6cf42273d30b2/log/container_logs/zk.log) and later the scheduler fails at 15:37:11. Is it possible that the excutor wants16:57
bolgto connect to ZK too early?16:57
*** bhavikdbavishi has quit IRC16:59
tristanCbolg: this seems to indicate that a single connection failure is not corrected by the following `zuul.zk.ZooKeeper: Retrying zookeeper connection` attempt.16:59
tristanCif that is the case, then perhaps there is something to be done in the zuul.zk module to ensure proper reconnection attempt17:00
tristanCotherwise we could delay zookeeper startup by waiting for the certificate to be provisioned by the setup playbook, and also wait that the certificates are readable by the zookeeper service user17:01
*** cdearborn has quit IRC17:02
*** jpena is now known as jpena|off17:13
bolgtristanC: I feel the problem may be connecting to ZK before the executor starts, maybe? https://review.opendev.org/#/c/716262/6/zuul/cmd/executor.py17:16
tristanCbolg: perhaps that early connection revealed another issue in zuul.zk not reconnecting properly in that situation (when service tls files are not readable)17:27
bolgtristanC: thanks for the hint I will dive into it17:28
tristanCbolg: you're welcome. Please let me know if I can help or review your changes.17:29
bolgI will17:31
*** sshnaidm is now known as sshnaidm|afk17:50
*** yolanda has quit IRC17:55
*** rlandy has quit IRC18:03
*** rlandy has joined #zuul18:03
*** jcapitao has quit IRC18:16
*** sgw has quit IRC18:48
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Support multi-arch image builds with docker buildx  https://review.opendev.org/72233919:20
openstackgerritAlbin Vass proposed zuul/zuul master: Add commit id to Change  https://review.opendev.org/72247819:23
avassbefore I spend too much time on this, would anyone be against something like that?19:23
tristanCavass: that looks great to me19:32
fungiavass: that and any other event data zuul knows about which you think might be useful in the mqtt payload19:35
* fungi gives thumbs-up19:35
avassfungi, tristanC: sure I'll go crazy and let you review then :)19:36
fungiavass: i think the feature has just been minimally implemented awaiting an interested user who could point out what was missing to make it more functional19:39
*** igordc has quit IRC19:39
corvusavass: i think that's good, and we may want to continue to not expose it in the job (unless we have a good reason) -- that might confuse some folks (we definitely don't want anyone doing 'git checkout {{commit_id}}'19:40
corvusbut i think it's probably fine in the reporters19:41
avasscorvus: sure19:42
avassoh and this is actually working for real this time now: https://review.opendev.org/#/c/717260/19:58
avassI'd appreciate if someone could take a look at it :)19:58
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Support multi-arch image builds with docker buildx  https://review.opendev.org/72233920:02
openstackgerritMonty Taylor proposed zuul/nodepool master: Build multi-arch images for x86 and arm  https://review.opendev.org/72248320:03
mordredcorvus: ^^20:04
mordredclarkb, ianw: ^^ you might also find that interesting20:04
*** adamw has quit IRC20:08
*** sgw has joined #zuul20:16
*** adamw has joined #zuul20:16
*** adamw has quit IRC20:17
noonedeadpunkfolks, what version of nodepool should I isntall so that it supported queens glance? as now I have kinda "openstack.exceptions.NotSupported: The image service for default:Default exists but does not have any supported versions."20:25
funginoonedeadpunk: it's probably going to depend more on the version of openstacksdk20:25
noonedeadpunkyeah, just started to write that20:26
noonedeadpunkthanks fungi20:26
funginoonedeadpunk: also that seems odd... i doubt it's that your sdk is "too new"20:26
fungiopenstacksdk aims to provide reasonable support for versions of openstack found in the wild, going pretty far back in the history of those apis20:27
fungiso it seems more like it's complaining that it expected to get version information and didn't20:27
noonedeadpunkit's 0.45.0 so quite new...20:27
fungii'm not super familiar with the glance version discover code in there, but maybe mordred has ideas20:28
fungier, version discovery20:28
*** igordc has joined #zuul20:32
noonedeadpunkmaybe I have configured region in some weird way...20:32
noonedeadpunkOk, thanks anyway!20:32
noonedeadpunkin terms configured nodepool to the weird region:)20:33
mordrednoonedeadpunk: openstacksdk should support all verisons of glance, and nodepool should support them too20:34
clarkbmaybe clouds.yaml says use a version that isnt available?20:35
clarkbI thibk we had issues like that when clouds dropped keystone v2 api20:35
noonedeadpunkclouds.yaml is pretty plain - has just identity_api_version: 320:41
noonedeadpunkok, from python shell I guess I know what's the issue is...20:44
noonedeadpunkthanks for help everyone!20:44
funginoonedeadpunk: don't keep us in suspense!20:45
noonedeadpunkglance had weird public endpoint which couldn't bbe resolved from nodepool20:47
noonedeadpunkso like conn.image() resulted in `Failed to contact the endpoint at http://controller:9292 for discovery. Fallback to using that endpoint as the base url.`20:48
fungiaha, glad you found it, and thanks for the details in case we see a similar error report in the future20:48
noonedeadpunksure, sorry for disturbing20:48
fungimaybe the error message coming out of openstacksdk could be improved20:48
noonedeadpunkyeah... but now don't have time fixing it unfortunatelly...20:50
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add tests for multiarch build  https://review.opendev.org/72249620:53
corvusmordred: ^ that's tests for your multiarch change20:53
mordredcorvus: neat!21:05
mordredcorvus: the nodepool-build-image job worked21:05
mordrednodepool-functional-k8s had a sad21:06
corvusmordred: via depends-on?21:06
corvusyep https://review.opendev.org/72248321:06
mordredyeah21:07
mordredsomething about minikube log export21:07
corvuslooks like we're still waiting for a report there21:07
corvushttps://zuul.opendev.org/t/zuul/build/92966a60125f4e0b82e5019996436ac221:08
*** dpawlik has quit IRC21:09
mordredcorvus: that seems unrelated - but I'd like to understand it more21:09
corvusit looks like everything succeeded except that log export21:11
mordredyeah21:12
mordredso - I mean - it seems like the image building parts worked21:12
mordredcorvus: nope!21:13
mordredcorvus: it did not run the new code21:13
mordredcorvus: like - it looks like it did not get the new role21:14
corvusk8s seems to have been cycling through coredns pods at that point.  i don't know why; maybe we just see if this happens again, and then try to figure out if there's something we need to fix with the k8s, or if we should just ignore errors in log collection21:15
corvusmordred: i think the 'not running new code' is probably more significant21:15
mordredyeah21:15
mordredyeah - the job in base-jobs isn't blocking it from being speculative is it?21:15
corvusmordred: yeah -- the build-docker-image role is in a trusted playbook21:17
mordredah. well that'll do it21:17
mordredcorvus: so your tests patch should at least tell us if landing it will break things21:18
corvusmordred: probably easiest thing is to iterate with my test change in zuul-jobs, then i think it should be safe to land.  that should be a thorough test of the whole system.21:18
mordredyeah21:18
corvus(alternatively, we could start splitting that job up into trusted and non-trusted parts; and maybe we should, but later?)21:18
mordredyeah - let's not go too far down the rabbit hole21:19
noonedeadpunksorry - another stupid question - "nodepool.exceptions.LaunchNetworkException: Unable to find public IP of server"21:23
noonedeadpunkLike I've provided private network for the pool, but nodepool has access to this network21:24
noonedeadpunkI obviously just don't see some missed option...21:24
mordrednoonedeadpunk: if you're wanting nodepool to just use the private network to talk to nodes, you should put "private: true" in the clouds.yaml entry21:24
mordredthat will tell openstacksdk to treat the private ip as "the interface for talking to the server"21:25
noonedeadpunkmordred: hm, will try, I just thought that openstacksdk is not the one who should talk to the server...21:26
mordrednoonedeadpunk: it's not- but it's the one that figures out from openstack how to talk to the server21:28
mordrednoonedeadpunk: it is sadly a very difficult topic21:28
noonedeadpunkyeah, I see :)21:28
noonedeadpunkWas just really expecting this to be configured in nodepool.yaml21:28
mordredthere are a _bunch_ of network-related settings one can make for openstack - instead of duplicating clouds.yaml, we decided to just have nodepool refer to a named cloud from clouds.yaml and let all of those options get configured there21:29
noonedeadpunknow that makes sense to me:)21:30
mordrednoonedeadpunk: it would be much better if we didn't have to have people configure crazy things about their clouds :)21:30
noonedeadpunkyeah lol21:30
noonedeadpunkbtw, the last thing (I hope). Today I was looking through DIB elements, but I think I didn't find any that would isntall cloud-init? Like only https://docs.openstack.org/diskimage-builder/latest/elements/cloud-init/README.html but it's for gentoo only?21:32
noonedeadpunkothers are more about cloud-init config21:32
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Support multi-arch image builds with docker buildx  https://review.opendev.org/72233921:33
noonedeadpunkmaybe the thing is that I'm using minimal element for the image itself...21:33
mordredcorvus: fixed your comment and then squashed with the tests21:33
mordrednoonedeadpunk: we tend to use simple-init/glean instead of cloud-init21:34
mordrednoonedeadpunk: largely because the only thing we need such a thing for is installing ssh key and setting up networking - and cloud-init pulls in python deps and does a bunch of extra stuff21:34
mordrednoonedeadpunk: which is mostly just an explanation of why you might not find great cloud-init support21:34
mordredthe folks who use cloud-init are more likely to use the non-minimal base images which are based on the upstream published cloud images21:35
openstackgerritOleksandr Kozachenko proposed zuul/zuul-jobs master: Fix the checking helm_values_file definition  https://review.opendev.org/72251621:35
noonedeadpunkmordred: oh, I see.21:35
mordrednoonedeadpunk: (simple-init is the dib element name, glean is the program it runs that's not cloud-init but doe the minimla things)21:35
mordrednoonedeadpunk: glean also only works with config-drive - so you want that enabled of course21:36
noonedeadpunkthat's actually good notice21:37
noonedeadpunkok, thank you so much for your time!21:38
tristanCThere are 19 zuul-operator changes pending reviews, the tip is starting at https://review.opendev.org/720822 . This include useful refactor and other important updates like cert-manager integration and zuul-registry configuration. Please have a look when you have sometime.21:46
*** igordc has quit IRC21:51
ianwmordred: thanks, will look at the arm64 work.  i don't think it will make much difference, but i have a change out to drop pip-and-virtualenv from the arm images .. i'd really like it if we started this work without depending on that so we don't have to unwind it21:51
ianw... looks like frickler raised something on that ... let me look21:52
openstackgerritMerged zuul/nodepool master: Parallelize initial static node synchronization  https://review.opendev.org/72120521:58
mordredianw: ah - I see that you did see that22:06
mordredcorvus: the multiarch test job failed - but it looks like it's unhappy with zuul_return processing which is weird22:10
*** Goneri has quit IRC22:21
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Support multi-arch image builds with docker buildx  https://review.opendev.org/72233922:25
*** igordc has joined #zuul22:26
corvusmordred: that's a red herring; it has ignore_errors set to true22:41
corvusmordred: the real problem was the one you fixed -- fail_message22:41
corvusmordred: now it is intentionally failing because buildset_registry is not defined22:42
*** zxiiro has quit IRC22:42
corvusmordred: ah i see22:45
corvusmordred: the job starts by building an image "out of band" and pushing it to the fake intermediate registry in order to test the situation where we come into a real job with an image already in the intermediate registry22:45
corvusmordred: i think we can back out the "arch" setting from that one, and only add that to the normal image build part of the job22:47
corvusi will push an update22:47
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Support multi-arch image builds with docker buildx  https://review.opendev.org/72233922:48
corvusmordred: the job calls those the "upstream" and "downstream" images.  we want to leave the upstream image alone, and just test the multi-arch stuff on the downstream image.22:49
mordredcorvus: yes - I agree22:55
mordredcorvus: is our "upstream" image based on an image that's already multiarch?22:55
*** tosky has quit IRC22:58
*** igordc has quit IRC23:05
corvusmordred: debian:testing23:08
corvusso yes i think so23:08
openstackgerritMerged zuul/nodepool master: Siblings container build: set work dir to nodepool  https://review.opendev.org/72151423:29
openstackgerritIan Wienand proposed zuul/zuul master: [wip] intermediate jobs  https://review.opendev.org/72220023:39
openstackgerritMerged zuul/nodepool master: func-tests: drop debuntu specific env vars  https://review.opendev.org/72175423:50

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