Skip to content
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

msrest import error while deploying to azure app #253

Closed
gdsuser1992 opened this issue Jun 16, 2022 · 1 comment
Closed

msrest import error while deploying to azure app #253

gdsuser1992 opened this issue Jun 16, 2022 · 1 comment

Comments

@gdsuser1992
Copy link

We are creating a flask app. It is working fine in local environment (no version conflict issues). Recently, when we tried pushing the code to azure app service, after successful build, when we access the webpage, its giving a 502 error.

We tried to identify the issue and when we checked the logstream, the following error was found :


2022-06-16T12:28:03.580219773Z     from .universal_http.requests import (
2022-06-16T12:28:03.580223173Z   File "/tmp/8da4ea7dc4b7018/antenv/lib/python3.7/site-packages/msrest/universal_http/__init__.py", line 53, in <module>
2022-06-16T12:28:03.580226973Z     from ..exceptions import ClientRequestError, raise_with_traceback
2022-06-16T12:28:03.580230373Z   File "/tmp/8da4ea7dc4b7018/antenv/lib/python3.7/site-packages/msrest/exceptions.py", line 31, in <module>
2022-06-16T12:28:03.580234173Z     from azure.core.exceptions import SerializationError, DeserializationError
2022-06-16T12:28:03.580237773Z ImportError: cannot import name 'SerializationError' from 'azure.core.exceptions' (/tmp/8da4ea7dc4b7018/antenv/lib/python3.7/site-packages/azure/core/exceptions.py)

Are we facing any version conflict issues with azure-core and the msrest ?

We are not adding the msrest package in requirements.txt and its loaded by default when we publish it to the app service.

We tried to change the version of azure-core to 1) the latest version 2) 1.9.0 3) 1.11.0 - All these still end up giving the same error.

Is there any work around for this issue ?? Please help.

@gdsuser1992
Copy link
Author

Closing the issue. Tried with azure-core version 1.24.0 and it fixed the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant