How are they setting this value and where? I'm not aware of any field in the UI that allows this... if so, please provide screenshots. Otherwise, this is an unsupported operation. If it is there, then this is a UI issue. That said, this has a simple workaround: use a shorter name. Since it seems this cluster never came up, the solution would be to delete the StorageCluster, force delete any stuck resources, and recreate the StorageCluster with an appropriate name. We can certainly take a look to see what we're doing with the name generation for the OSDs. In OCS 4.7 with TopologySpreadConstraints, this name generation should already be somewhat shorter. Since this doesn't seem like a critical bug, deferring this to OCS 4.8.
> How are they setting this value and where? I'm not aware of any field in the UI that allows this... if so, please provide screenshots. I checked how LSO setup is integrated in Create Storage Cluster wizard as provided by OCS plugin for OCP Console, and indeed in 2nd step "create storage class", there is an option to specify name of a volume set. > If it is there, then this is a UI issue. While it true that this is exposed via UI, I believe output checks should be done in ocs operator as well.
Created attachment 1755786 [details] screenshot