Description of problem: The use_devicesfile was initially introduced in RHEL-9.0 via BZ#2012830 as a means to manage LVM devices and replace the traditional filter method. However, the old filter regex default to "accept all" devices. Only a blacklist was needed. The introduction of use_devicesfile is enabled by default per BZ#2129176. This value results in non-bootable systems after upgrade and requires manual whitelisting of devices. Version-Release number of selected component (if applicable): 9.0, 9.1, 9.2 How reproducible: Very Steps to Reproduce: 1. Install 9.1 (single disk, multiple disk, does not matter) 2. Upgrade to 9.2 3. System drops to maintenance mode 4. The system devices file does not contain all PV's. Actual results: System fails to boot and drops to maintenance mode. Requires manual intervention to either set `use_devicesfile = 0` or to manually add devices. Expected results: All devices get added to system devices, or set use_devicesfile to default to off. Additional info: This has affected multiple customers now, creating high visibility Sev 1 cases for support due to non bootable systems.
Do you have some specific examples of the system.devices file prior to the update and a recreated system.devices file after the update?
One bug has been identified in bug 2208039 that would cause this -- a change in how 9.2 handles line feed characters in wwids.
(In reply to David Teigland from comment #2) > One bug has been identified in bug 2208039 that would cause this -- a change > in how 9.2 handles line feed characters in wwids. The other bug was actually a change in handling trailing spaces in t10 wwids. In 9.0/9.1 trailing spaces where replaced by _ and in 9.2 they are ignored. If system.devices on 9.0 or 9.1 contains an IDNAME starting with "t10" and ending with "_" then it's likely to run into bug 2208039 on upgrade.