az aks update fails due to ERROR: (LinkedInvalidPropertyId) Property id '' at path 'properties.addonProfiles.omsagent.config.LogAnalyticsWorkspaceResourceID' is invalid. #29210
Labels
AKS
az aks/acs/openshift
Auto-Assign
Auto assign by bot
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Service Attention
This issue is responsible by Azure service team.
Describe the bug
Whenever
az aks update
runs, it fails with an errorERROR: (LinkedInvalidPropertyId) Property id '' at path 'properties.addonProfiles.omsagent.config.LogAnalyticsWorkspaceResourceID' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'. Code: LinkedInvalidPropertyId Message: Property id '' at path 'properties.addonProfiles.omsagent.config.LogAnalyticsWorkspaceResourceID' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'.
Related command
az aks update
Errors
ERROR: (LinkedInvalidPropertyId) Property id '' at path 'properties.addonProfiles.omsagent.config.LogAnalyticsWorkspaceResourceID' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'. Code: LinkedInvalidPropertyId Message: Property id '' at path 'properties.addonProfiles.omsagent.config.LogAnalyticsWorkspaceResourceID' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'.
Issue script & Debug output
$ az aks show -n cluster-name -g rg-name
I don't know when exactly this started, but we were running same clusters for years already in the same configuration and this was never an issue. The monitoring addon was never enabled on these clusters. Now we have a bunch of clusters where update operation fails randomly.
Expected behavior
Do not fail update configuration with disabled addon config.
Environment Summary
"azure-cli": "2.61.0",
"azure-cli-core": "2.61.0",
"azure-cli-telemetry": "1.1.0",
Additional context
No response
The text was updated successfully, but these errors were encountered: