Issues creating Azure Managed Instance for Apache Cassandra

Question

Hello,

I can't create an "Azure Managed Instance for Apache Cassandra". I get an Internal Server Error and doesn't show any inner errors/details :

The template deployment '95f605c639424ea1b57f7b9ddc667f2d' is not valid according to the validation procedure. The tracking id is 'a49b7919-5d9d-4c25-99a5-96ae2a40043e'. See inner errors for details. ActivityId: cadaaf4c-fa3a-414a-b7bc-2b7b49895c47, Microsoft.Azure.Documents.Common/2.14.0 (Code: InternalServerError)

Network permission are granted and I've the required Quota.
I'm using these parameters:

location: westeurope

cassandraVersion: 4.1

dcName: dc-1

enableAvailabilityZones: true

sku: Standard_E8as_v5

diskCapacity: 1

nodeCount: 3

autoReplicate: AllKeyspaces

scheduledEventStrategy: StopByRack

clusterType: Production

extensions: []

clientCertificates: []

Thanks

Answer 1

Hi Ben

We checked this issue from the backend and found that there was internal mapping issue, which has now been fixed. After the fix, the deployment path was unblocked.

Additionally, as you confirmed, the deployment succeeded after manually assigning the required Cosmos DB permissions on the virtual network. Once the correct network permissions were in place, the Azure Managed Instance for Apache Cassandra was able to deploy successfully.

Answer 2

It seems that you're encountering an Internal Server Error while trying to create an Azure Managed Instance for Apache Cassandra. Here are some troubleshooting steps you can consider:

1. Check Permissions: Ensure that the necessary permissions are granted for your virtual network. You can apply permissions manually from the Azure portal if you encounter issues using the Azure CLI. This includes checking if the Azure Cosmos DB service principal is correctly assigned.
2. Validate Parameters: Double-check the parameters you are using for the deployment. Ensure that the location, cassandraVersion, dcName, sku, and other parameters are correctly specified and supported in the region you are deploying.
3. Quota Limits: Although you mentioned that you have the required quota, it's a good idea to verify that you have not exceeded any limits for the resources you are trying to create.
4. Review Azure Activity Logs: Check the Azure Activity Logs for any additional details related to the error. This might provide more context or specific issues related to your deployment.
5. Contact Support: If the issue persists, consider reaching out to Azure support with the tracking ID and Activity ID provided in the error message for further assistance.

These steps should help you identify and resolve the issue with your Azure Managed Instance for Apache Cassandra deployment.

---

References:

• Quickstart: Create an Azure Managed Instance for Apache Cassandra cluster by using the Azure CLI
• Quickstart: Create a multi-region cluster with Azure Managed Instance for Apache Cassandra