[Bug 1846762] Re: automatic creation of casper-rw breaks installation from "disk"

[Mario Limonciello]

#1:

Thanks!  I'll get that added to the default factory install kernel
command line.

Regarding how to find this out sooner, I think some discussions internal
to Canonical OEM services would be a good idea.  Some automation in
continuous integration for daily images doing tests like how factory
install works in a VM seem possible to me.

For other use cases, everything done in initramfs currently is here:
https://github.com/dell/dell-recovery/blob/master/casper/scripts/99dell_bootstrap

Basically images are built with that in the initramfs (or initramfs is
modified to put that inside).

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

Title:
  automatic creation of casper-rw breaks installation from "disk"

Status in casper package in Ubuntu:
  In Progress
Status in casper source package in Eoan:
  In Progress

Bug description:
  OEM factory installation typically puts the Ubuntu media onto a
  recovery partition and uses a preseeding recipe to install into the
  remaining free space on the disk.

  This casper change appears to have broken that behavior:

  casper (1.415) eoan; urgency=medium

    * Persist logs on the install media by default:
      - Try to auto create a casper-rw filesystem on the install media if there
        appears to be at least 100MiB free on it.
      - Use a casper-rw filesystem for /var/log if it is not being used for
        persistence.
    * Fix some '|| continue's that got missed when check_dev got refactored into
      a function.

   -- Michael Hudson-Doyle <michael.hudson at ubuntu.com>  Thu, 08 Aug 2019
  16:26:41 +1200

  In my testing (in QEMU) I can see errors from the installer that no
  free space can be found.  Examining the disk I see that a casper-rw
  partition has been created in the free space taking up the entire
  disk.

  Would you please consider to recognize the "nopersistent" kernel
  command line option already supported by casper to disable this
  behavior?

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