Cryptography module released 44.0.0 - Deployment Issues with GitHub Actions on ubuntu-latest due to cryptography module update

[VashBik]

Description:
We have been experiencing issues with Azure Functions deployments using GitHub Actions after deploying code that relies on the cryptography module. Despite the deployment showing as successful, the functions are not visible in the Azure portal. In the logs, we observed errors related to missing modules and container start issues, which we traced back to changes in the cryptography module.

Key Points:

• Issue started after November 27th, 6 PM UTC.
• The errors occur when using GitHub Actions with the ubuntu-latest runner.
• The issue involves missing Azure Functions or "module not found" errors after deploying code that utilizes azure-identity and cryptography.

Affected Versions:

• Python version: 3.11
• cryptography module version: 44.0.0
• GitHub Actions runner: ubuntu-latest

Temporary Workaround:
We have temporarily resolved the issue by changing the GitHub Actions YAML configuration to use ubuntu-20.04 instead of ubuntu-latest for the runner.

Steps to Reproduce:

1. Create a Python app that uses the azure-identity library and the cryptography module.
2. Deploy the app using GitHub Actions with the ubuntu-latest runner.
3. Observe that the functions do not appear in the Azure portal after deployment.

Expected Behavior:
The functions should be deployed correctly and visible in the Azure portal after a successful GitHub Actions deployment.

Actual Behavior:
The functions are not visible in the portal, and errors are logged related to the cryptography module.

Relevant Links:

• For more context, see this GitHub issue where similar problems with the cryptography module were discussed.

We would appreciate any assistance or updates on this matter to help resolve the issue in GitHub Actions deployments.

Thank you for your attention.

[reaperhulk]

This is not a bug in cryptography, I’ve provided advice to the Azure teams responsible for Functions UX (the final option being something users can do themselves), and for other reasons we removed this wheel for 44.0.0 (although it will return again in future versions) so the error should not currently occur unless you have caches you need to delete.

Is there something else we can do here?