Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 28, 2025
Merged

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

merged 1 commit into from
Aug 28, 2025

Conversation

chiragkyal
Copy link
Member

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:

/cc @bharath-b-rh @lunarwhite

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 25, 2025
@openshift-ci-robot
Copy link

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

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:

/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
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 25, 2025
@openshift-ci-robot
Copy link

@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 ([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.

@chiragkyal
Copy link
Member Author

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

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 25, 2025
@chiragkyal
Copy link
Member Author

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

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 25, 2025
@lunarwhite
Copy link
Member

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

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Aug 26, 2025

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

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
Copy link
Member

/retest

@lunarwhite
Copy link
Member

/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 OpenShift CI
Copy link

openshift-ci bot commented Aug 26, 2025

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

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
Copy link
Member

/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 OpenShift CI
Copy link

openshift-ci bot commented Aug 26, 2025

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

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
Copy link
Member

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

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Aug 26, 2025

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

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
Copy link
Member

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

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Aug 26, 2025

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

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
Copy link
Member

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

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Aug 26, 2025

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

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
Copy link
Member

/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 openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 27, 2025
@openshift-ci-robot
Copy link

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

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
Copy link
Member

/lgtm
/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. and removed jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 27, 2025
@openshift-ci-robot
Copy link

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

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.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2025
@lunarwhite
Copy link
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 27, 2025
@openshift-ci-robot
Copy link

@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 ([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.

@bharath-b-rh
Copy link
Contributor

/approve

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Aug 28, 2025

[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

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 28, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 69960ad into openshift:main Aug 28, 2025
13 checks passed
@openshift-ci-robot
Copy link

@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. 🕓

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:

/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 chiragkyal deleted the fix-1.16.1-channel branch August 28, 2025 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bharath-b-rh bharath-b-rh Awaiting requested review from bharath-b-rh

@lunarwhite lunarwhite Awaiting requested review from lunarwhite

Assignees

@lunarwhite lunarwhite

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@chiragkyal @openshift-ci-robot @lunarwhite @bharath-b-rh