do-release-upgrade left machine in unrebootable state

Bug #1608689 reported by Dean Henrichsmeyer
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Confirmed
High
Unassigned

Bug Description

I performed a do-release-upgrade on a digital ocean droplet running trusty. The end result was a system in which systemd wasn't running but every tool thought it was. Can't reboot, etc.

I get error messages such as:

<root@valor>:~# /sbin/reboot
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.
Couldn't find an alternative telinit implementation to spawn.
failed to run telinit 6 for upstart fallback
Failed to talk to init daemon.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.14
ProcVersionSignature: Ubuntu 3.2.0-23.36-virtual 3.2.14
Uname: Linux 3.2.0-23-virtual x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: ubuntu
Date: Mon Aug 1 15:51:34 2016
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2016-08-01 (0 days ago)

Revision history for this message
Dean Henrichsmeyer (dean) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
Revision history for this message
Ralf Heiringhoff (frosty-geek) wrote : apport information

ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: ubuntu
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader (not installed)
ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
Tags: xenial dist-upgrade
Uname: Linux 3.13.0-91-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-08-03 (0 days ago)
UserGroups:

VarLogDistupgradeLspcitxt:

_MarkForUpload: True

tags: added: apport-collected
Revision history for this message
Ralf Heiringhoff (frosty-geek) wrote : CurrentDmesg.txt.txt

apport information

Revision history for this message
Ralf Heiringhoff (frosty-geek) wrote : ProcEnviron.txt

apport information

Revision history for this message
Ralf Heiringhoff (frosty-geek) wrote : VarLogDistupgradeAptHistorylog.txt

apport information

Revision history for this message
Ralf Heiringhoff (frosty-geek) wrote : VarLogDistupgradeAptclonesystemstate.tar.gz

apport information

Revision history for this message
Ralf Heiringhoff (frosty-geek) wrote : VarLogDistupgradeAptlog.txt

apport information

Revision history for this message
Ralf Heiringhoff (frosty-geek) wrote : VarLogDistupgradeApttermlog.txt

apport information

Revision history for this message
Ralf Heiringhoff (frosty-geek) wrote : VarLogDistupgradeMainlog.txt

apport information

Revision history for this message
Ralf Heiringhoff (frosty-geek) wrote : VarLogDistupgradeScreenlog.txt

apport information

Revision history for this message
Dean Henrichsmeyer (dean) wrote :

To close the loop here - /sbin/reboot -f did reboot the system and it came back in a perfectly working, systemd enabled system. It was definitely a broken user experience though.

Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → High
Revision history for this message
molosser (molosser) wrote :

After finishing upgrading and before restarting, I choone N and then typed /sbin/reboot -f on the terminal but still it doesn't work.

tags: added: trusty2xenial
Revision history for this message
Pavel Piatruk (piatruk-p) wrote :

Make sure upstart package is installed before you issue reboot. Then remove upstart package after 1st boot. That worked for me.

Revision history for this message
kokoye2007  (kokoye2007) wrote :

Yes
after install upstart
init 6 or reboot is working

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.