Bare Metal RHOCP installation fails with duplicated boot labeling error

Issue

• The startup of a bare metal node (during or after installation) fails with an error similar to the following, which is appearing in the CoreOS boot stage:

  Displaying logs from failed units: coreos-unique-boot.service
  Jun 12 07:52:09 systemd[1]: Starting Ensure Unique `boot` Filesystem Label...
  Jun 12 07:52:09 rdcore[788]: Error: System has 2 devices with a filesystem labeled 'boot': ["/dev/sdd3", "/dev/sda3"]
  Jun 12 07:52:09 systemd[1]: coreos-unique-boot.service: Main process exited, code=exited, status=1/FAILURE
  Jun 12 07:52:09 systemd[1]: coreos-unique-boot.service: Failed with result 'exit-code'.
  Jun 12 07:52:09 systemd[1]: Failed to start Ensure Unique `boot` Filesystem Label.
  Jun 12 07:52:09 systemd[1]: coreos-unique-boot.service: Triggering OnFailure= dependencies.
  

• The boot label related error is appearing randomly during the startup of nodes that have several disks connected

• This error can affect bare metal nodes that have several physical disks