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.

Sign up for GitHub

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

Jump to bottom

[ISSUE] Chart upgrade fails due to *.tgz not evaluating to a real path #1622

Closed
jessesimpson36 opened this issue Apr 15, 2024 · 0 comments · Fixed by #1638 · May be fixed by #1630
Closed

[ISSUE] Chart upgrade fails due to *.tgz not evaluating to a real path #1622

jessesimpson36 opened this issue Apr 15, 2024 · 0 comments · Fixed by #1638 · May be fixed by #1630
Assignees
@jessesimpson36
Labels
kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between

Comments

@jessesimpson36
Copy link
Contributor

jessesimpson36 commented Apr 15, 2024 •
edited

Describe the issue:

Recent change in the helm chart caused the upgrade CI to fail, since we now reference *.tgz, but earlier in the CI, where we run helm pull and helm package, we pull those into TEST_TMP_DIR or /tmp

https://github.com/camunda/camunda-platform-helm/actions/runs/8694679254/job/23844101939?pr=1619

Actual behavior:

Expected behavior:

How to reproduce:

Logs:

Environment:

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

  • Platform:
  • Helm CLI version:
  • Chart version:
  • Values file:
@jessesimpson36 jessesimpson36 added the kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between label Apr 15, 2024
@jessesimpson36 jessesimpson36 mentioned this issue Apr 15, 2024
Closed
6 tasks
@jessesimpson36 jessesimpson36 self-assigned this Apr 15, 2024
@jessesimpson36 jessesimpson36 mentioned this issue Apr 16, 2024
Draft
6 tasks
@aabouzaid aabouzaid mentioned this issue Apr 17, 2024
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jessesimpson36 jessesimpson36

Labels
kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between
Projects
None yet
Milestone
No milestone
1 participant
@jessesimpson36