Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to run 'helm dependency build' command #7586

Closed
alarud opened this issue Oct 30, 2020 · 3 comments
Closed

failed to run 'helm dependency build' command #7586

alarud opened this issue Oct 30, 2020 · 3 comments

Comments

@alarud
Copy link

alarud commented Oct 30, 2020

Summary

jx boot cannot finish sucessfully as throwing error regarding 'helm dependency build' command

Steps to reproduce the behavior

'jx boot' command throws the error:
STEP: install-jx-crds command: /bin/sh -c jx upgrade crd in dir: /home/vagrant/jenkinsx/jenkins-x-boot-config

Jenkins X CRDs upgraded with success

STEP: install-velero command: /bin/sh -c jx step helm apply --boot --remote --no-vault --name velero in dir: /home/vagrant/jenkinsx/jenkins-x-boot-config/systems/velero

Modified file /home/vagrant/jenkinsx/jenkins-x-boot-config/systems/velero/Chart.yaml to set the chart to version 1
error: failed to build the dependencies of chart '/tmp/jx-helm-apply-169561611/velero': failed to run 'helm dependency build' command in directory '/tmp/jx-helm-apply-169561611/velero', output: 'Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):
Get "http://127.0.0.1:8879/charts/index.yaml": dial tcp 127.0.0.1:8879: connect: connection refused'
error: failed to interpret pipeline file jenkins-x.yml: failed to run '/bin/sh -c jx step helm apply --boot --remote --no-vault --name velero' command in directory 'systems/velero', output: ''

Expected behavior

jx boot working as expected

Actual behavior

jx boot throws an error as above

Jx version

The output of jx version is:

Version 2.1.150
Commit c038751
Build date 2020-09-26T19:20:02Z
Go version 1.13.8
Git tree state clean

Diagnostic information

The output of jx diagnose version is:

Running in namespace: jx
Version 2.1.150
Commit c038751
Build date 2020-09-26T19:20:02Z
Go version 1.13.8
Git tree state clean
NAME VERSION
jenkins x platform 2.0.2405
Kubernetes cluster v1.19.2
kubectl (installed in JX_BIN) v1.16.6-beta.0
helm client 2.16.9
git 2.24.1
Operating System Unknown Linux distribution Linux version 3.10.0-957.5.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) ) #1 SMP Fri Feb 1 14:54:57 UTC 2019

Kubernetes cluster

Kubernetes cluster on vagrant VM k8 node.

Kubectl version

The output of kubectl version --client is:

Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:41:02Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}

Operating system / Environment

CentOS Linux release 7.8.2003 (Core)

@jenkins-x-bot
Copy link
Contributor

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

@jenkins-x-bot
Copy link
Contributor

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

@msvticket
Copy link
Member

This story is about Jenkins-X 2 which is not developed or supported what so ever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants