OCPBUGS-60289: Fix upgrade path for v1.15.0->v1.15.1->v1.16.1

[chiragkyal]

Update channel entries for all OCP index (v4.14-v4.19) having support for v1.16.0 in stable-v1, stable-v1.16, stable-v1.17 (if has) channels.

And we would need to re-release FBCs for all supported OCP versions (v4.14-v4.19).

- name: cert-manager-operator.v1.16.1
  ## Update this to new v1.15 z stream release, when added.
  replaces: cert-manager-operator.v1.15.1
  skipRange: '>=1.15.1 <1.16.1'
  skips: 
  - cert-manager-operator.v1.16.0

See the following Slack threads for more details:

• https://redhat-internal.slack.com/archives/C3VS0LV41/p1755073224707029
• https://redhat-internal.slack.com/archives/C045Y7FL3A6/p1754980744497329

/cc @bharath-b-rh @lunarwhite

[openshift-ci-robot]

@chiragkyal: This pull request references Jira Issue OCPBUGS-60289, which is invalid:

• expected the bug to target the "4.20.0" version, but no target version was set

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.

Details

In response to this:

Update channel entries for all OCP index (v4.14-v4.19) having support for v1.16.0 in stable-v1, stable-v1.16, stable-v1.17 (if has) channels.

And we would need to re-release FBCs for all supported OCP versions (v4.14-v4.19).

- name: cert-manager-operator.v1.16.1
 ## Update this to new v1.15 z stream release, when added.
 replaces: cert-manager-operator.v1.15.1
 skipRange: '>=1.15.1 <1.16.1'
 skips: 
 - cert-manager-operator.v1.16.0

See the following Slack threads for more details:

• https://redhat-internal.slack.com/archives/C3VS0LV41/p1755073224707029
• https://redhat-internal.slack.com/archives/C045Y7FL3A6/p1754980744497329

/cc @bharath-b-rh @lunarwhite

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.

[chiragkyal]

/jira refresh

[openshift-ci-robot]

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

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 ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (yuewu@redhat.com), skipping review request.

Details

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.

[chiragkyal]

/hold
I want to visualise the rendered graph using the newly added changes: operator-framework/operator-registry#1744

[chiragkyal]

After considering operator-framework/operator-registry#1744 changes done in the opm tool behind --draw-v0-semantics flag, we could see the red dotted line around the buggy version v1.16.0; instead of earlier v1.15.1

> ../../operator-framework/operator-registry/bin/opm alpha render-graph ./catalogs/v4.14/catalog --draw-v0-semantics

4.14 : Previous vs With this PR

> ../../operator-framework/operator-registry/bin/opm alpha render-graph ./catalogs/v4.19/catalog --draw-v0-semantics

4.19: Previous vs With this PR

/hold cancel

[lunarwhite]

/test cert-manager-operator-index-4-14-on-pull-request

[openshift-ci]

@lunarwhite: No presubmit jobs available for openshift/cert-manager-operator-release@main

Details

In response to this:

/test cert-manager-operator-index-4-14-on-pull-request

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.

[lunarwhite]

/retest

[lunarwhite]

/test cert-manager-operator-index-4-15-on-pull-request cert-manager-operator-index-4-16-on-pull-request cert-manager-operator-index-4-17-on-pull-request cert-manager-operator-index-4-18-on-pull-request cert-manager-operator-index-4-19-on-pull-request

[openshift-ci]

@lunarwhite: No presubmit jobs available for openshift/cert-manager-operator-release@main

Details

In response to this:

/test cert-manager-operator-index-4-15-on-pull-request cert-manager-operator-index-4-16-on-pull-request cert-manager-operator-index-4-17-on-pull-request cert-manager-operator-index-4-18-on-pull-request cert-manager-operator-index-4-19-on-pull-request

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.

[lunarwhite]

/test cert-manager-operator-index-4-16-on-pull-request

/test cert-manager-operator-index-4-17-on-pull-request

/test cert-manager-operator-index-4-18-on-pull-request

/test cert-manager-operator-index-4-19-on-pull-request

[openshift-ci]

@lunarwhite: No presubmit jobs available for openshift/cert-manager-operator-release@main

Details

In response to this:

/test cert-manager-operator-index-4-16-on-pull-request

/test cert-manager-operator-index-4-17-on-pull-request

/test cert-manager-operator-index-4-18-on-pull-request

/test cert-manager-operator-index-4-19-on-pull-request

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.

[lunarwhite]

/test cert-manager-operator-index-4-17-on-pull-request

[openshift-ci]

@lunarwhite: No presubmit jobs available for openshift/cert-manager-operator-release@main

Details

In response to this:

/test cert-manager-operator-index-4-17-on-pull-request

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.

[lunarwhite]

/test cert-manager-operator-index-4-18-on-pull-request

[openshift-ci]

@lunarwhite: No presubmit jobs available for openshift/cert-manager-operator-release@main

Details

In response to this:

/test cert-manager-operator-index-4-18-on-pull-request

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.

[lunarwhite]

/test cert-manager-operator-index-4-19-on-pull-request

[openshift-ci]

@lunarwhite: No presubmit jobs available for openshift/cert-manager-operator-release@main

Details

In response to this:

/test cert-manager-operator-index-4-19-on-pull-request

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.

[lunarwhite]

/verified by premerge

Semi-auto script helper https://gist.github.com/lunarwhite/df30d8a991ea3d0faa1ea7022cbb36e5

Covered the upgrade paths from the least recent CSV to the latest CSV across all channels of each FBC

[openshift-ci-robot]

@lunarwhite: This PR has been marked as verified by premerge.

Details

In response to this:

/verified by premerge

Semi-auto script helper https://gist.github.com/lunarwhite/df30d8a991ea3d0faa1ea7022cbb36e5

Covered the upgrade paths from the least recent CSV to the latest CSV across all channels of each FBC

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.

[lunarwhite]

/lgtm
/jira refresh

[openshift-ci-robot]

@lunarwhite: This pull request references Jira Issue OCPBUGS-60289, 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.

Details

In response to this:

/lgtm
/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.

[lunarwhite]

/jira refresh

[openshift-ci-robot]

@lunarwhite: This pull request references Jira Issue OCPBUGS-60289, 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)

No GitHub users were found matching the public email listed for the QA contact in Jira (yuewu@redhat.com), skipping review request.

Details

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.

[bharath-b-rh]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bharath-b-rh, chiragkyal

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:

• OWNERS [bharath-b-rh]

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]

@chiragkyal: Jira Issue Verification Checks: Jira Issue OCPBUGS-60289
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-60289 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Update channel entries for all OCP index (v4.14-v4.19) having support for v1.16.0 in stable-v1, stable-v1.16, stable-v1.17 (if has) channels.

And we would need to re-release FBCs for all supported OCP versions (v4.14-v4.19).

- name: cert-manager-operator.v1.16.1
 ## Update this to new v1.15 z stream release, when added.
 replaces: cert-manager-operator.v1.15.1
 skipRange: '>=1.15.1 <1.16.1'
 skips: 
 - cert-manager-operator.v1.16.0

See the following Slack threads for more details:

• https://redhat-internal.slack.com/archives/C3VS0LV41/p1755073224707029
• https://redhat-internal.slack.com/archives/C045Y7FL3A6/p1754980744497329

/cc @bharath-b-rh @lunarwhite

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.