Modify cloud block volume is successful but size is not updated

sodafoundation / strato

SODA Strato (Multi-cloud) project provides a cloud vendor agnostic data management for hybrid cloud, intercloud or intracloud. This project is renamed as 'Strato'

Apache License 2.0

234 stars 329 forks source link

Modify cloud block volume is successful but size is not updated #1103

Open anvithks opened 4 years ago

anvithks commented 4 years ago

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

himanshuvar commented 4 years ago

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

anvithks commented 4 years ago

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 commented 4 years ago

@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

API response

From AWS Console

AWS Console API response

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

himanshuvar commented 4 years ago

@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