Description of problem:

lvm should ignore leading and trailing spaces on sys_wwid and sys_serial device ids, and replace spaces in the middle with underscores. For t10 wwids, multiple sequential spaces in the middle of the value are replaced with a single underscore.

Spaces have been handled inconsistently in past releases. In some cases, lvm would be able to use a device with the spaces, and in others it wouldn't.

In RHEL 9.0 and 9.1, lvm replaced leading and trailing spaces in sys_wwid and sys_serial with underscores, and was able to use the device. So, we want to recognize and handle any system.devices entries with leading/trailing underscores. These versions also replaced every middle space with an underscore, so we also want to recognize those (this bit of handling was already added in 9.2.)

In RHEL 9.2, wwids with leading spaces are not usable, and wwids with trailing spaces are usable only for the t10 type. wwids with spaces in the middle of the wwid are only usable for the t10 type. sys_serial is handled like 9.0 and 9.1, by replacing all spaces with underscores.

In practice, only t10 wwids and serial numbers are expected to contain spaces (naa and eui wwid standards do not permit spaces.)

Examples (quotes show spaces, and are not in the values):

reported sysfs wwid: " t10.123 456 "
expected system.devices: "t10.123_456"

reported sysfs wwid: " naa.123 456 "
expected system.devices: "naa.123__456"

reported sysfs serial: " 123 456 "
expected system.devices "123__456"

Possible system.devices values created by previous lvm versions that we want to handle:

"_t10.123456_"
"_naa.123456_"
"_123456_"

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info: