NO-ISSUE: [release-4.15] Backport flaky CRD upgrade block e2e test fix

[perdasilva]

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 85d9de20d53b025ed62ec2fa0ab7fd8980669fb8

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

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

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]

@perdasilva: This pull request explicitly references no jira issue.

In response to this:

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 85d9de20d53b025ed62ec2fa0ab7fd8980669fb8

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.

[kevinrizza]

This is a test pr backport to improve ci signal in the 4.15 release branch. Since nothing will get modified in the ocp payload, I'm going to force apply the approval labels.

/label cherry-pick-approved
/label backport-risk-assessed

[openshift-ci]

@kevinrizza: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

This is a test pr backport to improve ci signal in the 4.15 release branch. Since nothing will get modified in the ocp payload, I'm going to force apply the approval labels.

/label cherry-pick-approved
/label backport-risk-assessed

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]

@perdasilva: 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.

[kevinrizza]

/lgtm

[perdasilva]

/jira refresh

[openshift-ci-robot]

@perdasilva: This pull request explicitly references no jira issue.

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.

[joelanford]

This is a test pr backport to improve ci signal in the 4.15 release branch. Since nothing will get modified in the ocp payload, I'm going to force apply the jira/valid-bug label.

/label jira/valid-bug

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-registry-container-v4.15.0-202402131807.p0.g0e8b957.assembly.stream.el9 for distgit operator-registry.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-lifecycle-manager-container-v4.15.0-202402131807.p0.g0e8b957.assembly.stream.el9 for distgit operator-lifecycle-manager.
All builds following this will include this PR.