vCD IOPS value is not applied to VMs created with the autoscale function.

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• Autoscaling cannot apply the vCD IOPS value set in the storage policy to the VM.

• If you manually create a vApp with the same storage policy and template, the IOPS values are applied correctly.

• This issue can be seen as follows. Once the correct IOPS value is set, it is returned to the default value.

vpxd.log
----
2023-12-07T16:36:41.867+09:00 verbose vpxd[05189] [Originator@6876 sub=vmmoVm opID=vcd-4d935984-####-####-####-########471-cbf6e26d-####-####-####-########e54;activity=urn:uuid:50f2f270-####-####-####-########091-d8-01] Changes after reconfigureVM config.hardware.device(2000).storageIOAllocation.limit: -1 -> 200;
-->
--> config.hardware.device(2000).storageIOAllocation.reservation: 0 -> 200;
-->
--> config.hardware.device(2001).storageIOAllocation.limit: -1 -> 200;
-->
--> config.hardware.device(2001).storageIOAllocation.reservation: 0 -> 200;
-->
--> added deleted
:
:
2023-12-07T16:36:52.804+09:00 verbose vpxd[05011] [Originator@6876 sub=vmmoVm opID=vcd-4d935984-####-####-####-########471-cbf6e26d-####-####-####-########e54;activity=urn:uuid:78274669-####-####-####-########c9b-12-01] Changes after reconfigureVM config.hardware.device(2000).storageIOAllocation.limit: 200 -> -1;
-->
--> config.hardware.device(2000).storageIOAllocation.reservation: 200 -> 0;
-->
--> config.hardware.device(2001).storageIOAllocation.limit: 200 -> -1;
-->
--> config.hardware.device(2001).storageIOAllocation.reservation: 200 -> 0;
-->
--> added deleted
----

Environment

VMware Cloud Director 10.5
VMware Cloud Director 10.4.1
VMware Cloud Director 10.x
VMware Cloud Director 10.5.1

Cause

Autoscale resets the IOPS value to null during the VM creation process.

Resolution

VMware is aware of this issue and working to resolve this in a future release.

Workaround:

vSphere IOPS is not affected by this issue and can be used instead of vCD IOPS.
Refer to Enabling the I/O Operations Per Second Setting in Your VMware Cloud Director.