Use https://issues.redhat.com/browse/CNV-55287 as part of the setup.

Define another C-UDN, on the same/new namespace, with a different VLAN tag that the one already exists in CNV-55287, and connect it to the same NNCP (We can use the same network name, with a different physicalNetworkName).

Create a VM connected to the new localnet network, and set an affinity in it so that it will run on the same node as one of the VMs created in CNV-55287.

Verify no connectivity (ping fails) between this new vm and the VM running on the same node, connected to a localnet with a different VLAN tag.

This localnet test case can be used as a general reference.

The verification steps for this bug can be used as a general example for this.

Please notes:

1. Since we currently don't have the CUDN implemented in the product we will create the desired localnet directly. In the future, when we have it available downstream the test case (and automation) should be changed accordingly.
2. Since we don't have the infrastructure implemented to create NNCP with bridge mapping, this step will be done manually and will be added to the automation in the future.

DOD:

Write a detailed test plan in Polarion.

Verify the test manually.