Friday, 2020-07-24

openstackgerritMerged zuul/nodepool master: Use python3 for building releases.  Everywhere.  https://review.opendev.org/74276100:07
ianwdamn it, i did something that gave useful scroll in the debugger/inspect, but then reloaded.  now i can't figure out what i did again :/00:28
*** jamesmcarthur has joined #zuul01:01
openstackgerritIan Wienand proposed zuul/zuul master: web: restore scrollbars and scroll behaviour  https://review.opendev.org/74275901:10
ianwclarkb/corvus: perhaps have a look at ^ in your browser of choice when zuul returns and see if it fixes things for you too.  i won't claim it's right, but nothing gets people interested like an obviously incorrect patch :)01:12
ianwdoes anyone edit the webui with emacs?  i find that npm/react/whatever dies every time emacs writes out a temp file01:14
*** masterpe has quit IRC01:16
ianwhttps://github.com/facebook/create-react-app/issues/9056 - Development server errors due to emacs file lock01:16
*** masterpe has joined #zuul01:20
ianwbasically, there's no solution it seems.  great01:26
*** jamesmcarthur has quit IRC01:26
corvusianw: i edited the webpack config file -- it's a temporary solution, but i expect it to hold for a while (i don't plan on blowing that dir away).  tristanC turned of tempfiles.01:30
corvusoff01:30
*** jamesmcarthur has joined #zuul01:30
*** jamesmcarthur has quit IRC02:02
*** jamesmcarthur has joined #zuul02:03
*** jamesmcarthur has quit IRC02:08
*** jamesmcarthur has joined #zuul02:13
*** rlandy|bbl is now known as rlandy02:16
*** sgw has quit IRC02:20
ianwhttps://0a753ebf90e04a6fa838-d3b9488846fd47e876cca24d70452d35.ssl.cf2.rackcdn.com/742759/2/check/zuul-build-dashboard-opendev/bfe802e/npm/html/t/openstack/status02:22
ianwpage with scrolling from above for reference02:22
*** bhavikdbavishi has joined #zuul02:36
*** jamesmcarthur has quit IRC02:38
*** jamesmcarthur has joined #zuul02:38
*** jamesmcarthur has quit IRC02:43
*** bhavikdbavishi1 has joined #zuul02:44
*** bhavikdbavishi has quit IRC02:45
*** bhavikdbavishi1 is now known as bhavikdbavishi02:45
*** bhavikdbavishi has quit IRC03:33
*** jamesmcarthur has joined #zuul03:45
*** sgw has joined #zuul03:46
*** bhavikdbavishi has joined #zuul03:52
*** rfolco has quit IRC03:53
*** bhavikdbavishi has quit IRC04:13
*** bhavikdbavishi has joined #zuul04:15
*** smyers has quit IRC04:55
*** smyers has joined #zuul04:56
*** sgw has quit IRC04:56
*** sgw has joined #zuul05:07
*** saneax has joined #zuul05:25
*** jamesmcarthur has quit IRC05:49
*** jamesmcarthur has joined #zuul05:50
*** jamesmcarthur has quit IRC05:54
*** bhavikdbavishi1 has joined #zuul05:58
*** bhavikdbavishi has quit IRC06:00
*** bhavikdbavishi1 is now known as bhavikdbavishi06:00
*** jamesmcarthur has joined #zuul06:13
*** jamesmcarthur has quit IRC06:14
*** jamesmcarthur has joined #zuul06:17
*** jamesmcarthur has quit IRC06:22
*** bhavikdbavishi has quit IRC06:23
*** jamesmcarthur has joined #zuul06:27
*** dmellado has quit IRC06:27
*** jamesmcarthur has quit IRC06:40
*** jamesmcarthur has joined #zuul06:40
openstackgerritIan Wienand proposed zuul/zuul-jobs master: build-python-release: default to Python 3  https://review.opendev.org/74279906:41
openstackgerritIan Wienand proposed zuul/zuul-jobs master: build-python-release: default to Python 3  https://review.opendev.org/74279906:42
openstackgerritIan Wienand proposed zuul/zuul-jobs master: build-python-release: default to Python 3  https://review.opendev.org/74279906:43
*** jamesmcarthur has quit IRC06:44
*** sgw1 has quit IRC06:53
openstackgerritMerged zuul/zuul master: Re-add temporarily removed pending release notes  https://review.opendev.org/74235406:58
*** jcapitao has joined #zuul07:09
*** jpena|off is now known as jpena07:11
*** jamesmcarthur has joined #zuul07:13
*** bhavikdbavishi has joined #zuul07:13
*** jamesmcarthur has quit IRC07:20
*** tosky has joined #zuul07:37
*** harrymichal has joined #zuul07:37
openstackgerritTobias Henkel proposed zuul/zuul-jobs master: Consolidate common log upload code into module_utils  https://review.opendev.org/74273608:14
*** dmellado has joined #zuul08:20
openstackgerritTobias Henkel proposed zuul/zuul-jobs master: Consolidate common log upload code into module_utils  https://review.opendev.org/74273608:25
*** avass has quit IRC08:27
openstackgerritTobias Henkel proposed zuul/zuul-jobs master: Merge upload logs modules into common role  https://review.opendev.org/74273208:29
openstackgerritTobias Henkel proposed zuul/zuul-jobs master: Consolidate common log upload code into module_utils  https://review.opendev.org/74273608:29
openstackgerritTobias Henkel proposed zuul/zuul-jobs master: Merge upload logs modules into common role  https://review.opendev.org/74273208:32
openstackgerritTobias Henkel proposed zuul/zuul-jobs master: Consolidate common log upload code into module_utils  https://review.opendev.org/74273608:32
*** nils has joined #zuul08:59
*** bhavikdbavishi has quit IRC09:20
*** bhavikdbavishi has joined #zuul09:21
*** zbr is now known as zbr|ruck09:26
*** nils has quit IRC09:32
*** bhavikdbavishi has quit IRC09:46
*** bhavikdbavishi has joined #zuul09:53
openstackgerritTobias Henkel proposed zuul/zuul master: Support promote via tenant scoped rest api  https://review.opendev.org/74284810:24
*** antony-king has joined #zuul10:27
zbr|rucki wonder how hard to would be to enable annotations in zuul/gerrit using the same format as one from github actions, https://docs.github.com/en/actions/reference/workflow-commands-for-github-actions#setting-an-error-message10:31
*** harrymichal has quit IRC10:48
*** harrymichal has joined #zuul10:48
*** holser has joined #zuul10:57
tobiashzbr|ruck: you mean reporting file comments?10:59
*** harrymichal has quit IRC11:02
*** jcapitao is now known as jcapitao_lunch11:04
antony-kingHi, We are struggling with our zuul installation as it is now refusing to start up the scheduler with the following error "alembic.util.exc.CommandError: Can't locate revision identified by '269691d2220e'" - any ideas how to clear it ?11:13
zbr|rucktobiash: YES11:13
tobiashzbr|ruck: zuul already supports leaving file based comments, e.g. see https://review.opendev.org/#/c/742736/411:14
zbr|ruckon gh actions/workflows it is enough to produce this format on console and you get annotations for free.11:14
zbr|rucki know that zuul added ability to add comments on gerrit reviews recently, but i doubt is as easy11:15
zbr|ruckmaybe we can improve it to make it compatible11:15
tobiashimho zuul's way is more generic as you can parse the output of any tool and return it11:17
*** holser_ has joined #zuul11:17
zbr|rucki wonder if these are also working when referring to lines not covered inside review11:17
tobiashbut yes, that currently comes at the expense of some extra complexity11:17
tobiashnope, that doesn't work11:17
tobiashgerrit and github both only accept comments for files that are part of the change/pr11:18
tobiashthus zuul filters those11:18
zbr|ruckthat is a problem: think about a change bumps the linter and produce errors in various places11:18
tobiashthat cannot be solved in zuul11:19
tobiashin this case you have to look at the job log11:19
zbr|rucki am 100% github adds annotation to any file, unrelated to touched files11:19
zbr|ruckbut i do realise this is more gerrit than zuul11:19
*** holser_ has quit IRC11:19
tobiashmaybe github, I didn't test that but gerrit refuses certainly11:19
*** holser_ has joined #zuul11:20
*** holser has quit IRC11:20
zbr|ruckbut ti does make sense what I say? sometimes the error is not in touched code11:21
*** holser_ has quit IRC11:21
tobiashyes sure, but gerrit is limiting that and the linter log is just one click away ;)11:21
*** holser has joined #zuul11:22
zbr|ruckwith current implementation it may take a while for the newbie to find the error, especially if the linter is verbose and error was somewhere before the "42" character limit11:22
*** harrymichal has joined #zuul11:23
zbr|ruckin fact in older zuul versions is even worse, rdo still lacks the "more" link.11:23
antony-kingClient: HexChat 2.14.1 • OS: Ubuntu "bionic" 18.04 • CPU: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (800MHz) • Memory: Physical: 15.1 GiB Total (7.3 GiB Free) Swap: 953.1 MiB Total (640.7 MiB Free) • Storage: 179.0 GB / 269.1 GB (90.1 GB Free) • VGA: Intel Corporation Skylake GT2 [HD Graphics 520] @ Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers • Uptime: 1w 1d 13h 13m 51s11:23
tobiashzbr|ruck: for that it's always useful to tee the linter's output into a separate file and register it as an artifact in zuul11:24
zbr|ruckthat reminds me another thing i was looking to implement. making an html report visible as a "tab".11:25
zbr|rucknow when you produce a html file as an artifact, it is accessible from middle of summary page, not quite strait in the face11:26
tobiashthat would be interesting11:26
zbr|ruckif we can expose some artifacts as tabs (unittest results), it would improve the browsing experience11:26
zbr|ruckwe can likely even load them as an iframe to avoid loosing the navigation context11:27
openstackgerritSimon Westphahl proposed zuul/zuul master: Add optional support for circular dependencies  https://review.opendev.org/68535411:27
*** holser has quit IRC11:27
tobiashwe might be able to judge on the artifact type and if it's of type html or so add it as a tab11:27
zbr|ruckyep, or have another attribute that tells it to expose it as a tab11:28
*** holser has joined #zuul11:28
* zbr|ruck bit worried that some users may produce 20 html files, and that they may not want 20 tabs.11:28
tobiashthen judge on type html_for_inline_tab11:30
*** holser has quit IRC11:30
*** holser_ has joined #zuul11:30
*** holser_ has quit IRC11:31
*** jpena is now known as jpena|lunch11:32
*** holser has joined #zuul11:32
*** bhavikdbavishi has quit IRC11:48
*** holser_ has joined #zuul11:48
*** holser has quit IRC11:50
*** jamesmcarthur has joined #zuul11:56
*** holser has joined #zuul11:58
*** holser has quit IRC11:58
*** holser has joined #zuul11:59
*** holser_ has quit IRC11:59
*** jamesmcarthur has quit IRC12:00
*** bhavikdbavishi has joined #zuul12:01
tristanCantony-king: what versions of zuul are you using?12:02
*** holser has quit IRC12:03
*** holser has joined #zuul12:03
*** rfolco has joined #zuul12:03
antony-kingtristanC: we are using the latest 3.19 release from the docker environment (I am using the version tagged with "3")12:05
tristanCantony-king: that's odd, because revision '269691d2220e' doesn't seems to be released yet, it got introduced by the `Report retried builds via sql reporter.` changeid I5960df8a997c7ab81a07b9bd8631c14dbe22b8ab12:05
antony-kingtristanC: Ah, I was using the latest tag but thought I would be "smart" and use a blessed version - I did a docker-compose pull and then everything broke, hence switching to a tagged release. How do I get hold of the correct id ?12:07
*** holser has quit IRC12:08
*** holser has joined #zuul12:08
tristanCantony-king: that's a good question... i don't think zuul can do database rollback12:08
tristanCperhaps there is a magical sql expression that can fool alembic to use your existing database12:10
antony-kingtristanC: well I can move to latest again - I have no problems with that. I have tried forcing a rebuild of the alembic_version table but I get different error - "relation "alembic_version_pkc" already exists"12:11
tristanCantony-king: another solution would be to dump the database, remove the added field, drop the database and reimport12:12
tristanCantony-king: otherwise you might want to stick to master until the next release12:12
antony-kingTBH this is getting beyond my knowledge of database recovery (up until now it was a bit of a magic box); your suggestions may be the only solution. I will give them a go.12:14
*** jcapitao_lunch is now known as jcapitao12:15
*** bhavikdbavishi has quit IRC12:17
tristanCantony-king: i'm not an sql expert either, but running `mysqldump --databases zuul | gzip` periodically is quite handy for such situation12:17
antony-kingtristanC: The docker-compose pull of the latest tag seems to have done the trick, fingers crossed !. Maybe when I did the pull yesterday (when I broke the system), I got an inconsistent set. Thanks for the suggestions. Have a good day.12:19
tristanCantony-king: that's good to hear, have a good day too!12:20
*** antony-king has quit IRC12:29
openstackgerritTobias Henkel proposed zuul/zuul master: Support promote via tenant scoped rest api  https://review.opendev.org/74284812:36
*** jpena|lunch is now known as jpena12:39
*** harrymichal has quit IRC12:43
*** harrymichal has joined #zuul12:44
tobiashzuul-maint: could you please add https://review.opendev.org/718157 and child to your review list? This implements executor lifecycle improvements (graceful shutdown) that made our lives much much easier.12:47
*** avass has joined #zuul12:56
*** nils has joined #zuul13:24
felixedelzuul-maint: Regarding the scroll behaviour with pageup/down and spacebar in the new UI: I just took a look and the problem seems to be the drawer component which we use to display config errors. When I remove the drawwer component (which is kind of a wrapper around the page content) the scrolling works as expected.13:27
felixedelThough I'm not sure if that is the expected behaviour of the drawer or if I used that component the wrong way :D13:35
felixedelThere are also a few issues on GitHub https://github.com/patternfly/patternfly/issues?q=is%3Aissue+is%3Aopen+drawer regarding the drawer component (which is officially in "beta" state), so there might also be some fixes for that in the future13:36
*** bhavikdbavishi has joined #zuul13:45
*** jamesmcarthur has joined #zuul13:46
felixedelBut apart from that, everything I've read so far says that scrolling via spacebar or pageup/down is native browser behaviour. So to me that looks like the drawer is messing with this in some way13:48
corvusfelixedel: does it need to wrap the page, or can we just include it in in the banner?13:48
*** harrymichal has quit IRC13:49
*** harrymichal has joined #zuul13:50
felixedelcorvus: Not sure, currently it is inside the page, but wraps the content, so Page -> Drawer -> <content>. I think this was necessary to make the drawer show up next to the content without moving the content down below the drawer panel when opening it13:50
felixedelBut I can check that again13:50
*** harrymichal has quit IRC13:55
mnaserok, i'm actually digging down to fix the multiarch image fails13:56
felixedelI will check that on Monday13:57
mnaserso this is building on opendev -- "time="2020-07-24T12:33:42Z" level=fatal msg="Error initializing image from source docker://127.0.0.1:58547/vexxhost/node-labeler:latest: unsupported docker v2s2 media type: \"application/vnd.oci.image.layer.v1.tar+gzip\"""13:57
mnaseris it zuul-registry that runs on 127.0.0.1 ?13:58
mnaseri see https://github.com/containers/buildah/issues/2266#issuecomment-60841663913:58
mnaserwell, or i guess its the intermediate registry because that's probably the socat'd port13:59
corvusmnaser: it could be the temporary registry; do you have a link to the log?13:59
mnasercorvus: https://review.opendev.org/#/c/742276/ and the failed job https://zuul.opendev.org/t/vexxhost/build/3efbe52cd48f4738ba97c9fcf3aa5d8813:59
mnasercorvus: ok it is the socat, because the slurp task, when base64 decoding returned "2020/07/24 12:32:59 socat[18] N listening on AF=2 0.0.0.0:58547"14:01
mnaserwhich is the exact port i'm trying to push to, so i think this is zuul-registry (i.e. intermediate registry) that's not being happy14:01
corvusit's the buildset registry14:03
corvusmnaser: the path is buildx -> temp registry -> buildset registry -> intermediate registry14:03
mnaserah, in my case buildset registry is running on the same host as im doing a single docker image and not consuming it later (at least for now)14:04
corvusall three of those are zuul-registry14:04
mnasercorvus: would it then be useful to maybe add collect-docker-logs to the build docker image jobs, for debugging things like this in hte future14:05
corvusmnaser: yes14:05
corvusmnaser: i'm not convinced this is a registry problem yet14:05
mnasercorvus: i agree that there's no leads on where the issue is right now, i just don't have any weird things here, and im inheriting the opendev build jobs which i think zuul/nodepool also consumes14:06
mnaseri remain with the 'feeling' that it might be because of the way the golang parent image is built14:06
mnaserso some of the layers dont have the 'docker' format, so those layers fail to be accepted14:06
mnaserbut i feel like we'd see the same failure happen with non-multiarch images too14:07
*** sgw1 has joined #zuul14:07
corvusmnaser: did we talk about adding the docker flag to buildx?14:08
mnasercorvus: i think we did but at the time i didn't dig toooooo much into it as i was busy with a bunch of other stuff, but i plan slash need to get to the bottom of this today :>14:09
mnaserOpen10K8S is going to work on a zuul-jobs patch and then add a depends-on14:09
corvusmnaser: or maybe it was the '--format=docker' arg to skopeo14:10
*** dpawlik2 has quit IRC14:11
corvusmnaser: my gut says that if we examined all the registry traffic, we'd see this: https://github.com/containers/buildah/issues/2266#issuecomment-62657954814:12
corvusmnaser: i'm guessing the bug is in skopeo.  like 60% confident there, but enough that i think i'd start by adding that option and see if it works14:13
mnasercorvus: i think so too.  ok, let me throw a `--format=docker` attempt at it14:13
mnaseragreed14:13
*** bhavikdbavishi1 has joined #zuul14:19
*** bhavikdbavishi has quit IRC14:20
*** bhavikdbavishi1 is now known as bhavikdbavishi14:20
*** jamesmcarthur has quit IRC14:26
*** Goneri has joined #zuul14:26
*** jamesmcarthur has joined #zuul14:26
openstackgerritOleksandr Kozachenko proposed zuul/zuul-jobs master: Add docker format option to skopeo in push-to-intermediate-registry role  https://review.opendev.org/74289214:27
openstackgerritOleksandr Kozachenko proposed zuul/zuul-jobs master: Add docker format option to skopeo in push-to-intermediate-registry role  https://review.opendev.org/74289214:28
openstackgerritOleksandr Kozachenko proposed zuul/zuul-jobs master: Modify push-to-intermediate-registry role  https://review.opendev.org/74289214:29
*** nils has quit IRC14:41
corvustristanC: https://review.opendev.org/718157 and child are ready for your +314:42
*** jamesmcarthur has quit IRC14:50
*** jamesmcarthur has joined #zuul14:51
mnasercorvus: same failure, but, just realized that this happens in post in a trusted job14:52
mnaserso i dont think our depends-on is going to do much14:52
mnasercause it ran skopeo without it14:52
mnaseri think the best path might be to request a node hold14:53
mnasertry and run it with --format=docker, and then if that works.. that's 'proof'?  i dunno ;(14:53
corvusmnaser: yeah, we can do that; we also have full testing of this in zuul-jobs, you could probably modify the test to use the problematic images?14:57
corvusmnaser: but i'm happy to hold a node after the opendev rename maintenance14:57
mnasercorvus: oh yeah we could do that.. let's do the held node so i can try and see if i can make a very tiny reproducer on that system too14:58
mnasercorvus: for later, reviewing Open10K8S change https://review.opendev.org/#/c/742895/2 shows up an interesting problem, if our push to intermediate registry fails, we don't end up gathering logs so :(14:58
mnaserturns out we _do_ capture the logs, but if the post fails there, we stop14:59
corvusoops; we should separate that out into a different playbook15:04
corvus(we run all the post playbooks)15:04
corvusthat way the push can fail, we'll then run the logs playbook, and the job will still fail15:04
*** jcapitao has quit IRC15:04
corvus(we don't have to do anything tricky like save the error code and re-raise)15:04
*** sgw is now known as sgw_away15:06
*** holser_ has joined #zuul15:14
*** holser has quit IRC15:15
*** holser_ has quit IRC15:19
*** holser has joined #zuul15:19
-openstackstatus- NOTICE: We are renaming projects in Gerrit and review.opendev.org will experience a short outage. Thank you for your patience.15:23
*** holser_ has joined #zuul15:36
*** holser__ has joined #zuul15:39
*** holser has quit IRC15:39
*** holser_ has quit IRC15:40
mnasercorvus: can you have multiple post playbooks? that might be a TIL for me15:56
clarkbmnaser: yes it takes a list iirc15:56
clarkblooking for docs on that15:56
clarkbhttps://zuul-ci.org/docs/zuul/reference/job_def.html#attr-job.post-run yup it takes a list15:57
mnaserahhh ok perfect15:57
mnasercorvus: dang, skopeo runs on the executor :(16:18
mnaserso my hold is not really productive16:19
*** holser__ has quit IRC16:19
*** holser has joined #zuul16:19
clarkbmnaser: what you can do is run skopeo on the test node against the registry there16:20
clarkbmnaser: and at least confirm ti work if you add the flag16:20
mnaserclarkb: oh yes, that's a good idea16:20
mnaserthank you16:20
*** jpena is now known as jpena|off16:21
corvusthat should work, but also the skopeo process was copying to the intermediate registry using our secret creds16:22
corvusmnaser: so i think you'll want to maybe just copy both from and to the buildset registry16:22
corvusmnaser: hopefully that should still trigger the problem16:22
*** jamesmcarthur has quit IRC16:22
mnaserok cool, will do, let me pull down skopeo16:22
corvusi have to prepare for my hazmat shopping expidition; i'll be back in a little while and will finish up the nodepool release then and check back in with mnaser16:23
*** holser has quit IRC16:24
mnasercorvus: thanks, stay safe! and i'll be reporting here16:24
mnaserhttps://www.irccloud.com/pastebin/wSLlQ4AK/16:25
mnaserFATA[0000] unknown format "docker". Choose one of the supported formats: 'oci', 'v2s1', or 'v2s2'16:26
mnaserformat is defined as: "MANIFEST TYPE (oci, v2s1, or v2s2) to use when saving image to directory using the 'dir:' transport (default is manifest type of source)"16:27
*** SpamapS has quit IRC16:27
*** SpamapS has joined #zuul16:29
mnaserso it sounds to me like the image that's pushed to 'temp' registry is a 'source' format that cannot be consumed16:33
*** jamesmcarthur has joined #zuul16:39
*** zbr|ruck is now known as zbr16:41
mnaseri dont seem to be able to run docker buildx16:41
corvusmnaser: i'm really about to leave :)  but you might try skopeo copying the upstream images too, to see if they're in an unusable format upstream16:41
mnasercorvus: ah good call ,i can try that too16:41
mnaser`skopeo --insecure-policy copy --all docker://docker.io/golang:1.13 docker://insecure-ci-registry.opendev.org:5000/vexxhost/node-labeler:d830455b9d714906bb5b8d1e7fdaaaf5_latest` didn't blow up16:42
mnaseri mean, it complained at 'FATA[0001] Error trying to reuse blob sha256:31dd5ebca5efc5e96a425402fa85e492b02c8fe757dfd3edfdea2a7c67322909 at destination: unable to retrieve auth token: invalid username/password: unauthorized: authentication required ' but thats expected16:42
mnaseroh i need DOCKER_CLI_EXPERIMENTAL=enabled16:44
openstackgerritMerged zuul/zuul master: Implement graceful termination for the executor  https://review.opendev.org/71815717:02
openstackgerritMerged zuul/zuul master: Ensure deletion of the command socket  https://review.opendev.org/71977617:02
*** sgw_away is now known as sgw17:23
*** hamalq has joined #zuul17:29
*** jamesmcarthur has quit IRC17:30
corvusmnaser: try copying it to the buildset registry instead of the intermediate registry17:37
mnasercorvus: oh, so from docker.io to buildset, the buildset to intermediate ? yeah that makes sense as a repro17:38
corvusmnaser: you won't be ably to copy anything to intermediate17:38
corvusmnaser: we'll just have to use the buildset registry to stand in for the intermediate registry17:39
corvusintermediate has production creds we need to keep private, but you can do whatever you want with the buildset registry, or the temp registry17:39
*** AJaeger has quit IRC17:45
mnaserok, finally around to take this17:49
*** bhavikdbavishi has quit IRC17:52
mnasercorvus: i'm really sorry but i'm really struggling to troubleshoot.  i can add your keys to help, but in this case buildset registry needs me to maybe do auth first?17:53
mnaserhttps://www.irccloud.com/pastebin/PJUl2IE1/17:53
mnasertrying to copy to the temp registry which seems to be on 0.0.0.017:54
mnaser:5000 leads to `Get https://zuul-jobs.buildset-registry:5100/v2/: http: server gave HTTP response to HTTPS client `17:54
mnaseri have to use zuul-jobs.buildset-registry cause if i use localhost or anything else, it complains about ssl cert validity17:54
corvusmnaser: what's the ip?17:54
mnaser`error pinging docker registry localhost:15000: Get https://localhost:15000/v2/: x509: certificate is valid for zuul-jobs.buildset-registry, 198.72.124.203, not localhost `17:54
mnaser198.72.124.20317:54
mnaserand https://zuul.opendev.org/t/vexxhost/build/d830455b9d714906bb5b8d1e7fdaaaf5 is the build if we need to 'rebuild' things17:55
mnaseri'm happy to watch in a screen :)17:55
*** jamesmcarthur has joined #zuul17:56
corvusmnaser: this is working for me: skopeo --insecure-policy copy --all docker://docker.io/golang:1.13 docker://zuul-jobs.buildset-registry:5000/golang:1.1317:56
corvusmnaser: note the port17:56
corvus5000 not 1500017:56
mnaserah, i was using 5100 because `docker ps` seemed to tell me 5100 was going to the registry17:57
corvushrm that is confusing17:59
corvusmnaser: oh the socat is on 500018:01
mnaseryeah, i think that is for the scenario where buildset is hosted on another vm18:01
mnaserbut in this case, it is hosted on teh same system, so its a 'noop'18:01
corvusmnaser: so it's localhost:5000(socat) -> localhost:15000(buildset registry)18:01
mnaserbut i guess the 'docker login' happened. for port 5000, so thats why it works with auth18:01
corvusmnaser: exactly18:01
mnaseryeah ~/.docker/config.json confirms that, ok, well that helps a bit18:02
corvusmnaser: i started that copy, and it was running, but i aborted after 3 images -- i'll leave it to you to continue debugging18:02
mnasercorvus: yes, that's helpful, i'll try to do something of doing copy => copy and see if thats a possible failure case, thank you18:02
corvusmnaser: and if we need to get more info from the buildset registry, we can -- it's pretty easy to edit it in place and print debug output, or inspect the storage, etc (since it's all local files)18:03
corvusmnaser: i notice that the test registry (localhost:5100) is the docker registry software, not zuul-registry -- that may be helpful for testing too18:04
mnaserright, yeah, so i think this also means that we are at a state where copying the same image is failing18:05
mnaser`skopeo --insecure-policy copy --all docker://zuul-jobs.buildset-registry:5000/vexxhost/node-labeler:latest docker://zuul-jobs.buildset-registry:5000/vexxhost/node-labeler:d830455b9d714906bb5b8d1e7fdaaaf5_latest` fails18:06
corvusi've re-enqueued the nodepool tag so we can re-run the python release18:06
mnaserinteresting, it's 'resolving' the image for both arm64 and amd64 to be the same one... this could be 'ok' though, i'm digging https://www.irccloud.com/pastebin/ti7J0Hxy/18:12
clarkbcorvus: nodepool python release succeeded18:12
*** gmann is now known as gmann_lunch18:13
corvushuzzah18:17
corvusemail sent18:19
mnaseroh18:28
mnaserunless im missing something it looks like no projects are doing multiarch builds.. except for python base image right now?18:28
mnasersearching for `linux/arm64` doesn't yield anything except system-config18:28
clarkbmnaser: system-config/zuul.d/docker-images/python.yaml:18:29
clarkber drop the : suffix18:29
mnaseryeah, hence 'except system-config' i am looking at the build jobs there now to see if the build logs look.. different18:30
clarkbthose are doing it. We have been trying to get nodepool to do it but the compiles for cryptography, bcrypt, and pynacl are just too slow so we've disabled it18:30
clarkbmnaser: you can look at what nodepool did look like I got it working with hacks to use openstack constraints and python wheel cache18:30
*** jamesmcarthur has quit IRC18:30
clarkbmnaser: https://review.opendev.org/#/c/741973/ is the end of that stack and should show you what it looks like18:31
mnaserclarkb: oh i see, yeah in my case it's a golang project and it builds in 30s, so i'm good on that front, except for the publishing, but looking at 'working' publish logs will be very helpful18:31
mnaserok so something interesting is that in my failure case, my buildset-registry is on teh same host18:35
*** jamesmcarthur has joined #zuul18:41
openstackgerritMohammed Naser proposed zuul/zuul-jobs master: dnm: test multiarch  https://review.opendev.org/74296718:46
*** jamesmcarthur has quit IRC18:47
*** jamesmcarthur has joined #zuul18:50
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Allow ara-report to run on any node  https://review.opendev.org/74297118:52
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Allow ara-report to run on any node  https://review.opendev.org/74297118:56
mnaseri learned something today19:02
mnaseryou don't need to do apt clean all19:02
mnaserhttps://github.com/moby/moby/blob/03e2923e42446dbb830c654d0eec323a0b4ef02a/contrib/mkimage/debootstrap#L82-L10519:02
fungii assume you mean specifically when doing docker container builds19:11
fungijudging from that code snippet19:11
mnaserfungi: yes, correct19:18
mnaseralso -- tried another much simpler build and not seeing that same issue -- https://review.opendev.org/#/c/742976/19:18
*** gmann_lunch is now known as gmann19:19
mnaserit must be something to do either with base image or multistage19:19
mnaserbut nodepool does multistage, so that narrows it down to the image19:23
mnaserOOOH, i use FROM scratch for the final image19:25
mnaseri wonder if that has to do with it19:25
corvusmnaser: oooh that sounds plausible.  also, neat.  :)19:28
mnasercorvus: i will try to rebuild that same thing with buildx but not using from scratch19:28
mnasercorvus: well, that did it..19:38
mnaserchanging the FROM scratch to FROM golang:1.13 .. fixed it ;\19:38
mnaserim gonna guess that maybe its literally taking FROM scratch.. or something19:42
corvusmnaser: okay, so from scratch, with buildx, produces something that skopeo doesn't like?19:42
mnasercorvus: yeah, let me try to make an even smaller reproducer19:42
mnaserok i have a really small reproducer19:46
mnasercorvus: http://paste.openstack.org/show/796298/ this is a 100% fail19:47
mnaserso i think the thing here is 'scratch' might actually exist in registry as `application/vnd.oci.image.layer.v1.tar+gzip` format19:48
openstackgerritJimmy McArthur proposed zuul/zuul-website master: Add new Supporter Logos  https://review.opendev.org/74298419:55
corvusmnaser: huh, i was thinking that maybe buildx built it in that format19:55
corvusjamesmcarthur: i think you may be missing some "git add"s in that change19:57
mnasercorvus: or that too, i don't know enough about the details to be honest :(19:57
corvusmnaser: can you retry your test case with the temporary registry?19:57
mnasercorvus: ah good idea!  one second19:57
corvusif it fails, that should completely exclude zuul-registry19:58
mnaser"Error initializing source docker://127.0.0.1:5100/test:latest: error pinging docker registry 127.0.0.1:5100: Get https://127.0.0.1:5100/v2/: http: server gave HTTP response to HTTPS client " -- i was running into this earlier19:59
corvusmnaser: "127.0.0.1:5100" is the temp registry, and should be logged in19:59
mnaserlet me find how to force http19:59
mnaser`--src-tls-verify=false` seems to be the trick20:00
mnaser`FATA[0000] Error initializing image from source docker://127.0.0.1:5100/test:latest: unsupported docker v2s2 media type: "application/vnd.oci.image.layer.v1.tar+gzip"` -- yep, ain't the registries' fault20:00
corvusw00t20:00
mnaserits a buildx/skopeo thing20:00
corvusmnaser: i think maybe that's enough to open a skopeo issue20:00
mnaseryeah.  the reproducer is helpful20:01
*** SpamapS has quit IRC20:03
mnasercorvus: https://github.com/containers/skopeo/issues/99120:05
*** SpamapS has joined #zuul20:05
corvusmnaser: ++20:14
mnaserin the meantime my workaround is to do FROM debian:stable-slim .. good enough20:15
mnaserah its so nice that this is working, the chrony image is already deployed and working across multiple archs :D20:15
corvusmnaser: want to leave that node held for a bit in case they have followups?20:15
mnasercorvus: i think that might be useful indeed20:15
corvuscool, will do20:15
*** jamesmcarthur has quit IRC20:17
corvusdmsimard: sent announcement http://lists.zuul-ci.org/pipermail/zuul-announce/2020-July/000080.html20:19
*** jamesmcarthur has joined #zuul20:36
jamesmcarthurOh crap.20:38
jamesmcarthurCorvus: so true.20:38
openstackgerritJimmy McArthur proposed zuul/zuul-website master: Add new Supporter Logos  https://review.opendev.org/74298420:47
jamesmcarthurcorvus: should be there now: https://review.opendev.org/#/c/742984/20:47
*** jamesmcarthur has quit IRC20:49
*** jamesmcarthur has joined #zuul20:59
openstackgerritJimmy McArthur proposed zuul/zuul-website master: Add new Supporter Logos  https://review.opendev.org/74298421:01
*** rfolco has quit IRC21:07
*** rfolco has joined #zuul21:08
*** rfolco has quit IRC21:12
tristanCjamesmcarthur: hello, has the survey results been published somewhere?21:15
jamesmcarthurtristanC: not yet.  We typically let the surveys run through late July/early August.  Then we have to anonymize the data and do analysis.21:26
jamesmcarthurWe're looking for community volunteers if anyone is interested.  Only requirement is to sign an NDA to protect the anonymity of the companies that respond.21:26
*** jamesmcarthur has quit IRC21:34
*** jamesmcarthur has joined #zuul21:48
*** jamesmcarthur has quit IRC21:55
*** rlandy has quit IRC22:14
mnasermm, this seems like a zuul bug22:21
mnaserhttps://review.opendev.org/#/c/742981/1 -- you can see that the `openstack-operator:images:upload:chronyd` job was actually removed (specifically https://review.opendev.org/#/c/742981/1/zuul.d/chronyd-jobs.yaml )22:22
mnaseryet zuul still ... ran it?22:22
mnasergit grep shows no references when checking that out locally22:22
clarkbmnaser: for debugging that the zuul inventory for the job is a good start it shows you wher ethe job came from22:22
*** _erlon_ has quit IRC22:23
mnaserhttps://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_2e2/742981/1/gate/openstack-operator:images:upload:chronyd/2e2ab0d/zuul-info/inventory.yaml22:23
mnaserthe file it pulls it from has been deleted?22:24
mnaser<Job openstack-operator:images:upload:chronyd branches: None source: vexxhost/openstack-operator/zuul.d/chronyd-jobs.yaml@master#13> -> <Job openstack-operator:images:upload:chronyd branches: None source: vexxhost/openstack-operator/zuul.d/chronyd-jobs.yaml@master#26>22:24
clarkbya that implies to me that it is using merged state22:24
clarkbdoes it use secrets maybe?22:24
mnaserooou, `vexxhost-upload-docker-image` does use secrets22:25
mnaserbut this job was running in gate so it .. should be ok?22:25
clarkbya gate is post review, but I'm not sure if it uses speculative state for secrets?22:26
clarkbcorvus: ^22:26
clarkbI wonder if removals from job lists can be speculatively applied regardless (since it removes potentially dangerous things)22:26
corvusmnaser, clarkb: i suspect it's because of the file removal22:32
corvusand i agree, that's a little buggish22:32
corvusit might be due to how the caching is implemented22:32
corvusmnaser: can you try truncating the file first, then removing it in a second change?22:33
corvusi think that would confirm the bug/provide immediate relief22:33
mnasercorvus: ok will try that’s22:46
mnasercorvus: that did it. https://usercontent.irccloud-cdn.com/file/9q7ET5vc/image.png22:49
*** rfolco has joined #zuul22:54
*** holser has joined #zuul22:57
*** rfolco has quit IRC22:58
*** hamalq has quit IRC23:10
*** holser has quit IRC23:19
*** holser has joined #zuul23:29
*** sgw1 has quit IRC23:35
*** tosky has quit IRC23:55

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