[Bug 1386153] Re: Inconsistent behaviour between 2 ways of launching Ubiquity

[Colin Watson]

I *think* that this has not much to do with the different ways you're
launching ubiquity - the debug log shows that the preseed file has
definitely been applied successfully by casper - and a lot to do with
the second scenario having been run after the first on a disk that's no
longer blank.  lvm2's udev rules are going to have brought up all the
LVM volumes they can find on the system, and nothing in ubiquity takes
care to bring them down again before partitioning.  (Of course it's also
possible that there's some kind of race that means the two ways of
starting ubiquity behave a bit differently, but it doesn't look like
anything very fundamental.)

Try something like this as a workaround?

  d-i partman/early_command string vgchange -a n

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

Title:
  Inconsistent behaviour between 2 ways of launching Ubiquity

Status in ubiquity package in Ubuntu:
  New

Bug description:
  I need to perform a partially automated installation of a desktop
  Ubuntu trusty. The partitioning part should be fully automated
  creating a entire-disk encrypted lvm.

  While debugging my preseeding script I have encountered an inconsisted
  behaviour of ubiquity.

  In both cases I use the same image of desktop CD with a preseed file
  added to the CD.

  Scenario 1:
  1. Launch desktop live CD
  2. Select "Try Ubuntu"
  3. Load my preseed file with:
  # debconf-set-selections /cdrom/preseed/ubuntu2.seed
  4. Start ubiquity:
  # ubiquity -d --automatic
  5. Select language
  6. Continue after the internet connection check and drive space check.

  With Secnario 1 everything works fine - the partitioning is fully
  automated.

  Scenario 2:
  1. Boot a customized entry in isolinux/txt.cfg passing the preseed file in the kernel command line
  label live-install-test
    menu label ^Install Ubuntu (test)
    kernel /casper/vmlinuz.efi
    append debug-ubiquity file=/cdrom/preseed/ubuntu2.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash
  2. Select language
  3. Continue after the internet connection check and drive space check.

  With Scenario 2 I'm getting an error dialog:
  "No modifications can be made to the device Encrypted volume (sda5_crypt) for the following reasons: In use by LVM volume group ubuntu-vg."

  Please find the provided preseed files and the logs from the failing
  case.

  Note: this contains a patch included in #1386113 to get pass the
  keyfile generation error.

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