libmultipath's prio routines can deal with pp->priority == PRIO_UNDEF just fine. PRIO_UNDEF is just a very low priority. So there's no reason to reject setting up a multipath map because paths have undefined priority. Signed-off-by: Martin Wilck <mwilck@xxxxxxxx> --- libmultipath/configure.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/libmultipath/configure.c b/libmultipath/configure.c index fa6e21cb31af..bb3d8771592d 100644 --- a/libmultipath/configure.c +++ b/libmultipath/configure.c @@ -993,9 +993,6 @@ int coalesce_paths (struct vectors * vecs, vector newmp, char * refwwid, continue; } - if (pp1->priority == PRIO_UNDEF) - mpp->action = ACT_REJECT; - if (!mpp->paths) { condlog(0, "%s: skip coalesce (no paths)", mpp->alias); remove_map(mpp, vecs, 0); @@ -1021,8 +1018,6 @@ int coalesce_paths (struct vectors * vecs, vector newmp, char * refwwid, mpp->size); mpp->action = ACT_REJECT; } - if (pp2->priority == PRIO_UNDEF) - mpp->action = ACT_REJECT; } verify_paths(mpp, vecs); -- 2.16.1 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel