suryag1201 opened a new issue, #14261: URL: https://github.com/apache/cloudstack/issues/14261
### problem Problem Description On Resize Volume, the form did not show the volume’s current size and Custom IOPS. It also used the first disk offering in the list, not the offering already attached to the volume. So the dialog often opened empty or with the wrong IOPS fields. Root cause Three UI issues in fetchData(): 1- Size unit — the API stores size in bytes. The form label is GB. Size was never copied onto the form, so the GB field stayed empty. 2- Wrong offering — the code always used this.offerings[0] (first offering returned by listDiskOfferings), not this.resource.diskofferingid (the volume’s offering). Custom size / custom IOPS flags could be wrong. 3- IOPS not filled — even when min/max IOPS existed on the volume, they were not copied into form.miniops / form.maxiops. ### versions _No response_ ### The steps to reproduce the bug Steps to reproduce Create a volume with a custom IOPS disk offering (for example min 2000, max 5000) and a known size (for example 20 GB). Open Storage → Volumes → Resize. Check the Size (GB) field and the Min/Max IOPS fields. ### What to do about it? Expected behaviour When Resize opens: 1-Size is the current volume size in GB 2-Custom IOPS fields follow this volume’s disk offering. 3-If that offering has custom IOPS, min/max are prefilled from the volume. User can then change size or IOPS and submit resizeVolume with the right values. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
