Azure / Azure/OpenShift

Creating a cluster with monitoring enabled results in a "not found" error but cluster creates successfully

Open
#137 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
121
Forks
42
PR merge metrics
No merged PRs in 30d

Description

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 successfully

Disabling monitoring and subsequently re-enabling it results in the same "not found" error but according to `az openshift show` the operations are successfull

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.