-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
s3 pillar fails on python3 #54696
Labels
Bug
broken, incorrect, or confusing behavior
Pillar
python3
regarding Python 3 support
severity-high
2nd top severity, seen by most users, causes major problems
Comments
Akm0d
added
Bug
broken, incorrect, or confusing behavior
Pillar
and removed
needs-triage
labels
Dec 5, 2019
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. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
I reckon it's a bit early to close this bug. |
Thank you for updating this issue. It is no longer marked as stale. |
sagetherage
added
python3
regarding Python 3 support
severity-high
2nd top severity, seen by most users, causes major problems
labels
Apr 22, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
broken, incorrect, or confusing behavior
Pillar
python3
regarding Python 3 support
severity-high
2nd top severity, seen by most users, causes major problems
Description of Issue
Configuring an S3 pillar and doing a pillar.items yields the following stack strace:
Setup
The most simple s3 pillar setup.
Steps to Reproduce Issue
Configure S3 pillar, refer to it, things go boom.
Versions Report
The minion I used for testing is the master with the same versions.
The fix is to open the cache file in binary write mode:
I'll make a PR after some more testing.
The text was updated successfully, but these errors were encountered: