do-release-upgrade -s -d not possible to create the sandbox environment

Bug #1651569 reported by kfsone
This bug report is a duplicate of:  Bug #1605259: do-release-upgrade --sandbox fails. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
New
Undecided
Unassigned

Bug Description

Fresh ubuntu 16.04 install, virtual machine under VMware, apt-get update && apt-get upgrade have been run, system rebooted.

$ sudo do-release-upgrade -s -d

Checking for a new Ubuntu release
Get:1 Upgrade tool signature [836 B]
Get:2 Upgrade tool [1,260 kB]
Fetched 1,261 kB in 0s (0 B/s)
authenticate 'zesty.tar.gz' against 'zesty.tar.gz.gpg'
extracting 'zesty.tar.gz'

Reading cache

Checking package manager

Sandbox setup failed

It was not possible to create the sandbox environment.

Preparing the upgrade failed

Preparing the system for the upgrade failed so a bug reporting
process is being started.

ubuntu@ubuntuvm:~$ comm: /var/log/dmesg: No such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubuntu-release-upgrader-core 1:16.10.9
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CrashDB: ubuntu
Date: Tue Dec 20 11:54:41 2016
InstallationDate: Installed on 2016-12-20 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to yakkety on 2016-12-20 (0 days ago)

Revision history for this message
kfsone (kfsone) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1605259, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

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.