Charts: Dependency is not getting resolved while using with Helm install

[ymallipe]

Is this a request for help?:

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug

Version of Helm and Kubernetes:
helm version
Client: &version.Version{SemVer:"v2.8.1", GitCommit:"6af75a8fd72e2aa18a2b278cfe5c7a1c5feca7f2", GitTreeState:"clean"}
Serv

er: &version.Version{SemVer:"v2.8.1", GitCommit:"6af75a8fd72e2aa18a2b278cfe5c7a1c5feca7f2", GitTreeState:"clean"}

Which chart:
incubator/kafka

What happened:
Installing using below command say missing charts in requirements.yaml
helm install --name myzk incubator/kafka
Error: found in requirements.yaml, but missing in charts/ directory: zookeeper, schema-registry

What you expected to happen:
Install Kafka with Zookeeper dependency charts.

How to reproduce it (as minimally and precisely as possible):
Installed GKE and using Helm tarball, Added repo executed kafka charts.

Anything else we need to know:
NA

[JMLizano]

Hi,

I think this isn't bug, but one of the following scenarios:

1. You are trying to install the kafka chart from source code, instead from the release in the helm repo. If you want to this you have to run 'helm dependency update kafka' before installing.

2. You added the repo as stated in the README.md and you are trying to install from it, but since you are in /charts dir, helm first evaluates 'incubator/kafka' to the local source code directory, and thus failing for the same reason as 1. In this case you should try installing from another directory.

[fejta-bot]

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[dove-young]

I got the same error when I tried to add one more sub-chart to a Helm chart

It says Error: found in requirements.yaml, but missing in charts/ directory: local-volume-provisioner, but this directory does exist and contains the sub-chart there.

helm version --tls
Client: &version.Version{SemVer:"v2.7.3", GitCommit:"27442e4cfd324d8f82f935fe0b7b492994d4c289", GitTreeState:"dirty"}
Server: &version.Version{SemVer:"v2.7.3", GitCommit:"27442e4cfd324d8f82f935fe0b7b492994d4c289", GitTreeState:"dirty"}

[root@test ]# ls
additionalFiles  david.install.log  README.md          templates             values.yaml
charts           LICENSE            requirements.lock  test.values.yaml
Chart.yaml       LICENSES           requirements.yaml  values-metadata.yaml
[root@test]# ls charts/local-volume-provisioner/
charts  Chart.yaml  local-storage-class.yaml  provisional_local_ssd_volumes.yaml  templates
[root@test]# helm install --debug . --tls -n test --values /tmp/test.values.yaml
[debug] Created tunnel using local port: '36996'

[debug] SERVER: "127.0.0.1:36996"

[debug] Original chart version: ""
[debug] Key="/root/.helm/key.pem", Cert="/root/.helm/cert.pem", CA="/root/.helm/ca.pem"

[debug] CHART PATH: /root/charts/test

Error: found in requirements.yaml, but missing in charts/ directory: local-volume-provisioner
[root@test ]#

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity.