can't upgrade multipathd on 12.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
multipath-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Upgrade script tries to stop running multipathd while volume is in use:
apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
squid squid3 squid3-common
The following packages will be upgraded:
multipath-tools
1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
15 not fully installed or removed.
Need to get 0 B/166 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
(Reading database ... 304505 files and directories currently installed.)
Preparing to replace multipath-tools 0.4.9-3ubuntu5 (using .../multipath-
* Stopping multipath daemon multipathd Feb 03 07:38:35 | mpath1: map in use
invoke-rc.d: initscript multipath-tools, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
* Stopping multipath daemon multipathd Feb 03 07:38:35 | mpath1: map in use
invoke-rc.d: initscript multipath-tools, action "stop" failed.
dpkg: error processing /var/cache/
subprocess new pre-removal script returned error exit status 1
* Starting multipath daemon multipathd [ OK ]
Errors were encountered while processing:
/var/cache/
E: Sub-process /usr/bin/dpkg returned an error code (1)
Is there any wrokaround?
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Won't Fix'. If you disagree or have
new information, we would be grateful if you could please add a comment
stating why and then change the status of the bug to 'New'.