Comment 0 for bug 2017949

Revision history for this message
Grant Orndorff (orndorffgrant) wrote : [SRU] ubuntu-advantage-tools (27.14.4 -> 27.15) Xenial, Bionic, Focal, Jammy, Kinetic, Lunar

[Impact]
This is for the release of the latest upstream version of the Ubuntu Pro Client, which contains several bugfixes and new features that are desirable on all releases. 27.15 is mostly a polish release but there are some notable features.

The most notable changes are:
 - ua-timer.timer will now only run when attached
 - we're adding code that introduces the concept of service "variants", to be activated by the resource definition on the backend, beginning with realtime-kernel
 - new criteria for "yes-kernel-livepatches-applied" value of `pro system reboot-required`
   livepatch status must be either "applied" or "nothing-to-apply" and
   livepatch support status must say "supported"
 - polish to the output of `pro security-status`

See the changelog entry below for a full list of changes and bugs.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/UbuntuAdvantageToolsUpdates

The ubuntu-advantage-tools team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. ubuntu-advantage-tools team members will not mark ‘verification-done’ until this has happened.

[Regression Potential]
This release includes a refactors of our reboot-cmds systemd service. If the refactor causes the reboot-cmds script to fail, then users who are upgrading from trusty to xenial may not get livepatch automatically enabled, and some users may end up with some unnecessary package holds on fips packages.

The timer now doesn't run all the time. If there was a mistake here, it may not be properly started on attach, which could interfere with contract metering.

Previous versions of u-a-t attempted to load a `uaclient.conf` if it existed in the current working directory where the cli was called. This version removes that functionality. If users had workflows that depended on that, then they will break.

More generally, there are several new features and lots of code changed. We could have inadvertently introduced new failure cases in any of this.

[Discussion]
This isn't quite ready yet since we're still finalizing the implementation of service variants.

[Changelog]

TODO add once finalized