During autopkgtest we are creating VMs with 768MB of RAM, that used to
be enough in the past, but nowdays we typically require more memory and
we may trigger some sporadic out-of-memory failures during autopkgtest.
Bump up the memory size to 1G to prevent such potential OOM issues.
New changelog entries:
* Move check for fallback persistent filesystem label (casper-rw) later as
it seems sometimes it takes time for block devices to appear and be
processed by udev. (LP: #1863672)
New changelog entries:
* Make fsckd under spinner/logo themes produce consistent output
* Make plymouth-less progress output less bad
* Use theme-specific keys: or fsckd-cancel-msg: for Ctrl+C message LP:
#1870018
* Add fsck.mode=skip sensitivity to casper-md5check
* ubuntu-server: skip mounting swap (as hacked by livecd-rootfs currently)
* Leave fsck result as a json /run/casper-md5check.json file.
* ubuntu-server: adapt runtime netplan into cloud-config cloud.cfg
* Fix cmdline parsing, it was always broken
New changelog entries:
* casper-md5check:
+ flush pending events for actually fluid progress updates
+ drop reboot includes
+ watch for s keystroke to skip checks
+ always finish on 100% update, to remove the progress message
+ always drop the keystrokes message
+ always display the result of the checks, with a slight delay
+ make the failed message linger for longer
+ clear all messages before quiting
+ ignore unused-result warnings during compilation
New changelog entries:
* casper-md5check:
+ Use fsck progress text, whilst verifying the disk.
+ Do not reboot, but simply continue booting after the integrity check.
+ Perform integrity check on every boot (TODO allow skipping the check)
