Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

Scheduled maintenance on the database layer will take place on 2022-07-02. We expect GitLab.com to be unavailable for up to 2 hours starting from 06:00 UTC. Kindly follow our status page for updates and read more in our blog post.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #54760
Closed (moved) (moved)
Open
Created Dec 02, 2018 by Thong Kuah@tkuahMaintainer

Auto DevOps : Helm cannot upgrade over initial failed release

Steps to reproduce

  1. Have a failed Helm release (e.g. forgot to set base domain)
  2. Fix issue from 1, run Auto DevOps pipeline again
  3. Failure below occurs
$ deploy
secret "review-secrets-ayz3io-secret" deleted
secret "review-secrets-ayz3io-secret" replaced
Initializing...
Error: UPGRADE FAILED: "review-secrets-ayz3io" has no deployed releases
ERROR: Job failed: exit code 1

Notes

  • This seems to only occur if ALL releases for that chart have only ever failed.
  • If there is a successful release in the past, then Helm can upgrade over a previously failed release

Workaround

As shown by @tnir in https://gitlab.com/gitlab-org/gitlab-ce/issues/54760#note_146627376

  1. Run the following script locally. For the production job, the <chart-name> is production. For other jobs, run helm ls which should show you which chart to delete.
$ tiller -version
v2.13.0
$ export KUBE_NAMESPACE=<CI_PROJECT_NAME>-<CI_PROJECT_ID>
$ export TILLER_NAMESPACE=$KUBE_NAMESPACE
$ tiller -listen localhost:44134 &
[1] 28659
$ export HELM_HOST="localhost:44134"
$ helm init --client-only
$ helm delete <chart-name> --purge --tiller-namespace $KUBE_NAMESPACE
release "<chart-name>" deleted
  1. Retry the deploy job

Links

See also discussion in https://github.com/helm/helm/issues/3208 and https://github.com/helm/helm/issues/3353

Edited Apr 02, 2019 by Thong Kuah
Assignee
Assign to
Time tracking