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

[IPI] coredns-monitor continuously reporting "Failed to read ip from file /run/nodeip-configuration/ipv4"


    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Minor Minor
    • 4.16.0
    • 4.13, 4.12, 4.14, 4.15
    • None
    • Low
    • No
    • False
    • Hide



      Description of problem:

      After installing an OpenShift IPI vSPhere cluter the coredns-monitor containers in the "openshift-vsphere-infra" namespace continuously report the message: "Failed to read ip from file /run/nodeip-configuration/ipv4" error="open /run/nodeip-configuration/ipv4: no such file or directory". The file "/run/nodeip-configuration/ipv4" present on the nodes is not actually moutned on the coredns pods. Apparently doesn't look to have any impact on the functionality of the cluster, but having a "failed" message on the container can triggers allarm or reserach for problem in the cluster.

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

      Any 4.12, 4.13, 4.14

      How reproducible:


      Steps to Reproduce:

      1. Install OpenShift IPI vSphere cluster
      2. Wait forthe installation to complete
      3. Read the logs of any coredns-monitor container in the "openshift-vsphere-infra" namespace

      Actual results:

      coredns-monitor continuously report the failed message, mesleading a cluster administartor for searching if there is a real issue.

      Expected results:

      coredns-monitor should not report this failed message if is not needed to fix it.

      Additional info:

      The same issue happens in Baremetal IPI clusters.

            mkowalsk@redhat.com Mat Kowalski
            rhn-support-cpassare Christian Passarelli
            Zhanqi Zhao Zhanqi Zhao
            0 Vote for this issue
            8 Start watching this issue