-
Bug
-
Resolution: Done
-
Normal
-
None
-
CNV v4.14.0
-
None
-
0.42
-
False
-
-
False
-
---
-
---
-
-
No
Description of problem:
Starting with OCP 4.14, we have decided to start using OCP's own "bridge" CNI build instead of our "cnv-bridge" rebuild. To make sure that current users of "cnv-bridge" don't have to change their configuration, we kept "cnv-bridge" as a symlink to "bridge". While the old name still functions, we should make an effort to move users to "bridge". To do that, we can start by replacing all mentions of "cnv-bridge" with "bridge" in our 4.14+ docs.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
Always
Steps to Reproduce:
1. Go to https://docs.openshift.com/container-platform/4.14/virt/vm_networking/virt-connecting-vm-to-linux-bridge.html#virt-creating-linux-bridge-nad-cli_virt-connecting-vm-to-linux-bridge
Actual results:
It mentions "cnv-bridge" as the NAD type
Expected results:
It should only use "bridge"
Additional info:
- account is impacted by
-
CNV-49886 [DOC BUG][4.16]Network documentation should use type "bridge" instead of "cnv-bridge"
- Closed
-
CNV-49888 [DOC BUG][4.15]Network documentation should use type "bridge" instead of "cnv-bridge"
- Closed
- relates to
-
CNV-38746 Cannot live migrate VMs with bridge interface after performing a 4.12 to 4.14 EUS upgrade
- ASSIGNED
- links to