-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
CosmosDB throws Unknown service error #241
Comments
Hey @TsuyoshiUshio Thanks for opening this issue So that we can look into this further would it be possible to know which Region you're attempting to deploy the CosmosDB instance into (i.e. the value of Thanks! |
@tombuildsstuff I tried running the sample provided by @TsuyoshiUshio and got the same error"Message=Unknown service error" for location values "westus" and "centralus". I did not try for any other locations |
Hey @maniSbindra / @TsuyoshiUshio Using the following configuration I'm able to successfully deploy a CosmosDB instance - would you mind confirming if this works for you? In addition - have you deployed a CosmosDB/DocumentDB Account into this Azure Subscription + Region previously? I'm trying to isolate if this is related to a missing Resource Provider registration (which will be added into the next release of the AzureRM Provider) or if this is specific to these regions?
Thanks! |
@tombuildsstuff I need to double check this again, but I created a Azure cosmosdb account from the portal in centralus, after doing this my terraform apply failed with regions westus, eastus (same unknown service error), but succeeded for location centralus. |
@tombuildsstuff I tried my terraform.tf on West US. Today, I tried your terraform.tf. It works both on west europe and west us. Also, it works on my script as well. Hmm. Something has changed on the Azure side? Anyway, thank you for your help. |
Hey @TsuyoshiUshio
I'm unaware of any changes there, but possibly - I think it's more likely this is the missing Resource Provider registration which will be fixed in the next release. Regardless it's good to hear that this is now working again :) @maniSbindra @TsuyoshiUshio out of interest, have you been using CosmosDB/DocumentDB back when it was available in Preview/less regions than today? I'm wondering if this is the Resource Provider registration being exposed in manor I've not seen before. If you've got the Azure CLI 2.0 installed, would you mind showing me the output of this command?
which I'm hoping should show something similar too:
Thanks! |
@tombuildsstuff details as requested
|
Also, I realize one difference between last time and now. I usually stay in Japan. However, at that time, I was staying in Redmond.
|
Hi, We've been having the same issue and then realised that the db name need to be globally unique. which fixed the error for us. |
This is likely that the name being used is in use - we should change this to check if the name exists |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Hi there,
I encounter the error when I deploy Cosmos DB. It might be very basic configuration. However, it says
Unknow service error
I have no clue to fix this.Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Debug Output
Error
Expected Behavior
It should be create a CosmosDB (DocumentDB) instance on Azure
Actual Behavior
The error cause. we can see empty Resource Group.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
References
nothing
The text was updated successfully, but these errors were encountered: