You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The RestoreSize of each volumesnapshotcontent is set to 0 even though CSI responds back the size the VolumeGroupSnapshostCreate Response, This might be because the snapshotter create the VSC with empty status and its also reconciling the VSC and Doing GetVolumeSnapshot and updating the size
@xing-yang is this something that we can fix? i tried to fix it Madhu-1@9382f1a this way i am not sure if this is the correct approach or not, if yes i can make a PR from it.
Calling the ListSnapshots CSI procedure should not be required. The RestoreSize of each snapshot is returned as part of the reply to the CreateGroupSnapshot CSI procedure (see repeated Snapshot snapshots = 2in the spec).
What happened:
The RestoreSize of each volumesnapshotcontent is set to
0
even though CSI responds back the size the VolumeGroupSnapshostCreate Response, This might be because the snapshotter create the VSC with empty status and its also reconciling the VSC and Doing GetVolumeSnapshot and updating the sizeexternal-snapshotter/pkg/sidecar-controller/snapshot_controller.go
Lines 282 to 296 in 533a2ee
Not all CSI drivers implement ListSnapshots as it's not a mandatory RPC call.
What you expected to happen:
How to reproduce it:
The RestoreSize of each volumesnapshotcontent is set to the actual size returned in VolumeGroupSnapshostCreate Response
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: