Handle error when CR is in conflict

[opokornyy]

What this PR does / why we need it:

When action on CR is rejected by API server,
dont show the error in log and reenque the request.

Which issue(s) this PR fixes:

Fixes #323

Release note:

NONE

Signed-off-by: Ondrej Pokorny opokorny@redhat.com

[openshift-ci]

Hi @opokornyy. Thanks for your PR.

I'm waiting for a kubevirt 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.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[ksimon1]

/ok-to-test

[ksimon1]

/retest

[akrejcir]

Have you tested that the error is no longer in logs after this change?

[akrejcir]

/lgtm
/approve

[akrejcir]

/lgtm
/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akrejcir

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 [akrejcir]

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