Saucy -> Trusty upgrade failed: procps fails to configure

This is the message displayed at the very end.

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1347721

It does boot, looks like Trusty running a Saucy kernel:

lance@lance-desktop:~$ uname -a
Linux lance-desktop 3.11.0-26-generic #45-Ubuntu SMP Tue Jul 15 04:04:15 UTC 2014 i686 i686 i686 GNU/Linux
lance@lance-desktop:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty

I found that it did not reboot as expected at the end, but when rebooted the system as found was upgraded and viable. Both on 32 and 64 bit.

I'm trying to figure out an unrelated release-upgrade bug and stumbled upon bug #1310411 where the kernel did not upgrade - possible duplicate?

Error from term.log

Setting up libprocps3:i386 (1:3.3.9-1ubuntu2) ...
dpkg: dependency problems prevent configuration of procps:
 procps depends on initscripts; however:
  Package initscripts is not configured yet.

dpkg: error processing package procps (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of udev:
 udev depends on procps; however:
  Package procps is not configured yet.

dpkg: error processing package udev (--configure):
 dependency problems - leaving unconfigured

Also reproduced in the lab:
https://jenkins.qa.ubuntu.com/view/Upgrade/job/upgrade-ubuntu-saucy-trusty-desktop-amd64/140/

The jenkins log shows packages being configured out of order:

Preparing to unpack .../initscripts_2.88dsf-41ubuntu6_amd64.deb ...
Unpacking initscripts (2.88dsf-41ubuntu6) over (2.88dsf-41ubuntu3) ...
[...]
dpkg: dependency problems prevent configuration of procps:
 procps depends on initscripts; however:
  Package initscripts is not configured yet.

dpkg: error processing package procps (--configure):
 dependency problems - leaving unconfigured
[...]

So this probably points to an apt bug. Michael, can you take a look?

I just tried to reproduce it locally without much success, I try again tomorrow.

It seems like the issue is the following:

There is a dependency loop mountall->udev->procps->initscripts->mountall. When apt tries to deal with it, it configures them all initially together, then it finds the "libplymouth4" dependency of mountall that is not unpacked yet and inserts the unpack at this point wich breaks the condition that all packages in the loop need to be unpacked at the same time.

        Unpacking mountall:i386 to avoid loop initscripts:i386 Depends on mountall [ i386 ] < 2.53 -> 2.54build1 > ( admin ) (>= 2.28)
          SmartUnPack mountall:i386 (replace version 2.53 with 2.54build1) immediately
          PreDepends order for mountall:i386
          Found ok package dpkg:i386
            SmartConfigure mountall:i386 (2.54build1)
            Unpacking udev:i386 to avoid loop mountall:i386 Depends on udev [ i386 ] < 204-10ubuntu1 -> 208-6ubuntu2 > ( admin )
              SmartUnPack udev:i386 (replace version 204-10ubuntu1 with 208-6ubuntu2) immediately
              PreDepends order for udev:i386
              Found ok package debconf:i386
                SmartConfigure udev:i386 (208-6ubuntu2)
                Unpacking procps:i386 to avoid loop udev:i386 Depends on procps [ i386 ] < 1:3.3.9-1ubuntu2 -> 1:3.3.9-1ubuntu5 > ( admin )
                  SmartUnPack procps:i386 (replace version 1:3.3.9-1ubuntu2 with 1:3.3.9-1ubuntu5) immediately
                    SmartConfigure procps:i386 (1:3.3.9-1ubuntu5)
                    Unpacking libprocps3:i386 to avoid loop procps:i386 Depends on libprocps3 [ i386 ] < 1:3.3.9-1ubuntu2 -> 1:3.3.9-1ubuntu5 > ( libs )
                      SmartUnPack libprocps3:i386 (replace version 1:3.3.9-1ubuntu2 with 1:3.3.9-1ubuntu5) immediately
                      PreDepends order for libprocps3:i386
                      Found ok package multiarch-support:i386
                        SmartConfigure libprocps3:i386 (1:3.3.9-1ubuntu5)
                    Configure already unpacked initscripts [ i386 ] < 2.88dsf-41ubuntu6 -> 2.88dsf-41ubuntu16 > ( admin )
                      SmartConfigure initscripts:i386 (2.88dsf-41ubuntu16) (Only Correct Dependencies)
                    Configure already unpacked initscripts [ i386 ] < 2.88dsf-41ubuntu6 -> 2.88dsf-41ubuntu16 > ( admin )
                      SmartConfigure initscripts:i386 (2.88dsf-41ubuntu16) (Only Correct Dependencies)
            Unpacking libplymouth4:i386 to avoid loop mountall:i386 Depends on libplymouth4 [ i386 ] < none -> 0.9.0-0ubuntu2 > ( libs ) (>= 0.8.1-3)
              SmartUnPack libplymouth4:i386 (install version 0.9.0-0ubuntu2) immediately
              PreDepends order for libplymouth4:i386
              Found ok package multiarch-support:i386
                SmartConfigure libplymouth4:i386 (0.9.0-0ubuntu2)

I bisected this now (as the precise apt did not trigger the bug in the chroot) and it it appears to be caused by: 42d51f333e8ef522fed02cdfc48663488d56c3a3

And I just verified that the commit before the offending one (66706285) fully works and upgrades the system correctly. The immediate-configure property is also better honored.

This diff works for me:

diff --git a/apt-pkg/packagemanager.cc b/apt-pkg/packagemanager.cc
index 393f836..57d4b5a 100644
--- a/apt-pkg/packagemanager.cc
+++ b/apt-pkg/packagemanager.cc
@@ -406,6 +406,12 @@ bool pkgPackageManager::SmartConfigure(PkgIterator Pkg, int
               if (Cache[DepPkg].InstallVer != *I || List->IsNow(DepPkg) == fals
                  continue;

+ // only packages that are in the unpacked state may need
+ // configure so ignore anything that is not currently
+ // unpacked
+ if (List->IsFlag(DepPkg,pkgOrderList::UnPacked) == false)
+ continue;
+
               if (PkgLoop == true)
               {
                  if (Debug)
---

Hm, now that saucy is closed, how can I upload a updated apt into saucy-updates that contains the fix?

Some more work is needed fo the patch, its eliminating too many case. But the direction is there, the SmartConfigure() is currently trying to configure too much too early when its not really needed.

A improved version of the patch, I tested it with:

- precise build chroot -> trusty
- saucy build chroot -> trusty
- trusty build chroot -> utopic (2014-07-29)

and it worked for those cases correctly.

The bug was that apt tried to SmartUnPack packages that were dependencies but did not need action just yet (i.e. where the dependencies of the installed version are fine now and the unpack/configure of the updated version would be hapen in a later stages of the ordering).

I also did a precise->trusty->utopic upgrade cycle with the patch (the precise base that triggered #1347964 before) and again all good.

This bug was fixed in the package apt - 1.0.4ubuntu6

---------------
apt (1.0.4ubuntu6) utopic; urgency=low

  * apt-pkg/packagemanager.cc:
    - fix incorrect configure ordering in the SmartConfigure step
      by skiping packages that do not need immediate action
      (LP: #1347721)
 -- Michael Vogt <email address hidden> Tue, 29 Jul 2014 11:46:18 +0200

For those of us who have been affected by the bug, it would be good to have guidance on whether we need to do a clean install of 14.04 or if there's some other action that should be taken. As some others have reported, my system seems to be working properly, but would like to know if there's some inconsistency I'm not seeing.

@Jim - its hard to know with our more information from you. Did you upgrade from 12.04 or from 13.10? How did you go about working around the upgrade failure?

Hello Erick, or anyone else affected,

Accepted apt into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/apt/0.9.9.1~ubuntu3.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

@Brian - I updated from 13.10. All I did to recover was wait for the aborted upgrade to complete or recover, and rebooted my system, and it claims to be running 14.04 now. The only thing that seemed potentially funny was a message, "error: diskfilter writes are not supported" when I booted it. Someone (I think in one of the duplicate bugs) mentioned that rebooting was successful on both 32-bit and 64-bit processors.

@Adam - would love to test it but I no longer have a Saucy system to test it on unless I need to restore from backup, which I'm hoping isn't necessary.

@Adam, I'm installing Saucy now - will follow up ASAP.

@Jim, be sure to check and see what kernel you're now running via uname -r as I did in comment #4. As best I recall I seemed to be able to recover simply by running update-grub and apt-get -f install (and following suggestions provided by -f install), possibly a few times until things appeared to resolve. But I was using a test installation that was long since erased.

Installed and updated Saucy, enabled proposed, and ran apt-get install apt:

Start-Date: 2014-08-11 23:15:49
Commandline: apt-get install apt
Upgrade: apt:i386 (0.9.9.1~ubuntu3.2, 0.9.9.1~ubuntu3.3), libapt-pkg4.12:i386 (0.9.9.1~ubuntu3.2, 0.9.9.1~ubuntu3.3)
End-Date: 2014-08-11 23:16:02

Then disabled proposed, refreshed the cache using update-manager and was offered the upgrade via GUI so I proceeded and all went perfectly so I'm marking this verification-done.

Many thanks.

This bug was fixed in the package apt - 0.9.9.1~ubuntu3.3

---------------
apt (0.9.9.1~ubuntu3.3) saucy-proposed; urgency=low

  * apt-pkg/packagemanager.cc:
    - fix incorrect configure ordering in the SmartConfigure step
      by skiping packages that do not need immediate action
      (LP: #1347721)
 -- Michael Vogt <email address hidden> Tue, 29 Jul 2014 21:37:01 +0200

The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This was never fixed in Trusty and has manifested itself as bug 1497688 when upgrading to Vivid. The test case for fixing this exists in the other bug.

Hello Erick, or anyone else affected,

Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.11 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Verification done via the other bug report.

This bug was fixed in the package apt - 1.0.1ubuntu2.11

---------------
apt (1.0.1ubuntu2.11) trusty; urgency=medium

  * apt-pkg/packagemanager.cc:
    - fix incorrect configure ordering in the SmartConfigure step by skipping
      packages that do not need immediate action. (LP: #1347721, #1497688)

 -- Brian Murray <email address hidden> Fri, 08 Jan 2016 16:09:22 -0800