UTAH doesn't notice installation failure

Bug #1126115 reported by Jean-Baptiste Lallement
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UTAH
Fix Released
High
Javier Collado

Bug Description

http://10.97.0.1:8080/job/ps-indicators-autopilot-release-testing/131/label=autopilot-ati/

success_command failed to install a package (error in installer_syslog.log attached) but UTAH continued as if nothing happened and of course the test setup failed on reboot because the package database was inconsistent

Tags: ue-desktop

Related branches

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
Revision history for this message
Javier Collado (javier.collado) wrote :

@Jean Baptiste
Please could you point to the line where the package installation failed?

I see a couple of lines pointed out by Didier this morning:
Feb 15 08:37:16 ubuntu ubiquity: Failed to symbolic-link /boot/initrd.img-3.8.0-6-generic to initrd.img:File exists at /var/lib/dpkg/info/linux-image-3.8.0-6-generic.postinst line 614.
Feb 15 08:42:13 ubuntu in-target: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1

After that, I see some packages installed and a problem that seems to come from the late command:
Feb 15 08:44:57 ubuntu ubiquity: sh: 1: cannot create /home/jenkins/installer_log.log: Directory nonexistent

and some other error that is repeated quite a lot of times:
Feb 15 08:45:16 ubuntu ubiquity: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

However, I'm in doubt when trying to decide which is the definitive line that
is causing the real problem in which UTAH should stop. Please let me know.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Starting at line 2066 in the file attached:
Feb 15 08:41:59 ubuntu in-target: Setting up linux-image-3.8.0-6-generic (3.8.0-6.13) ...
Feb 15 08:42:00 ubuntu in-target: Running depmod.
Feb 15 08:42:00 ubuntu in-target: update-initramfs: deferring update (hook will be called later)
Feb 15 08:42:00 ubuntu in-target: Not updating initrd symbolic links since we are being updated/reinstalled
Feb 15 08:42:00 ubuntu in-target: (3.8.0-6.11 was configured last, according to dpkg)
Feb 15 08:42:00 ubuntu in-target: Not updating image symbolic links since we are being updated/reinstalled
Feb 15 08:42:00 ubuntu in-target: (3.8.0-6.11 was configured last, according to dpkg)
Feb 15 08:42:00 ubuntu in-target: Examining /etc/kernel/postinst.d.
Feb 15 08:42:00 ubuntu in-target: run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.8.0-6-generic /boot/vmlinuz-3.8.0-6-generic
Feb 15 08:42:00 ubuntu in-target: run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.8.0-6-generic /boot/vmlinuz-3.8.0-6-generic
Feb 15 08:42:00 ubuntu in-target:
Feb 15 08:42:00 ubuntu in-target: update-initramfs: Generating /boot/initrd.img-3.8.0-6-generic
Feb 15 08:42:13 ubuntu in-target: run-parts: executing /etc/kernel/postinst.d/pm-utils 3.8.0-6-generic /boot/vmlinuz-3.8.0-6-generic
Feb 15 08:42:13 ubuntu in-target: run-parts: executing /etc/kernel/postinst.d/update-notifier 3.8.0-6-generic /boot/vmlinuz-3.8.0-6-generic
Feb 15 08:42:13 ubuntu in-target: run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.8.0-6-generic /boot/vmlinuz-3.8.0-6-generic
Feb 15 08:42:13 ubuntu in-target: /usr/sbin/grub-probe: error: failed to get canonical path of /dev/sda1.
Feb 15 08:42:13 ubuntu in-target: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Feb 15 08:42:13 ubuntu in-target: Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.8.0-6-generic.postinst line 1010.
Feb 15 08:42:13 ubuntu in-target: dpkg: error processing linux-image-3.8.0-6-generic (--configure):
Feb 15 08:42:13 ubuntu in-target: subprocess installed post-installation script returned error exit status 2

Changed in utah:
importance: Undecided → High
status: New → In Progress
assignee: nobody → Javier Collado (javier.collado)
Revision history for this message
Javier Collado (javier.collado) wrote :

Success command is now wrapped in a separate script that uses the -e flag to
exit on any command error. The return code from that script is checked and a
message is written to syslog and /var/log/utah-install to make clear that a
success command failure has been detected.

I haven't been able to reproduce exactly the same problem as in the bug
description, but I'm going to mark the bug as fix committed since any kind of
problem should be detected assuming that apt-get returns a failure code.

Please reopen if the assumption turns out to be false.

Changed in utah:
status: In Progress → Fix Committed
Changed in utah:
status: Fix Committed → Fix Released
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.