The UA screen is now shown only if we are running on an LTS release.
In dry-run mode, we pretend to always be on Ubuntu focal.
To implement the possibility to skip the screen, we added another POST
resource to inform the server that we are finished configuring
UbuntuAdvantage.
Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
- This is a cleanup for SystemSetup per DEENG-134 and DEENG-139
- Default user should be set by the WSL launcher.
- Shutdown/reboot actions also.
- Added a structured form of communication between OOBE and launcher.
- /run/launcher-command
Introduce a new view, model and controllers pair to enable Ubuntu
Advantage from Subiquity. For now, we expect the user to input an
alphanumeric token and rely on cloud-init to enable the features
associated with the subscription.
This implementation comes with a number of limitations:
* inability to validate the token before first-boot
* inability to check what features are associated with the Ubuntu
Advantage subscription, before first-boot
* the user must input the token directly: there is no mechanism to
deduce the token based on email address and password.
The new screen is placed after the identity scree. The installation
should already be running when the UA screen will be shown to the user.
Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
Read ID_MODEL/VENDOR_ENC for disks to allow the GUI installer to show
pretty disk names without having to call libudev through FFI.
As a bonus, this also fixes disk names to match the machine config in
dry-run mode.
Related issues
- FR-1710
- canonical/ubuntu-desktop-installer#415
When comparing version numbers (i.e., to determine if we want to suggest
and upgrade of subiquity) we now support version numbers of the
following form:
{major}.{minor}.{patch}+git{build_id}.{commit_id}
The commit ID is ignored in the resolution because it is not a number
that is growing.
Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
In specific scenarios, the version of the snap as returned by snapd is
older than the version currently running. When that happens, we were
suggesting the user to update. This action would effectively result in a
downgrade.
We now attempt to determine if the snapd version is greater than the one
currently running. If we can't the behavior is unaffected.
Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>