strato icon indicating copy to clipboard operation
strato copied to clipboard

Published 20 hours ago • verified publisher icon sodafoundation

Modify cloud block volume is successful but size is not updated

Open anvithks opened this issue 3 years ago • 5 comments

Issue/Feature Description: When an AWS cloud block volume is updated from the dashboard the update API is successful and the API returns the updated value in the response. After a while in the subsequent GET requests the value of the Volume is reverted back to the original value.

Why this issue to fixed / feature is needed(give scenarios or use cases): Size is modified but the incorrect, old value is returned.

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

PUT Request Payload vol-modify-1

PUT Request response vol-modify-2

Docker logs for PUT vol-modify-3

Subsequent GET response value in dashboard vol-modify-4

anvithks avatar Sep 24 '20 11:09 anvithks

@anvithks Are you sending GET Volume after the PUT operation successful or in between PUT operation going on?

himanshuvar avatar Sep 25 '20 03:09 himanshuvar

There is one get operation immediately after to populate the table. In that the status is updating. After a while when the table is refreshed the status is available. This is where the size is inconsistent.

anvithks avatar Sep 25 '20 03:09 anvithks

@himanshuvar I encountered this issue again when I was making a demo. I have a video recording that shows the updated the size and then after a few GET calls the size is reverted back to the original size.

Display in SODA Dashboard image

API response image

From AWS Console image

AWS Console API response image

The volume is still available in the console if you want to debug.

anvithks avatar Oct 02 '20 15:10 anvithks

@anvithks I am not able to reproduce this Issue. I have tested the following API calls/operations on Greenland release. All operations worked fine successfully as expected. Are you sure you have encountered this Issue from Dashboard using Greenland multi-cloud release. Please check the following Snapshots for the API calls.

Create a 1GB gp2 Volume 1

docker logs 2

Volume Created Successfully with the expected size in Backend 3

Get Volume API result 4

Update the created Volume to Resize it to 300GB 5

docker logs 6

Volume Size is updated at Backend 7

Get Volume API result 8

@kumarashit @skdwriting Please review this Issue and let me know if APIs are deviated from expected results.

himanshuvar avatar Oct 05 '20 12:10 himanshuvar

@himanshuvar You can check the video recording for the above API responses. Please check from 00:46 onwards.

anvithks avatar Oct 14 '20 03:10 anvithks