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.

Sign up for GitHub

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

Jump to bottom

Cosmos DB CheckNameExists failing with 500 (again) #9891

Closed
jackofallops opened this issue Jun 3, 2020 · 5 comments
Closed

Cosmos DB CheckNameExists failing with 500 (again) #9891

jackofallops opened this issue Jun 3, 2020 · 5 comments
Labels
Cosmos customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library.

Comments

@jackofallops
Copy link

Bug Report

Issue #5157 appears to have resurfaced with the same symptoms.

az cosmosdb check-name-exists --name doesntexist
request failed: Error occurred in request., RetryError: HTTPSConnectionPool(host='management.azure.com', port=443): Max retries exceeded with url: /providers/Microsoft.DocumentDB/databaseAccountNames/doesntexist?api-version=2019-12-12 (Caused by ResponseError('too many 500 error responses'))

hashicorp/terraform-provider-azurerm#7173
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jun 3, 2020
@jackofallops jackofallops mentioned this issue Jun 3, 2020
Closed
@erikschlegel
Copy link

JFYI, this issue is blocking my team from provisioning cosmos envionments. Verified this issue exists for eastus, centralus, westus and eastus2 regions.

@markjbrown
Copy link

We have identified the root cause for this and are actively working on a hot fix to the issue. ETA should be tomorrow.

Thanks.

@markjbrown
Copy link

We've deployed the fix for this and the issue is resolved.

@ArcturusZhang
Copy link
Member

Hi @jackofallops could you please have a try if the fix works or not?

@ArcturusZhang ArcturusZhang added Cosmos Mgmt This issue is related to a management-plane library. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jun 4, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jun 4, 2020
@jackofallops
Copy link
Author

Hi @jackofallops could you please have a try if the fix works or not?

A quick test suggests this is resolved, thanks for the timely action!

@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Cosmos customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@markjbrown @erikschlegel @ArcturusZhang @jackofallops