OCPBUGS-33894: Avoid dumping Go struct in potentially user-facing reason annotation

[djoshy]

- What I did

• Use nodeName instead of node in error message for setting node annotations. On a degraded node, such an error would result in the entire node object to be dumped in the node's annotation which was not user friendly.
• I also changed retry mechanism to use a backoff of retry.DefaultRetry, instead of retry.DefaultBackoff which is recommended for conflicts.

- How to verify it

• Reading through the bug, this seems to surface during upgrades/installs when the APIServer goes unavailable/nodes have high activity. It may be useful to simulate such conditions and see if the errors resurface.
• I suppose one could also explore ways to make the API update calls from the MCO to fail to simulate a retry error scenario.

[openshift-ci-robot]

@djoshy: This pull request references Jira Issue OCPBUGS-33894, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

- What I did

• Use nodeName instead of node in error message for setting node annotations. On a degraded node, such an error would result in be stored in the node's annotation which was not user friendly.
• I also changed retry mechanism to use a backoff of retry.DefaultRetry, instead of retry.DefaultBackoff which is recommended for conflicts.

- How to verify it

• Reading through the bug, this seems to surface during upgrades/installs when the APIServer goes unavailable/nodes have high activity. It may be useful to simulate such conditions and see if the errors resurface.
• I suppose one could also explore ways to make the API update calls from the MCO to fail to simulate a retry error scenario.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy

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

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

[djoshy]

/jira refresh

This may potentially alleviate https://issues.redhat.com/browse/OCPBUGS-33891, but I am unsure at this time

[openshift-ci-robot]

@djoshy: This pull request references Jira Issue OCPBUGS-33894, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

In response to this:

/jira refresh

This may potentially alleviate https://issues.redhat.com/browse/OCPBUGS-33891, but I am unsure at this time

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@djoshy: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-azure-ovn-upgrade-out-of-change	fb86e86	link	false	/test e2e-azure-ovn-upgrade-out-of-change
ci/prow/okd-scos-e2e-aws-ovn	fb86e86	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-hypershift	fb86e86	link	true	/test e2e-hypershift
ci/prow/bootstrap-unit	fb86e86	link	false	/test bootstrap-unit

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@djoshy: This pull request references Jira Issue OCPBUGS-33894, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

In response to this:

- What I did

• Use nodeName instead of node in error message for setting node annotations. On a degraded node, such an error would result in the entire node object to be dumped in the node's annotation which was not user friendly.
• I also changed retry mechanism to use a backoff of retry.DefaultRetry, instead of retry.DefaultBackoff which is recommended for conflicts.

- How to verify it

• Reading through the bug, this seems to surface during upgrades/installs when the APIServer goes unavailable/nodes have high activity. It may be useful to simulate such conditions and see if the errors resurface.
• I suppose one could also explore ways to make the API update calls from the MCO to fail to simulate a retry error scenario.

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 openshift-eng/jira-lifecycle-plugin repository.