Property 'dataDisk.diskIOPSReadWrite' can be enabled only on VMs in a Virtual Machine Scale Set.

[jsanchezmartinez]

What happened:
Since a few hours ago I'm having issues attaching PVCs in OpenShift (ARO).

What you expected to happen:
PVC disks attached to VMs.

How to reproduce it:
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: managed-premium
provisioner: disk.csi.azure.com
parameters:
storageaccounttype: Premium_LRS
reclaimPolicy: Delete
allowVolumeExpansion: true
volumeBindingMode: WaitForFirstConsumer

Anything else we need to know?:

RESPONSE 400: 400 Bad Request
ERROR CODE: InvalidParameter
{
"error": {
"code": "InvalidParameter",
"message": "Property 'dataDisk.diskIOPSReadWrite' can be enabled only on VMs in a Virtual Machine Scale Set.",
"target": "dataDisk.diskIOPSReadWrite"
}
}

Environment:

• CSI Driver version: v1.32.0
• Kubernetes version (use kubectl version): v1.32.9
• OS (e.g. from /etc/os-release): Red Hat Enterprise Linux
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[andyzhangx]

that's a limitation or by design, @jsanchezmartinez how did you set that value? by using ModifyVolume API?

[jsanchezmartinez]

Hi,
The issue started last Friday evening and no longer happening after Sunday evening. I'm just using the default ARO StorageClass and a PVC object:

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: managed-premium
  annotations:
    storageclass.kubernetes.io/is-default-class: 'true'
provisioner: disk.csi.azure.com
parameters:
  kind: Managed
  storageaccounttype: Premium_LRS
reclaimPolicy: Delete
allowVolumeExpansion: true
volumeBindingMode: WaitForFirstConsumer
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: test
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 4Gi
  storageClassName: managed-premium
  volumeMode: Filesystem
status:
  phase: Bound
  accessModes:
    - ReadWriteOnce
  capacity:
    storage: 4Gi

Maybe a change in Azure API? Do you want to analyze anything (i.e., logs) or just close the issue as is no longer happening?
Regards,

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale