-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
3
-
False
-
-
False
-
None
-
-
Yes
-
Important
-
Customer Reported
-
No
Description of problem:
As of now, it is required to create new bridge mappings with a unique name for every VLANs. So we cannot have two different NAD configuration pointing to same bridge maping. Please also refer OCPBUGS-31679.
Since, this is not explicitly prevented and its' not easy to find in the logs, we need to document this limitation at https://docs.openshift.com/container-platform/4.15/virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.html#virt-creating-localnet-nad-cli_virt-connecting-vm-to-ovn-secondary-network
- causes
-
CNV-77604 [localnet tier-2] Add test for verifying one NAD for specific localnet mapping
-
- New
-
- is related to
-
CNV-44070 [Doc] Document how to use a VLAN ID in a OVN secondary network with localnet topology
-
- Closed
-
-
CNV-66250 [CLOSED LOOP for] [DOC] Document the requirement of having new bridge mapping for new VLANs
-
- Refinement
-
- links to
- mentioned in
-
Page Loading...