10.04 LTS -> 12.04 upgrade failed: ifupdown depends on upstart and initscripts but they are not configured

[MarcRandolph]

Attempting to upgrade from Mythbuntu 10.04 to 12.04. Here is the important part of the upgrade log output. Complete logs will be attached, and if more info is needed, please just ask!

dpkg: dependency problems prevent configuration of ifupdown:
 ifupdown depends on upstart-job; however:
  Package upstart-job is not installed.
  Package upstart which provides upstart-job is not configured yet.
 ifupdown depends on initscripts (>= 2.88dsf-13.3); however:
  Package initscripts is not configured yet.
dpkg: error processing ifupdown (--configure):
 dependency problems - leaving unconfigured
dpkg: error processing dpkg (--configure):
 package dpkg is already installed and configured
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 ifupdown
 dpkg
Log ended: 2012-02-20 11:43:29

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: update-manager 1:0.134.7
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Mon Feb 20 13:43:48 2012
InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager

[Jean-Baptiste Lallement (jibel)]

Thanks for your report:

Error from term.log:
dpkg: dependency problems prevent configuration of ifupdown:
 ifupdown depends on upstart-job; however:
  Package upstart-job is not installed.
  Package upstart which provides upstart-job is not configured yet.
 ifupdown depends on initscripts (>= 2.88dsf-13.3); however:
  Package initscripts is not configured yet.
dpkg: error processing ifupdown (--configure):
 dependency problems - leaving unconfigured

[Stéphane Graber (stgraber)]

I'll have a look at this, trying to upgrade a minimal 10.04 system to 12.04 and see if I can reproduce.
As far as I can remember, I haven't changed any of the ifupdown dependencies lately so I'm a bit surprised this appears now.

[Stéphane Graber (stgraber)]

I can't reproduce here, here's the relevant section of the log:
(Reading database ... 92517 files and directories currently installed.)
Preparing to replace initramfs-tools 0.92bubuntu78 (using .../initramfs-tools_0.99ubuntu10_all.deb) ...
Unpacking replacement initramfs-tools ...
dpkg: considering deconfiguration of upstart, which would be broken by installation of friendly-recovery ...
dpkg: yes, will deconfigure upstart (broken by friendly-recovery).
Preparing to replace friendly-recovery 0.2.10 (using .../friendly-recovery_0.2.24_all.deb) ...
De-configuring upstart ...
Unpacking replacement friendly-recovery ...
Preparing to replace upstart 0.6.5-6 (using .../upstart_1.4-0ubuntu8_i386.deb) ...
Unpacking replacement upstart ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up libnih1 (1.0.3-4ubuntu9) ...

Setting up libnih-dbus1 (1.0.3-4ubuntu9) ...

Setting up insserv (1.14.0-2.1ubuntu1) ...
Installing new version of config file /etc/insserv.conf ...
Setting up sysv-rc (2.88dsf-13.10ubuntu10) ...

dpkg: dependency problems prevent configuration of ifupdown:
 ifupdown depends on upstart-job; however:
  Package upstart-job is not installed.
  Package upstart which provides upstart-job is not configured yet.
 ifupdown depends on initscripts (>= 2.88dsf-13.3); however:
  Package initscripts is not configured yet.
dpkg: error processing ifupdown (--configure):
 dependency problems - leaving unconfigured
dpkg: error processing dpkg (--configure):
 package dpkg is already installed and configured
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 ifupdown
 dpkg

[Stéphane Graber (stgraber)]

Upgrading on my system, I see a similar sequence:
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M
Preparing to replace module-init-tools 3.11.1-2ubuntu1 (using .../module-init-tools_3.16-1ubuntu2_amd64.deb) ...^M
Unpacking replacement module-init-tools ...^M
Preparing to replace initramfs-tools 0.92bubuntu78 (using .../initramfs-tools_0.99ubuntu10_all.deb) ...^M
Unpacking replacement initramfs-tools ...^M
dpkg: considering deconfiguration of upstart, which would be broken by installation of friendly-recovery ...^M
dpkg: yes, will deconfigure upstart (broken by friendly-recovery).^M
Preparing to replace friendly-recovery 0.2.10 (using .../friendly-recovery_0.2.24_all.deb) ...^M
De-configuring upstart ...^M
Unpacking replacement friendly-recovery ...^M
Preparing to replace upstart 0.6.5-8 (using .../upstart_1.4-0ubuntu8_amd64.deb) ...^M
Unpacking replacement upstart ...^M
Processing triggers for ureadahead ...^M
Processing triggers for man-db ...^M
Setting up libnih1 (1.0.3-4ubuntu9) ...^M
Setting up libnih-dbus1 (1.0.3-4ubuntu9) ...^M
Setting up libudev0 (175-0ubuntu5) ...^M
Processing triggers for libc-bin ...^M
ldconfig deferred processing now taking place^M
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M
Preparing to replace ifupdown 0.6.8ubuntu29.2 (using .../ifupdown_0.7~beta2ubuntu6_amd64.deb) ...^M
Transitioning /etc/network/if-up.d/upstart to be a conffile ...^M
Transitioning /etc/init/network-interface.conf to be a conffile ...^M
Transitioning /etc/init/networking.conf to be a conffile ...^M
Transitioning /etc/init/network-interface-security.conf to be a conffile ...^M
Unpacking replacement ifupdown ...^M
Preparing to replace initscripts 2.87dsf-4ubuntu17.5 (using .../initscripts_2.88dsf-13.10ubuntu10_amd64.deb) ...^M
Removing unmodified and obsolete conffile /etc/default/tmpfs ...^M
Unpacking replacement initscripts ...^M
Preparing to replace mountall 2.15.3 (using .../mountall_2.34_amd64.deb) ...^M
Moving obsolete conffile /etc/init/mounted-varrun.conf out of the way...^M
Unpacking replacement mountall ...^M
Processing triggers for ureadahead ...^M
Processing triggers for man-db ...^M
Setting up initramfs-tools-bin (0.99ubuntu10) ...^M
Setting up upstart (1.4-0ubuntu8) ...^M
Installing new version of config file /etc/init/tty3.conf ...^M
Installing new version of config file /etc/init/tty6.conf ...^M
Installing new version of config file /etc/init/tty1.conf ...^M
Installing new version of config file /etc/init/rc-sysinit.conf ...^M
Installing new version of config file /etc/init/rc.conf ...^M
Installing new version of config file /etc/init/rcS.conf ...^M
Installing new version of config file /etc/init/tty2.conf ...^M
Installing new version of config file /etc/init/tty4.conf ...^M
Installing new version of config file /etc/init/tty5.conf ...^M
Installing ne...

[Stéphane Graber (stgraber)]

Subscribing Michael Vogt as I don't have a clear idea of what's happening there (especially as all the other lts-to-lts upgrade tests seem to work fine).

[Stéphane Graber (stgraber)]

Oh, worth noting that I'm running the same apt and update-manager as the reporter (looking at main.log) and that's the latest backported one available in Lucid.

[Steve Langasek (vorlon)]

I don't know why this is not reproducible, but I certainly see a circular relationship that can be contributing to it

  Package: upstart
  Depends: ifupdown (>= 0.6.10ubuntu5) # newer than lucid

  Package: ifupdown
  Depends: upstart-job

  Package: friendly-recovery
  Breaks: upstart (<< 1.3-0ubuntu9)
  Depends: upstart-job, upstart, whiptail

Not sure we can remove the circular dep though, so maybe this just needs to be addressed as an apt ordering bug. The log shows the upgrade being done with update-manager; does that already have the backport of the GSoC ordering fixes?

[Stéphane Graber (stgraber)]

2012-02-20 09:17:27,749 INFO apt version: '0.8.16~exp12ubuntu1~upgrader1'
2012-02-20 09:17:27,749 INFO release-upgrader version '0.156.5' started

Not sure if that version has all the fixes.

[MarcRandolph (mrand)]

When I got this to happen, I did a fresh Mythbuntu 10.04.1 install and did not do the megaload of updates before issuing "do-release-upgrade -d"

[Steve Langasek (vorlon)]

chances are this will not be reproducible with the newest release-upgrader apt that's landed in lucid. Leaving it open in case anyone else runs into it, but marking incomplete.

[PeterPall (peterpall)]

Did update from oneiric. But go the same error.

[S.Toonen (s-toonen)]

Just tried an update from Ubuntu server 10.04 to 12.04 using the "sudo do-release-upgrade -d" command. Got the same error. As a result the installation did not succeed.

[MarcRandolph (mrand)]

Changing back to confirmed for the following reasons:

1) people are still seeing it (and not just on 10.04, apparently)
2) people might not update their 10.04 install before doing the upgrade

[S.Toonen (s-toonen)]

For the record, I did an apt-get update && apt-get upgrade before the release upgrade.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Steve Langasek (vorlon)]

We believe this to be a bug in the package manager, rather than in ifupdown. The circular dependency between ifupdown/upstart/initscripts is not ideal, but the package manager is supposed to be able to handle this.

[Steve Langasek (vorlon)]

this is probably the same bug as bug #1017001.

[Brian Murray (brian-murray)]

Attached is apt clone data from duplicate bug 989436.