-
-
Notifications
You must be signed in to change notification settings - Fork 908
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
New release is broken, had to revert #987
Comments
Thank you very much for the notice. |
Oh yeah that was the issue. But it crashes instead of giving an informative error like the last version. I was trying to use the server's IAM role, but s3cmd doesn't get it automatically so I need to query server metadata and parse it myself, working on setting that up now. |
Yes, it is a recent change that was probably not safe enough for encoding issues. |
The error before was: ERROR: /home/admin/.s3cfg: None It seems in the new version you're trying to automagically get the role credentials. However it doesn't seem to be working. Maybe you only tested on python2? |
Confirmed. It automatically works with a role in python2, but crashes in python3. |
Ok, because normally you should still create your configuration with --configure or manually creating a .s3cfg. |
I have found another related issue that I have fixed, but I was testing with python 3.6 and trying with python 3.5 as you shows that there is another issue. :-s |
Your issue should now be fixed. |
hi, looks it's still broken IAM Role
|
Seeing the exact same issue when running it with AWS EC2 roles.
Including the Dockerfile to give more context as well.
|
update: solved by basically cloning and building it on the image. Looks like fixed merged only 3 days after the last release.
|
2.0.1 works fine so I reverted to that thanks.
The text was updated successfully, but these errors were encountered: