OCPBUGS-28230: add FallbackToLogsOnError for easier debugging

[deads2k]

All openshift operators must include FallbackToLogsOnError to ease debugging.

[openshift-ci-robot]

@deads2k: This pull request references Jira Issue OCPBUGS-28230, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)

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

In response to this:

All openshift operators must include FallbackToLogsOnError to ease debugging.

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

[yuqi-zhang]

There's technically also the MachineConfigServer pod (which normally is idle and doesn't really break), do you want to add that as well?

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, 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 2464fef and 2 for PR HEAD bee2519 in total

[deads2k]

There's technically also the MachineConfigServer pod (which normally is idle and doesn't really break), do you want to add that as well?

Good catch. That one is already set: https://github.com/openshift/machine-config-operator/blob/master/manifests/machineconfigserver/daemonset.yaml#L30

[yuqi-zhang]

Ack, thanks for the clarification! This is for catching any remaining containers (rbac-proxy's) I see

[djoshy]

/override ci/prow/e2e-gcp-op-single-node

Test is currently broken, and this change is unrelated

[openshift-ci]

@djoshy: Overrode contexts on behalf of djoshy: ci/prow/e2e-gcp-op-single-node

In response to this:

/override ci/prow/e2e-gcp-op-single-node

Test is currently broken, and this change is unrelated

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.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a3dbd65 and 1 for PR HEAD bee2519 in total

[deads2k]

/retest

[deads2k]

/retest

[djoshy]

/override ci/prow/e2e-gcp-op-single-node

[openshift-ci]

@djoshy: Overrode contexts on behalf of djoshy: ci/prow/e2e-gcp-op-single-node

In response to this:

/override ci/prow/e2e-gcp-op-single-node

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.

[djoshy]

/retest-required

[djoshy]

/override ci/prow/e2e-gcp-op-single-node

[openshift-ci]

@djoshy: Overrode contexts on behalf of djoshy: ci/prow/e2e-gcp-op-single-node

In response to this:

/override ci/prow/e2e-gcp-op-single-node

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.

[openshift-ci]

@deads2k: The following test 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/okd-scos-e2e-aws-ovn	bee2519	link	false	/test okd-scos-e2e-aws-ovn

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]

@deads2k: Jira Issue OCPBUGS-28230: Some pull requests linked via external trackers have merged:

• openshift/cloud-credential-operator#663
• openshift/machine-api-operator#1211

The following pull requests linked via external trackers have not merged:

• openshift/origin#28547 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to this:

All openshift operators must include FallbackToLogsOnError to ease debugging.

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 openshift-proxy-pull-test-container-v4.16.0-202401281812.p0.gc5f53e2.assembly.stream for distgit openshift-proxy-pull-test.
All builds following this will include this PR.