zesty lvm install hangs while creating device mapper device

Bug #1664731 reported by Joshua Powers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
Invalid
Critical
Mathieu Trudel-Lapierre
Zesty
Invalid
Critical
Mathieu Trudel-Lapierre
os-prober (Debian)
Fix Released
Unknown
os-prober (Ubuntu)
Fix Released
Critical
Mathieu Trudel-Lapierre
Zesty
Fix Released
Critical
Mathieu Trudel-Lapierre

Bug Description

Using the ISO dated 20170214, the install appears to hang while 'Running "update-grub"...'. Changing to console 4 the last message is:

50mounted-tests: debug: creating device mapper device /dev/mapper/osprober-linux-vda1

During a successful install the following messages are printed and the install completes:

50mounted-tests: debug: creating device mapper device /dev/mapper/osprober-linux-sda1
50mounted-tests: debug: mounting /dev/mapper/osprober-linux-sda1 (/dev/sda1) as LVM2_member failed: mount: mounting: /dev/mapper/osprober-linux-sda1 on /var/lib/os-prober/mount failed: No such device
50mounted-tests: debug: remove device mapper device /dev/mapper/osprober-linux-sda1
os-prober: debug: /dev/mapper/ubuntu--vg-swap_1: is active swap

On a recent instance of this I killed the dmsetup job and the install completed successfully. Something during the create is causing the
lockup.

The preseed used is available [1], however you should be able to do a default install using the ppc64el ISO to reproduce this as LVM is now the default. The server LVM ISO tests [2] have been failing consistently on ppc64el and intermittently on i386 and amd64.

[1] https://bazaar.launchpad.net/~ubuntu-server-qa/ubuntu-test-cases/server-tests-raring/view/head:/preseeds/lvm.preseed
[2] https://platform-qa-jenkins.ubuntu.com/view/server/

Revision history for this message
Joshua Powers (powersj) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :
Joshua Powers (powersj)
description: updated
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1664731

tags: added: iso-testing
Joshua Powers (powersj)
description: updated
Revision history for this message
Scott Moser (smoser) wrote :

possibly related we saw issues like this in curtin:
 https://launchpad.net/bugs/1656369

tags: added: zesty
Changed in debian-installer (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Changed in os-prober (Debian):
status: Unknown → Fix Released
Revision history for this message
Joshua Powers (powersj) wrote :

The fix was released in Debian it appears; is there a plan to update the version in Zesty? Anything I can do to help?

Changed in debian-installer (Ubuntu Zesty):
status: New → In Progress
status: In Progress → Invalid
Changed in os-prober (Ubuntu Zesty):
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
milestone: none → ubuntu-17.03
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package os-prober - 1.74ubuntu1

---------------
os-prober (1.74ubuntu1) zesty; urgency=medium

  * Merge from Debian unstable. (LP: #1664731) Remaining changes:
    - Mount btrfs subvolume @ when present to access a btrfs formatted
      rootfs.
    - When called with WINOSDATA, return the list of Windows partitions
      containing the system instead of only listing these containing the
      bootrecord.
    - Sort detected kernels by modification time, if possible.

 -- Mathieu Trudel-Lapierre <email address hidden> Mon, 06 Mar 2017 17:05:41 -0500

Changed in os-prober (Ubuntu Zesty):
status: In Progress → Fix Released
Revision history for this message
Joshua Powers (powersj) wrote :

Just to loop around, I can confirm this fixed all errors :) Thanks!

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.