changes for snapshot creation in CG #1417
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: hemalathagajendran <[email protected]>
Signed-off-by: hemalathagajendran <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snapshot creation is not allowed within snap window once a snapshot is taken for any dependent volume under CG. In the customer env snapshot creation fails due to snap window not expired but at the same time earlier snapshot was also deleted. Even though it got deleted the failed request would be triggered again by kubernetes and snapshot would be created in next request. Here the fix is given to check and create snapshot the first time only
Please check the type of change your PR introduces:
How risky is this change?