[Bug 1512589] Re: partman-efi should follow partman-auto/disk to reuse the ESP.

[Mathieu Trudel-Lapierre]

Thanks. At first glance this looks correct (though I'll give it a spin
here before sponsoring).

However, we don't ship partman-efi in d-i images, so this doesn't need
to affect debian-installer -- marking those tasks as Invalid.

** Changed in: debian-installer (Ubuntu)
       Status: New => Invalid

** Changed in: debian-installer (Ubuntu Trusty)
       Status: New => Invalid

** Changed in: debian-installer (Ubuntu Wily)
       Status: New => Invalid

** Changed in: partman-efi (Ubuntu)
     Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

** Changed in: partman-efi (Ubuntu)
       Status: Triaged => In Progress

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

Title:
  partman-efi should follow partman-auto/disk to reuse the ESP.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in debian-installer package in Ubuntu:
  Invalid
Status in partman-efi package in Ubuntu:
  In Progress
Status in debian-installer source package in Trusty:
  Invalid
Status in partman-efi source package in Trusty:
  Triaged
Status in debian-installer source package in Wily:
  Invalid
Status in partman-efi source package in Wily:
  Triaged
Status in partman-efi package in Debian:
  New

Bug description:
  [Impact]

   * It may cause the installation failed when the users use
  https://wiki.debian.org/DebianInstaller/Preseed under some conditions.

  [Test Case]

   * Prepare a computer with UEFI secure boot enabled that has two system storage drives, such as /dev/nvme0n1 and /dev/sda.
   * Install the general Ubuntu system on /dev/nvme0n1 first.
   * Use debian-installer netboot images with the following d-i preseeds to install another Ubuntu on /dev/sda.
   * During the installation on /dev/sda, it will use /dev/nvme0n1p1 instead of /dev/sda1 as the EFI System Partition.

  [Regression Potential]

   * None

  [Other Info]

   * This issue is found in Ubuntu OEM projects that used dell-recovery
  /ubuntu-recovery on the platforms that have more than one system
  storage drive.

  ----
     Current implementation in partman-efi/fstab.d/efi is to find the
     first EFI System Partition (abbr. ESP) to use when we provided
     some kind of partman-auto/expert_recipe.

     However if the system has more than two ESPs, partman-efi will still
     use the first ESP it found even when we specify what we want in
     partman-auto/disk.

     For example, when the system has /dev/nvme0n1 and /dev/sda and we
     specified partman-auto/disk and partman-auto/expert_recipe as the following.

         d-i partman-auto/disk string /dev/sda
         d-i partman-auto/expert_recipe string \
                                               \
           ubuntu ::                           \
               100 150 200 free                \
               $iflabel{ gpt }                 \
               $reusemethod{ }                 \
               method{ efi }                   \
               format{ } .                     \
                                               \
               500 10000 4000000 ext4          \
               $primary{ }                     \
               method{ format }                \
               format{ }                       \
               use_filesystem{ }               \
               filesystem{ ext4 }              \
               mountpoint{ / } .               \
                                               \
               105% 150% 200% linux-swap       \
               method{ swap }                  \
               format{ }                       \
               .

     If there is already another Linux system installed in /dev/nvme0n1,
     partman-efi will reuse /dev/nvme0n1p1 and mount it at
     /target/boot/efi instead of reusing /dev/sda1 that we specify in
     partman-auto/disk.

     This should not be the behavior that we expected it will be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1512589/+subscriptions