-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bug: Error on sam build command #4527
Bug: Error on sam build command #4527
Comments
cryptography 39.0.0 no longer supports openssl 1.1.0 or older and thus is causing this issue.
aws-sam-cli uses the latest cryptography while using pyopenssl 22.0.0. These two are incompatible. |
Getting this in all our github actions using aws-actions/setup-sam. New years day dependency bomb! |
Thank you so much. I got it work! |
aws-sam-cli/requirements/base.txt Line 21 in 07fa5f4
Once the pin is updated you won't see this type of issue again in the future. Note that the drop of OpenSSL 1.1.0 is not really related to this issue, as over 98% of |
How did you get it to work? |
If you're on MacOS/Homebrew here's how to implement the workaround:
|
Having this issue in codebuild as well (aws/codebuild/standard:5.0) |
@nszeitli for aws-actions/setup-sam, you can add the following step to github workflow (worked for us):
|
We are checking this issue. Could you please confirm do you see this issue only on homebrew installation or also on the pkg installation? |
Error using setup-sam GH action (with |
This issue is only affecting the people who use For macOS users, We recommend using the PKG installation approach, and For Linux users, we recommend the Command line installer way. You can find all the installation details here. For We are working on the fix for this issue, we will update this issue once it got released. |
Thanks @getanwar for raising this issue. Could you please try the PKG installation and let us know if it fixed your issue? |
Thanks, it worked ! |
as of now, github actions that depends on sam cli still failed Edit: In the meantime, while waiting for the release of the fixes, you can try add this temporary workaround step right after this step: |
Kudos to @altaurog, his line of the fixed version of cryptography worked like a charm:
|
Thanks @Raul-CC ! As an aside, note that the latest version of aws-actions/setup-sam is v2. (Sorry, I realize this isn’t exactly on-topic) |
sam-cli broke due to some OpenSSL dependency issues. Attempting this fix: aws/aws-sam-cli#4527 (comment)
Closing as the fix has been released with AWS SAM CLI v1.68.0 - https://github.com/aws/aws-sam-cli/releases/tag/v1.68.0 |
|
Hi guys, help! I am having the same problem with my CI/CD pipelines on Google Cloud. I tried to reinstall cryptography but doesn't seem to work - it keeps returning the same AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms'. Not sure if my syntax below is correct? pip install --force-reinstall "cryptography==38.0.4" I also tried to include cryptography==38.0.4 in my requirements.txt file and reinstall it, only to receive the same error: |
Check |
Thanks @altaurog I was looking at the wrong place. However when I tried to run Below is a screenshot of the beginning of the error: Apologies if my question sounds silly, I'm super new on this :) |
@Gordonbaes it is difficult to diagnose this without more information, but it doesn’t look like the same error as reported here. This error arose when invoking |
Description:
I can not build projects after upgrading sam cli from 1.65.0 to 1.67.0
After facing the issue for a couple of times I thought it might fix if I remove python3.8 manually and reinstall aws-sam-cli. But it did not solve it. I confirmed that python3.8 was reinstall with aws-sam-cli
Steps to reproduce:
brew upgrade aws-sam-cli
I encountered the following error after doing that.
Observed result:
sam build --debug
Expected result:
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: SAM CLI, version 1.67.0Add --debug flag to command you are running
The text was updated successfully, but these errors were encountered: