Time out error when downloading images #16545
Comments
fragpic
added
the
kind/bug
che-bot
added
the
status/need-triage
|
@cbyreddy |
ericwill
added
area/chectl
|
storage provision error, yes. Workaround is to use the storageClassName in crd: minikube creates a VM for setting up the cluster so /data and /data/wksp have to be created and chmod 777 in the vm for this to work. Sames goes to whatever path you choose if you modify this values. SIDE NOTE: this could also require to disable default tls option in yaml too: SIDE NOTE2: also the domain should be forced in yaml: #file: /usr/local/lib/chectl/templates/che-operator/crds/org_v1_che_cr.yaml
postgresPVCStorageClassName: eclipseche
workspacePVCStorageClassName: eclipsechewksp
ingressDomain: 'minikube-lan-ip.nip.io' #CHANGE TO A REAL minikube-lan-ip
tlsSupport: false create storage classes and volumes accordingly: #file: storageclass_and_volumes.yaml
apiVersion: v1
kind: PersistentVolume
metadata:
name: eclipsechewksp
labels:
type: local
spec:
storageClassName: eclipsechewksp
capacity:
storage: 5Gi
accessModes:
- ReadWriteOnce
hostPath:
path: "/data/wksp"
---
apiVersion: v1
kind: PersistentVolume
metadata:
name: eclipseche
labels:
type: local
spec:
storageClassName: eclipseche
capacity:
storage: 5Gi
accessModes:
- ReadWriteOnce
hostPath:
path: "/data/"
---
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: eclipsechewksp
annotations:
storageclass.kubernetes.io/is-default-class: "false"
provisioner: k8s.io/minikube-hostpath
reclaimPolicy: Retain
---
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: eclipseche
annotations:
storageclass.kubernetes.io/is-default-class: "false"
provisioner: k8s.io/minikube-hostpath
reclaimPolicy: Retainafter this use the additional argument in chectl server:start: chectl server:start --platform minikube --multiuser --che-operator-cr-yaml=/usr/local/lib/chectl/templates/che-operator/crds/org_v1_che_cr.yamlupon attempts to start chectl (using chectl server:delete and server:start again) the postgres folder (called userdata) has to be removed and the volumes in the minikube cluster have to ve removed and created again (using kubectl delete -f and apply -f with the provided yaml). so to recap: chectl server:delete
kubectl delete -f <storageclass_and_volumes.yaml>
rm -rf /data/userdatato try again: kubectl apply -f <storageclass_and_volumes.yaml>
chectl server:start --platform minikube --multiuser --che-operator-cr-yaml=/usr/local/lib/chectl/templates/che-operator/crds/org_v1_che_cr.yaml |
I was having issues with v1.8 too so I tried again using k3s. I got to a much later stage of the install process before it errored out again. Any idea what could have gone wrong now? I don't think it is a storage provisioning issue but I'm not sure. |
|
I have had this problem with both |
|
@cbyreddy Pls provide logs for the second installation. |
Sorry, here you go. This seems to be the issue but I'm not sure
|
|
related one |
Is there anything I can try to fix the error or is it a bug? |
|
It is a bug. I will take a look on it later. What I can suggest for now:
|
|
@cbyreddy |
|
@zarinfam |
|
@cbyreddy |
Describe the bug
Times out when scheduling/downloading images.
Logs indicate timeout waiting for postgres volumes to be bound
Che version
Steps to reproduce
ran
chectl server:start --platform minikube --multiuser
Expected behavior
Eclipse che is deployed and a url is generated
Runtime
kubectl version)oc version)minikube versionandkubectl version)minishift versionandoc version)docker versionandkubectl version)minikube version: v1.9.1
commit: d8747aec7ebf8332ddae276d5f8fb42d3152b5a1
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:50:46Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Screenshots
✔ Verify Kubernetes API...OK✈️ Minikube preflight checklist
✔ 👀 Looking for an already existing Eclipse Che instance
✔ Verify if Eclipse Che is deployed into namespace "che"...it is not
✔
✔ Verify if kubectl is installed
✔ Verify if minikube is installed
✔ Verify if minikube is running
↓ Start minikube [skipped]
→ Minikube is already running.
✔ Check Kubernetes version: Found v1.18.0.
✔ Verify if minikube ingress addon is enabled
✔ Enable minikube ingress addon
✔ Retrieving minikube IP and domain for ingress URLs...172.17.0.2.nip.io.
Eclipse Che logs will be available in '/tmp/chectl-logs/1586030573786'
✔ Start following logs
✔ Start following Operator logs...done
✔ Start following Eclipse Che logs...done
✔ Start following Postgres logs...done
✔ Start following Keycloak logs...done
✔ Start following Plugin registry logs...done
✔ Start following Devfile registry logs...done
✔ Start following events
✔ Start following namespace events...done
✔ 🏃 Running the Eclipse Che operator
✔ Copying operator resources...done.
✔ Create Namespace (che)...It already exists.
✔ Create ServiceAccount che-operator in namespace che...It already exists.
✔ Create Role che-operator in namespace che...It already exists.
✔ Create ClusterRole che-operator...It already exists.
✔ Create RoleBinding che-operator in namespace che...It already exists.
✔ Create ClusterRoleBinding che-operator...It already exists.
✔ Create CRD checlusters.org.eclipse.che...It already exists.
✔ Waiting 5 seconds for the new Kubernetes resources to get flushed...done.
✔ Create deployment che-operator in namespace che...It already exists.
✔ Create Eclipse Che cluster eclipse-che in namespace che...It already exists.
❯ ✅ Post installation checklist
❯ Eclipse Che pod bootstrap
✖ scheduling
→ ERR_TIMEOUT: Timeout set to pod wait timeout 300000. podExist: false, currentPhase: undefined
downloading images
starting
Retrieving Eclipse Che server URL
Eclipse Che status check
› Error: Error: ERR_TIMEOUT: Timeout set to pod wait timeout 300000. podExist: false, currentPhase: undefined
› Installation failed, check logs in '/tmp/chectl-logs/1586030573786'
Installation method
Environment
Eclipse Che Logs
time="2020-04-04T20:02:45Z" level=info msg="Default 'info' log level is applied"
time="2020-04-04T20:02:45Z" level=info msg="Go Version: go1.12.12"
time="2020-04-04T20:02:45Z" level=info msg="Go OS/Arch: linux/amd64"
time="2020-04-04T20:02:45Z" level=info msg="operator-sdk Version: v0.5.0"
time="2020-04-04T20:02:45Z" level=info msg="Operator is running on Kubernetes"
time="2020-04-04T20:02:45Z" level=info msg="Registering Che Components Types"
time="2020-04-04T20:02:45Z" level=info msg="Starting the Cmd"
time="2020-04-04T20:02:45Z" level=info msg="Waiting for PVC postgres-data to be bound. Default timeout: 10 seconds"
time="2020-04-04T20:02:55Z" level=warning msg="Timeout waiting for a PVC postgres-data to be bound. Current phase is Pending"
time="2020-04-04T20:02:55Z" level=warning msg="Sometimes PVC can be bound only when the first consumer is created"
time="2020-04-04T20:02:56Z" level=info msg="Waiting for deployment postgres. Default timeout: 420 seconds"
The text was updated successfully, but these errors were encountered: