package nfs-common 1:1.2.8-9ubuntu1.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 5

[Alfred Tuinman]

just tried to uninstall nfs-common as I am experiencing problems running nfs. Next step was to install it again.

nfs won't mount. it is just timing out.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nfs-common 1:1.2.8-9ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
AptOrdering: nfs-common: Remove
Architecture: amd64
Date: Tue Apr 14 12:16:25 2015
DpkgTerminalLog:
 Removing nfs-common (1:1.2.8-9ubuntu1.1) ...
 Failed to issue method call: Unit idmapd.service not loaded.
 invoke-rc.d: initscript idmapd, action "stop" failed.
DuplicateSignature: package:nfs-common:1:1.2.8-9ubuntu1.1:subprocess installed pre-removal script returned error exit status 5
ErrorMessage: subprocess installed pre-removal script returned error exit status 5
InstallationDate: Installed on 2014-04-26 (352 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: nfs-utils
Title: package nfs-common 1:1.2.8-9ubuntu1.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 5
UpgradeStatus: Upgraded to utopic on 2015-03-28 (17 days ago)

[Steve Langasek (vorlon)]

Confirmed; the nfs-common package has a different name for the systemd unit for idmapd, vs the upstart job and sysvinit script. This inconsistency prevents the invoke-rc.d handling from working correctly.

Martin, I think we should rename the units to match the existing upstart/sysvinit names? It diverges from upstream but seems to be the simplest way to maintain cross-init-system compatibility.

[Martin Pitt (pitti)]

Please don't run systemd under Ubuntu 14.10. It's known to have lots of issues like that which have been fixed in 15.04.