Zero-to-jupyterhub-k8s: Investigate recent errors and failures in Travis test builds

Created on 22 Dec 2017  路  14Comments  路  Source: jupyterhub/zero-to-jupyterhub-k8s

Recent Travis builds have been throwing errors or failing since about #327. The passing PRs since then do not appear to have run the build fully.

Perhaps #365 related??? or build.py changes.

Most helpful comment

Thank you, @willingc! I rebased https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/365 and it is passing now! Yay we fixed the build! <3

All 14 comments

I'm convinced it's a race condition somewhere, it's hard to investigate because the same script passes on my local machine :'(

@yuvipanda Does this line look correct to you in .travis.yml ?

- . ci/minikube.env

yup, it does!

I suspect the problem might be fixed by https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/367, let's see!

Why isn't that line . ./ci/minikube.env or source ./ci/minikube.env?

Not sure why @minrk picked the particular style, I think all three variants would be equivalent at that point.

Mmm... I don't think @minrk wrote those lines ;-)

Ah, it's @manics - apologies for misattributing :)

I've actual error messages now (see https://travis-ci.org/jupyterhub/zero-to-jupyterhub-k8s/builds/320458819)!

Warning  Failed                 11s               kubelet, travis-job-f9b24008-9030-400d-bec9-cf2c1b1a5746  Failed to pull image "jupyterhub/k8s-hub:8a3d6f2": rpc error: code = Unknown desc = Error response from daemon: manifest for jupyterhub/k8s-hub:8a3d6f2 not found

seemst o be the culprit. Investigating more

https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/350 was the last PR that was successfully merged, and I think that's what broke all succeeding PRs. It looks like the hub image wasn't pushed properly from the deploy step, so all future builds keep looking for a hub image they can't find.

I've fixed it now! I think #350 fixed our deploy process, but the merge of #314 happened when it was broken, causing the image pushes to not happen.

So for this case, I could fix it by making sure the image that these PRs are looking for is present. I did so by:

git checkout 8a3d6f2
./build.py --push

This has made all the PRs work!

365 is still failing, but I'd like to get https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/367 merged so we can debug it more easily.

@yuvipanda Just reviewed #367 if you wish to merge.

Thank you, @willingc! I rebased https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/365 and it is passing now! Yay we fixed the build! <3

I'm closing this now since our builds are good to go :)

Was this page helpful?
0 / 5 - 0 ratings