Bug 1099054 - multipath-tools 0.7.7 shouldn't change SUSE path detection default
multipath-tools 0.7.7 shouldn't change SUSE path detection default
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: Martin Wilck
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-06-25 20:01 UTC by Martin Wilck
Modified: 2019-01-10 00:19 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Wilck 2018-06-25 20:01:10 UTC
upstream multipath's default for considering devices multipath members is "find_multipaths strict", meaning that only devices with matching WWIDs in the wwids_file are considered. Under SUSE and openSUSE, the default has always been to grab all devices that aren't explicitly blacklisted, which corresponds to the upstream "find_multipaths greedy" setting. Changing the default would be highly unexpected; customer systems may cease to boot if they are configured to access devices by device-mapper names, and new installations would behave very differently. libstorage-ng would most probably fail to detect multipath.

Change the default for the factory multipath-tools package to "greedy". Later, we may consider changing it to "smart". "smart" would also cause some devices which are multipathed today not to be multipathed any more, but it would do so more intelligently.
Comment 1 Martin Wilck 2019-01-10 00:19:50 UTC
Done in SLE15-SP1 and factory.