pro attach `Unexpected error(s) occurred`
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-advantage-tools (Ubuntu) |
Triaged
|
Undecided
|
Unassigned |
Bug Description
pro attach $TOKEN has failed with `Unexpected error(s) occurred.`
For more details, see the log: /var/log/
To file a bug run: ubuntu-bug ubuntu-
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-
ubuntu-
Installed: 30~20.04
Candidate: 30~20.04
Version table:
*** 30~20.04 500
500 http://
100 /var/lib/
20.3 500
500 http://
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 5.4.0-172-generic aarch64
ApportVersion: 2.20.11-
Architecture: arm64
CasperMD5CheckR
Date: Fri Mar 1 23:28:39 2024
SourcePackage: ubuntu-
UpgradeStatus: No upgrade log present (probably fresh install)
cloud-id.txt: maas
livepatch-
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:/
log_level: debug
tags: | removed: need-arm64-retrace |
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.