You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugThis issue requires a change to an existing behavior in the product in order to be resolved.MgmtThis issue is related to a management-plane library.
400 Bad Request
x-ms-request-id df3d1ef8-177b-431f-a8c2-08951bc36c3e
x-ms-correlation-request-id df3d1ef8-177b-431f-a8c2-08951bc36c3e
{
"error": {
"code": "CannotSetResourceIdentity",
"message": "Resource type 'Microsoft.AzureStackHCI/clusters' does not support creation of 'UserAssigned' resource identity. The supported types are 'SystemAssigned'."
}
}
Environment
postman
The text was updated successfully, but these errors were encountered:
teowa
added
the
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
label
Mar 14, 2024
bugThis issue requires a change to an existing behavior in the product in order to be resolved.MgmtThis issue is related to a management-plane library.
API Spec link
azure-rest-api-specs/specification/azurestackhci/resource-manager/Microsoft.AzureStackHCI/stable/2024-01-01/clusters.json
Line 163 in 475747f
API Spec version
2023-08-01, 2024-01-01
Describe the bug
According to swagger,
UserAssigned
should be supported for identity, but accually API does not.azure-rest-api-specs/specification/azurestackhci/resource-manager/Microsoft.AzureStackHCI/stable/2024-01-01/clusters.json
Line 492 in 475747f
azure-rest-api-specs/specification/common-types/resource-management/v4/managedidentity.json
Lines 35 to 75 in 475747f
Expected behavior
The API should support
UserAssigned
for identity.Actual behavior
The API does not support
UserAssigned
for identity.Reproduction Steps
PUT https://management.azure.com/subscriptions/xxx/resourceGroups/wt-hcitest/providers/Microsoft.AzureStackHCI/clusters/cluster?api-version=2024-01-01
400 Bad Request
x-ms-request-id df3d1ef8-177b-431f-a8c2-08951bc36c3e
x-ms-correlation-request-id df3d1ef8-177b-431f-a8c2-08951bc36c3e
Environment
postman
The text was updated successfully, but these errors were encountered: