** Also affects: auto-upgrade-testing
Importance: Undecided
Status: New
** Changed in: auto-upgrade-testing
Status: New = In Progress
** Changed in: auto-upgrade-testing
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a
** Branch linked: lp:auto-upgrade-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage notifications about this bug
I applied a workaround for trusty in http://bazaar.launchpad.net/~auto-
upgrade-testing-dev/auto-upgrade-testing/trunk/revision/92 . Not pretty,
but it'll do.
** Changed in: auto-upgrade-testing
Status: In Progress = Fix Released
--
You received this bug notification because you are a
Err, I meant for quantal, not for trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage notifications about this bug
For the record, this hasn't fully been fixed in Quantal: Quantal's
/etc/kernel/postinst.d/zz-update-grub does NOT have the container check
as introduced in precise's grub2 (1.99-21ubuntu3.9) SRU. This breaks
upgrades from quantal to saucy in containers:
** Changed in: lxc (Ubuntu Precise)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage
This bug was fixed in the package grub2 - 1.99-21ubuntu3.9
---
grub2 (1.99-21ubuntu3.9) precise; urgency=low
* Also skip update-grub when running in a container (LP: #1060404).
-- Colin Watson cjwat...@ubuntu.com Tue, 22 Jan 2013 14:43:32 +
** Changed in: grub2 (Ubuntu
** Branch linked: lp:ubuntu/precise-updates/grub2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage notifications about
The posted fix works for me too: running Juju on Raring with precise
charms using juju-origin: proposed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage
Ran into this bug trying out juju, the posted fix for precise
(1.99-21ubuntu3.9) works for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails
On Tue, Jan 22, 2013 at 03:32:12AM -, Sebastian Hoffmann wrote:
I can't reproduce fix on precise. I've used ppa:juju/0.6 (r608), grub-pc
is ubuntu3.8, juju-origin: proposed, but I still get the same error.
Can I please have a transcript of the error you're seeing? There are
(at least) two
I installed the version from precise-updates on a precise lxc, which didn't
have grub-pc before. It worked for me. Here is the output:
(...)
Processing triggers for ureadahead ...
Setting up libfreetype6 (2.4.8-1ubuntu2.1) ...
Setting up gettext-base (0.18.1.1-5ubuntu3) ...
Setting up libfuse2
Andreas: Thanks. I already noticed the running-in-container output and
fixed it in Debian experimental (which will be merged into raring at
some point); it probably isn't worth revising precise for in the absence
of another pressing need to touch those lines of code, though.
--
You received
Agreed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage notifications about this bug go to:
Output when NOT running on LXC (a linode machine in this case):
(...)
Preparing to replace grub-pc 1.99-21ubuntu3.7 (using
.../grub-pc_1.99-21ubuntu3.8_i386.deb) ...
Unpacking replacement grub-pc ...
Preparing to replace grub-pc-bin 1.99-21ubuntu3.7 (using
Hello Serge, or anyone else affected,
Accepted grub2 into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/grub2/1.99-21ubuntu3.9
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I can confirm this fix working on precise for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage notifications about
** Branch linked: lp:debian/experimental/grub2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage notifications about
I can't reproduce fix on precise. I've used ppa:juju/0.6 (r608), grub-pc
is ubuntu3.8, juju-origin: proposed, but I still get the same error.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Confirmed in precise, thanks.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and
Hello Serge, or anyone else affected,
Accepted grub2 into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/grub2/1.99-21ubuntu3.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/grub2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage notifications about
What is the work-around that I might be missing? Trying out juju with
LXC by following https://juju.ubuntu.com/docs/getting-started.html will
make you run directly into this bug. Quite a let-down as everything else
runs so smoothly with juju ...
--
You received this bug notification because you
@Henning,
At one point we thought a workaround was to have devtmpfs mounted in the
container. However that is a bad thing to do as changes in the
container's /dev will be reflected in the host's /dev.
So the only workaround right now (until grub is fixed in precise) is to
check (with 'mount')
Any idea if this will be fixed for precise, or is it too risky?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage
** Description changed:
- ==
- SRU justification for lxc part:
- 1. Impact: update-grub fails, causing apt-get updates to fail if there is a
new kernel.
- 2. Development fix: modify ubuntu templates to mount devtmpfs before starting
container
- 3. Stable fix: same as
@Andreas,
it needs to be fixed in grub. However the fix in raring should be
SRUable.
** Changed in: grub2 (Ubuntu Precise)
Importance: Undecided = High
** No longer affects: upstart (Ubuntu)
** No longer affects: upstart (Ubuntu Precise)
** No longer affects: upstart (Ubuntu Quantal)
--
Right, grub, and for now my workaround is to remove grub-pc if I'm in a
container.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in
** Description changed:
+ [Impact] GRUB upgrades fail in containers.
+ [Test Case] Upgrade the grub-pc package in a container.
+ [Regression Potential] In itself, this postinst fix should be quite safe.
It's possible it won't solve the whole problem - e.g. linux-image-* upgrades
calling
** Branch linked: lp:~ubuntu-core-dev/ubuntu/precise/grub2/precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage
** Branch linked: lp:ubuntu/lxc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Branch linked: lp:~cjwatson/ubuntu/quantal/grub2/2.00
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage notifications
This bug was fixed in the package grub2 - 2.00-7ubuntu3
---
grub2 (2.00-7ubuntu3) quantal; urgency=low
* If the postinst is running in a container, skip grub-install and all its
associated questions (LP: #1060404).
* Merge UEFI secure boot tweaks from Fedora:
- Don't
** Branch linked: lp:ubuntu/grub2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1060404
Title:
update-grub runs and fails in containers
To manage notifications about this bug go to:
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Also affects: grub2 (Ubuntu Quantal)
Importance: High
Assignee: Colin Watson (cjwatson)
Status: Fix Committed
** Also
** Also affects: grub2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu Precise)
** Description changed:
- If grub is installed in a container (as happens, for instance, with the
- ubuntu-cloud template) then an update of grub or linux-image will cause
- update-grub to be run. It tries, finds it can't access the root device,
- fails, and causes the update to fail.
+
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
After talking to cjwatson on irc, there is another option. update-grub
is failing because /dev/disk/ is not set up in the container. So we
could add an upstart job which runs only in containers, and manually
sets up /dev/disk/. This also might help other software which relies on
/dev/disk/.
As hrw pointed out on #ubuntu-devel, a third option is to simply add
devtmpfsdev devtmpfs defaults 0 0
to /var/lib/lxc/$c/fstab
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I've pushed a patch to ubuntu:lxc which will cause devtmpfs to be
mounted in ubuntu containers.
There remains the problem that grub-install then queries the user about
installing grub on /dev/vda1 (or whatever is hosting the container fs).
** Changed in: upstart (Ubuntu)
Status: New =
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu37
---
lxc (0.8.0~rc1-4ubuntu37) quantal; urgency=low
* update 0222-debian-dhcp3-package: use dhcp3-client, not server!
* 0224-ubuntu-templates-devtmpfs: mount devtmpfs in ubuntu containers.
(LP: #1060404)
-- Serge
45 matches
Mail list logo
