problem
Calling resizeVolume with the existing volume details and not changing anything in wizard still invoked the storage driver, causing an unnecessary driver resize request for volumes.There is a flag for checking volumeresizerequire and volumemigraterequired but they aren't used to handle this case.
versions
The versions of ACS, hypervisors, storage, network etc..
4.23
The steps to reproduce the bug
1.Go to the volumes Tab
2.click on resize and do not change anything and click okay
3.It then shows volume resize in progress and in backend the driver call is made.
...
What to do about it?
using the already existing flags volumeresizerequired, newdiskoffering and volumemigraterequired, we can check those and return volume immediately when nothing is been changed.
problem
Calling resizeVolume with the existing volume details and not changing anything in wizard still invoked the storage driver, causing an unnecessary driver resize request for volumes.There is a flag for checking volumeresizerequire and volumemigraterequired but they aren't used to handle this case.
versions
The versions of ACS, hypervisors, storage, network etc..
4.23
The steps to reproduce the bug
1.Go to the volumes Tab
2.click on resize and do not change anything and click okay
3.It then shows volume resize in progress and in backend the driver call is made.
...
What to do about it?
using the already existing flags volumeresizerequired, newdiskoffering and volumemigraterequired, we can check those and return volume immediately when nothing is been changed.