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

Failed to connect to PurView caused CI tests failure #349

Closed
windoze opened this issue Jun 11, 2022 · 0 comments · Fixed by #350
Closed

Failed to connect to PurView caused CI tests failure #349

windoze opened this issue Jun 11, 2022 · 0 comments · Fixed by #350
Assignees
Labels
bug Something isn't working

Comments

@windoze
Copy link
Member

windoze commented Jun 11, 2022

Recently we have CI test failure in every PR, the error message:

E           requests.exceptions.ConnectionError: HTTPSConnectionPool(host='some-purview-name.catalog.purview.azure.com', port=443): Max retries exceeded with url: /api/atlas/v2/types/typedefs (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f90c3e7ea60>: Failed to establish a new connection: [Errno 111] Connection refused'))

Looks like that we have some issue with the PurView service.

Please help to resolve as it affects all PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants