automatic creation of casper-rw breaks installation from "disk"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
casper (Ubuntu) |
Fix Released
|
Critical
|
Michael Hudson-Doyle | ||
Eoan |
Fix Released
|
Critical
|
Michael Hudson-Doyle |
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 <email address hidden> 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?
Changed in casper (Ubuntu): | |
assignee: | nobody → Michael Hudson-Doyle (mwhudson) |
description: | updated |
Changed in casper (Ubuntu): | |
importance: | Undecided → Critical |
tags: | added: rls-ee-incoming |
tags: |
added: eoan regression-release removed: rls-ee-incoming |
tags: | added: id-5d977fddc1b17468188cc866 |
tags: | added: id-5daf76eda2a6e5756012409b |
Oops, sorry for the disruption. Yes, having "nopersistent" suppressing this behaviour makes sense to me.
Is there any way we could have found out about this breaking your use case earlier? casper has tests now, so if you can describe other use cases sufficiently precisely we can make sure we keep them working...