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

configure interface level dns on ipv6 single-stack cluster failed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.16.0
    • None
    • Moderate
    • Yes
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      apply nncp to configure interface level DNS on ipv6 single-stack cluster, file /etc/resolv.conf is not updated

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

      OCP version: 4.16.0-0.nightly-2024-03-13-061822
      kubernetes-nmstate-operator.4.16.0-202403111814

      How reproducible:

      always

      Steps to Reproduce:

      1. install knmstate operator
      2. apply below nncp to configure dns on one of the node
      ---
      apiVersion: nmstate.io/v1
      kind: NodeNetworkConfigurationPolicy
      metadata:
        name: dns-static-int2
      spec:
        nodeSelector:
          kubernetes.io/hostname: worker-2.sriov.openshift-qe.sdn.com
        desiredState:
          dns-resolver:
            config:
              search:
              - testint.com
              server:
              - fd2e:6f44:5dd8:c956::19
              - 2088::9999
          interfaces:
          - ipv6:
              address:
              - ip: 2006:db8::1:66
                prefix-length: 64
              auto-dns: false
              dhcp: false
              enabled: true
            name: dummy6
            state: up
            type: dummy
      # oc apply -f dns-int.yaml 
      nodenetworkconfigurationpolicy.nmstate.io/dns-static-int2 created
      # oc get nncp
      NAME              STATUS      REASON
      dns-static-int2   Available   SuccessfullyConfigured
      # oc get nnce
      NAME                                                  STATUS      STATUS AGE   REASON
      worker-2.sriov.openshift-qe.sdn.com.dns-static-int2   Available   4s           SuccessfullyConfigured

      Actual results:

      file /etc/resolv.conf is not updated:
      
      sh-5.1# cat /etc/resolv.conf 
      # Generated by KNI resolv prepender NM dispatcher script
      search sriov.openshift-qe.sdn.com
      nameserver fd2e:6f44:5dd8:c956::19
      nameserver fd2e:6f44:5dd8:c956::1
      nameserver fe80::5054:ff:fe60:a44d%br-ex
      sh-5.1#
      
      /var/run/NetworkManager/resolv.conf is updated correctly:
      sh-5.1# cat /var/run/NetworkManager/resolv.conf 
      # Generated by NetworkManager
      search testint.com sriov.openshift-qe.sdn.com
      nameserver fd2e:6f44:5dd8:c956::19
      nameserver 2088::9999
      nameserver fd2e:6f44:5dd8:c956::1
      # NOTE: the libc resolver may not support more than 3 nameservers.
      # The nameservers listed below may not be recognized.
      nameserver fe80::5054:ff:fe60:a44d%br-ex
      sh-5.1#
      sh-5.1# nmcli | grep 'DNS config' -A 10
      DNS configuration:
      	servers: fd2e:6f44:5dd8:c956::19 2088::9999
      	domains: testint.com
      	interface: dummy6
      ... ...

      Expected results:

      the file /etc/resolv.conf can be updated accordingly

      Additional info:

       

            mkowalsk@redhat.com Mat Kowalski
            rh-ee-qiowang Qiong Wang
            Qiong Wang Qiong Wang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: