OCPBUGS-44970: Excluding loki prod-bearer-token container from excessive restarts test in SNO

[jaypoulz]

This container is deployed by https://github.com/openshift/release/tree/master/ci-operator/step-registry/ipi/install/hosted-loki and is sensitive to resolving sso.redhat.com. During an SNO upgrade, there is a brief period of time where dns is unavailable because the only instance of the pod has been killed and the new pod is starting up. The goal of this change is to exclude this container from the excessive restart checks since, depending on the exact timing, it can restart enough times to trigger a failed test.

[openshift-ci-robot]

@jaypoulz: This pull request references Jira Issue OCPBUGS-44970, 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:

This container is deployed by https://github.com/openshift/release/tree/master/ci-operator/step-registry/ipi/install/hosted-loki and is sensitive to resolving sso.redhat.com. During an SNO upgrade, there is a brief period of time where dns is unavailable because the only instance of the pod has been killed and the new pod is starting up. The goal of this change is to exclude this container from the excessive restart checks since, depending on the exact timing, it can restart enough times to trigger a failed test.

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.

[jaypoulz]

/jira refresh

[openshift-ci-robot]

@jaypoulz: This pull request references Jira Issue OCPBUGS-44970, 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)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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.

[jaypoulz]

/hold

I really don't like this fix. But it's here in case this test creates too much noise in the blocking SNO upgrade lane.
See https://redhat-internal.slack.com/archives/C01CQA76KMX/p1732646630858199?thread_ts=1732543112.314749&cid=C01CQA76KMX for follow up.

[jaypoulz]

/retest-required

[openshift-ci]

@jaypoulz: 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-openstack-ovn	6428725	link	false	/test e2e-openstack-ovn
ci/prow/e2e-agnostic-ovn-cmd	6428725	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/okd-scos-e2e-aws-ovn	6428725	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-single-node-serial	6428725	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node-upgrade	6428725	link	false	/test e2e-aws-ovn-single-node-upgrade

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.

[jeff-roche]

/unhold
/lgtm

[sosiouxme]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jaypoulz, jeff-roche, sosiouxme

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

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 a44573b and 2 for PR HEAD 6428725 in total

[openshift-ci-robot]

@jaypoulz: Jira Issue OCPBUGS-44970: All pull requests linked via external trackers have merged:

• openshift/origin#29329

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

In response to this:

This container is deployed by https://github.com/openshift/release/tree/master/ci-operator/step-registry/ipi/install/hosted-loki and is sensitive to resolving sso.redhat.com. During an SNO upgrade, there is a brief period of time where dns is unavailable because the only instance of the pod has been killed and the new pod is starting up. The goal of this change is to exclude this container from the excessive restart checks since, depending on the exact timing, it can restart enough times to trigger a failed test.

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]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.19.0-202412060336.p0.g4def802.assembly.stream.el9.
All builds following this will include this PR.

[jaypoulz]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@jaypoulz: new pull request created: #29360

In response to this:

/cherry-pick release-4.18

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.