Ubuntu
linux package

precise → saucy upgrade fails: /usr/sbin/grub-probe: error: failed to get canonical path of none.

Bug #1279658 reported by Martin Pitt
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

In our quantal to saucy test upgrades, configuring the kernel fails as follows:

Setting up linux-image-3.11.0-15-generic (3.11.0-15.25) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.11.0-15-generic /boot/vmlinuz-3.11.0-15-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.11.0-15-generic /boot/vmlinuz-3.11.0-15-generic
update-initramfs: Generating /boot/initrd.img-3.11.0-15-generic
cryptsetup: WARNING: could not determine root device from /etc/fstab
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.11.0-15-generic /boot/vmlinuz-3.11.0-15-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.11.0-15-generic /boot/vmlinuz-3.11.0-15-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.11.0-15-generic /boot/vmlinuz-3.11.0-15-generic
/usr/sbin/grub-probe: error: failed to get canonical path of none.
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.11.0-15-generic.postinst line 1010.
dpkg: error processing linux-image-3.11.0-15-generic (--configure):
 subprocess installed post-installation script returned error exit status 2

Full logs are at https://jenkins.qa.ubuntu.com/job/upgrade-ubuntu-quantal-saucy-desktop-amd64/27/ in particular the apt log: http://d-jenkins.ubuntu-ci:8080/view/Upgrade/job/upgrade-ubuntu-quantal-saucy-desktop-amd64/27/artifact/results/apt-term.log

Revision history for this message
Martin Pitt (pitti) wrote :

This test runs in LXC, but I haven't seen it in any of the upgrades to trusty yet (which use the same mechanics in terms of LXC and calling do-release-upgrade, etc.). But still, at this point it could very well be a flaw in our test machinery as well, so I don't set to "triaged" yet and don't assign a priority.

Revision history for this message
Martin Pitt (pitti) wrote :

the i386 and all quantal-saucy-server-* tests fail with the exact same reason, e. g.

https://jenkins.qa.ubuntu.com/job/upgrade-ubuntu-quantal-saucy-desktop-i386/25/artifact/results/apt-term.log
https://jenkins.qa.ubuntu.com/job/upgrade-ubuntu-quantal-saucy-server-tasks-i386/25/

older tests fail in the same way, e. g.

https://jenkins.qa.ubuntu.com/job/upgrade-ubuntu-quantal-saucy-server-tasks-i386/19/

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1279658

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: saucy
Martin Pitt (pitti)
tags: added: bot-stop-nagging
Changed in linux (Ubuntu):
status: Incomplete → New
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Martin Pitt (pitti) wrote :

This already happens in quantal proper, in the pristine container:

$ sudo /etc/kernel/postinst.d/zz-update-grub 3.5.0-45-generic /boot/vmlinuz-3.5.0-45-generic
/usr/sbin/grub-probe: error: failed to get canonical path of none.

The installed version of /etc/kernel/postinst.d/zz-update-grub does not have the running-in-container check, unlike the one I get in precise and trusty:

$ dpkg -S /etc/kernel/postinst.d/zz-update-grub
grub-pc: /etc/kernel/postinst.d/zz-update-grub

grub-pc is version 2.00-7ubuntu11. I see that the container check was added in a precise SRU in bug 1060404, so this is really a duplicate of that bug.

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

Other bug subscribers

Remote bug watches

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