TRT-2560: Revert #638 "OCPBUGS-65634: add service account to verify pod"

[petr-muller]

Reverts #638 ; tracked by TRT-2560

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

The verify-all-openshiftredhatoperators pod introduced by this PR triggers the KubePodNotReady alert (alert/KubePodNotReady should not be at or above info in ns/default) in 4.22 upgrade-from-4.21 CI jobs across multiple platforms (AWS, Azure with OVN). This is causing aggregated job failures and blocking nightly payloads.

Example aggregated failure: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-aws-ovn-upgrade-4.22-minor-release-openshift-release-analysis-aggregator/2026880209889792000
Example individual failure: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-azure-ovn-upgrade/2026898179982626816

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

• e2e-aws-ovn-upgrade (4.22 from 4.21)
• e2e-azure-ovn-upgrade (4.22 from 4.21)

CC: @ehearne-redhat

[openshift-ci-robot]

@petr-muller: This pull request references TRT-2560 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the ticket to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Reverts #638 ; tracked by TRT-2560

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

The verify-all-openshiftredhatoperators pod introduced by this PR triggers the KubePodNotReady alert (alert/KubePodNotReady should not be at or above info in ns/default) in 4.22 upgrade-from-4.21 CI jobs across multiple platforms (AWS, Azure with OVN). This is causing aggregated job failures and blocking nightly payloads.

Example aggregated failure: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-aws-ovn-upgrade-4.22-minor-release-openshift-release-analysis-aggregator/2026880209889792000
Example individual failure: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-azure-ovn-upgrade/2026898179982626816

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

• e2e-aws-ovn-upgrade (4.22 from 4.21)
• e2e-azure-ovn-upgrade (4.22 from 4.21)

CC: @ehearne-redhat

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 NOT APPROVED

This pull-request has been approved by: petr-muller
Once this PR has been reviewed and has the lgtm label, please assign perdasilva for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[petr-muller]

/payload-aggregate periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-azure-ovn-upgrade 10

[openshift-ci]

@petr-muller: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/82ce5630-1309-11f1-9d45-a4fe0be5e7cf-0

[petr-muller]

/hold

wait for #647 (comment)

[tmshort]

@petr-muller, #638 broke our downstream bumper, so we have to manually revert it using our bumper process anyways... I'm working on it now.

[tmshort]

See #648 for a bumper fix.

[petr-muller]

No signs of the issue in https://pr-payload-tests.ci.openshift.org/runs/ci/82ce5630-1309-11f1-9d45-a4fe0be5e7cf-0 which confirms the revert addresses TRT-2560

[petr-muller]

/verified by https://pr-payload-tests.ci.openshift.org/runs/ci/82ce5630-1309-11f1-9d45-a4fe0be5e7cf-0

Not sure if #648 is the thing that needs to merge instead of the revert here, asking on Slack. Leaving the hold here for now.

[openshift-ci-robot]

@petr-muller: This PR has been marked as verified by https://pr-payload-tests.ci.openshift.org/runs/ci/82ce5630-1309-11f1-9d45-a4fe0be5e7cf-0.

Details

In response to this:

/verified by https://pr-payload-tests.ci.openshift.org/runs/ci/82ce5630-1309-11f1-9d45-a4fe0be5e7cf-0

Not sure if #648 is the thing that needs to merge instead of the revert here, asking on Slack. Leaving the hold here for now.

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.

[petr-muller]

/close

We need #648

[openshift-ci]

@petr-muller: Closed this PR.

Details

In response to this:

/close

We need #648

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.