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 s3 reindex throws error #96

Closed
benejo opened this issue Nov 26, 2019 · 5 comments
Closed

helm s3 reindex throws error #96

benejo opened this issue Nov 26, 2019 · 5 comments

Comments

@benejo
Copy link

benejo commented Nov 26, 2019

I did s3 sync of helm repo bucket to another bucket(disaster recovery region). The idea is to copy chart zips to DR bucket and setup that bucket as a new S3 repo for DR region.
When running "helm s3 reindex repo-name" I get the following error,

traverse the chart repository: unserialize chart meta: invalid character '=' looking for beginning of value
Error: plugin "s3" exited with error

helm client version: v2.11.0
helm s3 version: 0.8.0

@premkumar-gg
Copy link

Happens for us too.. this is especially after the "hazelcast" chart was included in our repository. Did you get to resolve this?

@mstrejczek
Copy link

I've just seen it too.

helm plugin list
NAME      	VERSION	DESCRIPTION                                                                                
nexus-push	0.0.1  	Pushes a chart directory or packaged chart tgz to a specified repo,                        
          	       	either by named repo ...                                                                   
s3        	0.9.2  	The plugin allows to use s3 protocol to upload, fetch charts and to work with repositori...

@ilunie
Copy link

ilunie commented Feb 9, 2021

do you already have a solution to this?

@hypnoglow
Copy link
Owner

I believe this should be fixed already. Please try using the latest plugin release.

I'm going to close this issue, feel free to reach out again if you still experience the problem, and please provide the Chart.yaml file.

@Shion1305
Copy link

I was getting the same error, and this was because of #461 .

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

No branches or pull requests

6 participants