-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18, 4.19
This is a clone of issue OCPBUGS-47657. The following is the description of the original issue:
—
Description of problem:
Some new instance types are not listed in azure_dd_max_disk_count.go (1.29.11) in current 4.18
$ oc get node jima-26series-a-5f82p-worker-eastus1-gn84s -ojson | jq .metadata.labels
"node.kubernetes.io/instance-type": "Standard_D4alds_v6",
$ oc get csinode jima-26series-a-5f82p-worker-eastus1-gn84s -ojson | jq .spec.drivers[].allocatable
{
"count": 16
}
$ oc describe pod
12-26 11:25:17.298 Warning FailedAttachVolume 14m (x4 over 14m) attachdetach-controller AttachVolume.Attach failed for volume "pvc-66c09846-baf5-4a4a-bc00-3638e5c79c97" : rpc error: code = Internal desc = Attach volume /subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/jima-26series-a-5f82p-rg/providers/Microsoft.Compute/disks/pvc-66c09846-baf5-4a4a-bc00-3638e5c79c97 to instance jima-26series-a-5f82p-worker-eastus1-gn84s failed with Retriable: false, RetryAfter: 0s, HTTPStatusCode: 409, RawError: {\r
12-26 11:25:17.298 "error": {\r
12-26 11:25:17.298 "code": "OperationNotAllowed",\r
12-26 11:25:17.298 "message": "The maximum number of data disks allowed to be attached to a VM of this size is 8.",\r
12-26 11:25:17.298 "target": "dataDisks"\r
12-26 11:25:17.298 }\r
The instance types we found are:
Standard_D8ads_v6 Standard_D4ads_v6 Standard_D8alds_v6 Standard_D4alds_v6 Standard_D8als_v6 Standard_D4als_v6 Standard_D8as_v6 Standard_D4as_v6 Standard_E8ads_v6 Standard_E4ads_v6 Standard_E8as_v6 Standard_E4as_v6 Standard_F8als_v6 Standard_F4als_v6 Standard_F8ams_v6 Standard_F4ams_v6 Standard_F8as_v6 Standard_F8as_v6
Checked the upstream files, these types are present in master branch: https://github.com/kubernetes-sigs/azuredisk-csi-driver/blame/master/pkg/azuredisk/azure_dd_max_disk_count.go
Version-Release number of selected component (if applicable):
4.18
How reproducible:
Always
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to