Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: ubuntu-advantage charm successfully enables pro esm repos, but returns exit code 2 #3374

Open
ethanmye-rs opened this issue Dec 17, 2024 · 0 comments
Assignees
Labels
bug something isn't working

Comments

@ethanmye-rs
Copy link
Member

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:

  • Ubuntu release: "22.04.5 LTS (Jammy Jellyfish)"
  • Pro Client version: 34~22.04

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

@ethanmye-rs ethanmye-rs added the bug something isn't working label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants