[release-4.15] OCPBUGS-25798: Fix snapshot failure, backport e2es

[kevinrizza]

This pr fixes an issue with deprecation propogation with certain operatorgroup contexts

Additionally, this pr pulls in a set of e2e improvements to increase our signal for release backports

[openshift-ci-robot]

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

Details

In response to this:

This pr pulls in a set of e2e improvements to increase our signal for release backports

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 APPROVED

This pull-request has been approved by: kevinrizza

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS [kevinrizza]

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

[dtfranz]

/lgtm

[kevinrizza]

these test failures seem unrelated to the pull request

/test e2e-gcp-ovn

[openshift-ci]

@kevinrizza: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[dtfranz]

@Xia-Zhao-rh , this PR contains both #666 and e2e fixes required to enable us to merge changes to 4.15. Would you also mind giving your labels here?

[kevinrizza]

/label backport-risk-assessed

[openshift-ci-robot]

@kevinrizza: This pull request references Jira Issue OCPBUGS-25798, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-24526 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-24526 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
• bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

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

Details

In response to this:

This pr pulls in a set of e2e improvements to increase our signal for release backports

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.

[Xia-Zhao-rh]

/label cherry-pick-approved

[openshift-ci-robot]

@kevinrizza: Jira Issue OCPBUGS-25798: Some pull requests linked via external trackers have merged:

• openshift/operator-framework-olm#643

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

• openshift/operator-framework-olm#666 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-25798 has not been moved to the MODIFIED state.

Details

In response to this:

This pr fixes an issue with deprecation propogation with certain operatorgroup contexts

Additionally, this pr pulls in a set of e2e improvements to increase our signal for release backports

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.

[perdasilva]

/cherry-pick release-4.14

[openshift-cherrypick-robot]

@perdasilva: #670 failed to apply on top of branch "release-4.14":

Applying: Improve condition check for installplan (#3145)
Using index info to reconstruct a base tree...
M	staging/operator-lifecycle-manager/test/e2e/subscription_e2e_test.go
Falling back to patching base and 3-way merge...
Auto-merging staging/operator-lifecycle-manager/test/e2e/subscription_e2e_test.go
CONFLICT (content): Merge conflict in staging/operator-lifecycle-manager/test/e2e/subscription_e2e_test.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Improve condition check for installplan (#3145)
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick release-4.14

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.