Skip to content

Conversation

@ormergi
Copy link
Contributor

@ormergi ormergi commented Oct 23, 2025

This is manual check-pick of IP conflict detection tests [1] (commits 1-3) and MAC conflict detection tests [2] (commit 4).
Commits were cherry-picked from release-4.21 branch.

[1] #30197
[2] #30314

RamLavi and others added 3 commits October 23, 2025 17:16
Validates that KubeVirt VMs with preconfigured MAC and IP addresses
maintain those addresses correctly before and after a vmi with duplicate
IP/MAC request is made, and that the vmi with the duplicate address get
the appropriate address conflict error event.

Co-authored-by: Miguel Duarte Barroso <mdbarroso@redhat.com>
Signed-off-by: Ram Lavi <ralavi@redhat.com>
(cherry picked from commit 6dd2a93)
The requested IPs for the primary UDN attachment are not in the VMI
spec, but in an annotation in the VMI. Hence, we need to fetch that
particular annotation, and set it in the duplicate VMI.

This was implemented using the builder pattern, since I suspect in the
future we will need to further customize the VMI spec / metadata; this
will make it simpler to extend the framework in the future.

Signed-off-by: Miguel Duarte Barroso <mdbarroso@redhat.com>
(cherry picked from commit 13fdf10)
This way we can ensure appropriate cases are caught in a generic way.
With it, we can safely expect to find IP conflicts when there are
duplicate IPs in the network.
In future commits, we will be able to catch MAC conflicts when there are
duplicate MACs in the network

Co-authored-by: Ram Lavi <ralavi@redhat.com>
Signed-off-by: Miguel Duarte Barroso <mdbarroso@redhat.com>
(cherry picked from commit fdb0584)
@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 23, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 23, 2025

@ormergi: This pull request references CORENET-6378 which is a valid jira issue.

In response to this:

This is manual check-pick of IP conflict detection tests [1] (commits 1-3) and MAC conflict detection tests [2] (commit 4).
Commits were cherry-picked from release-4.21 branch.

[1] #30197
[2] #30314

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 miheer and pperiyasamy October 23, 2025 14:21
@ormergi
Copy link
Contributor Author

ormergi commented Nov 2, 2025

/testwith openshift/origin/main/e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview openshift/ovn-kubernetes#2827 #30415

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2025

@ormergi, testwith: could not generate prow job. ERROR:

No ref for requested test included in command. The org, repo, and branch containing the requested test need to be targeted by at least one of the included PRs.

@ormergi
Copy link
Contributor Author

ormergi commented Nov 2, 2025

/testwith openshift/origin/main/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-dualstack openshift/ovn-kubernetes#2827 #30415

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2025

@ormergi, testwith: could not generate prow job. ERROR:

BUG: test 'periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-dualstack' not found in injected config

@ormergi
Copy link
Contributor Author

ormergi commented Nov 2, 2025

/testwith openshift/origin/release-4.20/e2e-metal-ipi-ovn-bgp-virt-dualstack openshift/ovn-kubernetes#2827 #30415

@ormergi
Copy link
Contributor Author

ormergi commented Nov 5, 2025

Testing this PR with the incoming IP & MAC conflict bits and the [missing fix in tests] (#30415) on on 4.20 is green
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/multi-pr-openshift-origin-30414-openshift-ovn-kubernetes-2827-openshift-origin-30415-e2e-metal-ipi-ovn-bgp-virt-dualstack/1984947085962645504
Although this is a dualstack job, I think it provide some indication its safe to backport.
In any case we have incomming a new lane, in case of an issue we will get indication and fix it.

Copy link
Contributor

@maiqueb maiqueb 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 Nov 5, 2025
@ormergi
Copy link
Contributor Author

ormergi commented Nov 9, 2025

/retest-required

@ormergi
Copy link
Contributor Author

ormergi commented Nov 9, 2025

/retitle [release-4.20] OCPBUGS-64836: back-port IP & MAC conflict detection e2e tests

@openshift-ci openshift-ci bot changed the title [release-4.20] CORENET-6378: back-port IP & MAC conflict detection e2e tests [release-4.20] OCPBUGS-64836: back-port IP & MAC conflict detection e2e tests Nov 9, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Nov 9, 2025
@openshift-ci-robot
Copy link

@ormergi: This pull request references Jira Issue OCPBUGS-64836, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-64837 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-64837 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is manual check-pick of IP conflict detection tests [1] (commits 1-3) and MAC conflict detection tests [2] (commit 4).
Commits were cherry-picked from release-4.21 branch.

[1] #30197
[2] #30314

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.

@ormergi
Copy link
Contributor Author

ormergi commented Nov 9, 2025

/tide refresh

@ormergi
Copy link
Contributor Author

ormergi commented Nov 12, 2025

/testwith openshift/origin/release-4.20/e2e-metal-ipi-ovn-bgp-virt-ipv4 openshift/ovn-kubernetes#2827

/testwith openshift/origin/release-4.20/e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview openshift/ovn-kubernetes#2827

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 12, 2025

@ormergi, testwith: could not generate prow job. ERROR:

BUG: test 'e2e-metal-ipi-ovn-bgp-virt-ipv4' not found in injected config

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 12, 2025

@ormergi, testwith: could not generate prow job. ERROR:

BUG: test 'e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview' not found in injected config

@ormergi
Copy link
Contributor Author

ormergi commented Nov 12, 2025

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

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 12, 2025

@ormergi, testwith: could not generate prow job. ERROR:

BUG: test 'periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4' not found in injected config

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 12, 2025

@ormergi, testwith: could not generate prow job. ERROR:

BUG: test 'periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview' not found in injected config

@ormergi
Copy link
Contributor Author

ormergi commented Nov 12, 2025

/testwith openshift/origin/release-4.20/e2e-metal-ipi-ovn-bgp-virt-dualstack openshift/ovn-kubernetes#2827 #30415

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2025

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

  • periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/30143170-cea9-11f0-8e15-d791a3d4c5de-0

@kyrtapz
Copy link
Contributor

kyrtapz commented Dec 1, 2025

/payload-job periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview
@ormergi looks like verify is failing.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2025

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

  • periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7acce030-cecd-11f0-9576-b3bf9e4e76e0-0

Verify KubeVirt VMs with preconfigured MAC address retain a
requested MAC address before and after another VM is created
requesting the same MAC address.
And verify the other VM requesting the same MAC address get
the appropriate address conflict error event.

Signed-off-by: Or Mergi <ormergi@redhat.com>
(cherry picked from commit 0c58f2a)
@ormergi ormergi force-pushed the bp-ip-mac-conflict-detection-e2e branch from 49ac8bc to d21f207 Compare December 2, 2025 12:03
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 2, 2025
@ormergi
Copy link
Contributor Author

ormergi commented Dec 2, 2025

verify job is green, lets see how payloads acts

/payload-job-with-prs periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4 openshift/api#2546

@ormergi
Copy link
Contributor Author

ormergi commented Dec 2, 2025

/payload-job periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 2, 2025

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

  • periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8afd2ba0-cf7b-11f0-8c45-0ce31a7b30da-0

@kyrtapz
Copy link
Contributor

kyrtapz commented Dec 3, 2025

/retest-required

@kyrtapz
Copy link
Contributor

kyrtapz commented Dec 4, 2025

/lgtm
@ormergi please add the /verified label

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

ormergi commented Dec 7, 2025

/payload-job periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 7, 2025

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

  • periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f4dc71d0-d344-11f0-943e-e0e6c7c62142-0

@ormergi
Copy link
Contributor Author

ormergi commented Dec 9, 2025

/verified

@openshift-ci-robot
Copy link

@ormergi: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

In response to this:

/verified

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.

@ormergi
Copy link
Contributor Author

ormergi commented Dec 9, 2025

/verified later

@openshift-ci-robot
Copy link

@ormergi: /verified later <@username> requires at least one GitHub @username to be specified (it can be a comma delimited list). It indicates the engineer(s) that will be performing the verification. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

In response to this:

/verified later

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.

@ormergi
Copy link
Contributor Author

ormergi commented Dec 9, 2025

/verified later @ormergi

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Dec 9, 2025
@openshift-ci-robot
Copy link

@ormergi: This PR has been marked to be verified later by @ormergi.

In response to this:

/verified later @ormergi

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.

@neisw
Copy link
Contributor

neisw commented Dec 9, 2025

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kyrtapz, maiqueb, neisw, ormergi

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 Dec 9, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 11e5d68 and 2 for PR HEAD d21f207 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 75ff26f and 1 for PR HEAD d21f207 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 9, 2025

@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/prow/okd-scos-e2e-aws-ovn 49ac8bc link false /test okd-scos-e2e-aws-ovn

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

/retest-required

Remaining retests: 0 against base HEAD 70c1be8 and 0 for PR HEAD d21f207 in total

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-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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 verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants