Installng jupyterhub wiht helm failed

JupyterHub
1

Hi ,

This is my first post in this forum .

i am trying ot deploy jupyterhub on Redhat openshift with helm 3 .

I am getting this below errror .

$ helm upgrade --cleanup-on-fail --install $RELEASE jupyterhub/jupyterhub --namespace $NAMESPACE --create-namespace --version=0.10.6 --values config.yaml
Error: UPGRADE FAILED: pre-upgrade hooks failed: timed out waiting for the condition

2

Any update on this ?

3

Have you looked at your pods using kubectl ... describe pods?

4

I have tried again with single subnet but still fails .

looks like the api server subnet is not talking to weave net cni

[root@master ~]# kubectl logs coredns-74ff55c5b-9wbnx -n kube-system
.:53
[INFO] plugin/reload: Running configuration MD5 = db32ca3650231d74073ff4cf814959a7
CoreDNS-1.7.0
linux/amd64, go1.14.4, f59c03d
[ERROR] plugin/errors: 2 519613332737584968.506009032237894752. HINFO: read udp 10.32.0.3:56304->192.168.100.1:53: read: no route to host
[ERROR] plugin/errors: 2 519613332737584968.506009032237894752. HINFO: read udp 10.32.0.3:60726->192.168.100.1:53: read: no route to host
[root@master ~]#

5

[root@master ~]# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.96.0.1 443/TCP 17m
[root@master ~]#

6

192.168.100.0 --. Public IP range of master and worker nodes
10.96.0.1 — cluster IP of api-server
10.32.0.0 – range of weave net cni
10.224.0.0 – IP arange of pod cidr .

Where i am going wrong ?

7

It sounds like your K8S cluster is having problems. You may be able to get more help on a kubernetes or openshift forum.

8

I have tried it on Redhat Openshift Sandbox and still doesnt work out . This seems to be some issue with the helm repo .

$ helm upgrade --cleanup-on-fail --install $RELEASE jupyterhub/jupyterhub --namespace $NAMESPACE --create-namespace --version=0.11.1 --values config.yaml
Release “jhub” does not exist. Installing it now.

Error: failed pre-install: timed out waiting for the condition

$ helm upgrade --cleanup-on-fail --install $RELEASE jupyterhub/jupyterhub --namespace $NAMESPACE --create-namespace --version=0.10.6 --values config.yaml
Error: UPGRADE FAILED: pre-upgrade hooks failed: timed out waiting for the condition

1 Like
9

This is probably due to Openshift being more restrictive than a standard Kubernetes distribution. You could try running kubectl describe on the failed resources to see if that gives you any clues.

There are a few posts on the internet about people running JupyterHub on OpenShift, so you might find more ideas through Google.

10

HI! @manics

I have the same problem.
I can only start two kinds of pods, and then an error occurs. pod name: hook-image-puller-brltq and hook-image-awaiter-2zd6h

The following is my environmental information.

Helm error message：

[root@k8s-master helm]# helm upgrade --cleanup-on-fail --install v3.7.0 jupyterhub/jupyterhub --namespace limy-test --create-namespace --version=1.1.3 --values config.yaml
Release "v3.7.0" does not exist. Installing it now.
Error: failed pre-install: timed out waiting for the condition

config.yaml file information：

[root@k8s-master helm]# cat config.yaml
hub:
  config:
    JupyterHub:
      admin_access: true
      admin_users:
        - limy
        - test

pod error message：

[root@k8s-master kubespawner]# kubectl logs hook-image-awaiter-l8h8w -n limy-test
2021/09/23 07:15:35 [DEBUG] GET https://kubernetes.default.svc:443/apis/apps/v1/namespaces/limy-test/daemonsets/hook-image-puller
2021/09/23 07:16:15 [ERR] GET https://kubernetes.default.svc:443/apis/apps/v1/namespaces/limy-test/daemonsets/hook-image-puller request failed: Get "https://kubernetes.default.svc:443/apis/apps/v1/namespaces/limy-test/daemonsets/hook-image-puller": dial tcp: lookup kubernetes.default.svc on 10.96.0.10:53: read udp 10.244.113.152:58140->10.96.0.10:53: i/o timeout
2021/09/23 07:16:15 [DEBUG] GET https://kubernetes.default.svc:443/apis/apps/v1/namespaces/limy-test/daemonsets/hook-image-puller: retrying in 5s (5 left)
2021/09/23 07:17:00 [ERR] GET https://kubernetes.default.svc:443/apis/apps/v1/namespaces/limy-test/daemonsets/hook-image-puller request failed: Get "https://kubernetes.default.svc:443/apis/apps/v1/namespaces/limy-test/daemonsets/hook-image-puller": dial tcp: lookup kubernetes.default.svc on 10.96.0.10:53: read udp 10.244.113.152:50998->10.96.0.10:53: i/o timeout
2021/09/23 07:17:00 [DEBUG] GET https://kubernetes.default.svc:443/apis/apps/v1/namespaces/limy-test/daemonsets/hook-image-puller: retrying in 10s (4 left)
2021/09/23 07:17:50 [ERR] GET https://kubernetes.default.svc:443/apis/apps/v1/namespaces/limy-test/daemonsets/hook-image-puller request failed: Get "https://kubernetes.default.svc:443/apis/apps/v1/namespaces/limy-test/daemonsets/hook-image-puller": dial tcp: lookup kubernetes.default.svc on 10.96.0.10:53: read udp 10.244.113.152:53431->10.96.0.10:53: i/o timeout
2021/09/23 07:17:50 [DEBUG] GET https://kubernetes.default.svc:443/apis/apps/v1/namespaces/limy-test/daemonsets/hook-image-puller: retrying in 20s (3 left)

Helm version information:

[root@k8s-master kubespawner]# helm version
version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}

kubernetes version information:

[root@k8s-master kubespawner]# kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:59:11Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:53:14Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"linux/amd64"}
11

As mentioned above if you’re using OpenShift you may need to do some searching yourself, as it is more restrictive than a standard Kubernetes cluster.