Comment 3 for bug 1665584

As per azvyagintsev comment in review [1], proposed timeout may not be big enough to allow OS to initialize mpath devices. As a result, it will break a previous fix [2]. I think that proposed change [1] is still a good WA for reported issue, but some solid solution is needed to close the bug in a right way. Assigning the bug to fuel-sustaining group and will wait for the fix to backport.

[1] https://review.openstack.org/#/c/444310/2
[2] https://review.openstack.org/#/c/285340/