Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-1671

Better dispatch way for DNS changes

XMLWordPrintable

    • NetworkManager-1.45.4-1.el9
    • None
    • ZStream
    • 1
    • rhel-sst-network-management
    • ssg_networking
    • 8
    • 3
    • False
    • Hide

      None

      Show
      None
    • No
    • NMT - RHEL 8.10/9.4 DTM 04
    • Approved Blocker
    • Hide

      Given a OCP cluster 4.12 or later version with nmstate operator with br-ex holding DNS configurations

      When customer using nmstate operator to change DNS settings using desire state which only contain DNS configuration with `br-ex` marked as ignored.

      Then NetworkManger will invoke dispatcher script of OCP `30-resolv-prepender` to setup the expected `/etc/resolv.conf`.

       

      Given a OCP cluster 4.12 or later version with nmstate operator installed.

      When customer using nmstate operator to create 50+ VLANs without DNS changes.

      Then the `30-resolv-prepender` will not change content of `/etc/resolv.conf`.

       

      Show
      Given a OCP cluster 4.12 or later version with nmstate operator with br-ex holding DNS configurations When customer using nmstate operator to change DNS settings using desire state which only contain DNS configuration with `br-ex` marked as ignored. Then NetworkManger will invoke dispatcher script of OCP `30-resolv-prepender` to setup the expected `/etc/resolv.conf`.   Given a OCP cluster 4.12 or later version with nmstate operator installed. When customer using nmstate operator to create 50+ VLANs without DNS changes. Then the `30-resolv-prepender` will not change content of `/etc/resolv.conf`.  
    • None
    • None
    • None

      The `30-resolv-prepender` NetworkManager dispatcher script of openshift
      has been invoked even there is no DNS changes at all.

      Introducing new NetworkManager dispatch event/action could eliminate the unneeded invoke of `30-resolv-prepender`

              fge@redhat.com Gris Ge
              fge@redhat.com Gris Ge
              Network Management Team Network Management Team
              Matej Berezny Matej Berezny (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: