-
Notifications
You must be signed in to change notification settings - Fork 343
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
DNM:Upgrade awscli #1703
DNM:Upgrade awscli #1703
Conversation
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 14s |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 4m 46s |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 5m 22s |
This change depends on a change that failed to merge. Change ansible/ansible-zuul-jobs#1819 is needed. |
recheck |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 5m 25s |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 4m 12s |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 4m 50s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awscli versions are closely tied to botocore/boto3 versions we can't just bump this version without bumping botocore and boto3 See the comment in constraints.txt
Understood. I am trying a few workarounds to fix the cpython issue we see in amazon.aws integration tests on py3.11. This is not the final fix. |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 4m 09s |
Build failed. ✔️ ansible-galaxy-importer SUCCESS in 5m 30s |
@GomathiselviS Have you tried to upgrade/downgrade pyyaml version? It seems it is an error happening in pyyaml 5.4 yaml/pyyaml#724 |
Hi @alinabuzachis @tremble @jillr @gravesm The issue mentioned in the description occurs with the current version of awscli that we're using, which is 1.23.0. This version comes with pyyaml 5.4, and we're facing a failure during pip installation of awscli. Unfortunately, we cannot simply pin pyyaml to a lower version due to security issues. (https://www.cvedetails.com/cve/CVE-2020-14343/) I've attempted to resolve this issue by using --no-build-isolation with awscli, pyyaml, and cython, but it hasn't fixed the cython dependency problem. After considering the possible solutions, I believe that upgrading awscli to version 1 or migrating to awscli v2 might be the best course of action. I've run some tests with the following versions, and most of the tests have passed. However, I still need to investigate the failed tests.
What do you think? Would upgrading awscli be a good solution, or do you have any other ideas? Let me know! |
I think this one can be close. CI should be working again, aside from the current problems with zuul |
Bump release_version for eks_nodegroup SUMMARY Couldn't bump the version in ansible-collections#1415 - bumping it here ISSUE TYPE Docs Pull Request COMPONENT NAME eks_nodegroup ADDITIONAL INFORMATION
Bump release_version for eks_nodegroup SUMMARY Couldn't bump the version in ansible-collections#1415 - bumping it here ISSUE TYPE Docs Pull Request COMPONENT NAME eks_nodegroup ADDITIONAL INFORMATION
Looks like this was solved another way. Closing for now (we also bumped botocore in #1763) |
Bump release_version for eks_nodegroup SUMMARY Couldn't bump the version in ansible-collections#1415 - bumping it here ISSUE TYPE Docs Pull Request COMPONENT NAME eks_nodegroup ADDITIONAL INFORMATION
SUMMARY
pip install awscli (version 1.23.0) results in the following error
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION