Comment 2 for bug 1628163

First of all, we have to support more than just ubuntu. Second, the purpose of find_multipath_device_path() is to find a single path, not all paths and it has to work in the configuration of having friendly names off and on. So, the lowest common denominator was chosen for the path search algorithm.

We have to be distro agnostic. The paths that are searched now are the lowest common denominator in all the distros/platforms/architectures that os-brick supports. We don't know if friendly names are on or off, and can't find out without calling the multipath app, which is incredibly slow and unreliable. So, the algorithm that is in place now is the fastest and most reliable way to discover multipath devices on the system. The last resort, which is still in code, is to call multipath to discover the paths.

Also, we don't need to find the volume in every possible path it may show up. We just need to find one. Once one of those paths shows up, we can find the rest of them.