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

Helm Chart Dependency Issue on scylla-manager #2113

Open
pggb25 opened this issue Sep 6, 2024 · 3 comments
Open

Helm Chart Dependency Issue on scylla-manager #2113

pggb25 opened this issue Sep 6, 2024 · 3 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@pggb25
Copy link

pggb25 commented Sep 6, 2024

Note: I’ve already opened this issue on scylladb/scylla-manager, but I was asked to open it here instead.

I encountered an issue when using the scylla-manager Helm chart to install Scylla Manager.
• Helm version: v3.15.4
• Scylla-Manager chart version: v1.13.0

When running the following command:

helm dependency list scylla-manager

I get the following output:

NAME  	VERSION	REPOSITORY      	STATUS
scylla	1.0.0  	file://../scylla	wrong version

with the status showing wrong version.

Additionally, running:

helm dependency update scylla-manager

returns the error:

Error: directory scylla not found

Workaround:
I was able to resolve the issue by modifying the dependencies section in the Chart.yaml file:
• I changed the version to 0.0.0 (as this is the version of scylla in the charts/scylla directory).
• I also updated the repository path to file://charts/scylla.

After making these changes, both commands succeed without errors.

Question:
Could you confirm whether this is a problem with the chart dependencies configuration, or if it is a misunderstanding on my side?

What did you expect to happen?

I expect the command

helm dependency list scylla-manager

returns a status equal to unpacked

and the command

helm dependency update scylla-manager

finished with

Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Deleting outdated charts

How can we reproduce it (as minimally and precisely as possible)?

helm pull --repo https://scylla-operator-charts.storage.googleapis.com/stable scylla-manager --version v1.13.0 --untar
helm dependency list scylla-manager

returns wrong version as status

helm dependency update scylla-manager

returns Error: directory scylla not found

Scylla Operator version

scylla manager version is v1.13.0

Kubernetes platform name and version

not relevant

Please attach the must-gather archive.

not relevant

Anything else we need to know?

Note: I’ve already opened this issue on scylladb/scylla-manager, but I was asked to open it here instead.

@pggb25 pggb25 added the kind/bug Categorizes issue or PR as related to a bug. label Sep 6, 2024
@scylla-operator-bot scylla-operator-bot bot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Sep 6, 2024
@mykaul
Copy link
Contributor

mykaul commented Sep 23, 2024

@zimnx , @tnozicka - did anyone look at this?

@zimnx
Copy link
Collaborator

zimnx commented Sep 23, 2024

I briefly went over it to understand whether it's a deployment issue and to my understanding it isn't. So at least to me it's a low priority.

I don't know why command returns "wrong version", it's specified in Chart.yaml of the chart.

$ cat scylla-manager/Chart.yaml | yq .version 
v1.13.0

Path to the dependency chart is aligned with how documentation states how locally stored deps should be referenced: https://helm.sh/docs/helm/helm_dependency

Copy link
Contributor

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out

/lifecycle stale

@scylla-operator-bot scylla-operator-bot bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 24, 2024
@tnozicka tnozicka added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Nov 21, 2024
@scylla-operator-bot scylla-operator-bot bot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

4 participants