OCPBUGS-61872: Add ClusterVersionOperator manifests to TechPreviewNoUpgrade clusters #1232

DavidHurta · 2025-09-19T13:32:59Z

Start applying the ClusterVersionOperator manifests in TechPreview.

deps: Bump github.com/openshift/api module
This is needed as the CRDs of the ClusterVersionOperator objects are being imported
from the github.com/openshift/api module. To bring a new TechPreview CRD of the
ClusterVersionOperator object, the module must be upgraded.

install: Add TechPreview ClusterVersionOperator CR manifest

This is needed as the CRDs of the ClusterVersionOperator objects are being imported from the github.com/openshift/api module. To bring a new TechPreview CRD of the ClusterVersionOperator object, the module must be upgraded. Steps: ```console $ go get github.com/openshift/api $ go mod tidy $ go mod vendor ```

openshift-ci-robot · 2025-09-19T13:33:45Z

@DavidHurta: This pull request references Jira Issue OCPBUGS-61872, which is invalid:

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

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.

DavidHurta · 2025-09-19T13:39:50Z

/hold

I need to examine the CI logs.

DavidHurta · 2025-09-19T13:40:00Z

/jira refresh

openshift-ci-robot · 2025-09-19T13:40:09Z

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

Requesting review from QA contact:
/cc @jiajliu

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.

jiajliu · 2025-09-22T01:47:15Z

/jira refresh

openshift-ci-robot · 2025-09-22T01:47:20Z

@jiajliu: This pull request references Jira Issue OCPBUGS-61872, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.21.0) matches configured target version for branch (4.21.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.

DavidHurta · 2025-09-22T22:14:25Z

/unhold

DavidHurta · 2025-09-25T13:33:52Z

/uncc jiajliu
/cc JianLi-RH

wking

Looks good to me!

/lgtm

Also Cluster Bot testing with launch 4.21,openshift/cluster-version-operator#1232 aws,techpreview (logs), there's the default cluster resource setting operatorLogLevel: Normal:

$ oc get -o yaml clusterversionoperators.operator.openshift.io cluster
apiVersion: operator.openshift.io/v1alpha1
kind: ClusterVersionOperator
metadata:
  annotations:
    include.release.openshift.io/ibm-cloud-managed: "true"
    include.release.openshift.io/self-managed-high-availability: "true"
    release.openshift.io/create-only: "true"
    release.openshift.io/feature-set: TechPreviewNoUpgrade
  creationTimestamp: "2025-10-05T04:56:00Z"
  generation: 1
  name: cluster
  ownerReferences:
  - apiVersion: config.openshift.io/v1
    kind: ClusterVersion
    name: version
    uid: 04bec884-4d38-4459-918d-b3eb3fecdddf
  resourceVersion: "3275"
  uid: d2bd9f8f-e739-4263-981c-b830e3b3f861
spec:
  operatorLogLevel: Normal
status:
  observedGeneration: 1

And patching to Trace gets logs about the transition and also detailed networking stuff that we don't usually get:

$ oc patch clusterversionoperators.operator.openshift.io cluster --type json -p '[{"op": "add", "path": "/spec/operatorLogLevel", "value": "Trace"}]'
clusterversionoperator.operator.openshift.io/cluster patched
$ oc -n openshift-cluster-version logs -l k8s-app=cluster-version-operator --tail -1 | grep 'configuration.go.*updated'
I1005 05:31:01.460216       1 configuration.go:170] Successfully updated the log level from 'Normal' to 'Trace'
$ oc -n openshift-cluster-version logs -l k8s-app=cluster-version-operator --tail 20
I1005 05:31:15.167757       1 streamwatcher.go:123] "Unable to decode an event from the watch stream" err="read tcp 10.0.13.69:56342->10.0.7.1:6443: read: connection reset by peer"
I1005 05:31:15.167794       1 reflector.go:879] github.com/openshift/client-go/config/informers/externalversions/factory.go:125: Watch close - *v1.FeatureGate total 3 items received
I1005 05:31:15.168062       1 streamwatcher.go:123] "Unable to decode an event from the watch stream" err="read tcp 10.0.13.69:56342->10.0.7.1:6443: read: connection reset by peer"
I1005 05:31:15.168458       1 reflector.go:879] k8s.io/client-go/informers/factory.go:160: Watch close - *v1.ConfigMap total 3 items received
I1005 05:31:15.168069       1 streamwatcher.go:123] "Unable to decode an event from the watch stream" err="read tcp 10.0.13.69:56342->10.0.7.1:6443: read: connection reset by peer"
I1005 05:31:15.168749       1 reflector.go:879] github.com/openshift/client-go/config/informers/externalversions/factory.go:125: Watch close - *v1.ClusterVersion total 4 items received
I1005 05:31:15.168172       1 streamwatcher.go:123] "Unable to decode an event from the watch stream" err="read tcp 10.0.13.69:56342->10.0.7.1:6443: read: connection reset by peer"
I1005 05:31:15.168937       1 reflector.go:879] k8s.io/client-go/informers/factory.go:160: Watch close - *v1.ConfigMap total 3 items received
...

/verified by @wking

openshift-ci-robot · 2025-10-06T16:52:34Z

/retest-required

Remaining retests: 0 against base HEAD 2f5d502 and 2 for PR HEAD 12d7960 in total

openshift-ci-robot · 2025-10-07T21:39:38Z

/retest-required

Remaining retests: 0 against base HEAD 95685e0 and 1 for PR HEAD 12d7960 in total

DavidHurta · 2025-10-08T12:53:40Z

/retest-required

JianLi-RH · 2025-10-09T10:07:12Z

/label qe-approved

openshift-ci-robot · 2025-10-09T10:07:21Z

@DavidHurta: This pull request references Jira Issue OCPBUGS-61872, which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified 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:

Start applying the ClusterVersionOperator manifests in TechPreview.

deps: Bump github.com/openshift/api module
This is needed as the CRDs of the ClusterVersionOperator objects are being imported
from the github.com/openshift/api module. To bring a new TechPreview CRD of the
ClusterVersionOperator object, the module must be upgraded.

install: Add TechPreview ClusterVersionOperator CR manifest

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.

DavidHurta · 2025-10-09T13:45:01Z

/hold let other CVO PRs go first

DavidHurta · 2025-10-09T17:06:21Z

/unhold

The main branch HyperShift PR has merged. Let's merge as well.

DavidHurta · 2025-10-09T17:06:50Z

/jira refresh

openshift-ci-robot · 2025-10-09T17:06:58Z

@DavidHurta: This pull request references Jira Issue OCPBUGS-61872, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.21.0) matches configured target version for branch (4.21.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.

openshift-ci-robot · 2025-10-09T17:23:22Z

/retest-required

Remaining retests: 0 against base HEAD 4b8d15e and 0 for PR HEAD 12d7960 in total

openshift-ci-robot · 2025-10-09T21:23:29Z

/hold

Revision 12d7960 was retested 3 times: holding

wking · 2025-10-10T15:48:29Z

The HAProxy router should be able to connect to a service that is idled because a GET on the route will unidle it failures are unrelated to this change, and that's the only thing that went wrong in that run.

/hold cancel
/override ci/prow/e2e-aws-ovn-techpreview

openshift-ci · 2025-10-10T15:49:21Z

@wking: Overrode contexts on behalf of wking: ci/prow/e2e-aws-ovn-techpreview

In response to this:

The HAProxy router should be able to connect to a service that is idled because a GET on the route will unidle it failures are unrelated to this change, and that's the only thing that went wrong in that run.

/hold cancel
/override ci/prow/e2e-aws-ovn-techpreview

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.

openshift-ci · 2025-10-10T18:24:01Z

@DavidHurta: all tests passed!

Full PR test history. Your PR dashboard.

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-ci-robot · 2025-10-10T18:26:17Z

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

Start applying the ClusterVersionOperator manifests in TechPreview.

deps: Bump github.com/openshift/api module
This is needed as the CRDs of the ClusterVersionOperator objects are being imported
from the github.com/openshift/api module. To bring a new TechPreview CRD of the
ClusterVersionOperator object, the module must be upgraded.

install: Add TechPreview ClusterVersionOperator CR manifest

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-robot · 2025-10-12T17:49:05Z

Fix included in accepted release 4.21.0-0.nightly-2025-10-12-115019

DavidHurta · 2025-10-13T11:41:07Z

/cherrypick release-4.20

openshift-cherrypick-robot · 2025-10-13T11:41:51Z

@DavidHurta: Failed to get PR patch from GitHub. This PR will need to be manually cherrypicked.

Error message

status code 406 not one of [200], body: {"message":"Sorry, the diff exceeded the maximum number of files (300). Consider using 'List pull requests files' API or locally cloning the repository instead.","errors":[{"resource":"PullRequest","field":"diff","code":"too_large"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#list-pull-requests-files","status":"406"}

In response to this:

/cherrypick release-4.20

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.

DavidHurta added 2 commits September 19, 2025 15:31

install: Add TechPreview ClusterVersionOperator CR manifest

12d7960

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 19, 2025

DavidHurta changed the title ~~WIP: Add ClusterVersionOperator manifests to TechPreviewNoUpgrade clusters~~ OCPBUGS-61872: Add ClusterVersionOperator manifests to TechPreviewNoUpgrade clusters Sep 19, 2025

openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Sep 19, 2025

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 19, 2025

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 Sep 19, 2025

openshift-ci bot requested a review from jiajliu September 19, 2025 13:40

petr-muller approved these changes Sep 22, 2025

View reviewed changes

openshift-ci bot assigned petr-muller Sep 22, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 22, 2025

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 22, 2025

openshift-ci bot requested review from JianLi-RH and removed request for jiajliu September 25, 2025 13:33

DavidHurta mentioned this pull request Sep 25, 2025

WIP: CVO configuration: Minor refactoring and changes #1234

Open

wking approved these changes Oct 5, 2025

View reviewed changes

openshift-ci bot assigned wking Oct 5, 2025

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Oct 9, 2025

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 Oct 9, 2025

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 9, 2025

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 9, 2025

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 Oct 9, 2025

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 9, 2025

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 10, 2025

openshift-merge-bot bot merged commit 75c15b5 into openshift:main Oct 10, 2025
17 checks passed

JianLi-RH mentioned this pull request Oct 11, 2025

OSDOCS-12713 CVO log levels release note openshift/openshift-docs#100340

Merged

1 task

DavidHurta mentioned this pull request Oct 14, 2025

OCPBUGS-63001: Add ClusterVersionOperator manifests to TechPreviewNoUpgrade clusters in 4.20 #1247

Merged

OCPBUGS-61872: Add ClusterVersionOperator manifests to TechPreviewNoUpgrade clusters #1232

OCPBUGS-61872: Add ClusterVersionOperator manifests to TechPreviewNoUpgrade clusters #1232

Uh oh!

Conversation

DavidHurta commented Sep 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Sep 19, 2025

Uh oh!

DavidHurta commented Sep 19, 2025

Uh oh!

DavidHurta commented Sep 19, 2025

Uh oh!

openshift-ci-robot commented Sep 19, 2025

Uh oh!

jiajliu commented Sep 22, 2025

Uh oh!

openshift-ci-robot commented Sep 22, 2025

Uh oh!

DavidHurta commented Sep 22, 2025

Uh oh!

DavidHurta commented Sep 25, 2025

Uh oh!

wking left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci-robot commented Oct 6, 2025

Uh oh!

openshift-ci-robot commented Oct 7, 2025

Uh oh!

DavidHurta commented Oct 8, 2025

Uh oh!

JianLi-RH commented Oct 9, 2025

Uh oh!

openshift-ci-robot commented Oct 9, 2025

Uh oh!

DavidHurta commented Oct 9, 2025

Uh oh!

DavidHurta commented Oct 9, 2025

Uh oh!

DavidHurta commented Oct 9, 2025

Uh oh!

openshift-ci-robot commented Oct 9, 2025

Uh oh!

openshift-ci-robot commented Oct 9, 2025

Uh oh!

openshift-ci-robot commented Oct 9, 2025

Uh oh!

wking commented Oct 10, 2025

Uh oh!

openshift-ci bot commented Oct 10, 2025

Uh oh!

openshift-ci bot commented Oct 10, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Oct 10, 2025

Uh oh!

openshift-merge-robot commented Oct 12, 2025

Uh oh!

DavidHurta commented Oct 13, 2025

Uh oh!

openshift-cherrypick-robot commented Oct 13, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

DavidHurta commented Sep 19, 2025 •

edited

Loading