OCPBUGS-60851: UPSTREAM: <carry>: Revert "Bump 1.33.4"

[stbenjam]

Reverts #2416

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

After this bump merged, metal IPv6 disconnected jobs started permafailing on image pulls. This appears similar to OCPBUGS-3016.

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:

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-upgrade-ovn-ipv6

cc: @kevinrizza

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

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

Reverts #2416

Floating a revert to see if it helps metal IPv6 jobs

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

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• e71435f|Revert "OCPBUGS-60507: Bump 1.33.4": does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[stbenjam]

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6

[openshift-ci]

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

• periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a32b4a20-8216-11f0-904a-cac3b38219be-0

[stbenjam]

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-upgrade-ovn-ipv6

[openshift-ci]

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

• periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-upgrade-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b53e5d60-8216-11f0-9a52-52259d90b819-0

[wangke19]

@vrutkovs failures of events should not repeat pathologically, It seems to be related to some recent updates for bug OCPBUGS-55217.

[vrutkovs]

It seems to be related to some recent updates for bug

We need openshift/cluster-kube-apiserver-operator#1901 to land in 4.19 to make it go away in 4.20 (its already fixed in 4.21)

[openshift-ci-robot]

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 05a24c5|UPSTREAM: : Revert "OCPBUGS-60507: Bump 1.33.4": does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[stbenjam]

/remove-label backports/unvalidated-commits
/label backports/validated-commits

[openshift-ci-robot]

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

Reverts #2416

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

After this bump merged, metal IPv6 disconnected jobs started permafailing on image pulls. This appears similar to OCPBUGS-3016.

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:

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-upgrade-ovn-ipv6

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

@stbenjam: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

Reverts #2416

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

After this bump merged, metal IPv6 disconnected jobs started permafailing on image pulls. This appears similar to OCPBUGS-3016.

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:

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-upgrade-ovn-ipv6

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

@stbenjam: This pull request references Jira Issue OCPBUGS-60851, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.0) matches configured target version for branch (4.20.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:

Reverts #2416

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

After this bump merged, metal IPv6 disconnected jobs started permafailing on image pulls. This appears similar to OCPBUGS-3016.

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:

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-upgrade-ovn-ipv6

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.

[smg247]

/lgtm

[bertinatto]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, smg247, stbenjam

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:

• DOWNSTREAM_OWNERS [bertinatto]

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

[stbenjam]

/label acknowledge-critical-fixes-only

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 42c7d00 and 2 for PR HEAD 05a24c5 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 42c7d00 and 2 for PR HEAD 05a24c5 in total

[openshift-ci]

@stbenjam: 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-aws-ovn-techpreview	05a24c5	link	false	/test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn-techpreview-serial	05a24c5	link	false	/test e2e-aws-ovn-techpreview-serial

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]

@stbenjam: Jira Issue OCPBUGS-60851: Some pull requests linked via external trackers have merged:

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

• openshift/kubernetes#2424 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-60851 has not been moved to the MODIFIED state.

In response to this:

Reverts #2416

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

After this bump merged, metal IPv6 disconnected jobs started permafailing on image pulls. This appears similar to OCPBUGS-3016.

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:

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-upgrade-ovn-ipv6

cc: @kevinrizza

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.