add 4.18 regress job

[qiliRedHat]

Added 3 test cases
case 1 and 2
https://issues.redhat.com/browse/OCPQE-28086
depends on openshift/svt#803 and openshift/svt#804 's merge

Test passed https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/60739/rehearse-60739-pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-ingress-scale-test/1881906571550658560

case 3
https://issues.redhat.com/browse/OCPQE-28152
depends on openshift/svt#806 merge
Test passed https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_release/60739/rehearse-60739-pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-networkpolicy-scale-ocp-41535/1882324539698843648/artifacts/networkpolicy-scale-ocp-41535/openshift-svt-regression/build-log.txt

[openshift-ci-robot]

@qiliRedHat, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: invalid ci-operator config: invalid configuration: tests[2].as: 'OCP-43281-router-scale-test' is not a valid Kubernetes object name

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci-robot]

@qiliRedHat, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: invalid ci-operator config: invalid configuration: tests[2].as: 'OCP-43281-router-scale-test' is not a valid Kubernetes object name

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[qiliRedHat]

/pj-rehearse pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-ingress-scale-test

[openshift-ci-robot]

@qiliRedHat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[qiliRedHat]

/pj-rehearse pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-ingress-scale-test

[openshift-ci-robot]

@qiliRedHat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[qiliRedHat]

/pj-rehearse pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-ingress-scale-test

[openshift-ci-robot]

@qiliRedHat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[qiliRedHat]

/pj-rehearse pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-ingress-scale-test

[openshift-ci-robot]

@qiliRedHat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[qiliRedHat]

/pj-rehearse pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-ingress-scale-test

[openshift-ci-robot]

@qiliRedHat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[qiliRedHat]

@paigerube14 PTAL

[openshift-ci-robot]

@qiliRedHat, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load Prow configuration from release repo: duplicated presubmit jobs (consider both inrepo and central config): [pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-regression-scale-affinity-rules pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-regression-scale-loaded-projects]

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci-robot]

@qiliRedHat, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load Prow configuration from release repo: duplicated presubmit jobs (consider both inrepo and central config): [pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-regression-scale-affinity-rules pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-regression-scale-loaded-projects]

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[qiliRedHat]

/pj-rehearse ack

[openshift-ci-robot]

@qiliRedHat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[qiliRedHat]

@paigerube14 PTAL. I addes ES credentials to the step to have ingres-perf in my scripts to run.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@qiliRedHat: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-ingress-scale-ocp-43281-ingress-tunning-ocp-43175	openshift/svt	presubmit	Presubmit changed
pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-networkpolicy-scale-ocp-41535	openshift/svt	presubmit	Presubmit changed
pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-regression-scale-loaded-projects	openshift/svt	presubmit	Registry content changed
pull-ci-openshift-svt-master-regression-aws-4.17-nightly-x86-regression-scale-loaded-projects	openshift/svt	presubmit	Registry content changed
pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-regression-scale-affinity-rules	openshift/svt	presubmit	Registry content changed
pull-ci-openshift-svt-master-regression-aws-4.17-nightly-x86-regression-scale-affinity-rules	openshift/svt	presubmit	Registry content changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[qiliRedHat]

/pj-rehearse pull-ci-openshift-svt-master-regression-aws-4.18-nightly-x86-networkpolicy-scale-ocp-41535

[openshift-ci-robot]

@qiliRedHat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[paigerube14]

@qiliRedHat I'm not sure if we want to index these regression test results into elastic search and I'm not sure if the indexing properly worked

�[1mThu Jan 23 09:26:15 UTC 2025 Indexing benchmark metadata to /ripsaw-kube-burner�[0m
curl: (3) URL using bad/illegal format or missing URL
�[1mThu Jan 23 09:26:15 UTC 2025 benchmark�[0m

[qiliRedHat]

@paigerube14
In the networkpolicy-scale regression test log the data is not indexed to ES because Elastic server is not defined. That's what I expected. Because in this test, the kube-burner is used to just load the custom workerload, I don't want to index anything to ES.

/tmp/svt/perfscale_regression_ci/scripts/network/e2e-benchmarking/workloads/kube-burner
�[1mThu Jan 23 09:23:40 UTC 2025 Indexing benchmark metadata to /ripsaw-kube-burner�[0m
curl: (3) URL using bad/illegal format or missing URL
�[1mThu Jan 23 09:23:40 UTC 2025 benchmark�[0m
Elastic server is not defined, please check

While in the first 2 cases ingresss-scale and ingress-tunning, I want to have the data indexed to ES because the test needs to compare performance from grafana dashboard. To do that I had the ES_SERVER defined in run_ingress_perf() func.
https://github.com/openshift/svt/blob/master/perfscale_regression_ci/utils/run_workload.sh#L36.

If any case need kube-burner to index to ES as well, we can do the same to define ES_SERVER in the test case script.

[paigerube14]

@qiliRedHat makes sense, I just don't think we should get in the habit of pushing data to ES for these test cases. The folder we are using is much older and don't want to be posting incorrect documents that mess up the ES instance

[paigerube14]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: paigerube14, qiliRedHat

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:

• ci-operator/config/openshift/svt/OWNERS [paigerube14,qiliRedHat]
• ci-operator/jobs/openshift/svt/OWNERS [paigerube14,qiliRedHat]
• ci-operator/step-registry/openshift/svt/OWNERS [paigerube14,qiliRedHat]

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

[qiliRedHat]

/pj-rehearse ack

[openshift-ci-robot]

@qiliRedHat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

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