[Bug 1099349] Please test proposed package

[Colin Watson]

Hello Michael, or anyone else affected,

Accepted mountall into quantal-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/mountall/2.42ubuntu0.4 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1099349

Title:
  mountall 2.36.3 hangs in recovery-menu (lvm; mountall 2.36 has no
  issue)

Status in “mountall” package in Ubuntu:
  Fix Released
Status in “mountall” source package in Precise:
  Fix Committed
Status in “mountall” source package in Quantal:
  Fix Committed
Status in “mountall” source package in Raring:
  Fix Released

Bug description:
  [Impact]
  Following the mountall SRUs for bug #643289, mountall --no-events does not work correctly; the lack of events causes mountall to not finish.  This breaks the recovery mode, which invokes mountall --no-events.

  [Test case]
  1. Boot Ubuntu using the 'recovery mode' option.
  2. Choose the 'Enable networking' option.
  3. Observe that mountall hangs.
  4. Reboot and install mountall from -proposed.
  5. Boot Ubuntu using the 'recovery mode' option.
  6. Choose the 'Enable networking' option.
  7. Confirm that mountall no longer hangs.

  [Regression potential]
  Minimal; the code changes should only have any effect when mountall is called with --no-events, which is only done in the recovery menu, and that's currently broken.

  
  Fresh Ubuntu 12.04.1 amd64 install with the following partition layout / lvm setup:
  $ lsblk
  NAME                            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  sr0                              11:0    1  1024M  0 rom
  sda                               8:0    0    20G  0 disk
  ├─sda1                            8:1    0   243M  0 part /boot
  ├─sda2                            8:2    0     1K  0 part
  └─sda5                            8:5    0  19.8G  0 part
    ├─u1204--64-swap_1 (dm-0)     252:0    0  1020M  0 lvm  [SWAP]
    ├─u1204--64-root (dm-1)       252:1    0   7.6G  0 lvm  /
    └─u1204--64-usr--local (dm-2) 252:2    0  11.1G  0 lvm  /usr/local

  The installation works as expected and there are no imminent issues during normal usage.
  The issue is with the recovery menu. If someone boots into a rescue entry in the boot menu the rescue menu appears as expected but all entries that remount the root volume rw will hang on mountall.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1099349/+subscriptions