release upgrade from Trusty to Wily failed due to sysvinit

[Brian Murray]

I was testing a release upgrade from Trusty to Wily, since Vivid will be End of Life-ing soon, and ran into a catastrophic failure. Here is the end of /var/log/dist-upgrade/main.log:

Setting up mount (2.26.2-6ubuntu3) ...^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(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 568301 files and directories currently installed.)^M
Preparing to unpack .../sysv-rc_2.88dsf-59.2ubuntu2_all.deb ...^M
Unpacking sysv-rc (2.88dsf-59.2ubuntu2) over (2.88dsf-41ubuntu6.2) ...^M
Preparing to unpack .../insserv_1.14.0-5ubuntu3_amd64.deb ...^M
Unpacking insserv (1.14.0-5ubuntu3) over (1.14.0-5ubuntu2) ...^M
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...^M
Setting up insserv (1.14.0-5ubuntu3) ...^M
Setting up sysv-rc (2.88dsf-59.2ubuntu2) ...^M
info: Reordering boot system, log to /var/lib/insserv/run-20160122T1444.log^M
error: Something failed while migrating.^M
^M
error: Unable to migrate to dependency based boot sequencing.^M
^M
See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for^M
more information about dependency based boot sequencing. To^M
reattempt the migration process run 'dpkg --configure sysv-rc'.^M
^M
dpkg: error processing package sysv-rc (--configure):^M
 subprocess installed post-installation script returned error exit status 1^M
Log ended: 2016-01-22 14:44:09

/var/lib/insserver/run-blahdeblah contained the following:

/var/lib/dpkg/info/sysv-rc.postinst: 60: /var/lib/dpkg/info/sysv-rc.postinst: insserv: not found

[Martin Pitt (pitti)]

Can you please attach the complete /var/log/dist-upgrade/main.log, so that I can see in which order things got upgraded and configured? Thanks!

[Brian Murray (brian-murray)]

On Mon, Jan 25, 2016 at 09:10:03PM -0000, Martin Pitt wrote:
> Can you please attach the complete /var/log/dist-upgrade/main.log, so
> that I can see in which order things got upgraded and configured?
> Thanks!

apport told me the bug was a duplicate of 1507151, which has a solution,
that I'll SRU to wily.

--
Brian Murray