Open mgahagan73 opened 4 years ago
Hi, @mgahagan73, thanks for reporting this issue. Can you please share the your ARO v3 cluster resource id and log analytics workspace resource id to investigate what caused this error:"The entity was not found. "?
Following the steps in: https://docs.microsoft.com/en-ca/azure/openshift/tutorial-create-cluster results in a "not found" error however the cluster creates successfully with monitoring enabled: ` export WORKSPACE_ID=$(az monitor log-analytics workspace show -g $workspace-RG -n $workspace-name --query id -o tsv) az openshift create -g $myRG -n $myClusterName --aad-client-app-id $AZURE_CLIENT_ID --aad-client-app-secret $AZURE_CLIENT_SECRET --aad-tenant-id $AZURE_TENANT_ID --workspace-id $WORKSPACE_ID
Deployment failed. Correlation ID: xxxxxxxxxx. Operation failed with status: 'Not Found'. Details: The entity was not found. ` After 30-40 minutes the cluster is successfully created with monitoring enabled:
az openshift show --name $myClusterName --resource-group $myRG ... "monitorProfile": { "enabled": true, "workspaceResourceId": "/subscriptions/xxxxxxx/resourcegroups/xxxxxxx/providers/microsoft.operationalinsights/workspaces/xxxxxx" }, "name": "xxxxxxx", "networkProfile": { "vnetCidr": "10.0.0.0/8", "vnetId": "/subscriptions/xxxxxxx/resourceGroups/xxxxxxx/providers/Microsoft.Network/virtualNetworks/vnet" }, "openShiftVersion": "v3.11", "provisioningState": "Succeeded", "publicHostname": "xxxxxxx", "resourceGroup": "xxxxx"
So monitoring is in fact showing up as enabled despite the error message and the cluster is created successfullyDisabling monitoring and subsequently re-enabling it results in the same "not found" error but according to
az openshift show
the operations are successfull