You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After attaching a token (with juju config ubuntu-advantage token=<token>), the attach fails with exit code 2. Looking at the machine itself, the pro attach seems to have worked (i.e, esm is enabled and running apt update shows the repos)
Expected behavior
If this is a partial attach (i.e a service failed on enablement) as suggested, it would be nice to know which one failed, and why, preferably at the charm level.
Current behavior
Machine fails with exit code 2, but there's no docs describing what exit code 2 actually is. The system then kicks off a retry loop, but it finds the system is already registered, see attached logs and chat.
To Reproduce
I do not have a reproducer readily available. However, if it is a failure to attach resources, then selectively blocking a resource (i.e esm, usg, livepatch, w/e) with a proxy or bad hosts entry should trigger the same issue.
Description of the bug
After attaching a token (with
juju config ubuntu-advantage token=<token>
), the attach fails with exit code 2. Looking at the machine itself, the pro attach seems to have worked (i.e, esm is enabled and running apt update shows the repos)Expected behavior
If this is a partial attach (i.e a service failed on enablement) as suggested, it would be nice to know which one failed, and why, preferably at the charm level.
Current behavior
Machine fails with exit code 2, but there's no docs describing what exit code 2 actually is. The system then kicks off a retry loop, but it finds the system is already registered, see attached logs and chat.
To Reproduce
I do not have a reproducer readily available. However, if it is a failure to attach resources, then selectively blocking a resource (i.e esm, usg, livepatch, w/e) with a proxy or bad hosts entry should trigger the same issue.
System information:
Additional context
See logs upload here, not sure if they have sensitive info, so I've marked it Canonical only in drive: https://drive.google.com/file/d/1yp-tJX5HEN3Fr4n7eEeaihedoixnKOZ3/view?usp=sharing
The text was updated successfully, but these errors were encountered: