Jx: Failed to re-install jenkins-x platform

Created on 13 Feb 2019  路  7Comments  路  Source: jenkins-x/jx

Summary

Unable to re-install jenkins-x

Steps to reproduce the behavior

  1. jx install --namespace n1 --provider eks --username admin --domain n1.com --buildpack kubernetes-workloads --no-tiller --git-private
  2. jx uninstall
  3. jx install --namespace n1 --provider eks --username admin --domain n1.com --buildpack kubernetes-workloads --git-private

    Actual behavior

error: installing the Jenkins X platform: failed to install/upgrade the jenkins-x platform chart: failed to run 'helm upgrade --namespace n1 --install --timeout 6000 --version 0.0.3368 --values /home/stephen/.jx/cloud-environments/env-eks/myvalues.yaml --values /home/stephen/.jx/myvalues.yaml --values /home/stephen/.jx/adminSecrets.yaml --values /home/stephen/.jx/extraValues.yaml --values /home/stephen/.jx/cloud-environments/env-eks/secrets.yaml jenkins-x jenkins-x/jenkins-x-platform' command in directory '/home/stephen/.jx/cloud-environments/env-eks', output: 'Release "jenkins-x" does not exist. Installing it now. Error: release jenkins-x failed: clusterroles.rbac.authorization.k8s.io "controllercommitstatus-n1" already exists'

Jx version

1.3.870

Jenkins type

  • [x ] Classic Jenkins
  • [ ] Serverless Jenkins

Kubernetes cluster

eksctl

Operating system / Environment


Ubuntu 18.04

areinstall arejenkins kinbug lifecyclrotten prioritimportant-longterm

Most helpful comment

a workaround for now is to add --no-tiller to the jx install command

All 7 comments

/kind bug
/priority backlog
/area install

a workaround for now is to add --no-tiller to the jx install command

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

/area jenkins

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Was this page helpful?
0 / 5 - 0 ratings