do-release-upgrade --sandbox fails ("submount of systemdir")
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Binary package hint: update-manager
after bug 562394 was reported fix, I decided to test it.
I ran:
$ sudo do-release-upgrade -d --sandbox
It promted me with:
Continue running under SSH?
I said "No". Then, started a screen session, and ran again.
The second run dies with:
Sandbox setup failed
It was not possible to create the sandbox environment.
Preparing the upgrade failed
Preparing the system for the upgrade failed. Please report this as a
bug against the 'update-manager' package and include the files in
/var/log/
----
/var/log/
2010-04-15 17:34:00,915 WARNING mountpoint /var/cache/
If I do 'sudo umount /var/cache/
Note, after the cancel there are still several aufs mounts and such left around, but they dont seem to prevent re-running as the /var/cache/
ProblemType: Bug
Architecture: i386
Date: Thu Apr 15 17:20:59 2010
DistroRelease: Ubuntu 9.10
Ec2AMI: ami-bb709dd2
Ec2AMIManifest: ubuntu-
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: aki-5f15f636
Ec2Ramdisk: ari-d5709dbc
Package: update-manager-core 1:0.126.9
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: update-manager
Tags: ec2-images
Uname: Linux 2.6.31-302-ec2 i686
Changed in update-manager (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
summary: |
- do-release-upgrade --sandbox fails after cancelling + do-release-upgrade --sandbox fails ("submount of systemdir") |
I ran into the same issue today, having bind-mounted /var/cache/ apt/archives to a temporary storage for the upgrade. During day-to- day-operation my /var partition is limited to 2G. Why is bind-mounting an issue here?