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
Empty size issue: 4.15.1.0 and later
Wrong offering issue : 4.17.0.0 and later
The steps to reproduce the bug
Steps to reproduce
1-Create a volume with a custom IOPS disk offering (for example min 2000, max 5000) and a known size (for example 20 GB).
2-Open Storage → Volumes → Resize.
3-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.
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
Empty size issue: 4.15.1.0 and later
Wrong offering issue : 4.17.0.0 and later
The steps to reproduce the bug
Steps to reproduce
1-Create a volume with a custom IOPS disk offering (for example min 2000, max 5000) and a known size (for example 20 GB).
2-Open Storage → Volumes → Resize.
3-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.