group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <2060732@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package ubuntu-advantage-tools - 32.3~23.10

---------------
ubuntu-advantage-tools (32.3~23.10) mantic; urgency=medium

  * Backport 32.3 to mantic (LP: #2060732)

ubuntu-advantage-tools (32.3) oracular; urgency=medium

  * d/apparmor: adjust the profiles to account for usr-merge consequences
    (LP: #2067319)

ubuntu-advantage-tools (32.2) oracular; urgency=medium

  * d/apparmor: adjust rules for violations found during testing (LP:
#2066929)

ubuntu-advantage-tools (32.1) oracular; urgency=medium

  * d/apparmor: allow access for /etc/os-release on all supported
    profiles (LP: #2065573)
  * apport: get path for timer job status from the correct place (LP: #2065616)

ubuntu-advantage-tools (32) oracular; urgency=medium

  * d/postinst: ensure migrations happen in correct package postinst (GH: #2982)
  * d/apparmor: introduce new ubuntu_pro_esm_cache apparmor policy
  * New upstream release 32 (LP: #2060732)
    - api:
      + u.pro.attach.token.full_token_attach.v1: add support for attach
        with token
      + u.pro.services.disable.v1: add support for disable operation
      + u.pro.services.enable.v1: add support for enable operation
      + u.pro.detach.v1: add support for detach operation
      + u.pro.status.is_attached.v1: add extra fields to API response
      + u.pro.services.dependencies.v1: add support for service dependencies
      + u.pro.security.fix.*.plan.v1: update ESM cache during plan API
        if needed
    - apt_news: add architectures and packages selectors filters for apt news
    - cli:
      + improved cli/log message for unexpected errors (GH: #2600)
      + properly handle setting empty config values (GH: #2925)
    - cloud-init: support ubuntu_pro user-data
    - collect-logs: update default output file to pro_logs.tar.gz (LP: #2033313)
    - config: create public and private config (GH: #2809)
    - entitlements:
      + update logic that checks if a service is enabled (LP: #2031192)
    - fips: warn/confirm with user if enabling fips downgrades the kernel
    - fix: warn users if ESM cache cannot be updated (GH: #2841)
    - logging:
      + use journald logging for all systemd services
      + add redundancy to secret redaction
    - messaging:
      + add consistent messaging for end of contract state
      + make explicit that unattached enable/disable is a noop (GH: #2487)
      + make explicit that disabling a disabled service is a noop
      + make explicit that enabling an enabled service is a noop
    - notices: filter unreadable notices when listing notices (GH: #2898)

 -- Renan Rodrigo <renanrodrigo@xxxxxxxxxxxxx>  Tue, 28 May 2024
15:15:45 -0300

** Changed in: ubuntu-advantage-tools (Ubuntu Mantic)
       Status: Fix Committed => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Jammy)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2060732

Title:
  [SRU] ubuntu-advantage-tools (31 -> 32) Xenial, Bionic, Focal, Jammy,
  Mantic

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Released
Status in ubuntu-advantage-tools source package in Focal:
  Fix Released
Status in ubuntu-advantage-tools source package in Jammy:
  Fix Released
Status in ubuntu-advantage-tools source package in Mantic:
  Fix Released
Status in ubuntu-advantage-tools source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  This release brings both bug-fixes and new features for the Pro
  Client, and we would like to make sure all of our supported customers
  have access to these improvements on all releases.

  The most important changes are:
   - d/apparmor:introduce new ubuntu_pro_esm_cache apparmor policy
   - api:
     + u.pro.attac.token.full_token_attach.v1: add suppport for attach with token
     + u.pro.services.disable.v1: add support for disable operation
     + u.pro.services.enable.v1: add support for enable operation
     + u.pro.detach.v1: add support for detach operation
     + u.pro.status.is_attached.v1: add extra fields to API response
     + u.pro.services.dependencies.v1: add support for service dependencies
     + u.pro.security.fix.*.plan.v1: update ESM cache during plan API if needed
   - config: create public and private config (GH: #2809)
   - messaging: add consistent messaging for end-of-contract

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

  [ Test Plan ]

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

  The Pro Client developers will be in charge of attaching the artifacts
  of the appropriate test runs to the bug, and will not mark
  ‘verification-done’ until this has happened.

  Additionally, we will perform manual tests for the public/private
  config feature that will be better discussed in the next section

  Finally, we will also perform another verification for an apparmor issue that
  is described here:

  https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
  tools/+bug/2067319

  We will run the full test suite for version 32.2 and run only again only the affected scenarios for this apparmor issue that is fixed on 32.3. Please refer
  to the apparmor bug for the full plan regarding the verification of this SRU

  [ Discussion]

  This release will be introducing a split on our config for public and private information. This is to be explicit in the behavior a non-root and root user will see when running pro config show. For example,
  we believe that a non-root user should not see proxy data in pro config show. This information is now stored in a private config file.

  We need a mechanism to ensure that old versions of the Pro client
  would also get that split. To do that, we have created a script to run
  on postinst to adapt the existing pro config into this new setting.

  However, we have recently introduced the new ubuntu-pro-client
  package. That means that we cannot know beforehand from which package
  the user would be upgrading from, ubuntu-advantage-tools or ubuntu-
  pro-client.

  If the system already has ubuntu-pro-client and is upgrading to a new
  version of ubuntu-pro-client, that means all migrations present in
  ubuntu-advantage-tools.postinst must have already run at the time the
  system upgraded to the renamed ubuntu-pro-client. That mean this
  config migration should happen on ubuntu-pro-client.postinst

  If upgrading from before the rename to the current version (from
  before version 31), then not necessarily all migrations inside of
  ubuntu-advantage-tools.postinst will have already run. Because the
  migrations present in this file may depend on those previous
  migrations, then we need to make the migration on ubuntu-advantage-
  tools.postinst

  That is because there might be users running an old version of ubuntu-
  advantage-tools that have not yet upgraded to version 27.14. This
  version is the one that introduces the /var/lib/ubuntu-advantage/user-
  config.json. Therefore, we need to ensure to this migration happens
  first, before our public/private migration.

  Because of that, we are coordinating which postinst script will
  execute the migration. A more detailed explanation of this logic can
  be found on the script itself, lib/postinst-migrations.sh

  [ Changelog ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2060732/+subscriptions