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

nodeip-configuration.service fails to enable forwarding - No such file or directory

    XMLWordPrintable

Details

    • Critical
    • Yes
    • Approved
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      nodeip-configuration.service is failed on cluster nodes:
      
      systemctl status nodeip-configuration.service
      × nodeip-configuration.service - Writes IP address configuration so that kubelet and crio services select a valid node IP
           Loaded: loaded (/etc/systemd/system/nodeip-configuration.service; enabled; preset: disabled)
           Active: failed (Result: exit-code) since Tue 2023-08-15 16:28:09 UTC; 18h ago
         Main PID: 3709 (code=exited, status=0/SUCCESS)
              CPU: 237ms
      
      Aug 15 16:28:09 openshift-worker-2.lab.eng.tlv2.redhat.com configure-ip-forwarding.sh[3761]: ++ [[ -z bond0.354 ]]
      Aug 15 16:28:09 openshift-worker-2.lab.eng.tlv2.redhat.com configure-ip-forwarding.sh[3761]: ++ echo bond0.354
      Aug 15 16:28:09 openshift-worker-2.lab.eng.tlv2.redhat.com configure-ip-forwarding.sh[3760]: + iface=bond0.354
      Aug 15 16:28:09 openshift-worker-2.lab.eng.tlv2.redhat.com configure-ip-forwarding.sh[3760]: + echo 'Node IP interface determined as: bond0.354. Enabling IP forwarding...'
      Aug 15 16:28:09 openshift-worker-2.lab.eng.tlv2.redhat.com configure-ip-forwarding.sh[3760]: Node IP interface determined as: bond0.354. Enabling IP forwarding...
      Aug 15 16:28:09 openshift-worker-2.lab.eng.tlv2.redhat.com configure-ip-forwarding.sh[3760]: + sysctl -w net.ipv4.conf.bond0.354.forwarding=1
      Aug 15 16:28:09 openshift-worker-2.lab.eng.tlv2.redhat.com configure-ip-forwarding.sh[3767]: sysctl: cannot stat /proc/sys/net/ipv4/conf/bond0/354/forwarding: No such file or directory
      Aug 15 16:28:09 openshift-worker-2.lab.eng.tlv2.redhat.com systemd[1]: nodeip-configuration.service: Control process exited, code=exited, status=1/FAILURE
      Aug 15 16:28:09 openshift-worker-2.lab.eng.tlv2.redhat.com systemd[1]: nodeip-configuration.service: Failed with result 'exit-code'.
      Aug 15 16:28:09 openshift-worker-2.lab.eng.tlv2.redhat.com systemd[1]: Failed to start Writes IP address configuration so that kubelet and crio services select a valid node IP.
      

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

      4.14.0-0.nightly-2023-08-08-005757
      

      How reproducible:

      so far once
      

      Steps to Reproduce:

      1. Deploy multinode spoke cluster with GitOps-ZTP
      2. Configure baremetal network to be on top of vlan interface
                    - name: bond0.354
                      description: baremetal network
                      type: vlan
                      state: up
                      vlan:
                        base-iface: bond0
                        id: 354
                      ipv4:
                        enabled: true
                        dhcp: false
                        address:
                        - ip: 10.x.x.20
                          prefix-length: 26
                      ipv6:
                        enabled: false
                        dhcp: false
                        autoconf: false
      

      Actual results:

      Cluster is deployed but nodeip-configuration.service is Failed
      

      Expected results:

      nodeip-configuration.service is Active
      

      Attachments

        Issue Links

          Activity

            People

              mkowalsk@redhat.com Mat Kowalski
              yprokule@redhat.com Yurii Prokulevych
              Yurii Prokulevych Yurii Prokulevych
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: