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

[Mathieu Trudel-Lapierre]

I've been testing this in qemu, with two different virtual machines
(built with the same default settings), one doing Scenario 1, then
Scenario 2, one the other way around.

I'm using the same preseed; with the exception that "d-i partman-
auto/choose_recipe select boot-crypto" is commented out (it shouldn't be
necessary, but I also testing without commenting it), and using /dev/vda
rather than /dev/sda as a target device.

I'm unable to get precisely the message "No modifications can be made to
the device Encrypted volume (sda5_crypt) for the following reasons: In
use by LVM volume group ubuntu-vg." when installing with scenario 2 if I
follow your steps precisely. I do get a message about creating the key
file, followed by a "An error occurred while configuring encrypted
volumes. The configuration has been aborted.". I am then left at the
partman dialog. In indeed appears to happen independently of any
previous installation artefacts on the disk.

However, if I re-run the same installer step for Scenario 2 (ie. fully
automated), but with the addition of "automatic-ubiquity" which behaves
the same as passing --automatic to ubiquity in Scenario 1, then the
installation completes successfully.

Could you please try again, with adding 'automatic-ubiquity' for
scenario 2; and report here whether it solves the problem?

Thanks!

** Changed in: ubiquity (Ubuntu)
       Status: New => Incomplete

** Changed in: ubiquity (Ubuntu)
   Importance: Undecided => Low

-- 
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:
  Incomplete

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