upgrading to multipath 0.4.9 presents incompatible config file changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
multipath-tools (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
The priority checkers have been converted from individual binaries that callout to dynamically loaded libraries (dlopen). As a result, should a circa 0.4.8 config file remain in place, the priority checker becomes undefined, as that standalone path checker no longer exists. This will effect users who upgrade to Oneiric and users who upgrade from lucid to the next LTS.
One example of the format change is,
0.4.8:
prio_callout "/sbin/
0.4.9:
prio alua
There may be other config file changes, more exploration is needed.
Here's what the preconfigured, 0.4.9 priority checkers look like.
# echo 'show config' | multipathd -k | grep 'prio '| sort -u
prio alua
prio const
prio emc
prio hds
prio hp_sw
prio netapp
prio rdac
In 0.4.8:
# echo 'show config' | multipathd -k | grep 'prio_callout'| sort -u
prio_callout /sbin/mpath_
prio_callout /sbin/mpath_
prio_callout /sbin/mpath_
prio_callout /sbin/mpath_
prio_callout /sbin/mpath_
prio_callout /sbin/mpath_
prio_callout /sbin/mpath_
description: | updated |
Changed in multipath-tools (Ubuntu): | |
status: | New → Confirmed |
Changed in multipath-tools (Ubuntu): | |
importance: | Undecided → High |
Experimenting shows that we can have the older config values side by side
with the new ones. e.g.
... prio_alua /dev/%n
prio_callout /sbin/mpath_
prio alua
...
multipath doesn't have a rigid config file format, it seems to slurp symbols
and then seek the key/value pair out on demand. In doing this, we can safely
downgrade as well.