OCP 40556 fix

[mehabhalodiya]

https://issues.redhat.com/browse/OCPQE-29076

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mehabhalodiya

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:

• OWNERS [mehabhalodiya]

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

[mehabhalodiya]

@qiliRedHat PTAL
Tested on Jenkins: job/scale-ci/job/qili-e2e-benchmark/job/regression-test/137/

[qiliRedHat]

@mehabhalodiya

1. The cdv-2 test failed, please check
   first

07-10 03:24:10.020  time="2025-07-09 19:24:09" level=error msg="4h0m0s timeout reached" file="helpers.go:84"
07-10 03:24:10.020  time="2025-07-09 19:24:09" level=info msg="👋 kube-burner run completed with rc 2 for UUID 679246cd-a225-4d80-9541-7adbaa0c1f64" file="helpers.go:86"
07-10 03:24:10.021  + exit_code=2

second

07-10 07:41:27.010  time="2025-07-09 23:41:26" level=error msg="4h0m0s timeout reached" file="helpers.go:84"
07-10 07:41:27.010  time="2025-07-09 23:41:26" level=info msg="👋 kube-burner run completed with rc 2 for UUID 1abf9177-d5b1-459b-9232-339bb0640d0e" file="helpers.go:86"
07-10 07:41:27.010  + exit_code=2

3. The replace node was not really run

07-10 03:24:20.479  ~/ws/workspace/li-e2e-benchmark_regression-test/perfscale_regression_ci/scripts/scalability
07-10 03:27:26.842  Deploy new machineset and scale down one machine at a time from existing machinesets.
07-10 03:27:26.842  meha-reg-57mvb
07-10 03:27:26.842  python: can't open file '/home/jenkins/ws/workspace/li-e2e-benchmark_regression-test/perfscale_regression_ci/scripts/scalability/./replacenodes.py': [Errno 2] No such file or directory

4. The Polarion test case said 'Use 120 total iterations which is 4x30', but you used 270 iterations. If 270 works, that's fine, but let's sync the test case and the automation code.
5. The Polarion test case said to do the replace one by one, but the code logic is to create all new masters and then stop the origin one by one. That's not exactly the same.

[openshift-ci]

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