-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.16
-
None
-
No
-
False
-
-
Release Note Not Required
-
In Progress
This is a clone of issue OCPBUGS-33717. The following is the description of the original issue:
—
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 changing UI so it generates NADs of the type "bridge" instead of "cnv-bridge".
Version-Release number of selected component (if applicable):
4.14
How reproducible:
Always
Steps to Reproduce:
1. Use the NetworkAttachmentDefinition dialog to create a network of type bridge 2. Read the generated yaml
Actual results:
It has "type": "cnv-bridge"
Expected results:
It should have "type": "bridge"
Additional info:
The same should be done to any instance of "cnv-tuning" by changing it to "tuning".
- account is impacted by
-
CNV-49886 [DOC BUG][4.16]Network documentation should use type "bridge" instead of "cnv-bridge"
- New
-
CNV-49888 [DOC BUG][4.15]Network documentation should use type "bridge" instead of "cnv-bridge"
- New
- clones
-
OCPBUGS-33717 UI should use type "bridge" instead of "cnv-bridge"
- Closed
- is blocked by
-
OCPBUGS-33717 UI should use type "bridge" instead of "cnv-bridge"
- Closed
- links to
-
RHBA-2024:4316 OpenShift Container Platform 4.16.z bug fix update