origin icon indicating copy to clipboard operation
origin copied to clipboard

NO-JIRA: update cluster-autoscaler component

Open sunzhaohua2 opened this issue 1 month ago • 7 comments

cluster-autoscaler now is the Cluster Autoscaler component.

sunzhaohua2 avatar Nov 25 '25 05:11 sunzhaohua2

Pipeline controller notification This repository 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 avatar Nov 25 '25 05:11 openshift-ci-robot

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

In response to this:

cluster-autoscaler now is the Cluster Autoscaler component.

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 avatar Nov 25 '25 05:11 openshift-ci-robot

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sunzhaohua2 Once this PR has been reviewed and has the lgtm label, please assign dgoodwin for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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[bot] avatar Nov 25 '25 05:11 openshift-ci[bot]

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-vsphere-ovn /test e2e-vsphere-ovn-upi /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-vsphere-ovn /test e2e-vsphere-ovn-upi /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-vsphere-ovn /test e2e-vsphere-ovn-upi

openshift-ci-robot avatar Nov 25 '25 08:11 openshift-ci-robot

@sunzhaohua2: 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-gcp-ovn-upgrade 240f71e57dcf0a712eea7463a9ee9416fda78bc8 link true /test e2e-gcp-ovn-upgrade

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[bot] avatar Nov 25 '25 16:11 openshift-ci[bot]

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

New Test Risks for sha: 240f71e57dcf0a712eea7463a9ee9416fda78bc8

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn-upgrade Medium - "[Monitor:legacy-cvo-invariants][bz-Cluster Autoscaler] clusteroperator/cluster-autoscaler must go Progressing=True during an upgrade test" is a new test, and was only seen in one job.
pull-ci-openshift-origin-main-e2e-gcp-ovn-upgrade Medium - "[Monitor:legacy-cvo-invariants][bz-Cluster Autoscaler] clusteroperator/cluster-autoscaler should stay Progressing=False while MCO is Progressing=True" is a new test, and was only seen in one job.

New tests seen in this PR at sha: 240f71e57dcf0a712eea7463a9ee9416fda78bc8

  • "[Monitor:cluster-version-checker][bz-Cluster Autoscaler] clusteroperator/cluster-autoscaler must complete version change within limited time" [Total: 10, Pass: 10, Fail: 0, Flake: 0]
  • "[Monitor:legacy-cvo-invariants][bz-Cluster Autoscaler] clusteroperator/cluster-autoscaler must go Progressing=True during an upgrade test" [Total: 1, Pass: 1, Fail: 0, Flake: 1]
  • "[Monitor:legacy-cvo-invariants][bz-Cluster Autoscaler] clusteroperator/cluster-autoscaler should not change condition/Available" [Total: 12, Pass: 12, Fail: 0, Flake: 0]
  • "[Monitor:legacy-cvo-invariants][bz-Cluster Autoscaler] clusteroperator/cluster-autoscaler should not change condition/Degraded" [Total: 12, Pass: 12, Fail: 0, Flake: 0]
  • "[Monitor:legacy-cvo-invariants][bz-Cluster Autoscaler] clusteroperator/cluster-autoscaler should stay Progressing=False while MCO is Progressing=True" [Total: 1, Pass: 1, Fail: 0, Flake: 0]

openshift-trt[bot] avatar Nov 25 '25 16:11 openshift-trt[bot]

Hi @elmiko can you please help to take a look this, thanks!

sunzhaohua2 avatar Nov 26 '25 02:11 sunzhaohua2