package resolvconf 1.78ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
resolvconf (Ubuntu) |
Fix Released
|
Critical
|
Martin Pitt |
Bug Description
Upgrading from 14.04LTS to 16.04LTS (Xenial), I got this upgrade error.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu1
ProcVersionSign
Uname: Linux 4.3.0-6-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
Date: Wed Jan 20 19:57:02 2016
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
InstallationDate: Installed on 2014-10-05 (472 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitec
RelatedPackageV
dpkg 1.18.4ubuntu1
apt 1.1.10
SourcePackage: resolvconf
Title: package resolvconf 1.78ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
UpgradeStatus: Upgraded to xenial on 2016-01-20 (0 days ago)
Changed in resolvconf (Ubuntu): | |
assignee: | nobody → Martin Pitt (pitti) |
importance: | Undecided → High |
Changed in resolvconf (Ubuntu): | |
status: | Confirmed → Fix Committed |
I tried to reproduce this with a 14.04 → 16.04 upgrade in several scenarios, but I can't yet. Nicolas, do you actually use ifupdown on this system, i. e. can you please attach your /etc/network/ interfaces and /etc/network/ interfaces. d/* ?
Even if I remove "eth0" from /etc/network/ interfaces, 14.04's resolvconf still creates /run/resolvconf /interfaces/ (it will be empty then). This happens both in the upstart job (/etc/init/ resolvconf. conf) and in the systemd service (/lib/systemd/ system/ resolvconf. service) . So it appears to me that resolvconf was never started before you started the upgrade even.
Did you do anything to disable resolvconf in 14.04?
I suppose we could guard against this by teaching resolvconf to mkdir the runtime directory on resolvconf --enable-updates, instead of in the init scripts. But that doesn't help to understand what went wrong on your system.
Thanks!