Tiller v2.15.1 breaks Auto DevOps CI for some projects
Summary
https://github.com/helm/helm/issues/6751
Tiller v2.15.1 which is in use by the auto devops deploy job breaks all of my CI deployments!
They build successfully, but hang on the --wait
... a known tiller 2.15 issue, fixed on v2.16
This was really hard to figure out, the error is useless. My private tdps/learn-server, tdps/learn-admin, tdps/learn-web projects are all affected.
Steps to reproduce
Start a new kubernetes Auto DevOps cluster using kubernetes v16
What is the current bug behavior?
$ auto-deploy initialize_tiller
Checking Tiller...
Tiller is listening on localhost:44134
Client: &version.Version{SemVer:"v2.15.1",
...
$ auto-deploy deploy
secret "staging-secret" deleted
secret/staging-secret replaced
Deploying new release...
UPGRADE FAILED
Error: timed out waiting for the condition
Error: UPGRADE FAILED: timed out waiting for the condition
Full: fail-log.txt
What is the expected correct behavior?
$ auto-deploy initialize_tiller
Checking Tiller...
Tiller is listening on localhost:44134
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0",
...
$ auto-deploy deploy
secret "staging-secret" deleted
secret/staging-secret replaced
Deploying new release...
Release "staging" has been upgraded.
LAST DEPLOYED: Tue Nov 5 16:00:46 2019
Full: pass-log.txt
Possible fixes
https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/kubernetes/helm.rb#L6
- Upgrade to tiller v2.16.0.
- Upgrade to tiller v2.14.0.
- Allow us to specify tiller version to use on the deploy jobs
Edited by 🤖 GitLab Bot 🤖