Gitpod: Having problems during installation

Created on 19 Mar 2020 · 18Comments · Source: gitpod-io/gitpod

I'm trying to install Gitpod onto my kind Kubernetes cluster.

After installing 'kind`, I create a cluster. Then I clone this repository and follow the instructions, but there's a problem after the third command under installation.

First of all, I don't have the configuration.txt file, and after the update, it fails with

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

Commands with output:

kind create cluster

Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.17.0) 🖼 
 ✓ Preparing nodes 📦  
 ✓ Writing configuration 📜 
 ✓ Starting control-plane 🕹️ 
 ✓ Installing CNI 🔌 
 ✓ Installing StorageClass 💾 
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Have a question, bug, or feature request? Let us know! https://kind.sigs.k8s.io/#community 🙂

kubectl cluster-info --context kind-kind

Kubernetes master is running at https://127.0.0.1:32769
KubeDNS is running at https://127.0.0.1:32769/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

Clone and cd into self-hosted
Edited values.yaml (changed gitpod.hostname and gitpod.components.proxy.loadBalancerIP)

helm repo add charts.gitpod.io https://charts.gitpod.io

"charts.gitpod.io" has been added to your repositories

helm dep update

Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "charts.gitpod.io" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading gitpod from repo https://charts.gitpod.io/
Deleting outdated charts

helm upgrade --install $(for i in $(cat configuration.txt); do echo -e "-f $i"; done) gitpod .

cat: configuration.txt: No such file or directory
Release "gitpod" does not exist. Installing it now.
Error: failed post-install: timed out waiting for the condition

Whole console output

[server@server self-hosted]$ kind create cluster
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.17.0) 🖼 
 ✓ Preparing nodes 📦  
 ✓ Writing configuration 📜 
 ✓ Starting control-plane 🕹️ 
 ✓ Installing CNI 🔌 
 ✓ Installing StorageClass 💾 
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Have a question, bug, or feature request? Let us know! https://kind.sigs.k8s.io/#community 🙂
[server@server self-hosted]$ 
[server@server self-hosted]$ kubectl cluster-info --context kind-kind
Kubernetes master is running at https://127.0.0.1:32769
KubeDNS is running at https://127.0.0.1:32769/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
[server@server self-hosted]$ kind get clusters
kind
[server@server self-hosted]$ cd ..
[server@server tmp]$ mv self-hosted/ self_hosted
[server@server tmp]$ git clone https://github.com/gitpod-io/self-hosted
Cloning into 'self-hosted'...
remote: Enumerating objects: 11, done.
remote: Counting objects: 100% (11/11), done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 71 (delta 3), reused 4 (delta 1), pack-reused 60
Unpacking objects: 100% (71/71), 21.28 KiB | 239.00 KiB/s, done.
[server@server tmp]$ cd self-hosted
[server@server self-hosted]$ git remote rename origin upstream
[server@server self-hosted]$ vim values.yaml 
[server@server self-hosted]$ helm repo add charts.gitpod.io https://charts.gitpod.io
"charts.gitpod.io" has been added to your repositories
[server@server self-hosted]$ helm dep update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "charts.gitpod.io" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading gitpod from repo https://charts.gitpod.io/
Deleting outdated charts
[server@server self-hosted]$ helm upgrade --install $(for i in $(cat configuration.txt); do echo -e "-f $i"; done) gitpod .
cat: configuration.txt: No such file or directory
Release "gitpod" does not exist. Installing it now.
Error: failed post-install: timed out waiting for the condition

I might be missing something or doing something wrong.
I found the definition for the configuration.txt here, but I'm not sure if it's mandatory, because it says To get Gitpod running quickly, you may skip this chapter. and that's what I'm trying to do :smile:.

self-hosted

Source

MGlolenstine

All 18 comments

Hi @MGlolenstine !

that's an awesomely detailed bug report.

The message Error: failed post-install: timed out waiting for the condition can mean that a Kubernetes Job named db-migraiton failed. Right after running helm upgrade --install, can you check if there is a pod named db-migraiton... and inspect the log output of that pod? You can do that by running kubectl logs db-migraiton-foobarbaz, with foobarbaz being a random ID you'll see when you list the pods.

The pod db-migraiton tries to connect to your MySQL database and install or upgrade the database schema.

The file configuration.txt is not mandatory... The idea is that you list the filenames of all value.yamls that you have customized in there, to that in the end you can run

helm upgrade --install $(for i in $(cat configuration.txt); do echo -e "-f $i"; done) gitpod .

instead of running

helm upgrade --install -f values.yaml -f fooValues.yaml -f barValues.yaml gitpod .