Skip to content

OCPBUGS-77956: Update to use the 4.21 Operator Catalog#268

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
bfournie:use-4.21-catalog
Mar 9, 2026
Merged

OCPBUGS-77956: Update to use the 4.21 Operator Catalog#268
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
bfournie:use-4.21-catalog

Conversation

@bfournie
Copy link
Contributor

@bfournie bfournie commented Mar 8, 2026

It appears that all operators are available in the 4.21 catalog now particularly the mtv-operator which was previously requiring us to use the 4.20 catalog.

It appears that all operators are available in the 4.21 catalog
now particularly the mtv-operator which was previously requiring
us to use the 4.20 catalog.
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 8, 2026
@openshift-ci-robot
Copy link

@bfournie: This pull request references Jira Issue OCPBUGS-77956, 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 ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mhanss

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

Details

In response to this:

It appears that all operators are available in the 4.21 catalog now particularly the mtv-operator which was previously requiring us to use the 4.20 catalog.

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 celebdor, mhanss and rwsu March 8, 2026 16:41
@openshift-ci
Copy link

openshift-ci bot commented Mar 8, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bfournie

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 8, 2026
@bfournie
Copy link
Contributor Author

bfournie commented Mar 8, 2026

Using this catalog results in a successful installation:

oc get nodes
NAME       STATUS                     ROLES                         AGE   VERSION
master-0   Ready,SchedulingDisabled   control-plane,master,worker   14m   v1.34.4
master-1   Ready                      control-plane,master,worker   40m   v1.34.4
master-2   Ready                      control-plane,master,worker   40m   v1.34.4
+(./agent/agent_post_install_validation.sh:218): ((  3 != 3  ))
+(./agent/agent_post_install_validation.sh:223): oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.21.0-0.nightly-2026-03-04-191930   True        False         22s     Cluster version is 4.21.0-0.nightly-2026-03-04-191930

We can see that the mtv-operator is successfully install with the 2.11 version matching this catalog:

Conditions:
        Last Transition Time:  2026-03-08T15:49:00Z
        Last Update Time:      2026-03-08T15:49:00Z
        Message:               install strategy completed with no errors
        Reason:                InstallSucceeded
        Status:                True
        Type:                  Succeeded
      Kind:                    ClusterServiceVersion
      Name:                    mtv-operator.v2.11.0
      Namespace:               openshift-mtv
      API Version:             apiextensions.k8s.io/v1

@bfournie
Copy link
Contributor Author

bfournie commented Mar 8, 2026

/cc @andfasano

@openshift-ci openshift-ci bot requested a review from andfasano March 8, 2026 16:43
@bfournie
Copy link
Contributor Author

bfournie commented Mar 8, 2026

/test e2e-agent-compact-ipv4-iso-no-registry

@bfournie bfournie changed the title OCPBUGS-77956: Update to use the 4.21 Catalog OCPBUGS-77956: Update to use the 4.21 Operator Catalog Mar 8, 2026
@bfournie
Copy link
Contributor Author

bfournie commented Mar 9, 2026

/test e2e-agent-compact-ipv4-iso-no-registry

@openshift-ci
Copy link

openshift-ci bot commented Mar 9, 2026

@bfournie: 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/e2e-agent-compact-ipv4-iso-no-registry 1fe83a9 link false /test e2e-agent-compact-ipv4-iso-no-registry

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.

@andfasano
Copy link
Contributor

/lgtm

The iso-no-registry it's still failing due timeout, very likely there are still some issues with the operators, but if they are available now the patch seems worth to have it

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

bfournie commented Mar 9, 2026

/verified by @bfournie

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 9, 2026
@openshift-ci-robot
Copy link

@bfournie: This PR has been marked as verified by @bfournie.

Details

In response to this:

/verified by @bfournie

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-merge-bot openshift-merge-bot bot merged commit 347b398 into openshift:main Mar 9, 2026
12 of 13 checks passed
@openshift-ci-robot
Copy link

@bfournie: Jira Issue Verification Checks: Jira Issue OCPBUGS-77956
✔️ 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-77956 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:

It appears that all operators are available in the 4.21 catalog now particularly the mtv-operator which was previously requiring us to use the 4.20 catalog.

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.

@bfournie bfournie deleted the use-4.21-catalog branch March 9, 2026 12:54
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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants