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

[4.13] IPI redfish installation fails on inspect for EthernetInterfaces

XMLWordPrintable

    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-11753. The following is the description of the original issue:

      Description of problem:

      During the IPI bm provisioning process the deployment fails with the following error:
      
      Error: could not inspect: could not inspect node, node is currently 'inspect failed' , last error was 'Redfish exception occurred. Error: Failed to get network interface information on node 995431b0-14c8-4aae-9733-e02b42da29ac: The attribute EthernetInterfaces is missing from the resource /redfish/v1/Systems/<redacted>'

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

      4.12

      How reproducible:

      Snippet from my install-config.yaml
            - name: ocp-test-2
              role: master
              bmc:
                address: redfish-virtualmedia://<redacted>/redfish/v1/Systems/<redacted>
                username: admin
                password: <redacted>
                disableCertificateVerification: True
              bootMACAddress: <redacted>

      Steps to Reproduce:

      see above
      

      Actual results:

      Error: could not inspect: could not inspect node, node is currently 'inspect failed' , last error was 'Redfish exception occurred. Error: Failed to get network interface information on node 995431b0-14c8-4aae-9733-e02b42da29ac: The attribute EthernetInterfaces is missing from the resource /redfish/v1/Systems/<redacted>'

      Expected results:

      Because I already specified the bootMACAddress in the install-config.yaml I would like the installer to continue and don't fail when the Redfish API doesn't provide the EthernetInterfaces

      Additional info:

      The blades in this specific chassis don't have access to the NIC adapter.
      Therefore they can't get the MAC address and populate this field in the Redfish API.
      These blades are currently still selling and will need to be supported for another 5 years atleast.
      Our new servers in the new chassis don't have this problem (X-Series).
      
      Please keep the bootMACAddress as an optional field in the install-config.yaml to support these blades.

       

              janders@redhat.com Jacob Anders
              openshift-crt-jira-prow OpenShift Prow Bot
              Jad Haj Yahya Jad Haj Yahya
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: