In the documentation [1], we state the need to use UUIDS for OSDs. However, this seems to not get followed very often as we keep seeing customers over and over again not using UUIDS, run into issues when the kernel picks up the devices in the incorrect order [2], and [3] needs to be followed to enable UUIDS after the fact. As a workaround to get customers up and running a version of [4] is followed. Essentially, we update LSO symlinks to point to the correct devices and restart the OSDS.

This doc BZ bug is opened to elaborate on the importance of using UUIDS for OSD devices, and make this more clear (possibly adding this to the section "Chapter 1. Preparing to deploy OpenShift Data Foundation") to avoid issues down the road. I'm making this doc BZ urgent to prevent new customers from running into this issue.

Furthermore... using UUID devices should be enabled and used on ALL platforms if you're using LSO devices. So, this doc BZ is to update all of our documentation to reflect this.

[1] https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.12/html-single/deploying_openshift_data_foundation_on_vmware_vsphere/index#creating-an-openshift-data-foundation-service_cloud-storage
For VMs on VMware, ensure the disk.EnableUUID option is set to TRUE. You need to have vCenter account privileges to configure the VMs. For more information, see Required vCenter account privileges. To set the disk.EnableUUID option, use the Advanced option of the VM Options in the Customize hardware tab. For more information, see Installing RHCOS and starting the OpenShift Container Platform bootstrap process.
[2] https://access.redhat.com/solutions/44389
[3] https://access.redhat.com/solutions/4606201
[4] https://access.redhat.com/solutions/7025876