do-release-upgrade left machine in unrebootable state
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-
ProcVersionSign
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
PackageArchitec
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-
UpgradeStatus: Upgraded to xenial on 2016-08-01 (0 days ago)
Changed in ubuntu-release-upgrader (Ubuntu): | |
importance: | Undecided → High |
tags: | added: trusty2xenial |
Status changed to 'Confirmed' because the bug affects multiple users.