Releases: canonical/subiquity
21.01.1
The largest change in this release is one that should be largely invisible to users: subiquity is now split into a server process that actually runs the install and one or more client processes that the user interacts with to configure the install. One visible change to this is that for a non-interactive install, progress is shown in all clients, so on tty1 and any serial lines and if you log in via ssh.
Other changes and fixes:
- Improved support for DASD drives (a kind of storage found on IBM mainframes), including support for FBA DASD drives, unformatted ECKD drives and ECKD drives passed to KVM virtual machines via virtio-blk (LP: #1885890, LP: #1887669, LP: #1893775)
- Make matching a disk by model or vendor actually work properly
- Print autoinstall progress to console on s390x
- Make "update: no" inhibit updates in the refresh section of the autoinstall data.
- Update curtin to a new snapshot that contains fixes for a few bugs:
- Do not fail if ID_SERIAL contains "=" (LP: #1895021)
- Fix removing partitions on multipathed drives (LP: #1900900)
20.09.1
This release of subiquity fixes a couple of bugs and contains some internal refactoring.
- Fix a crash when an block device that is a multipath member does not have a wwn (LP: #1892725)
- Fix a crash when renaming a bond interface. (LP: #1892725)
20.07.1
This release of subiquity includes the following fixes:
- Preserve all documented storage fields when converting autoinstall config to curtin config (LP: #1885644)
- Treat a failure to detect a snap update as "unknown" rather than "no update" (LP: #1886816)
- Do not start the service when installed in a non-installer environment
- Fix editing a logical volume (LP: #1887997)
- Fix snap list view when no snaps are seeded (i.e. bionic) (LP: #1889429)
20.06.1
This release of subiquity contains the following changes:
- Configure cloud-init for first boot tasks in a way that will not get confused by a "cidata" partition containing autoinstall config (LP: #1879103, #790)
- Upgrade curtin, which fixes handling of partition flags on some existing MSDOS partitions (LP: #1878890)
- Fix detection of UEFI ESPs on disks with MBR partition tables (LP: #1879376, #777)
- Make the generated autoinstall file be acutally valid (LP: #1879708, #768, #769)
- Default to LVM in the guided storage screen (#767)
- Start in a very basic (no unicode, no colour) on serial and offer upgrade to "rich" mode (#778)
- Changes to make the codebase more translatable (but no improved translations, yet)
- Offer languages that cannot be rendered on the linux console over SSH or in rich mode over serial
- Do not set preserve_hostname if there is no hostname defined in the autoinstall config (#763)
- Do not create crash reports if not in a live session (#765)
20.05.2
This release fixes a bug where the luks passphrase for any encrypted volumes was leaked into the logs, which were then copied to the installed system. (LP: #1878115 CVE-2020-11932)
The updated subiquity to address this issue has been published in the snapstore, when online a snap refresh will be offered during live installer. Opting in to update the installer will address this issue and will prevent leaking this information in the logs.
20.05.1
This release includes the following fixes and improvements:
- Do not allow multiple boot devices in the UI when installing 19.10 or older releases (this change means we can release this version to users on 18.04) (#733)
- Stop staging libc6 and some other library packages now the snap is based on core18, making it a little smaller. (#717)
- Run autoinstall late-commands before copying logs to the target system or prompting the user to click reboot (if appropriate) (LP: #1874456, #734)
- Do not crash if one logs in via ssh and makes the terminal narrow (LP: #1874314, #735)
- Switch the tty settings to something sane when running a non-interactive autoinstall on a serial port (LP: #1874052, #736)
- Use better heuristics for sizing the root logical volume when using the "guided LVM" option (LP: #1785321, #737)
- Allow network config to be supplied as intended in the autoinstall config and fix handling of netplan apply failures (reported on discourse, #739)
- Do not allow block probes to run at the same time as installation, as they can interact in surprising ways (LP: #1874501, LP: #1875611, #742)
- When multiple subiquity instances are running (e.g. one on tty1 and one on a serial line) and one is performing a curtin install, mention this in a modal dialog on the others (#738)
- Restart installer after update when logged in via SSH (LP: #1874034, #741)
- Update probert to a version that does not pass --mknodes to vgscan (LP: #1874501 again, #745)
- Actually copy the network config provided in the autoinstall file to the target system (LP: #1876098, #746)
- Fix autoinstalls with no network (LP: #1876785, #750)
- Allow late-commands to use
curtin in-target --
without--target /target
as documented (#755) - Round autoinstall partition sizes using percentages down to a megabyte boundary (LP: #1876874, #752)
- A curtin update (#760) that
- Fixes handing of msdos partitions with the bootable flag (LP: #1875560, LP: #1875903, LP: #1876638)
- Fixes handling of unusual characters in a device's ID_SERIAL field (LP: #1875085)
- Works with the mounts set up by casper's "toram" mode (LP: #1876626)
- Works around a problem with drives with bogus 'wwn' values (LP: #1876848)
Thanks to all who tested the 20.04 release and provided reports of success and failure!
20.04.3
20.04.2
This release of subiquity adds:
- Support for installing (and maintaining) multiple boot volumes for UEFI and BIOS booting systems (LP: #1817066)
- Various autoinstall fixes, thanks to all who tested and reported bugs
- Fix for a sequence of operations that would start the install without setting up a bootloader partition
- Fetch both apport hooks and apport python code from focal, fixing an ugly traceback when an error occurred
- A new snapshot of curtin, fixing some more reuse scenarios
20.04.1
The biggest new feature in this release is autoinstall support. Please see the discourse post for more on that.
In this release:
- Use a newer snapshot of curtin, which should fix some complex scenarios involving reuse of existing devices
- Do not delete virtual network devices every time the network is reconfigured (this mostly affects s390x where ssh-ing over a vlan connection to the live environment is a common thing to do)
- Fix confusion where block device udev events could cause a probe to be erroneously considered as failed.
- Include help on how to SSH into the live server session.
There are also several other robustness fixes.
20.03.2
This releases fixes a few bugs reported to the error tracker since the 20.03.1 release. Thanks to everyone who submitted a report!
Specific fixes:
- Fix formatting a pre-existing, unformatted RAID
- Increase the block probe timeout
- Remove /target after unmounting it, this should fix retrying an installation after certain classes of failure
- Fix enabling DHCP on a virtual network interface (vlan or bond)
- Fix deleting a virtual network interface
- Better behaviour when block probing finds no or only small disks