Cannot use charmcraft login
Metadata
Current evaluation
Login failed over SSH ('Prompt dismissed'). Maintainer closed it pointing to Charmhub discourse instructions for authenticating in remote environments; no code change.
Resolution: closed not a bug
Reason: facundobatista closed the issue with a single comment linking the 'How to authenticate charmcraft in remote environments' Discourse guide, indicating the interactive browser-less login flow simply does not apply to headless SSH sessions rather than a charmcraft defect. No fixing PR or commit was referenced.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Login failed over SSH ('Prompt dismissed'). Maintainer closed it pointing to Charmhub discourse instructions for authenticating in remote environments; no code change. | |
| stealth/space-bunny-alpha | — | closed not a bug | Login failed over SSH with "Prompt dismissed"; maintainer closed it pointing to Charmhub discourse instructions for remote-environment authentication — no code fix. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed as an authentication-workflow issue: the maintainer linked remote-environment login instructions for SSH users; no code fix was cited. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as a support request. The SSH login failure was resolved by directing the user to official documentation for remote authentication. No code changes were required. | |
| qwen/qwen3.6-35b-a3b | — | — | charmcraft login failures over SSH were closed. Maintainers directed the user to official documentation for remote authentication, confirming the prompt dismissal error stems from standard SSH session limitations rather than a code defect. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as a usage issue. Maintainer directed the author to official documentation for authenticating charmcraft in remote SSH environments, resolving the prompt dismissal error. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#672
(confidence 80%)
Prior report of login failing on a host with no usable keyring; workaround there was exported CHARMCRAFT_AUTH credentials, the same remote/headless authentication scenario.
-
Related To:
canonical/charmcraft#192
(confidence 45%)
Discusses the design of the `charmcraft login` command, whose interactive-only behaviour makes it unusable over SSH.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #672 charmcraft 1.4.0: impossible to login to charmhub | charmcraft | closed | Closed as intended behavior: the headless remote host had no local keyring, so Charmcraft could not persist credentials; exporting credentials was the supported workaround. | |
| #759 charmcraft login produces an error | charmcraft | closed | Closed as superseded by #833, which improved the double-login error and recommended `charmcraft logout`; the follow-up was resolved by merged PR #916. | |
| #725 craft-store error when using `charmcraft login` command | charmcraft | closed | Confusing craft-store "Credentials found" error on `charmcraft login` (double login). Closed by facundobatista as tracked in the more specific #833, whose improved error landed via PR #916. | |
| #668 `charmcraft status` should work without needing to log in | charmcraft | closed | Closed by facundobatista (2022-02-16) as out of Charmcraft's hands: `status` is backed by Charmhub APIs, which require authentication. No code change made; login remains mandatory. | |
| #901 Charmcraft login on remote device has unhelpful error message | charmcraft | closed | Superseded by canonical/craft-store#58 and fixed there through PR #390 (d87f1bd), which converts keyring initialization failures into KeyringUnlockError. | |
| #719 [1.5.0] Charmcraft login not finding keyring | charmcraft | closed | Closed as a headless keyring/session configuration issue; running Charmcraft in dbus-run-session with gnome-keyring unlocked made login succeed. No code fix was recorded. | |
| #810 Confusing output from `charmcraft login` | charmcraft | closed | Superseded by #833 and resolved by merged PR #916, which clarified that stored credentials may be invalid and advised users to log out before logging in again. |