Skip to content

OCPBUGS-78999: Update quay-operator bundle version in OTE to fix missing arch#673

Open
dtfranz wants to merge 1 commit intoopenshift:mainfrom
dtfranz:ote-quay-version-update
Open

OCPBUGS-78999: Update quay-operator bundle version in OTE to fix missing arch#673
dtfranz wants to merge 1 commit intoopenshift:mainfrom
dtfranz:ote-quay-version-update

Conversation

@dtfranz
Copy link
Contributor

@dtfranz dtfranz commented Mar 24, 2026

Updates the quay-operator bundle version from v3.13.0, which was missing the arm64 architecture, to v3.13.10 which has it available.

…64 support

Signed-off-by: Daniel Franz <dfranz@redhat.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 24, 2026
@openshift-ci-robot
Copy link

@dtfranz: This pull request references Jira Issue OCPBUGS-78999, which is invalid:

  • expected the bug to target the "4.22.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:

Updates the quay-operator bundle version from v3.13.0, which was missing the arm64 architecture, to v3.13.10 which has it available.

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.

@coderabbitai
Copy link

coderabbitai bot commented Mar 24, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 61879f7e-4d0b-4e5a-9451-e8d059e9ae95

📥 Commits

Reviewing files that changed from the base of the PR and between 4f50aa7 and bdb1e85.

📒 Files selected for processing (1)
  • openshift/tests-extension/test/olmv1.go

Walkthrough

A test case in the OLMv1 operator installation test updates the requested ClusterExtension version for quay-operator from 3.13.0 to 3.13.10. All other test logic and assertions remain unchanged.

Changes

Cohort / File(s) Summary
Test Parameter Update
openshift/tests-extension/test/olmv1.go
Version string parameter change in CreateClusterExtension call from 3.13.0 to 3.13.10 within the OLMv1 operator installation test case.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot requested review from grokspawn and oceanc80 March 24, 2026 03:45
@dtfranz
Copy link
Contributor Author

dtfranz commented Mar 24, 2026

/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 Mar 24, 2026
@openshift-ci-robot
Copy link

@dtfranz: This pull request references Jira Issue OCPBUGS-78999, 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.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 24, 2026

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

@tmshort
Copy link
Contributor

tmshort commented Mar 24, 2026

/lgtm

@tmshort
Copy link
Contributor

tmshort commented Mar 24, 2026

/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 24, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 24, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dtfranz, tmshort

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:

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 Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants