NO-JIRA: Remove exceptions for NTO

[jmencak]

NTO should now correctly report ClusterOperator status conditions Available, Progressing and Degraded. See: OCPBUGS-62632

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci-robot]

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

Details

In response to this:

NTO should now correctly report ClusterOperator status conditions Available, Progressing and Degraded. See: OCPBUGS-62632

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.

[jmencak]

/cc @hongkailiu

[openshift-ci-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[hongkailiu]

Thanks, @jmencak

There is another place for this bug.

$ rg OCPBUGS-62632
pkg/monitortests/clusterversionoperator/legacycvomonitortests/operators.go
798:                            return "https://issues.redhat.com/browse/OCPBUGS-62632"

test/extended/machines/scale.go
251:                            return "https://issues.redhat.com/browse/OCPBUGS-62632"

I believe that it is the same cause for the symptom:

origin/test/extended/machines/scale.go

Line 269 in a325449

o.Expect(violations).To(o.BeEmpty(), "those cluster operators left Progressing=False while cluster was scaling: %v", violations)

The serial test will tell us if removing it is a good idea or not. I am fine if you want to do another pull for that.

Otherwise, I made a mistake to reuse OCPBUGS-62632 as the exception here. If you think that is the case, we should create a new one instead.

[jmencak]

Thanks, @jmencak

There is another place for this bug.

$ rg OCPBUGS-62632
pkg/monitortests/clusterversionoperator/legacycvomonitortests/operators.go
798:                            return "https://issues.redhat.com/browse/OCPBUGS-62632"

test/extended/machines/scale.go
251:                            return "https://issues.redhat.com/browse/OCPBUGS-62632"

I believe that it is the same cause for the symptom:

origin/test/extended/machines/scale.go

Line 269 in a325449

o.Expect(violations).To(o.BeEmpty(), "those cluster operators left Progressing=False while cluster was scaling: %v", violations)

The serial test will tell us if removing it is a good idea or not. I am fine if you want to do another pull for that.

Right, let's try this, removed another occurence.

[openshift-ci-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[jmencak]

The failure in e2e-aws-csi doesn't seem related and the test is not required.

/bin/bash: line 245: /usr/bin/jq: Argument list too long
{"component":"entrypoint","error":"wrapped process failed: exit status 126","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test

[hongkailiu]

This one from this job still passed.

started: 0/31/47 "[sig-cluster-lifecycle][Feature:Machines][Serial] Managed cluster should grow and decrease when scaling different machineSets simultaneously [Timeout:30m][apigroup:machine.openshift.io] [Suite:openshift/conformance/serial]"

passed: (6m20s) 2026-01-21T18:00:44 "[sig-cluster-lifecycle][Feature:Machines][Serial] Managed cluster should grow and decrease when scaling different machineSets simultaneously [Timeout:30m][apigroup:machine.openshift.io] [Suite:openshift/conformance/serial]"

/verified by "CI"

[hongkailiu]

/lgtm

[openshift-ci-robot]

@hongkailiu: This PR has been marked as verified by "CI".

Details

In response to this:

This one from this job still passed.

started: 0/31/47 "[sig-cluster-lifecycle][Feature:Machines][Serial] Managed cluster should grow and decrease when scaling different machineSets simultaneously [Timeout:30m][apigroup:machine.openshift.io] [Suite:openshift/conformance/serial]"

passed: (6m20s) 2026-01-21T18:00:44 "[sig-cluster-lifecycle][Feature:Machines][Serial] Managed cluster should grow and decrease when scaling different machineSets simultaneously [Timeout:30m][apigroup:machine.openshift.io] [Suite:openshift/conformance/serial]"

/verified by "CI"

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hongkailiu, jmencak
Once this PR has been reviewed and has the lgtm label, please assign deads2k 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:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hongkailiu]

I have seen a green run in history.

/test e2e-aws-csi

[openshift-ci]

@jmencak: 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.

[jmencak]

Thank you @hongkailiu !
Bot wants me to
/assign @deads2k
for approval.