-
Notifications
You must be signed in to change notification settings - Fork 332
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 clone controller shallow copy bug #1190
Fix clone controller shallow copy bug #1190
Conversation
Hi @1978629634. Thanks for your PR. I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@pohly Would you mind reviewing this PR for me? I value your expertise and feedback. |
Hi @RaunakShah @xing-yang, Could you please take a look at this pull request when you have a chance? I'd appreciate your review and feedback. |
/ok-to-test |
Thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 1978629634, jsafrane The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
What this PR does / why we need it:
If the cloner controller directly updates the PVC reference without using a deep copy and then calls the Update() method, it can lead to a situation where the cached PVC is updated (removing the finalizer), while the actual PVC remains unmodified in case the Update() operation fails.
Which issue(s) this PR fixes:
Fixes #1188
Special notes for your reviewer:
Does this PR introduce a user-facing change?: