-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
csiVolumeSnapshotsAttempted/Completed not correctly populated in backup status #7163
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Tried to reproduce.. looks like the CSI status were added but removed in finalizing phase. |
Regression sideeffect of #7111 which attempt to make another status update during finalize. During finalize, there is code in CSI plugin to delete finished snapshots
So it seems like to get reliable update of CSI snapshot status would be to track the snapshots in memory vs listing in cluster. Looking into if snapshots are only deleted upon successful CSI snapshot. |
Agree, because the CSI plugin will delete the VolumeSnapshot after backing up the volume, depending on VolumeSnapshot to count the metric is not right. |
If any plugin could add to the backup status that would also be cool. |
Update CSIVolumeSnapshotsCompleted in backup's status and the metric during backup finlize stage according to async operations content. Signed-off-by: Xun Jiang <jxun@vmware.com>
Update CSIVolumeSnapshotsCompleted in backup's status and the metric during backup finalize stage according to async operations content. Signed-off-by: Xun Jiang <jxun@vmware.com>
Update CSIVolumeSnapshotsCompleted in backup's status and the metric during backup finalize stage according to async operations content. Signed-off-by: Xun Jiang <jxun@vmware.com>
Update CSIVolumeSnapshotsCompleted in backup's status and the metric during backup finalize stage according to async operations content. Signed-off-by: Xun Jiang <jxun@vmware.com>
Reopen this issue to trace the v1.12.3 back port task. |
Update CSIVolumeSnapshotsCompleted in backup's status and the metric during backup finalize stage according to async operations content. Signed-off-by: Xun Jiang <jxun@vmware.com>
Update CSIVolumeSnapshotsCompleted in backup's status and the metric during backup finalize stage according to async operations content. Signed-off-by: Xun Jiang <jxun@vmware.com>
Update CSIVolumeSnapshotsCompleted in backup's status and the metric during backup finalize stage according to async operations content. Signed-off-by: Xun Jiang <jxun@vmware.com>
Update CSIVolumeSnapshotsCompleted in backup's status and the metric during backup finalize stage according to async operations content. Signed-off-by: Xun Jiang <jxun@vmware.com>
Close because the release-1.12 cherry-pick PR already merged. |
What steps did you take and what happened:
The backup CR's fields
.status.csiVolumeSnapshotsAttempted
&.status.csiVolumeSnapshotsCompleted
do not get populated when the backup completes even when csi snapshots are taken (not using data mover). Seems to be working on 1.12.1 so probably a regression somewhere?What did you expect to happen:
Fields to have non zero values.
The following information will help us better understand what's going on:
bk-1.txt
details.txt
logs.txt
Anything else you would like to add:
NA
Environment:
velero version
): commit 7320bb7velero client config get features
): EnableCSIkubectl version
):/etc/os-release
):Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: