-
Notifications
You must be signed in to change notification settings - Fork 550
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
[WIP][Testing]Flatten group snapshot #4973
base: devel
Are you sure you want to change the base?
Conversation
Signed-off-by: Rakshith R <[email protected]>
/test ci/centos/mini-e2e-helm/k8s-1.31 |
/test ci/centos/mini-e2e-helm/k8s-1.31 |
Signed-off-by: Rakshith R <[email protected]>
5 additional group snapshots are created and deleted successfully. |
d22ce45
to
234ae0c
Compare
/test ci/centos/mini-e2e-helm/k8s-1.31 |
/retest ci/centos/mini-e2e-helm/k8s-1.31 |
E2E changes in this pr adds creation & deletion of additional volumegroupsnapshots.
|
This commit consolidates flatten logic checks for cloneDepth and snapshotLimit in PrepareVolumeForSnapshot. This allows the function to be called for both CreateSnapshot and CreateVolumeGroupSnapshot. Clone Depth check and flattening of grand parent image now occurs before creation of snapshot starts. This aligns better with how PVC-PVC clone and PVC-restore process occurs currently. Flattening the grandparent image once prevents flattening of every newly created snapshot. Snapshot in above para refers to k8s VolumeSnapshot (which is backed by a rbd image). Signed-off-by: Rakshith R <[email protected]>
4c35c58
to
8882254
Compare
/test ci/centos/mini-e2e-helm/k8s-1.31 |
8882254
to
43cf95f
Compare
/test ci/centos/mini-e2e-helm/k8s-1.31 |
Signed-off-by: Rakshith R <[email protected]>
43cf95f
to
5edecc9
Compare
/test ci/centos/mini-e2e-helm/k8s-1.31 |
Signed-off-by: Rakshith R <[email protected]>
/test ci/centos/mini-e2e-helm/k8s-1.31 |
Describe what this PR does
Provide some context for the reviewer
Is there anything that requires special attention
Do you have any questions?
Is the change backward compatible?
Are there concerns around backward compatibility?
Provide any external context for the change, if any.
For example:
Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.
Fixes: #issue_number
Future concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.
Checklist:
guidelines in the developer
guide.
Request
notes
updated with breaking and/or notable changes for the next major release.
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>
: retest the<job-name>
after unrelatedfailure (please report the failure too!)