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

[4.18] Poor handling of incomplete Redfish URLs

XMLWordPrintable

    • Moderate
    • No
    • 1
    • Metal Platform 271
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, using a Redfish address without a system ID (e.g. redfish://host/redfish/v1/ instead of redfish://host/redfish/v1/Self) would cause a registration error about invalid JSON. Now this case is correctly handled: if the BMC manages only one system, this system is used, otherwise a proper error is displayed.
      Show
      Previously, using a Redfish address without a system ID (e.g. redfish://host/redfish/v1/ instead of redfish://host/redfish/v1/Self) would cause a registration error about invalid JSON. Now this case is correctly handled: if the BMC manages only one system, this system is used, otherwise a proper error is displayed.
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-56026. The following is the description of the original issue:
      —
      Description of problem:

      It's not rare for customers to forget to add a Redfish system ID (= the identifier of the specific server) to the URL, producing bmc.address values like redfish://host/redfish/v1/

      Doing so right now produces a very confusing JSON parsing error from Ironic. We can and should fix that, but even better, we can handle this situation gracefully. Ironic actually treats the system ID as optional. We need to make it optional in BMO.

      The goal of this bug is for BMO to treat URLs like redfish://host/redfish/v1/ or redfish://host/ as addresses without a system ID.

              rhn-engineering-dtantsur Dmitry Tantsur
              openshift-crt-jira-prow OpenShift Prow Bot
              Steeve Goveas Steeve Goveas
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: