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

[4.12] provisioning of baremetal nodes fails when using multipath device as rootDeviceHints

XMLWordPrintable

    • Important
    • 2
    • Metal Platform 227
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause: when provisioning a server, IPC was not shared between the host OS of the ramdisk and the Ironic agent container
      Consequence: provisioning CoreOS on multipath devices could hang on executing the partprobe command
      Fix: the Ironic agent container configuration has been updated to share IPC with the host
      Show
      Cause: when provisioning a server, IPC was not shared between the host OS of the ramdisk and the Ironic agent container Consequence: provisioning CoreOS on multipath devices could hang on executing the partprobe command Fix: the Ironic agent container configuration has been updated to share IPC with the host
    • Customer Escalated

      Description of problem:

      Customer is not able anymore to provision new baremetal nodes in 4.10.35 using the same rootDeviceHints used in 4.10.10.
Customer uses HP DL360 Gen10, with exteranal SAN storage that is seen by the system as a multipath device. Latest IPA versions are implementing some changes to avoid wiping shared disks and this seems to affect what we should provide as rootDeviceHints.
They used to put /dev/sda as rootDeviceHints, in 4.10.35 it doesn't make the IPA write the image to the disk anymore because it sees the disk as part of a multipath device, we tried using the on top multipath device /dev/dm-0, the system is then able to write the image to the disk but then it gets stuck when it tried to issue a partprobe command, rebooting the systems to boot from the disk does not seem to help complete the provisioning, no workaround so far.

       

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

       

      How reproducible:

      by trying to provisioning a baremetal node with a multipath device.

      Steps to Reproduce:

      1. Create a new BMH using a multipath device as rootDeviceHints
2.
3.

      Actual results:

      The node does not get provisioned

      Expected results:

      the node gets provisioned correctly

      Additional info:

       

            rhn-engineering-dtantsur Dmitry Tantsur
            fcristin1@redhat.com Francesco Cristini
            Jad Haj Yahya Jad Haj Yahya
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: