Skip to content

NO-JIRA: manifests: bump olm.skipRange upper bound to 4.22.0#55

Open
karampok wants to merge 2 commits into
openshift:mainfrom
karampok:OCPBUGS-61457-main
Open

NO-JIRA: manifests: bump olm.skipRange upper bound to 4.22.0#55
karampok wants to merge 2 commits into
openshift:mainfrom
karampok:OCPBUGS-61457-main

Conversation

@karampok

Copy link
Copy Markdown
Contributor

Summary

  • The art.yaml substitution for olm.skipRange searches for <{MAJOR}.{MINOR}.0 which expands to <4.22.0 on main
  • The CSV had a stale <4.19.0 value, causing the ART substitution to silently fail
  • Updated olm.skipRange from <4.19.0 to <4.22.0 so the search pattern matches

Fixes: OCPBUGS-61457

The art.yaml substitution searches for <{MAJOR}.{MINOR}.0 but the
CSV had <4.19.0, causing the substitution to silently fail for 4.21.

Fixes: OCPBUGS-61457

Assisted-By: Claude Sonnet 4.6
Signed-off-by: Konstantinos Karampogias <karampok@gmail.com>
The art.yaml substitution searches for <{MAJOR}.{MINOR}.0 which expands
to <4.22.0 on main. The CSV had <4.19.0, causing the substitution to
silently fail.

Fixes: OCPBUGS-61457

Assisted-By: Claude Sonnet 4.6
Signed-off-by: Konstantinos Karampogias <karampok@gmail.com>
@openshift-ci-robot openshift-ci-robot added 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 Mar 31, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@karampok: This pull request references Jira Issue OCPBUGS-61457, which is invalid:

  • expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "4.21" 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.

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

Details

In response to this:

Summary

  • The art.yaml substitution for olm.skipRange searches for <{MAJOR}.{MINOR}.0 which expands to <4.22.0 on main
  • The CSV had a stale <4.19.0 value, causing the ART substitution to silently fail
  • Updated olm.skipRange from <4.19.0 to <4.22.0 so the search pattern matches

Fixes: OCPBUGS-61457

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 requested review from mlguerrero12 and zeeke March 31, 2026 14:12
@openshift-ci

openshift-ci Bot commented Mar 31, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: karampok
Once this PR has been reviewed and has the lgtm label, please assign zeeke for approval. For more information see the Code Review Process.

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

Details 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

@karampok karampok changed the title OCPBUGS-61457: manifests: bump olm.skipRange upper bound to 4.22.0 NO-JIRA: manifests: bump olm.skipRange upper bound to 4.22.0 Mar 31, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

Details

In response to this:

Summary

  • The art.yaml substitution for olm.skipRange searches for <{MAJOR}.{MINOR}.0 which expands to <4.22.0 on main
  • The CSV had a stale <4.19.0 value, causing the ART substitution to silently fail
  • Updated olm.skipRange from <4.19.0 to <4.22.0 so the search pattern matches

Fixes: OCPBUGS-61457

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 openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 31, 2026
@openshift-ci

openshift-ci Bot commented Mar 31, 2026

Copy link
Copy Markdown

@karampok: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/unit 04bcd1d link true /test unit

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants