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

next-hop-interface cannot reference br-ex

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • 4.18
    • 4.13.z, 4.12.z, 4.14.z, 4.15.z, 4.17.z, 4.16.z
    • None
    • None
    • 3
    • OSDOCS Sprint 266
    • 1
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • In Progress

      Description of problem:

      In the DNS configuration section we have a note that the DNS config cannot be applied to br-ex because modifying the profile is not allowed. However, it was just reported that this also applies to custom routes with next-hop-interface pointing at br-ex. This breaks the network config in a similar way to applying a DNS config to br-ex.

      Version-Release number of selected component (if applicable):

          

      How reproducible:

          

      Steps to Reproduce:

          1. Apply NMState route config with next-hop-interface set to br-ex
          2.
          3.
          

      Actual results:

          Host networking fails

      Expected results:

          Route is applied successfully

      Additional info:

          This will not apply to clusters using the custom NMState br-ex feature because in that case there is no conflict with configure-ovs.

              dfitzmau@redhat.com Darragh Fitzmaurice
              bnemec@redhat.com Benjamin Nemec
              Ross Brattain Ross Brattain
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: