OCPBUGS-41549: [4.17] adds paginating lister for evaluating CRs' upgrade fitness versus new CRDs.

[grokspawn]

… (#3387)

• paging lister for CRDs
• review resolutions

---

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 48a856ab0972be8d421b454b854db117975f5cca

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn

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

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

[grokspawn]

/jira cherrypick OCPBUGS-35358

[openshift-ci-robot]

@grokspawn: Jira Issue OCPBUGS-35358 has been cloned as Jira Issue OCPBUGS-41549. Will retitle bug to link to clone.
/retitle OCPBUGS-41549: [4.17] adds paginating lister for evaluating CRs' upgrade fitness versus new CRDs.

In response to this:

/jira cherrypick OCPBUGS-35358

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]

@grokspawn: This pull request references Jira Issue OCPBUGS-41549, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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:

… (#3387)

• paging lister for CRDs
• review resolutions

---

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 48a856ab0972be8d421b454b854db117975f5cca

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.

[grokspawn]

/jira refresh

[openshift-ci-robot]

@grokspawn: This pull request references Jira Issue OCPBUGS-41549, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.0) matches configured target version for branch (4.17.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-35358 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-35358 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
• bug has dependents

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.

[kevinrizza]

/lgtm
/label backport-risk-assessed

[jianzhangbjz]

Test pass, details: https://issues.redhat.com/browse/OCPBUGS-41549
/lgtm
/label qe-approved
/label cherry-pick-approved

[openshift-ci-robot]

@grokspawn: This pull request references Jira Issue OCPBUGS-41549, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.0) matches configured target version for branch (4.17.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-35358 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-35358 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
• bug has dependents

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:

… (#3387)

• paging lister for CRDs
• review resolutions

---

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 48a856ab0972be8d421b454b854db117975f5cca

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]

/retest-required

Remaining retests: 0 against base HEAD 865e0dc and 2 for PR HEAD 8643e56 in total

[openshift-ci]

@grokspawn: 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-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@grokspawn: Jira Issue OCPBUGS-41549: All pull requests linked via external trackers have merged:

• openshift/operator-framework-olm#860

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

In response to this:

… (#3387)

• paging lister for CRDs
• review resolutions

---

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 48a856ab0972be8d421b454b854db117975f5cca

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: operator-registry
This PR has been included in build operator-registry-container-v4.17.0-202409101338.p0.gb0d86a0.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.17.0-202409101338.p0.gb0d86a0.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-operator-framework-tools
This PR has been included in build ose-operator-framework-tools-container-v4.17.0-202409101338.p0.gb0d86a0.assembly.stream.el9.
All builds following this will include this PR.

[grokspawn]

/cherry-pick release-4.16,release-4.15,release-4.14,release-4.13,release-4.12

[openshift-cherrypick-robot]

@grokspawn: cannot checkout release-4.16,release-4.15,release-4.14,release-4.13,release-4.12: error checking out "release-4.16,release-4.15,release-4.14,release-4.13,release-4.12": exit status 1 error: pathspec 'release-4.16,release-4.15,release-4.14,release-4.13,release-4.12' did not match any file(s) known to git

In response to this:

/cherry-pick release-4.16,release-4.15,release-4.14,release-4.13,release-4.12

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.

[grokspawn]

/cherrypick release-4.16 release-4.15 release-4.14 release-4.13 release-4.12

[openshift-cherrypick-robot]

@grokspawn: new pull request created: #863

In response to this:

/cherrypick release-4.16 release-4.15 release-4.14 release-4.13 release-4.12

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.