Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-34011

UI should use type "bridge" instead of "cnv-bridge"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • 4.16.z
    • 4.16
    • Management Console
    • None
    • No
    • False
    • Hide

      None

      Show
      None
    • 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".

              upalatuc@redhat.com Ugo Palatucci
              openshift-crt-jira-prow OpenShift Prow Bot
              Guohua Ouyang Guohua Ouyang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: