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

Error deleting chart with version in quotes #14607

Closed
twellspring opened this issue Apr 9, 2021 · 5 comments
Closed

Error deleting chart with version in quotes #14607

twellspring opened this issue Apr 9, 2021 · 5 comments

Comments

@twellspring
Copy link

A helm chart got uploaded with the version in quotes

image

If I try to delete it from the gui I get the error
fail to delete chart version: remove /chart_storage/ironnet/dns-tunneling-ss-"3.4-356".tgz: no such file or directory

The file does not exist. I have added that file
touch '/chart_storage/ironnet/dns-tunneling-ss-"3.4-356".tgz' and then the delete completes successfully, but the entry still exists in my repo and a helm repo update command on my workstation throws this error

index.go:339: skipping loading invalid entry for chart "dns-tunneling-ss" "\"3.4-356\"" from https://harbor.aws-dev.irondev.io/chartrepo/ironnet: validation: chart.metadata.version "\"3.4-356\"" is invalid

How can I get rid of this entry?

@twellspring
Copy link
Author

Harbor Version v2.2.0-6db1a349
Installed in EKS using the helm chart https://github.com/goharbor/harbor-helm

@ninjadq
Copy link
Member

ninjadq commented Apr 12, 2021

This is caused by upstream chartmuseum.
the file is already deleted, but the cache still left on cache.
you can try following steps as workaround

  1. stop harbor
  2. delete cache both in Redis and chart data storage
  3. start harbor

@piyush94
Copy link

Chartmuseum has newer releases >= 0.13.0 in which chart semantic versioning issues have been resolved. Kindly upgrade the chartmuseum version in Harbor release as well. PR: helm/chartmuseum#362

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Apr 16, 2022
@github-actions
Copy link

github-actions bot commented Jul 6, 2022

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.

@github-actions github-actions bot closed this as completed Jul 6, 2022
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

4 participants