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 repo up not working with helm-gcs #68

Closed
Talador12 opened this issue Sep 29, 2020 · 2 comments
Closed

helm repo up not working with helm-gcs #68

Talador12 opened this issue Sep 29, 2020 · 2 comments
Labels

Comments

@Talador12
Copy link

Talador12 commented Sep 29, 2020

Example:

→ helm gcs push staging-model-template-0-1-0.tgz bi-staging --force

→ helm repo up
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bi-staging" chart repository
Update Complete. ⎈Happy Helming!⎈

→ helm fetch bi-staging/staging-model-template-0-1-0
Error: chart "staging-model-template-0-1-0" matching  not found in bi-staging index. (try 'helm repo update'): no chart name found

→ helm gcs push staging-model-template-0-1-0.tgz bi-staging
Error: chart staging-model-template-0-1-0 already indexed. Use --force to still upload the chart

→ helm search repo  bi-staging
No results found

See - it is indexed when you try to push, but it is not when you try to fetch/update/search.

When viewing the GCS bucket, the .tgz is there, along with an index.yaml as follows:

Note: Just for privacy on a public post, I removed the digest variable and changed the bucket name to gs://HIDDEN. The information is correct on the real bucket

apiVersion: v1
entries:
  staging-model-template:
  - apiVersion: v2
    appVersion: 0-1-0
    created: "2020-09-29T12:14:32.763916-05:00"
    description: Model description goes here
    icon: https://i.imgur.com/lc9OKZr.png
    name: staging-model-template
    type: application
    urls:
    - gs://HIDDEN/staging-model-template-0-1-0.tgz
    version: 0-1-0
generated: "2020-09-29T12:14:32.763918-05:00"

Is this a caching issue related to #44 ? What is happening to cause this? How would it be resolved?

@stale
Copy link

stale bot commented Oct 29, 2020

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 wontfix label Oct 29, 2020
@stale stale bot closed this as completed Nov 12, 2020
@doctapp
Copy link

doctapp commented Feb 12, 2021

We see the same problem. Some push fail for no apparent reasons. Any idea?

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

No branches or pull requests

2 participants