@José María Pelayo Tijero Thanks for posting your question here. Apologize for any inconvenience caused on this.
I see this issue has been resolved and below are the workaround or mitigations shared. let me know if have any further questions on this.
Workaround: Multiple approaches to mitigate-
- [Azure Functions only] Use Remote Build when deploying - retry performing the deployment using the Remote Build: https://learn.microsoft.com/en-us/azure/azure-functions/functions-deployment-technologies?tabs=windows#remote-build
- Use older action image for azure pipelines and GitHub Action - in case you are using Azure Pipelines please change the
vmImageName
tag from “ubuntu-latest” to “ubuntu-20.04” for your yaml file- please refer to https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software - in case you are using GH Actions please change theruns-on
tag from “ubuntu-latest” to “ubuntu-20.04” for your yaml file- please refer to https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources - For local build, please use Ubuntu 20.04 or any Debian 11 based image when doing a zip-deploy.
- [to be used only if 1 and 2 cannot be done] If you use
azure-identity
or any library leveragingazure-identity
module - Please pin thecryptography
library tocryptography==43.0.3
.
- After making this change, redeploy your app. Note that change should be done with consideration to ongoing management of application dependency versions. Please avoid keeping this dependency pinned longer than necessary. For more details, refer to azure-sdk-for-python/issues/38725