jenkins-x installation using helm troubleshoot

[ghost]

Hello,

i'm trying to install jenkins-x using helm with the command :

helm install jenkins-x/jenkins-x-platform --name jenkins-x -f ./jx-values.yaml --values=~/.jx/gitSecrets.yaml --namespace=testing i've the error : Error: failed to download "jenkins-x/jenkins-x-platform"

any help please ?

[rawlingsj]

we recommend using the jx cli to create clusters or install on an existing one. This will setup the local helm repos, secrets, environments and much more https://jenkins-x.io/getting-started/

[ghost]

Thnx rawlingsj for your help. whene i run jx install i've this message : ? Cloud Provider kubernetes Did not set exposeController Config Domain Tiller Deployment is running in namespace kube-system remote: Counting objects: 4, done. remote: Total 4 (delta 3), reused 4 (delta 3), pack-reused 0 Unpacking objects: 100% (4/4), done. From https://github.com/jenkins-x/draft-packs 52b34e8..987e4ca master -> origin/master Updating 52b34e8..987e4ca Fast-forward packs/ruby/preview/Chart.yaml | 5 +++++ packs/ruby/preview/Makefile | 22 ++++++++++++++++++++++ packs/ruby/preview/requirements.yaml | 13 +++++++++++++ packs/ruby/preview/values.yaml | 22 ++++++++++++++++++++++ 4 files changed, 62 insertions(+) create mode 100644 packs/ruby/preview/Chart.yaml create mode 100755 packs/ruby/preview/Makefile create mode 100644 packs/ruby/preview/requirements.yaml create mode 100644 packs/ruby/preview/values.yaml existing ingress controller found, no need to install a new one Waiting for external loadbalancer to be created and update the nginx-ingress-controller service in kube-system namespace it seem like my nginx-ingress-controller is not working fine. the message : Waiting for external loadbalancer to be created and update the nginx-ingress-controller service in kube-system namespace stay undefinitly.

[ghost]

if i skip ingress using jx install --skip-ingress i have following errors :

Error: Looks like "https://chartmuseum.build.cd.jenkins-x.io" is not a valid chart repository or cannot be reached: Get https://chartmuseum.build.cd.jenkins-x.io/index.yaml: Forbidden make: *** [setup] Error 1 Error: Command failed make ARGS=--values=/root/.jx/gitSecrets.yaml --values=/root/.jx/adminSecrets.yaml --values=/root/.jx/extraValues.yaml --namespace=jx --timeout=6000 install error: exit status 2

[rawlingsj]

Hmm are you behind a proxy? I'm able to hit that URL here https://chartmuseum.build.cd.jenkins-x.io/health

[ghost]

exact i'm behind a proxy. thnx mister :+1: but it's strange behaviour because the http proxy is already defined and helm work fine with it. why jx dosen't check the proxy values from ~/.bash_profile ?

[ghost]

Now i play the release.sh script manually. here is detailed results : helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com "incubator" has been added to your repositories

# helm repo add stable https://kubernetes-charts.storage.googleapis.com "stable" has been added to your repositories

# helm repo add monocular https://kubernetes-helm.github.io/monocular "monocular" has been added to your repositories

helm repo add chartmuseum http://chartmuseum.build.cd.jenkins-x.io Error: Looks like "http://chartmuseum.build.cd.jenkins-x.io" is not a valid chart repository or cannot be reached: Failed to fetch http://chartmuseum.build.cd.jenkins-x.io/index.yaml : 403 Forbidden

# helm repo add jx http://chartmuseum.build.cd.jenkins-x.io Error: Looks like "http://chartmuseum.build.cd.jenkins-x.io" is not a valid chart repository or cannot be reached: Failed to fetch http://chartmuseum.build.cd.jenkins-x.io/index.yaml : 403 Forbidden

what it can be the root cause of unreachable state of jx and chartmuseum repos, in the same time stable , incubator and monocular worked fine ?

thnx for your precious help

[rawlingsj]

looks like the ones that failed are http and not https, needs a cleanup on our side but shouldn't affect anything

[ghost]

OK thnx mister James

[rawlingsj]

you're welcome :)

[dongdan39]

Hi, Arhe, May I ask where did you get the file "./jx-values.yaml " for helm install of jenkins-x on Kubernetes? Thanks!

Cheers, Dan

[alokrajiv]

@rawlingsj How to "setup the local helm repos, secrets, environments" on an existing cluster.

I setup jx using the cli using an older machine, but on a different box now. I tried jx upgrade platform but hitting the above error (probably because the repos are not setup locally).

Is there like a jx init --client-only? Coz I'm facing the same error now.

[jstrachan]

try jx init --skip-setup-tiller --skip-ingress

if jx upgrade platform still doesn't work you could try run this command first:

helm repo add jenkins-x http://chartmuseum.jenkins-x.io/

but we should fix jx upgrade platform so you don't need to do that

[alokrajiv]

@jstrachan thanks I will test it first thing tomorrow morning, and reply here. In the meantime, I see that my old box everything works fine. So clearly not a jx server side issue. I will not do jx upgrade platform here, but wait to test on the new machine to confirm, above does solve the problem (for confirming a soln 👍 ) thanks for the response!

[ay-man]

I am getting the following:

Error: configuring the Jenkins X helm repository: failed to add the jenkinx-x helm repo: failed to add the repository 'jenkins-x' with URL 'http://chartmuseum.jenkins-x.io': failed to run 'helm repo add jenkins-x http://chartmuseum.jenkins-x.io' command in directory '', output: 'Error: Looks like "http://chartmuseum.jenkins-x.io" is not a valid chart repository or cannot be reached: Failed to fetch http://chartmuseum.jenkins-x.io/index.yaml : 403 Forbidden'