OCPBUGS-33018: pkg/daemon: logSystem the Kube API errors that trigger a re-bootstrap

[wking]

OCPBUGS-33018 is wrestling with some surprise kubeletRebootstrap ErrAuxiliary 255 exits. Once the container exits, replacement containers crash-loop on content mismatch for file, which means that it's hard to get details about the error condition that triggered the re-bootstrap (and then exited leaving dirty disk state). By writing the error to the system logs, we're more likely to be able to understand what went wrong, and this will help us maintain the strings.Contains filtering going forward. If we notice re-bootstrap triggers that don't look like things that a re-bootstrap would help resolve, we can drop or adjust that trigger.

[openshift-ci-robot]

@wking: This pull request references Jira Issue OCPBUGS-33018, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

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:

OCPBUGS-33018 is wrestling with some surprise kubeletRebootstrap ErrAuxiliary 255 exits. Once the container exits, replacement containers crash-loop on content mismatch for file, which means that it's hard to get details about the error condition that triggered the re-bootstrap (and then exited leaving dirty disk state). By writing the error to the system logs, we're more likely to be able to understand what went wrong, and this will help us maintain the strings.Contains filtering going forward. If we notice re-bootstrap triggers that don't look like things that a re-bootstrap would help resolve, we can drop or adjust that trigger.

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.

[wking]

/jira refresh

[openshift-ci-robot]

@wking: This pull request references Jira Issue OCPBUGS-33018, 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.16.0) matches configured target version for branch (4.16.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

In response to this:

/jira refresh

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.

[yuqi-zhang]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wking, yuqi-zhang

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 [yuqi-zhang]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a9a5832 and 2 for PR HEAD 7df3a46 in total

[openshift-ci]

@wking: all tests passed!

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

[openshift-ci-robot]

@wking: Jira Issue OCPBUGS-33018: All pull requests linked via external trackers have merged:

• openshift/machine-config-operator#4337
• openshift/machine-config-operator#4342

Jira Issue OCPBUGS-33018 has been moved to the MODIFIED state.

In response to this:

OCPBUGS-33018 is wrestling with some surprise kubeletRebootstrap ErrAuxiliary 255 exits. Once the container exits, replacement containers crash-loop on content mismatch for file, which means that it's hard to get details about the error condition that triggered the re-bootstrap (and then exited leaving dirty disk state). By writing the error to the system logs, we're more likely to be able to understand what went wrong, and this will help us maintain the strings.Contains filtering going forward. If we notice re-bootstrap triggers that don't look like things that a re-bootstrap would help resolve, we can drop or adjust that trigger.

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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-machine-config-operator-container-v4.16.0-202405020546.p0.g203afde.assembly.stream.el9 for distgit ose-machine-config-operator.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.16.0-0.nightly-2024-05-08-222442