pro attach `Unexpected error(s) occurred`

[Patricia Domingues]

pro attach $TOKEN has failed with `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
Connection to 10.228.68.67 closed.

on a aarch64, Cortex-A72

ubuntu@d05-2:~$ lsb_release -rd
Description: Ubuntu 20.04.6 LTS
Release: 20.04
ubuntu@d05-2:~$

~$ apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
  Installed: 30~20.04
  Candidate: 30~20.04
  Version table:
 *** 30~20.04 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages
        100 /var/lib/dpkg/status
     20.3 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-advantage-tools 30~20.04
ProcVersionSignature: Ubuntu 5.4.0-172.190-generic 5.4.259
Uname: Linux 5.4.0-172-generic aarch64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: arm64
CasperMD5CheckResult: skip
Date: Fri Mar 1 23:28:39 2024
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
cloud-id.txt: maas
livepatch-status.txt-error: Invalid command specified '/snap/bin/canonical-livepatch status'.
pro-journal.txt:
 -- Logs begin at Tue 2024-02-20 16:20:41 UTC, end at Fri 2024-03-01 23:17:01 UTC. --
 Feb 20 16:22:57.985352 d05-2 systemd[1]: Condition check resulted in Ubuntu Pro reboot cmds being skipped.
 Feb 20 16:23:12.350305 d05-2 systemd[1]: Condition check resulted in Ubuntu Pro Background Auto Attach being skipped.
uaclient.conf:
 contract_url: https://contracts.canonical.com
 log_level: debug

[Lucas Albuquerque Medeiros de Moura (lamoura)]

Hi Patricia Domingues,

After discussing the issue with you and accessing the affected machine, it seems that the error was due to contract server being down for a short amount of time. That is because I was able to run attach on the affected machine in a later time and it worked as expected.

However, we understand that this error message is not ideal. We already have code that will improve that error message and it will be delivered on Pro client v32.

Finally, if this type of error keeps happening on your side, let us know and we can then better investigate this issue.

[Renan Rodrigo (renanrodrigo)]

We had several recent bug reports that also happened due to outages, really close to this one.
I will not mark the reports duplicates of this bug here because this one happened on arm64, but I am keeping track of this until we release the better error message.