-
Notifications
You must be signed in to change notification settings - Fork 108
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
fix(controller): prevent zfs volume cr deletion if snapshot exists #613
Conversation
a961d15
to
78048a5
Compare
@tiagolobocastro PR #607 is closed as there was some issue from my side while rebasing. I have created this PR with the same code base along with checking that ZV is present in the system as per your comment here. Splitting the test to run on different cluster can be taken sometime later. |
8e135cc
to
39b0fc7
Compare
39b0fc7
to
aa02172
Compare
5eb7e8f
to
54c716b
Compare
ff1251d
to
3d5c36a
Compare
3d5c36a
to
47da3ff
Compare
7e8f590
to
2005206
Compare
Looks good to me mostly. Thanks for taking this up. Will approve once the test passes and the other comments are addressed. |
46f95ef
to
d0ae251
Compare
d0ae251
to
0964543
Compare
0964543
to
ab012d5
Compare
Signed-off-by: sinhaashish <[email protected]>
ab012d5
to
94527d2
Compare
Pull Request template
Why is this PR required? What issue does it fix?:
Upon pvc deletion the zfs snapshot also gets deleted. this can be verified using ssh into the node and running the command zfs list -t all
What this PR does?:
Does this PR require any upgrade changes?:
If the changes in this PR are manually verified, list down the scenarios covered::
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>