CORENET-6474: ovn-k, bgp, virt, periodics: Add single stack IPv4 jobs for 4.20 #70601

ormergi · 2025-10-23T09:39:23Z

Replicate 4.21 jobs #69748 to 4.20

openshift-ci-robot · 2025-10-23T09:39:27Z

@ormergi: This pull request references CORENET-6474 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 either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20.z" instead.

In response to this:

Replicate 4.21 jobs #69748 to 4.20

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 · 2025-10-23T09:40:03Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

maiqueb

@qinqon please review.

maiqueb · 2025-10-23T10:00:12Z

...erator/config/openshift/ovn-kubernetes/openshift-ovn-kubernetes-release-4.20__periodics.yaml

+  steps:
+    cluster_profile: equinix-ocp-metal
+    env:
+      CNV_PRERELEASE_LATEST_CHANNEL: "true"


let's drop this. We don't need 4.99 versions of CNV. We want it to use 4.20 version of CNV.

@qinqon right ?

Doesn't it mean it will take the latest patch version?
If not and it takes the latest minor version, we may need to do some follow up work and align other jobs that specify env var https://github.com/search?q=repo%3Aopenshift%2Frelease%20CNV_PRERELEASE_LATEST_CHANNEL&type=code

We should remove this there is a CNV for 4.20

maiqueb · 2025-10-23T10:00:19Z

...erator/config/openshift/ovn-kubernetes/openshift-ovn-kubernetes-release-4.20__periodics.yaml

+  steps:
+    cluster_profile: equinix-ocp-metal
+    env:
+      CNV_PRERELEASE_LATEST_CHANNEL: "true"


qinqon · 2025-10-23T10:31:25Z

...erator/config/openshift/ovn-kubernetes/openshift-ovn-kubernetes-release-4.20__periodics.yaml

+  steps:
+    cluster_profile: equinix-ocp-metal
+    env:
+      CNV_PRERELEASE_LATEST_CHANNEL: "true"


We should remove this there is a CNV for 4.20

qinqon · 2025-10-23T10:31:37Z

...erator/config/openshift/ovn-kubernetes/openshift-ovn-kubernetes-release-4.20__periodics.yaml

+  steps:
+    cluster_profile: equinix-ocp-metal
+    env:
+      CNV_PRERELEASE_LATEST_CHANNEL: "true"


Signed-off-by: Or Mergi <[email protected]>

openshift-ci-robot · 2025-10-23T12:12:28Z

[REHEARSALNOTIFIER]
@ormergi: 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
periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview	N/A	periodic	Periodic changed
periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4	N/A	periodic	Periodic 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 list to get an up-to-date list of affected jobs
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.

maiqueb · 2025-10-23T12:20:38Z

/pj-rehearse

openshift-ci-robot · 2025-10-23T12:20:41Z

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

maiqueb · 2025-10-23T13:19:42Z

/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4

openshift-ci-robot · 2025-10-23T13:19:45Z

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

openshift-ci · 2025-10-23T16:18:03Z

@ormergi: 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/rehearse/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview	`0f5edce`	link	unknown	`/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview`

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.

maiqueb · 2025-10-23T16:24:41Z

it seems we need to get this commit down to 4.20 first.

Try to test with a backport of this PR to see if it succeeds then.

ormergi · 2025-10-23T18:01:29Z

/testwith periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview openshift/origin#30338

openshift-ci · 2025-10-23T18:01:33Z

@ormergi, testwith: Error processing request. ERROR:

could not determine job runs: requested job is invalid. needs to be formatted like: <org>/<repo>/<branch>/<variant?>/<job>. instead it was: periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview

ormergi · 2025-10-23T18:05:31Z

/testwith ci/rehearse/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview openshift/origin#30338

openshift-ci · 2025-10-23T18:05:43Z

@ormergi, testwith: Error processing request. ERROR:

could not determine job runs: requested job is invalid. needs to be formatted like: <org>/<repo>/<branch>/<variant?>/<job>. instead it was: ci/rehearse/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview

ormergi · 2025-10-23T18:12:48Z

it seems we need to get this commit down to 4.20 first.

Try to test with a backport of this PR to see if it succeeds then.

Thanks for the heads up 🙏

I dont think its possible to run non-merged job with some PR, at least I couldn't find a way.
@kyrtapz is it possible though?

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

openshift-ci bot requested review from jcaamano and tssurya October 23, 2025 09:40

maiqueb suggested changes Oct 23, 2025

View reviewed changes

openshift-ci bot assigned maiqueb Oct 23, 2025

qinqon suggested changes Oct 23, 2025

View reviewed changes

openshift-ci bot assigned qinqon Oct 23, 2025

ovn-k, bgp, virt, periodics: Add single stack IPv4 jobs for 4.20

0f5edce

Signed-off-by: Or Mergi <[email protected]>

ormergi force-pushed the ovnk-bgp-virt-bgp-metal-jobs-ipv4 branch from e609aeb to 0f5edce Compare October 23, 2025 12:09

CORENET-6474: ovn-k, bgp, virt, periodics: Add single stack IPv4 jobs for 4.20 #70601

Are you sure you want to change the base?

CORENET-6474: ovn-k, bgp, virt, periodics: Add single stack IPv4 jobs for 4.20 #70601

Uh oh!

Conversation

ormergi commented Oct 23, 2025

Uh oh!

openshift-ci-robot commented Oct 23, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci bot commented Oct 23, 2025

Uh oh!

maiqueb left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

openshift-ci-robot commented Oct 23, 2025

Uh oh!

maiqueb commented Oct 23, 2025

Uh oh!

openshift-ci-robot commented Oct 23, 2025

Uh oh!

maiqueb commented Oct 23, 2025

Uh oh!

openshift-ci-robot commented Oct 23, 2025

Uh oh!

openshift-ci bot commented Oct 23, 2025

Uh oh!

maiqueb commented Oct 23, 2025

Uh oh!

ormergi commented Oct 23, 2025

Uh oh!

openshift-ci bot commented Oct 23, 2025

Uh oh!

ormergi commented Oct 23, 2025

Uh oh!

openshift-ci bot commented Oct 23, 2025

Uh oh!

ormergi commented Oct 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

openshift-ci-robot commented Oct 23, 2025 •

edited by openshift-ci bot

Loading

ormergi commented Oct 23, 2025 •

edited

Loading