Skip to content

Comments

NO-ISSUE: Synchronize From Upstream Repositories#1230

Open
openshift-bot wants to merge 9 commits intoopenshift:mainfrom
openshift-bot:synchronize-upstream
Open

NO-ISSUE: Synchronize From Upstream Repositories#1230
openshift-bot wants to merge 9 commits intoopenshift:mainfrom
openshift-bot:synchronize-upstream

Conversation

@openshift-bot
Copy link
Contributor

@openshift-bot openshift-bot commented Feb 13, 2026

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2026-02-12 00:51:18 operator-framework/operator-lifecycle-manager@674bf3f Jian Zhang fix: add OpenAPIModelName for all PackageManifest related types (#3765)
2026-02-13 16:05:17 operator-framework/operator-lifecycle-manager@fe30afe Jordan Keister remove incompatible licensing statements (#3767)
2026-02-13 15:29:05 operator-framework/operator-lifecycle-manager@0e9d557 Rashmi Gottipati add rashmigottipati as a reviewer (#3768)
2026-02-16 21:00:46 operator-framework/operator-lifecycle-manager@68059b8 Todd Short Auto-generate OpenAPIModelName() via openapi-gen (#3769)
2026-02-17 04:53:05 operator-framework/operator-lifecycle-manager@0a96cb2 dependabot[bot] 🌱 Bump golang.org/x/net from 0.49.0 to 0.50.0 (#3764)
2026-02-18 17:17:21 operator-framework/operator-lifecycle-manager@2194d2a dependabot[bot] 🌱 Bump the k8s-dependencies group with 9 updates (#3771)
2026-02-18 17:20:25 operator-framework/operator-lifecycle-manager@c2010bb dependabot[bot] 🌱 Bump google.golang.org/grpc from 1.78.0 to 1.79.1 (#3772)
2026-02-19 01:25:34 operator-framework/operator-lifecycle-manager@feecd01 Jordan Keister abandon evaluation of any new catalogsource image which is pathological (#3766)
2026-02-19 15:48:46 operator-framework/operator-lifecycle-manager@12f8f48 Todd Short MON-4513: Use endpointslices for metrics (#3773)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

@openshift-bot openshift-bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels Feb 13, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 13, 2026
@openshift-ci-robot
Copy link

@openshift-bot: This pull request explicitly references no jira issue.

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2026-02-12 00:51:18 operator-framework/operator-lifecycle-manager@674bf3f Jian Zhang fix: add OpenAPIModelName for all PackageManifest related types (#3765)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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 Feb 13, 2026

@openshift-bot: GitHub didn't allow me to request PR reviews from the following users: openshift/openshift-team-operator-framework.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2026-02-12 00:51:18 operator-framework/operator-lifecycle-manager@674bf3f Jian Zhang fix: add OpenAPIModelName for all PackageManifest related types (#3765)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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.

@jianzhangbjz
Copy link
Member

/retitle OCPBUGS-76460: Synchronize From Upstream Repositories

@openshift-ci openshift-ci bot changed the title NO-ISSUE: Synchronize From Upstream Repositories OCPBUGS-76460: Synchronize From Upstream Repositories Feb 13, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical 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. labels Feb 13, 2026
@openshift-ci-robot
Copy link

@openshift-bot: This pull request references Jira Issue OCPBUGS-76460, 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 @huangmingxia

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

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2026-02-12 00:51:18 operator-framework/operator-lifecycle-manager@674bf3f Jian Zhang fix: add OpenAPIModelName for all PackageManifest related types (#3765)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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 a review from huangmingxia February 13, 2026 00:49
@jianzhangbjz
Copy link
Member

Hi @huangmingxia , could you help verify it? Thanks!
/assign @huangmingxia

@huangmingxia
Copy link

This issue still exists in 4.22. Waiting for the PR operator-framework/api#476 to be merged.

hive % oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.22.0-0-2026-02-13-030444-test-ci-ln-319mih2-latest   True        False         8m23s   Cluster version is 4.22.0-0-2026-02-13-030444-test-ci-ln-319mih2-latest

% oc get pods -n hive                                                                                                     
NAME                             READY   STATUS    RESTARTS   AGE
hive-operator-7cbbd6cf7d-mfbtg   1/1     Running   0          111s
                                                                                                                                                                 
hive % oc get hiveconfig hive -o yaml                                                                                             
apiVersion: hive.openshift.io/v1
kind: HiveConfig
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"hive.openshift.io/v1","kind":"HiveConfig","metadata":{"annotations":{},"name":"hive"},"spec":{"logLevel":"debug","targetNamespace":"hive"}}
  creationTimestamp: "2026-02-13T04:00:37Z"
  generation: 1
  name: hive
  resourceVersion: "34559"
  uid: 2c53cbcb-0ecd-4a3c-a43f-1f83343216e4
spec:
  logLevel: debug
  targetNamespace: hive
status:
  conditions:
  - lastProbeTime: "2026-02-13T04:01:05Z"
    lastTransitionTime: "2026-02-13T04:01:05Z"
    message: 'error getting OpenAPISchema: SchemaError(com.github.operator-framework.operator-lifecycle-manager.pkg.package-server.apis.operators.v1.CSVDescription.apiservicedefinitions):
      unknown model in reference: "github.com~1operator-framework~1api~1pkg~1operators~1v1alpha1.APIServiceDefinitions"'
    reason: ErrorCreatingResourceHelper
    status: "False"
    type: Ready
  observedGeneration: 1
mihuang@mihuang-mac hive % 

@tmshort
Copy link
Contributor

tmshort commented Feb 13, 2026

@huangmingxia that may not happen for a bit, since it needs to be merged (and it may be replaced by another PR from a different repo) and then incorporated upstream in operator-framework/operator-lifecycle-manager first. In the meantime, can this be verified?

@huangmingxia
Copy link

huangmingxia commented Feb 13, 2026

that may not happen for a bit, since it needs to be merged (and it may be replaced by another PR from a different repo) and then incorporated upstream in operator-framework/operator-lifecycle-manager first.

@tmshort Thanks for the status update. This issue is a blocker bug on the Hive side for OCP 4.22, since the Hive operator could not be successfully deployed.

In the meantime, can this be verified?

I created an OCP cluster today using a cluster-bot built image that includes this PR fix, but the issue still reproduces on the Hive side. Please refer to the results above #1230 (comment). Following this, @jianzhangbjz opened the operator-framework/api#476 to address the issue.
Please let me know if there are any additional items that need verification - I'm happy to validate

@openshift-bot openshift-bot changed the title OCPBUGS-76460: Synchronize From Upstream Repositories NO-ISSUE: Synchronize From Upstream Repositories Feb 14, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. label Feb 14, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 14, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 14, 2026
@openshift-ci-robot
Copy link

@openshift-bot: This pull request explicitly references no jira issue.

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2026-02-12 00:51:18 operator-framework/operator-lifecycle-manager@674bf3f Jian Zhang fix: add OpenAPIModelName for all PackageManifest related types (#3765)
2026-02-13 16:05:17 operator-framework/operator-lifecycle-manager@fe30afe Jordan Keister remove incompatible licensing statements (#3767)
2026-02-13 15:29:05 operator-framework/operator-lifecycle-manager@0e9d557 Rashmi Gottipati add rashmigottipati as a reviewer (#3768)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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-bot openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 15, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 17, 2026
@openshift-bot openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 18, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 18, 2026
@tmshort
Copy link
Contributor

tmshort commented Feb 18, 2026

/lgtm

@openshift-ci-robot openshift-ci-robot added the jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. label Feb 19, 2026
@openshift-ci-robot
Copy link

@openshift-bot: This pull request references Jira Issue OCPBUGS-76460, which is valid.

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

Requesting review from QA contact:
/cc @huangmingxia

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2026-02-12 00:51:18 operator-framework/operator-lifecycle-manager@674bf3f Jian Zhang fix: add OpenAPIModelName for all PackageManifest related types (#3765)
2026-02-13 16:05:17 operator-framework/operator-lifecycle-manager@fe30afe Jordan Keister remove incompatible licensing statements (#3767)
2026-02-13 15:29:05 operator-framework/operator-lifecycle-manager@0e9d557 Rashmi Gottipati add rashmigottipati as a reviewer (#3768)
2026-02-16 21:00:46 operator-framework/operator-lifecycle-manager@68059b8 Todd Short Auto-generate OpenAPIModelName() via openapi-gen (#3769)
2026-02-17 04:53:05 operator-framework/operator-lifecycle-manager@0a96cb2 dependabot[bot] 🌱 Bump golang.org/x/net from 0.49.0 to 0.50.0 (#3764)
2026-02-18 17:17:21 operator-framework/operator-lifecycle-manager@2194d2a dependabot[bot] 🌱 Bump the k8s-dependencies group with 9 updates (#3771)
2026-02-18 17:20:25 operator-framework/operator-lifecycle-manager@c2010bb dependabot[bot] 🌱 Bump google.golang.org/grpc from 1.78.0 to 1.79.1 (#3772)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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 added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 19, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-bot, 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

@tmshort
Copy link
Contributor

tmshort commented Feb 19, 2026

/retest-required

@bandrade
Copy link
Contributor

/label qe-approved
/verified by @bandrade

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 19, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 19, 2026
@openshift-ci-robot
Copy link

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

Details

In response to this:

/label qe-approved
/verified by @bandrade

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.

@tmshort
Copy link
Contributor

tmshort commented Feb 19, 2026

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Feb 19, 2026
jianzhangbjz and others added 9 commits February 20, 2026 00:02
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 674bf3f3547e8d8b56c230c5f0df7b5e8be9a3bd
Signed-off-by: grokspawn <jordan@nimblewidget.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: fe30afe2ef3d6b95804c2bdc1cfe0b0006ad1b07
Signed-off-by: Rashmi Gottipati <rgottipa@redhat.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 0e9d557ec6d9b7ededb96e95cfc11b08ae642cff
Replace hand-written model_name.go with generated zz_generated.model_name.go
by adding +k8s:openapi-model-package marker to doc.go and running openapi-gen
in update_codegen.sh.

Update boilerplate.go.txt to remove Red Hat copyright.

Assisted-By: Claude

Signed-off-by: Todd Short <todd.short@me.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 68059b8f2c7bcb60ae54f59d256cb9d61c7d9c8e
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.49.0 to 0.50.0.
- [Commits](golang/net@v0.49.0...v0.50.0)

---
updated-dependencies:
- dependency-name: golang.org/x/net
  dependency-version: 0.50.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 0a96cb289ab11ed8a6cb02e72be3e52974c3a401
Bumps the k8s-dependencies group with 9 updates:

| Package | From | To |
| --- | --- | --- |
| [k8s.io/api](https://github.com/kubernetes/api) | `0.35.0` | `0.35.1` |
| [k8s.io/apiextensions-apiserver](https://github.com/kubernetes/apiextensions-apiserver) | `0.35.0` | `0.35.1` |
| [k8s.io/apimachinery](https://github.com/kubernetes/apimachinery) | `0.35.0` | `0.35.1` |
| [k8s.io/apiserver](https://github.com/kubernetes/apiserver) | `0.35.0` | `0.35.1` |
| [k8s.io/client-go](https://github.com/kubernetes/client-go) | `0.35.0` | `0.35.1` |
| [k8s.io/code-generator](https://github.com/kubernetes/code-generator) | `0.35.0` | `0.35.1` |
| [k8s.io/component-base](https://github.com/kubernetes/component-base) | `0.35.0` | `0.35.1` |
| [k8s.io/kube-aggregator](https://github.com/kubernetes/kube-aggregator) | `0.35.0` | `0.35.1` |
| [sigs.k8s.io/controller-tools](https://github.com/kubernetes-sigs/controller-tools) | `0.20.0` | `0.20.1` |

Updates `k8s.io/api` from 0.35.0 to 0.35.1
- [Commits](kubernetes/api@v0.35.0...v0.35.1)

Updates `k8s.io/apiextensions-apiserver` from 0.35.0 to 0.35.1
- [Release notes](https://github.com/kubernetes/apiextensions-apiserver/releases)
- [Commits](kubernetes/apiextensions-apiserver@v0.35.0...v0.35.1)

Updates `k8s.io/apimachinery` from 0.35.0 to 0.35.1
- [Commits](kubernetes/apimachinery@v0.35.0...v0.35.1)

Updates `k8s.io/apiserver` from 0.35.0 to 0.35.1
- [Commits](kubernetes/apiserver@v0.35.0...v0.35.1)

Updates `k8s.io/client-go` from 0.35.0 to 0.35.1
- [Changelog](https://github.com/kubernetes/client-go/blob/master/CHANGELOG.md)
- [Commits](kubernetes/client-go@v0.35.0...v0.35.1)

Updates `k8s.io/code-generator` from 0.35.0 to 0.35.1
- [Commits](kubernetes/code-generator@v0.35.0...v0.35.1)

Updates `k8s.io/component-base` from 0.35.0 to 0.35.1
- [Commits](kubernetes/component-base@v0.35.0...v0.35.1)

Updates `k8s.io/kube-aggregator` from 0.35.0 to 0.35.1
- [Commits](kubernetes/kube-aggregator@v0.35.0...v0.35.1)

Updates `sigs.k8s.io/controller-tools` from 0.20.0 to 0.20.1
- [Release notes](https://github.com/kubernetes-sigs/controller-tools/releases)
- [Changelog](https://github.com/kubernetes-sigs/controller-tools/blob/main/RELEASE.md)
- [Commits](kubernetes-sigs/controller-tools@v0.20.0...v0.20.1)

---
updated-dependencies:
- dependency-name: k8s.io/api
  dependency-version: 0.35.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/apiextensions-apiserver
  dependency-version: 0.35.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/apimachinery
  dependency-version: 0.35.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/apiserver
  dependency-version: 0.35.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/client-go
  dependency-version: 0.35.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/code-generator
  dependency-version: 0.35.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/component-base
  dependency-version: 0.35.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/kube-aggregator
  dependency-version: 0.35.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: k8s-dependencies
- dependency-name: sigs.k8s.io/controller-tools
  dependency-version: 0.20.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: k8s-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 2194d2accd844b1bd53d3ca0dab95ac9bf42d7be
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.78.0 to 1.79.1.
- [Release notes](https://github.com/grpc/grpc-go/releases)
- [Commits](grpc/grpc-go@v1.78.0...v1.79.1)

---
updated-dependencies:
- dependency-name: google.golang.org/grpc
  dependency-version: 1.79.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: c2010bbcac3928ee7c1e8cd3ffeceb9bb3ead0db
…al (#3766)

* abandon evaluation of any new catalogsource image which pathologically restrts

Signed-off-by: grokspawn <jordan@nimblewidget.com>

* add CLBO container considerations to detection

Signed-off-by: grokspawn <jordan@nimblewidget.com>

---------

Signed-off-by: grokspawn <jordan@nimblewidget.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: feecd01c492f7233c8b215d37b91d69193189bf1
* Add permissions on endpointslice to Prometheus Role
* Use serviceDiscoveryRole: EndpointSlice in ServiceMonitors

Signed-off-by: Todd Short <todd.short@me.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 12f8f48cc6ec5c3233cb71d1b026399d087109f7
@openshift-bot openshift-bot changed the title OCPBUGS-76460: Synchronize From Upstream Repositories NO-ISSUE: Synchronize From Upstream Repositories Feb 20, 2026
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Feb 20, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. label Feb 20, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 20, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci-robot openshift-ci-robot removed the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 20, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 20, 2026

@openshift-bot: This pull request explicitly references no jira issue.

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2026-02-12 00:51:18 operator-framework/operator-lifecycle-manager@674bf3f Jian Zhang fix: add OpenAPIModelName for all PackageManifest related types (#3765)
2026-02-13 16:05:17 operator-framework/operator-lifecycle-manager@fe30afe Jordan Keister remove incompatible licensing statements (#3767)
2026-02-13 15:29:05 operator-framework/operator-lifecycle-manager@0e9d557 Rashmi Gottipati add rashmigottipati as a reviewer (#3768)
2026-02-16 21:00:46 operator-framework/operator-lifecycle-manager@68059b8 Todd Short Auto-generate OpenAPIModelName() via openapi-gen (#3769)
2026-02-17 04:53:05 operator-framework/operator-lifecycle-manager@0a96cb2 dependabot[bot] 🌱 Bump golang.org/x/net from 0.49.0 to 0.50.0 (#3764)
2026-02-18 17:17:21 operator-framework/operator-lifecycle-manager@2194d2a dependabot[bot] 🌱 Bump the k8s-dependencies group with 9 updates (#3771)
2026-02-18 17:20:25 operator-framework/operator-lifecycle-manager@c2010bb dependabot[bot] 🌱 Bump google.golang.org/grpc from 1.78.0 to 1.79.1 (#3772)
2026-02-19 01:25:34 operator-framework/operator-lifecycle-manager@feecd01 Jordan Keister abandon evaluation of any new catalogsource image which is pathological (#3766)
2026-02-19 15:48:46 operator-framework/operator-lifecycle-manager@12f8f48 Todd Short MON-4513: Use endpointslices for metrics (#3773)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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 Feb 20, 2026

@openshift-bot: The following tests 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-gcp-olm 15381df link true /test e2e-gcp-olm
ci/prow/e2e-gcp-ovn 15381df link true /test e2e-gcp-ovn

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.

@openshift-bot openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants