Skip to content

Conversation

@hongkailiu
Copy link
Member

@hongkailiu hongkailiu commented Oct 24, 2025

Revert aba036a "Revert "Merge pull request #30269 from hongkailiu/OTA-1626"" from #30425.

Add JUnitTestCase for success as well. Otherwise, it will screw up the aggregated job [1] when there is a failure for the same case.

Message: Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts to have a chance at success
name: '[Monitor:cluster-version-checker][bz-Networking] clusteroperator/network must
  complete version change under 30 minutes'
testsuitename: openshift-tests-upgrade
summary: 'Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts
  to have a chance at success'
passes: []
failures:
- jobrunid: "1981587413155188736"
  humanurl: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736
  gcsartifacturl: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736/artifacts
skips: []

[1]. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-azure-ovn-upgrade-4.21-micro-release-openshift-release-analysis-aggregator/1981691223231959040

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 24, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 24, 2025

@hongkailiu: This pull request references OTA-1626 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

In response to this:

Otherwise, it will screw up the aggregated job [1] when there is a failure for the same case.

Message: Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts to have a chance at success
name: '[Monitor:cluster-version-checker][bz-Networking] clusteroperator/network must
 complete version change under 30 minutes'
testsuitename: openshift-tests-upgrade
summary: 'Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts
 to have a chance at success'
passes: []
failures:
- jobrunid: "1981587413155188736"
 humanurl: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736
 gcsartifacturl: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736/artifacts
skips: []

[1]. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-azure-ovn-upgrade-4.21-micro-release-openshift-release-analysis-aggregator/1981691223231959040

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 deads2k and p0lyn0mial October 24, 2025 15:17
Copy link
Member

@wking wking left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 24, 2025
@openshift-trt
Copy link

openshift-trt bot commented Oct 24, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 9d8724d

  • "[Monitor:cluster-version-checker][bz-Bare Metal Hardware Provisioning] clusteroperator/baremetal must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/cloud-controller-manager must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/cluster-autoscaler must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/control-plane-machine-set must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/machine-api must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/machine-approver must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Credential Operator] clusteroperator/cloud-credential must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-DNS] clusteroperator/dns must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Etcd] clusteroperator/etcd must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Image Registry] clusteroperator/image-registry must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Insights Operator] clusteroperator/insights must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Machine Config Operator] clusteroperator/machine-config must complete version change under 90 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Management Console] clusteroperator/console must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Monitoring] clusteroperator/monitoring must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Networking] clusteroperator/network must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Node Tuning Operator] clusteroperator/node-tuning must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/marketplace must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/olm must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/operator-lifecycle-manager must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/operator-lifecycle-manager-catalog must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • (...showing 20 of 34 tests)

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 26, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 27, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 27, 2025
Otherwise, it will screw up the aggregated job [1] when there is
a failure for the same case.

```text
Message: Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts to have a chance at success
name: '[Monitor:cluster-version-checker][bz-Networking] clusteroperator/network must
  complete version change under 30 minutes'
testsuitename: openshift-tests-upgrade
summary: 'Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts
  to have a chance at success'
passes: []
failures:
- jobrunid: "1981587413155188736"
  humanurl: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736
  gcsartifacturl: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736/artifacts
skips: []
```

[1]. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-azure-ovn-upgrade-4.21-micro-release-openshift-release-analysis-aggregator/1981691223231959040
@hongkailiu hongkailiu changed the title OTA-1626: Add JUnitTestCase for success as well TRT-2373: Revert "Revert "Merge pull request openshift#30269 from hongkailiu/OTA-1626"" Oct 27, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 27, 2025

@hongkailiu: This pull request references TRT-2373 which is a valid jira issue.

In response to this:

Otherwise, it will screw up the aggregated job [1] when there is a failure for the same case.

Message: Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts to have a chance at success
name: '[Monitor:cluster-version-checker][bz-Networking] clusteroperator/network must
 complete version change under 30 minutes'
testsuitename: openshift-tests-upgrade
summary: 'Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts
 to have a chance at success'
passes: []
failures:
- jobrunid: "1981587413155188736"
 humanurl: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736
 gcsartifacturl: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736/artifacts
skips: []

[1]. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-azure-ovn-upgrade-4.21-micro-release-openshift-release-analysis-aggregator/1981691223231959040

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.

@hongkailiu
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 27, 2025

@hongkailiu: This pull request references TRT-2373 which is a valid jira issue.

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
Copy link

openshift-ci-robot commented Oct 27, 2025

@hongkailiu: This pull request references TRT-2373 which is a valid jira issue.

In response to this:

Revert "Revert "Merge pull request #30269 from hongkailiu/OTA-1626"".

Add JUnitTestCase for success as well. Otherwise, it will screw up the aggregated job [1] when there is a failure for the same case.

Message: Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts to have a chance at success
name: '[Monitor:cluster-version-checker][bz-Networking] clusteroperator/network must
 complete version change under 30 minutes'
testsuitename: openshift-tests-upgrade
summary: 'Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts
 to have a chance at success'
passes: []
failures:
- jobrunid: "1981587413155188736"
 humanurl: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736
 gcsartifacturl: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736/artifacts
skips: []

[1]. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-azure-ovn-upgrade-4.21-micro-release-openshift-release-analysis-aggregator/1981691223231959040

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.

@hongkailiu
Copy link
Member Author

/payload-aggregate periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 27, 2025

@hongkailiu: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/04a33270-b338-11f0-9dd5-3d3bbd953e3e-0

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 27, 2025

@hongkailiu: This pull request references TRT-2373 which is a valid jira issue.

In response to this:

Revert aba036a "Revert "Merge pull request #30269 from hongkailiu/OTA-1626"" from #30425.

Add JUnitTestCase for success as well. Otherwise, it will screw up the aggregated job [1] when there is a failure for the same case.

Message: Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts to have a chance at success
name: '[Monitor:cluster-version-checker][bz-Networking] clusteroperator/network must
 complete version change under 30 minutes'
testsuitename: openshift-tests-upgrade
summary: 'Passed 0 times, failed 1 times, skipped 0 times: we require at least 6 attempts
 to have a chance at success'
passes: []
failures:
- jobrunid: "1981587413155188736"
 humanurl: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736
 gcsartifacturl: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade/1981587413155188736/artifacts
skips: []

[1]. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-azure-ovn-upgrade-4.21-micro-release-openshift-release-analysis-aggregator/1981691223231959040

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-trt
Copy link

openshift-trt bot commented Oct 27, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 18eadc6

  • "[Monitor:cluster-version-checker][bz-Bare Metal Hardware Provisioning] clusteroperator/baremetal must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/cloud-controller-manager must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/cluster-autoscaler must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/control-plane-machine-set must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/machine-api must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/machine-approver must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Credential Operator] clusteroperator/cloud-credential must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-DNS] clusteroperator/dns must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Etcd] clusteroperator/etcd must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Image Registry] clusteroperator/image-registry must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Insights Operator] clusteroperator/insights must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Machine Config Operator] clusteroperator/machine-config must complete version change under 90 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Management Console] clusteroperator/console must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Monitoring] clusteroperator/monitoring must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Node Tuning Operator] clusteroperator/node-tuning must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/marketplace must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/olm must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/operator-lifecycle-manager must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/operator-lifecycle-manager-catalog must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/operator-lifecycle-manager-packageserver must complete version change under 30 minutes" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • (...showing 20 of 33 tests)

@hongkailiu
Copy link
Member Author

/payload-aggregate periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade 10

Try again. No RELEVANT failure in the previous try.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 27, 2025

@hongkailiu: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/72cbef90-b387-11f0-93d9-e982bdf39ed1-0

Originally, the test name contains the number
of minutes as the limited time for CO to update.
We have to go through the process/trouble [1]
if we need to change the number. Here we use
a more general test name to avoid it.

[1]. https://github.com/openshift-eng/ci-test-mapping?tab=readme-ov-file#renaming-tests
@xueqzhan
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 28, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongkailiu, wking, xueqzhan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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 Oct 28, 2025
@hongkailiu
Copy link
Member Author

"[Monitor:cluster-version-checker][bz-OLM] clusteroperator/operator-lifecycle-manager-catalog must complete version change within limited time" [Total: 6, Pass: 6, Fail: 0, Flake: 0]

The above stanza from #30426 (comment) shows that the tests are there for the success as well.

/verified by @hongkailiu

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 28, 2025
@openshift-ci-robot
Copy link

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

In response to this:

"[Monitor:cluster-version-checker][bz-OLM] clusteroperator/operator-lifecycle-manager-catalog must complete version change within limited time" [Total: 6, Pass: 6, Fail: 0, Flake: 0]

The above stanza from #30426 (comment) shows that the tests are there for the success as well.

/verified by @hongkailiu

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
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8a4ef2a and 2 for PR HEAD 51d8436 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f886e4e and 1 for PR HEAD 51d8436 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a91d3d0 and 0 for PR HEAD 51d8436 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 29, 2025

@hongkailiu: 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-trt
Copy link

openshift-trt bot commented Oct 29, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 51d8436

  • "[Monitor:cluster-version-checker][bz-Bare Metal Hardware Provisioning] clusteroperator/baremetal must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/cloud-controller-manager must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/cluster-autoscaler must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/control-plane-machine-set must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/machine-api must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Compute] clusteroperator/machine-approver must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Cloud Credential Operator] clusteroperator/cloud-credential must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-DNS] clusteroperator/dns must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Etcd] clusteroperator/etcd must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Image Registry] clusteroperator/image-registry must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Insights Operator] clusteroperator/insights must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Machine Config Operator] clusteroperator/machine-config must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Management Console] clusteroperator/console must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Monitoring] clusteroperator/monitoring must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Networking] clusteroperator/network must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-Node Tuning Operator] clusteroperator/node-tuning must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/marketplace must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/olm must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/operator-lifecycle-manager must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • "[Monitor:cluster-version-checker][bz-OLM] clusteroperator/operator-lifecycle-manager-catalog must complete version change within limited time" [Total: 22, Pass: 22, Fail: 0, Flake: 0]
  • (...showing 20 of 34 tests)

@openshift-merge-bot openshift-merge-bot bot merged commit 3879619 into openshift:main Oct 29, 2025
20 checks passed
@hongkailiu
Copy link
Member Author

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-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.

5 participants