sudo ua attach is not working

[slava]

[Impact]
This bug impacts users which:
- Do not have the '/usr/bin/cloud-id' command in their system,
- Do have the '/var/lib/cloud/data/result.json' file in their system, and
- Have a non-standard (by cloud-init definitions) content in the '/var/lib/cloud/data/result.json' file.

This is an unusual situation, given that the presence of the 'result.json' file with the absence of the 'cloud-id' command is observed on official Trusty images, but from Xenial onwards 'cloud-id' should be there. Even in the case where the command is not there, the file generated by cloud-init will have the required information.

Since we are doing the SRU process for Xenial onwards, the solution for those problems is to rely only on cloud-id when trying to determine the cloud type, and assuming not on cloud when the command is not present or if it fails.
https://github.com/canonical/ubuntu-advantage-client/commit/f6fbcee792cf42cc67e3ced02815b7d552dee19f

[Test Case]
To reproduce:
With ubuntu-advantage-tools 27.2 installed, in an Ubuntu machine:
- Make sure cloud-id is not there:
  $ sudo mv /usr/bin/cloud-id /usr/bin/cloud-id.old
- Make sure to have the result.json file with non-standard (empty, for instance) content:
  $ sudo mv /var/lib/cloud/data/result.json /var/lib/cloud/data/result.json.old (if the file exists)
  $ sudo touch /var/lib/cloud/data/result.json
- Try to attach a token using "ua attach"
- Verify that it fails

To verify the fix:
Repeat the above process using ubuntu-advantage tools 27.3, and verify that the attach operation succeeds.

[Regression Potential]
When running on a non-cloud system, this fix brings no impact, as we expect cloud-id to be absent and we are not running on cloud.

When running on a specific cloud, this fix brings the scenario where we should detect the cloud and are unable to, due to problems with cloud-init. This is minor though, given that if cloud-init didn't run properly, the instance has more problems than this one. Besides that, considering no-cloud when not in aws/azure/gcp has no impact on UA at all, and those three providers have images with cloud-id working properly.

No official Ubuntu image should be affected by this change.

[Discussion]
As stated above, this is an unusual situation, which led to an improvement to the cloud detection in UA.

[Original Description]
sudo ua status
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-advantage-tools 27.2.2~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-153.160-generic 4.15.18
Uname: Linux 4.15.0-153-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.24
Architecture: amd64
Date: Mon Aug 16 19:14:53 2021
InstallationDate: Installed on 2019-08-12 (735 days ago)
InstallationMedia:

SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)

[Richard Harding (rharding)]

Thanks for the bug report. Do you have any interesting details in the log file referenced?

/var/log/ubuntu-advantage.log

Marking incomplete while we collect information on what's failed.

Thanks!

[slava (whisperit)]

Please find the log attached.

On 16.08.21 19:31, Richard Harding wrote:
> Thanks for the bug report. Do you have any interesting details in the
> log file referenced?
>
> /var/log/ubuntu-advantage.log
>
>
> Marking incomplete while we collect information on what's failed.
>
> Thanks!
>
> ** Changed in: ubuntu-advantage-tools (Ubuntu)
> Status: New => Incomplete
>

[Richard Harding (rharding)]

Thank you for the log, it looks like we tried to get the cloud details for the machine and it was empty. Can you share a bit of information on what type of platform this was on? Is this on a machine, lxd container, cloud instance on a specific cloud?

  File "/usr/lib/python3/dist-packages/uaclient/clouds/identity.py", line 56, in get_cloud_type_from_result_file\
    dsname = result["v1"]["datasource"].split()[0].lower()\
AttributeError: 'NoneType' object has no attribute 'split'}

[slava (whisperit)]

You are welcome!

It's a VDS on Ikoulu.

On Hetzner and OVH it works fine.

On 17.08.21 13:43, Richard Harding wrote:
> Thank you for the log, it looks like we tried to get the cloud details
> for the machine and it was empty. Can you share a bit of information on
> what type of platform this was on? Is this on a machine, lxd container,
> cloud instance on a specific cloud?
>
> File "/usr/lib/python3/dist-packages/uaclient/clouds/identity.py", line 56, in get_cloud_type_from_result_file\
> dsname = result["v1"]["datasource"].split()[0].lower()\
> AttributeError: 'NoneType' object has no attribute 'split'}
>

[Lucas Albuquerque Medeiros de Moura (lamoura)]

Hi slava, thanks for reporting this.
I just want to confirm something some information regarding this bug:

1) Can you confirm that the system does not have the "cloud-id" command ?
2) What version of cloud-init are you running on the system ?
3) Can you upload the output of this file here: /var/lib/cloud/data/result.json

I originally thought that I might be running that on a Trusty instance, but I just realized that you mentioned you are running it on Bionic.

[slava (whisperit)]

Bionic

Description:    Ubuntu 18.04.5 LTS
Release:    18.04
Codename:    bionic

GNU/Linux 4.15.0-153-generic x86_64

On 17.08.21 15:24, Lucas Albuquerque Medeiros de Moura wrote:
> Hi slava, thanks for reporting this.
> I just want to confirm something, is this a Trusty instance ?
>

[Lucas Albuquerque Medeiros de Moura (lamoura)]

Hi slava, sorry I edited my question a little bit to gather other information about the issue. Also, I realized that you have mentioned you are using Bionic on the bug description, so sorry for that.

But if you can provide the extra information around cloud-init, that would be great for us to better understand this problem,

[slava (whisperit)]

> 1) Can you confirm that the system does not have the "cloud-id" command ?

yes, cloud-id: command not found

> 2) What version of cloud-init are you running on the system ?
Command 'cloud-init' not found, but can be installed with:

sudo apt install cloud-init

On two other VDS I've mentioned (where there is no such bug), cloud-init
is also not installed

> 3) Can you upload the output of this file here:
> /var/lib/cloud/data/result.json
{
  "v1": {
   "datasource": null,
   "errors": [
    "No instance datasource found.",
    "Can not apply stage config, no datasource found! Likely bad things
to come!",
    "Can not apply stage final, no datasource found! Likely bad things
to come!"
   ]
  }
}

On 17.08.21 16:22, Lucas Albuquerque Medeiros de Moura wrote:
> Hi slava, sorry I edited my question a little bit to gather other
> information about the issue. Also, I realized that you have mentioned
> you are using Bionic on the bug description, so sorry for that.
>
> But if you can provide the extra information around cloud-init, that
> would be great for us to better understand this problem,
>

[Lucas Albuquerque Medeiros de Moura (lamoura)]

Hi slava, thanks for this issue. I think we will have a more flexible approach on how we handle that cloud-init check.

If you want to avoid having that trouble on your machine at the moment, you can add this into /etc/ubuntu-advantage/uaclient.conf

-----------------
settings_overrides:
  cloud_type: ""
---------------

This should avoid the cloud-init logic check.
Let me know if that works for you

[slava (whisperit)]

Thank Lucas, but now I've got some other errors. Please find the log
attached.

However, I think the services themselves are working..

On 17.08.21 19:45, Lucas Albuquerque Medeiros de Moura wrote:
> Hi slava, thanks for this issue. I think we will have a more flexible
> approach on how we handle that cloud-init check.
>
> If you want to avoid having that trouble on your machine at the moment,
> you can add this into /etc/ubuntu-advantage/uaclient.conf
>
> -----------------
> settings_overrides:
> cloud_type: ""
> ---------------
>
> This should avoid the cloud-init logic check.
> Let me know if that works for you
>

[Lucas Albuquerque Medeiros de Moura (lamoura)]

That's weird, the logs show the same error as before.

Can you send me your /etc/ubuntu-advantage/uaclient.conf ? I want to see if I can reproduce that

[slava (whisperit)]

Yep, here it is:

# Ubuntu-Advantage client config file.
# If you modify this file, run "ua refresh config" to ensure changes are
# picked up by Ubuntu-Advantage client.

contract_url: https://contracts.canonical.com
data_dir: /var/lib/ubuntu-advantage
log_file: /var/log/ubuntu-advantage.log
log_level: debug
security_url: https://ubuntu.com/security
ua_config:
   cloud_type: ""
   apt_http_proxy: null
   apt_https_proxy: null
   http_proxy: null
   https_proxy: null

On 17.08.21 22:24, Lucas Albuquerque Medeiros de Moura wrote:
> That's weird, the logs show the same error as before.
>
> Can you send me your /etc/ubuntu-advantage/uaclient.conf ? I want to see
> if I can reproduce that
>

[Lucas Albuquerque Medeiros de Moura (lamoura)]

Hi slava, there is just one minor problem on the config. The cloud_type entry is incorrectly place on under ua_config. The config should be:

contract_url: https://contracts.canonical.com
data_dir: /var/lib/ubuntu-advantage
log_file: /var/log/ubuntu-advantage.log
log_level: debug
security_url: https://ubuntu.com/security
ua_config:
   apt_http_proxy: null
   apt_https_proxy: null
   http_proxy: null
   https_proxy: null
settings_overrides:
  cloud_type: ""

Let me know if that works out

[slava (whisperit)]

Hi Lucas and thank you!

Now it's working!

On 18.08.21 15:16, Lucas Albuquerque Medeiros de Moura wrote:
> Hi slava, there is just one minor problem on the config. The cloud_type
> entry is incorrectly place on under ua_config. The config should be:
>
> contract_url: https://contracts.canonical.com
> data_dir: /var/lib/ubuntu-advantage
> log_file: /var/log/ubuntu-advantage.log
> log_level: debug
> security_url: https://ubuntu.com/security
> ua_config:
> apt_http_proxy: null
> apt_https_proxy: null
> http_proxy: null
> https_proxy: null
> settings_overrides:
> cloud_type: ""
>
>
> Let me know if that works out
>

[Chad Smith (chad.smith)]

Hi @slava. Thank you for filing this bug, the response you have given in comment #9 raises a concern for me in that your image does not contain /usr/bin/cloud-id as delivered by the cloud-init package.

This implies to me that you are not running on an image based on an official Ubuntu cloud image provided here https://cloud-images.ubuntu.com/. All official cloudimages have cloud-init installed (as well as security updates and upgrade applied), images not based on official Ubuntu images containing cloud-init are likely going to be unsupported.

In your Bionic images that lack cloud-init is there a file /etc/cloud/build.info present? If so what are the contents? I believe this would tell us if your image was a derivative of official Ubuntu cloud images and what build date it was derived from.

[slava (whisperit)]

Hello Chad,

no, the build.info file is not present there

On 19.08.21 22:36, Chad Smith wrote:
> Hi @slava. Thank you for filing this bug, the response you have given in
> comment #9 raises a concern for me in that your image does not contain
> /usr/bin/cloud-id as delivered by the cloud-init package.
>
> This implies to me that you are not running on an image based on an
> official Ubuntu cloud image provided here https://cloud-
> images.ubuntu.com/. All official cloudimages have cloud-init installed
> (as well as security updates and upgrade applied), images not based on
> official Ubuntu images containing cloud-init are likely going to be
> unsupported.
>
> In your Bionic images that lack cloud-init is there a file
> /etc/cloud/build.info present? If so what are the contents? I believe
> this would tell us if your image was a derivative of official Ubuntu
> cloud images and what build date it was derived from.
>

[Chad Smith (chad.smith)]

Thanks @slava for the confirmation. So, no that image base is not derived from a supported Canonical cloud image. If you have control over what base image you are using for your machine launch or imaging process, or if you can talk to your cloud provider about obtaining official images from here https://cloud-images.ubuntu.com/ it may make your use-case a bit easier in the future.

That said, if your or your cloud providers are unable to move to Canonical official Ubuntu cloud images, we have also landed a fix in tip of ubuntu-advantage-tools[1] that will avoid that specific traceback you hit in this bug report. Once ubuntu-advantage-tools version > 27.2 is released, you will be able to drop your uaclient.conf settings_overrides without fear of Tracebacks.

[1] upstream fix to rely on cloud-id only if present https://github.com/canonical/ubuntu-advantage-client/commit/f6fbcee792cf42cc67e3ced02815b7d552dee19f

[slava (whisperit)]

Hello Chad,

/etc/cloud/build.info is not there

Out of interest I checked two other servers (Hetzner and OVH) and they
also do not contain /usr/bin/cloud-id

However, there is build.info on the OVH one with the following content:

build_name: server

serial: 20210512

/etc/cloud/build.info is not there.

thank you for the detailed info.

On 19.08.21 22:36, Chad Smith wrote:
> Hi @slava. Thank you for filing this bug, the response you have given in
> comment #9 raises a concern for me in that your image does not contain
> /usr/bin/cloud-id as delivered by the cloud-init package.
>
> This implies to me that you are not running on an image based on an
> official Ubuntu cloud image provided here https://cloud-
> images.ubuntu.com/. All official cloudimages have cloud-init installed
> (as well as security updates and upgrade applied), images not based on
> official Ubuntu images containing cloud-init are likely going to be
> unsupported.
>
> In your Bionic images that lack cloud-init is there a file
> /etc/cloud/build.info present? If so what are the contents? I believe
> this would tell us if your image was a derivative of official Ubuntu
> cloud images and what build date it was derived from.
>

[Steve Langasek (vorlon)]

Hello slava, or anyone else affected,

Accepted ubuntu-advantage-tools into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/27.3~21.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

Hello slava, or anyone else affected,

Accepted ubuntu-advantage-tools into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/27.3~21.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

Hello slava, or anyone else affected,

Accepted ubuntu-advantage-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/27.3~20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

Hello slava, or anyone else affected,

Accepted ubuntu-advantage-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/27.3~18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

Hello slava, or anyone else affected,

Accepted ubuntu-advantage-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/27.3~16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Lucas Albuquerque Medeiros de Moura (lamoura)]

Bug verified with the following script:

----------------------------------------------
series=$1
name=test-$series
UA_TOKEN=<UA_TOKEN>

lxc launch ubuntu-daily:$series $name
lxc exec $name -- ua version
lxc exec $name -- cloud-init status --wait
lxc exec $name -- mv /usr/bin/cloud-id /usr/bin/cloud-id.old
lxc exec $name -- mv /var/lib/cloud/data/result.json /var/lib/cloud/data/result.json.old
lxc exec $name -- touch /var/lib/cloud/data/result.json
# verify failure to attach
lxc exec $name -- ua attach $UA_TOKEN
lxc delete --force $name

lxc launch ubuntu-daily:$series $name
lxc exec $name -- cloud-init status --wait
lxc exec $name -- sh -c "cat <<EOF >/etc/apt/sources.list.d/ubuntu-$series-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ $series-proposed restricted main multiverse universe
EOF"
lxc exec $name -- apt update
lxc exec $name -- apt install ubuntu-advantage-tools
lxc exec $name -- ua version
lxc exec $name -- mv /usr/bin/cloud-id /usr/bin/cloud-id.old
lxc exec $name -- mv /var/lib/cloud/data/result.json /var/lib/cloud/data/result.json.old
lxc exec $name -- touch /var/lib/cloud/data/result.json
# verify attach works as expected
lxc exec $name -- ua attach $UA_TOKEN
lxc delete --force $name
-----------------------------------------------------------------------------

Test for xenial, bionic, focal, hirsute and impish are working as expected

[Lucas Albuquerque Medeiros de Moura (lamoura)]

Adding test results

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-advantage-tools - 27.3~21.10.1

---------------
ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium

  * d/tools.postinst:
    - consider cloud to be "none" on any cloud-id error
    - purge old ua-messaging.timer/service files
    - keep ua-timer.timer disabled if ua-messaging.timer was disabled by
      the user
    - properly configure both ubuntu-advantage-timer and
      ubuntu-advantage-licence-check logs
  * d/tools.postrm:
    - remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs
      during purge
  * systemd:
    - remove ua-messaging.timer/service
    - add new ua-timer.timer that runs every 6 hours
    - add new ua-license_check.timer that runs every 5 minutes only if
      activated by ua-license-check.path
  * New upstream release 27.3 (LP: #1942929)
    - ros:
      + add beta support to enable ros and ros-updates
      + add support for "required services" so that esm-infra and esm-apps
        get auto-enabled when enabling ros or ros-updates
      + add support for "dependent services" so that user gets prompted to
        disable ros/ros-updates if they disable esm-infra/esm-apps
    - fips:
      + allow fips on GCP bionic now that optimized kernel is ready
      + disallow enabling fips on focal on clouds until cloud-optimized focal
        fips-certified kernel is ready (LP: #1939449, LP: #1939932)
      + print warning about generic fips kernel if cloud-id fails
    - cloud:
      + rely only on cloud-id to determine cloud type (LP: #1940131)
      + catch errors when determining cloud type
        (LP: #1938207, LP: #1944676) (GH: #1541)
    - azure:
      + bump IMDS API version to support Azure published images
    - cli:
      + collect-logs command that creates a tar file with debug-relevant logs
        and status info (GH: #463)
      + clean locks on exceptions more thoroughly to avoid false "Operation in
        progress" status messages
      + retain past service state after detach
      + shows better error message when a port value in a proxy is invalid
    - non-unicode locale support:
      + remove unicode-only characters from help file
      + don't print unicode-only characters in ua fix if non-utf8 locale
        (GH: #1463)
    - logrotate:
      + add logrotate functionality for ubuntu-advantage-timer.log.
      + Fix root:root logrotate permissions.
    - ua-timer.timer:
      + introduce a single systemd timer to handle ua recurring jobs
      + timer runs every 2 hours to support most frequent timer job
      + recurring job intervals are configurable in uaclient.conf
      + individual jobs are disabled if their interval is set to 0
      - status job:
        + update ua status every 12 hours
      - messaging job:
        + update APT/MOTD ESM messaging every 6 hours
      - metering job:
        + disabled until infrastructure is ready
        + for attached machines only, periodically update contract server with
          status information for proper contract metering
    - ua-license-check.timer:
      + only runs on LTS GCP instances that are not attached
      + runs every 5 minutes to check if gcp instance has license r...

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for ubuntu-advantage-tools has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-advantage-tools - 27.3~21.04.1

---------------
ubuntu-advantage-tools (27.3~21.04.1) hirsute; urgency=medium

  * Backport new upstream release: (LP: #1942929) to hirsute

ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium

  * d/tools.postinst:
    - consider cloud to be "none" on any cloud-id error
    - purge old ua-messaging.timer/service files
    - keep ua-timer.timer disabled if ua-messaging.timer was disabled by
      the user
    - properly configure both ubuntu-advantage-timer and
      ubuntu-advantage-licence-check logs
  * d/tools.postrm:
    - remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs
      during purge
  * systemd:
    - remove ua-messaging.timer/service
    - add new ua-timer.timer that runs every 6 hours
    - add new ua-license_check.timer that runs every 5 minutes only if
      activated by ua-license-check.path
  * New upstream release 27.3 (LP: #1942929)
    - ros:
      + add beta support to enable ros and ros-updates
      + add support for "required services" so that esm-infra and esm-apps
        get auto-enabled when enabling ros or ros-updates
      + add support for "dependent services" so that user gets prompted to
        disable ros/ros-updates if they disable esm-infra/esm-apps
    - fips:
      + allow fips on GCP bionic now that optimized kernel is ready
      + disallow enabling fips on focal on clouds until cloud-optimized focal
        fips-certified kernel is ready (LP: #1939449, LP: #1939932)
      + print warning about generic fips kernel if cloud-id fails
    - cloud:
      + rely only on cloud-id to determine cloud type (LP: #1940131)
      + catch errors when determining cloud type
        (LP: #1938207, LP: #1944676) (GH: #1541)
    - azure:
      + bump IMDS API version to support Azure published images
    - cli:
      + collect-logs command that creates a tar file with debug-relevant logs
        and status info (GH: #463)
      + clean locks on exceptions more thoroughly to avoid false "Operation in
        progress" status messages
      + retain past service state after detach
      + shows better error message when a port value in a proxy is invalid
    - non-unicode locale support:
      + remove unicode-only characters from help file
      + don't print unicode-only characters in ua fix if non-utf8 locale
        (GH: #1463)
    - logrotate:
      + add logrotate functionality for ubuntu-advantage-timer.log.
      + Fix root:root logrotate permissions.
    - ua-timer.timer:
      + introduce a single systemd timer to handle ua recurring jobs
      + timer runs every 2 hours to support most frequent timer job
      + recurring job intervals are configurable in uaclient.conf
      + individual jobs are disabled if their interval is set to 0
      - status job:
        + update ua status every 12 hours
      - messaging job:
        + update APT/MOTD ESM messaging every 6 hours
      - metering job:
        + disabled until infrastructure is ready
        + for attached machines only, periodically update contract server with
          status information for proper contract metering
    - ua-license-check.timer:
   ...

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-advantage-tools - 27.3~20.04.1

---------------
ubuntu-advantage-tools (27.3~20.04.1) focal; urgency=medium

  * Backport new upstream release: (LP: #1942929) to focal

ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium

  * d/tools.postinst:
    - consider cloud to be "none" on any cloud-id error
    - purge old ua-messaging.timer/service files
    - keep ua-timer.timer disabled if ua-messaging.timer was disabled by
      the user
    - properly configure both ubuntu-advantage-timer and
      ubuntu-advantage-licence-check logs
  * d/tools.postrm:
    - remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs
      during purge
  * systemd:
    - remove ua-messaging.timer/service
    - add new ua-timer.timer that runs every 6 hours
    - add new ua-license_check.timer that runs every 5 minutes only if
      activated by ua-license-check.path
  * New upstream release 27.3 (LP: #1942929)
    - ros:
      + add beta support to enable ros and ros-updates
      + add support for "required services" so that esm-infra and esm-apps
        get auto-enabled when enabling ros or ros-updates
      + add support for "dependent services" so that user gets prompted to
        disable ros/ros-updates if they disable esm-infra/esm-apps
    - fips:
      + allow fips on GCP bionic now that optimized kernel is ready
      + disallow enabling fips on focal on clouds until cloud-optimized focal
        fips-certified kernel is ready (LP: #1939449, LP: #1939932)
      + print warning about generic fips kernel if cloud-id fails
    - cloud:
      + rely only on cloud-id to determine cloud type (LP: #1940131)
      + catch errors when determining cloud type
        (LP: #1938207, LP: #1944676) (GH: #1541)
    - azure:
      + bump IMDS API version to support Azure published images
    - cli:
      + collect-logs command that creates a tar file with debug-relevant logs
        and status info (GH: #463)
      + clean locks on exceptions more thoroughly to avoid false "Operation in
        progress" status messages
      + retain past service state after detach
      + shows better error message when a port value in a proxy is invalid
    - non-unicode locale support:
      + remove unicode-only characters from help file
      + don't print unicode-only characters in ua fix if non-utf8 locale
        (GH: #1463)
    - logrotate:
      + add logrotate functionality for ubuntu-advantage-timer.log.
      + Fix root:root logrotate permissions.
    - ua-timer.timer:
      + introduce a single systemd timer to handle ua recurring jobs
      + timer runs every 2 hours to support most frequent timer job
      + recurring job intervals are configurable in uaclient.conf
      + individual jobs are disabled if their interval is set to 0
      - status job:
        + update ua status every 12 hours
      - messaging job:
        + update APT/MOTD ESM messaging every 6 hours
      - metering job:
        + disabled until infrastructure is ready
        + for attached machines only, periodically update contract server with
          status information for proper contract metering
    - ua-license-check.timer:
      +...

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-advantage-tools - 27.3~18.04.1

---------------
ubuntu-advantage-tools (27.3~18.04.1) bionic; urgency=medium

  * Backport new upstream release: (LP: #1942929) to bionic

ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium

  * d/tools.postinst:
    - consider cloud to be "none" on any cloud-id error
    - purge old ua-messaging.timer/service files
    - keep ua-timer.timer disabled if ua-messaging.timer was disabled by
      the user
    - properly configure both ubuntu-advantage-timer and
      ubuntu-advantage-licence-check logs
  * d/tools.postrm:
    - remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs
      during purge
  * systemd:
    - remove ua-messaging.timer/service
    - add new ua-timer.timer that runs every 6 hours
    - add new ua-license_check.timer that runs every 5 minutes only if
      activated by ua-license-check.path
  * New upstream release 27.3 (LP: #1942929)
    - ros:
      + add beta support to enable ros and ros-updates
      + add support for "required services" so that esm-infra and esm-apps
        get auto-enabled when enabling ros or ros-updates
      + add support for "dependent services" so that user gets prompted to
        disable ros/ros-updates if they disable esm-infra/esm-apps
    - fips:
      + allow fips on GCP bionic now that optimized kernel is ready
      + disallow enabling fips on focal on clouds until cloud-optimized focal
        fips-certified kernel is ready (LP: #1939449, LP: #1939932)
      + print warning about generic fips kernel if cloud-id fails
    - cloud:
      + rely only on cloud-id to determine cloud type (LP: #1940131)
      + catch errors when determining cloud type
        (LP: #1938207, LP: #1944676) (GH: #1541)
    - azure:
      + bump IMDS API version to support Azure published images
    - cli:
      + collect-logs command that creates a tar file with debug-relevant logs
        and status info (GH: #463)
      + clean locks on exceptions more thoroughly to avoid false "Operation in
        progress" status messages
      + retain past service state after detach
      + shows better error message when a port value in a proxy is invalid
    - non-unicode locale support:
      + remove unicode-only characters from help file
      + don't print unicode-only characters in ua fix if non-utf8 locale
        (GH: #1463)
    - logrotate:
      + add logrotate functionality for ubuntu-advantage-timer.log.
      + Fix root:root logrotate permissions.
    - ua-timer.timer:
      + introduce a single systemd timer to handle ua recurring jobs
      + timer runs every 2 hours to support most frequent timer job
      + recurring job intervals are configurable in uaclient.conf
      + individual jobs are disabled if their interval is set to 0
      - status job:
        + update ua status every 12 hours
      - messaging job:
        + update APT/MOTD ESM messaging every 6 hours
      - metering job:
        + disabled until infrastructure is ready
        + for attached machines only, periodically update contract server with
          status information for proper contract metering
    - ua-license-check.timer:
     ...

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-advantage-tools - 27.3~16.04.1

---------------
ubuntu-advantage-tools (27.3~16.04.1) xenial; urgency=medium

  * Backport new upstream release: (LP: #1942929) to xenial

ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium

  * d/tools.postinst:
    - consider cloud to be "none" on any cloud-id error
    - purge old ua-messaging.timer/service files
    - keep ua-timer.timer disabled if ua-messaging.timer was disabled by
      the user
    - properly configure both ubuntu-advantage-timer and
      ubuntu-advantage-licence-check logs
  * d/tools.postrm:
    - remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs
      during purge
  * systemd:
    - remove ua-messaging.timer/service
    - add new ua-timer.timer that runs every 6 hours
    - add new ua-license_check.timer that runs every 5 minutes only if
      activated by ua-license-check.path
  * New upstream release 27.3 (LP: #1942929)
    - ros:
      + add beta support to enable ros and ros-updates
      + add support for "required services" so that esm-infra and esm-apps
        get auto-enabled when enabling ros or ros-updates
      + add support for "dependent services" so that user gets prompted to
        disable ros/ros-updates if they disable esm-infra/esm-apps
    - fips:
      + allow fips on GCP bionic now that optimized kernel is ready
      + disallow enabling fips on focal on clouds until cloud-optimized focal
        fips-certified kernel is ready (LP: #1939449, LP: #1939932)
      + print warning about generic fips kernel if cloud-id fails
    - cloud:
      + rely only on cloud-id to determine cloud type (LP: #1940131)
      + catch errors when determining cloud type
        (LP: #1938207, LP: #1944676) (GH: #1541)
    - azure:
      + bump IMDS API version to support Azure published images
    - cli:
      + collect-logs command that creates a tar file with debug-relevant logs
        and status info (GH: #463)
      + clean locks on exceptions more thoroughly to avoid false "Operation in
        progress" status messages
      + retain past service state after detach
      + shows better error message when a port value in a proxy is invalid
    - non-unicode locale support:
      + remove unicode-only characters from help file
      + don't print unicode-only characters in ua fix if non-utf8 locale
        (GH: #1463)
    - logrotate:
      + add logrotate functionality for ubuntu-advantage-timer.log.
      + Fix root:root logrotate permissions.
    - ua-timer.timer:
      + introduce a single systemd timer to handle ua recurring jobs
      + timer runs every 2 hours to support most frequent timer job
      + recurring job intervals are configurable in uaclient.conf
      + individual jobs are disabled if their interval is set to 0
      - status job:
        + update ua status every 12 hours
      - messaging job:
        + update APT/MOTD ESM messaging every 6 hours
      - metering job:
        + disabled until infrastructure is ready
        + for attached machines only, periodically update contract server with
          status information for proper contract metering
    - ua-license-check.timer:
     ...

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-advantage-tools - 27.3~21.10.1

---------------
ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium

  * d/tools.postinst:
    - consider cloud to be "none" on any cloud-id error
    - purge old ua-messaging.timer/service files
    - keep ua-timer.timer disabled if ua-messaging.timer was disabled by
      the user
    - properly configure both ubuntu-advantage-timer and
      ubuntu-advantage-licence-check logs
  * d/tools.postrm:
    - remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs
      during purge
  * systemd:
    - remove ua-messaging.timer/service
    - add new ua-timer.timer that runs every 6 hours
    - add new ua-license_check.timer that runs every 5 minutes only if
      activated by ua-license-check.path
  * New upstream release 27.3 (LP: #1942929)
    - ros:
      + add beta support to enable ros and ros-updates
      + add support for "required services" so that esm-infra and esm-apps
        get auto-enabled when enabling ros or ros-updates
      + add support for "dependent services" so that user gets prompted to
        disable ros/ros-updates if they disable esm-infra/esm-apps
    - fips:
      + allow fips on GCP bionic now that optimized kernel is ready
      + disallow enabling fips on focal on clouds until cloud-optimized focal
        fips-certified kernel is ready (LP: #1939449, LP: #1939932)
      + print warning about generic fips kernel if cloud-id fails
    - cloud:
      + rely only on cloud-id to determine cloud type (LP: #1940131)
      + catch errors when determining cloud type
        (LP: #1938207, LP: #1944676) (GH: #1541)
    - azure:
      + bump IMDS API version to support Azure published images
    - cli:
      + collect-logs command that creates a tar file with debug-relevant logs
        and status info (GH: #463)
      + clean locks on exceptions more thoroughly to avoid false "Operation in
        progress" status messages
      + retain past service state after detach
      + shows better error message when a port value in a proxy is invalid
    - non-unicode locale support:
      + remove unicode-only characters from help file
      + don't print unicode-only characters in ua fix if non-utf8 locale
        (GH: #1463)
    - logrotate:
      + add logrotate functionality for ubuntu-advantage-timer.log.
      + Fix root:root logrotate permissions.
    - ua-timer.timer:
      + introduce a single systemd timer to handle ua recurring jobs
      + timer runs every 2 hours to support most frequent timer job
      + recurring job intervals are configurable in uaclient.conf
      + individual jobs are disabled if their interval is set to 0
      - status job:
        + update ua status every 12 hours
      - messaging job:
        + update APT/MOTD ESM messaging every 6 hours
      - metering job:
        + disabled until infrastructure is ready
        + for attached machines only, periodically update contract server with
          status information for proper contract metering
    - ua-license-check.timer:
      + only runs on LTS GCP instances that are not attached
      + runs every 5 minutes to check if gcp instance has license r...