🐛 allow fakeclient to patch CR with no RV

[alexandremahdhaoui]

Context

This PR should fix a bug #2678 where patching a resource would throw a conflict error when the new object doesn't specify any RV.

Changes

• Fix patch by setting the new accessors' RV to the old accessors' RV.
• Add test to ensure the correct behavior

[k8s-ci-robot]

Hi @alexandremahdhaoui. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[sbueringer]

/ok-to-test

[sbueringer]

Thx!

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: c3d84995b9825e753818b3cd1dfb3691a9ec5ae7

[sbueringer]

/assign @alvaroaleman

[alvaroaleman]

thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexandremahdhaoui, alvaroaleman

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:

• OWNERS [alvaroaleman]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment