Merge pull request #65708 from kquinn1204/TELCODOCS-899

TELCODOCS-899 Doc customer feedback on rootDeviceHints

Author: bburt-rh

modules/ipi-install-troubleshooting-misc-issues.adoc

@@ -77,6 +77,30 @@ $ kubectl -n openshift-network-operator logs -l "name=network-operator"
 +
 On high availability clusters with three or more control plane (master) nodes, the Operator will perform leader election and all other Operators will sleep. For additional details, see https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md[Troubleshooting].
 
+== Addressing the "No disk found with matching rootDeviceHints" error message
+
+After you deploy a cluster, you might receive the following error message:
+
+[source,text]
+----
+No disk found with matching rootDeviceHints
+----
+
+To address the `No disk found with matching rootDeviceHints` error message, a temporary workaround is to change the `rootDeviceHints` to `minSizeGigabytes: 300`.
+
+After you change the `rootDeviceHints` settings, boot the CoreOS and then verify the disk information by using the following command:
+
+[source,terminal]
+----
+$ udevadm info /dev/sda
+----
+
+If you are using DL360 Gen 10 servers, be aware that they have an SD-card slot that might be assigned the `/dev/sda` device name. If no SD card is present in the server, it can cause conflicts. Ensure that the SD card slot is disabled in the server's BIOS settings.
+
+If the `minSizeGigabytes` workaround is not fulfilling the requirements, you might need to revert `rootDeviceHints` back to `/dev/sda`. This change allows ironic images to boot successfully.
+
+An alternative approach to fixing this problem is by using the serial ID of the disk. However, be aware that finding the serial ID can be challenging and might make the configuration file less readable. If you choose this path, ensure that you gather the serial ID using the previously documented command and incorporate it into your configuration.
+
 == Cluster nodes not getting the correct IPv6 address over DHCP
 
 If the cluster nodes are not getting the correct IPv6 address over DHCP, check the following: