← Back to issue list

charmcraft revisions <bundle> fails with "Name juju-qa-bundle-test not found in the charm namespace"

View original Github issue

Metadata

Project
charmcraft
Number
#851
Type
issue
State
closed
Author
hmlanigan
Labels
—
Created
Updated
Closed

Current evaluation

Closed without a code fix after the intermittent Charmhub lookup error could not be reproduced under Charmcraft 3; maintainers suspected a server-side glitch.

Resolution: closed stale

Reason: No resolving PR or commit was linked. A maintainer explained that revisions queries Charmhub independently of the local project and asked for a Charmcraft 3 reproducer; none was provided before the report became inactive.

Evaluated by: mr-cal-bot

No scores available.

Issue body

$ charmcraft revisions juju-qa-bundle-test Store operation failed: - resource-not-found: Name juju-qa-bundle-test not found in the charm namespace Full execution log: 'charmcraft-20220830-182951.089271.log' However I'm working on a bundle $ cat charmcraft.yaml type: bundle parts: bundle: prime: ["bundle.yaml", "README.md"] charmhub: api-url: https://api.charmhub.io storage-url: https://storage.snapcraftcontent.com Remembered about the cache, tried to clean: $ charmcraft clean Cannot read the metadata.yaml file: FileNotFoundError(2, 'No such file or directory') Full execution log: 'charmcraft-20220830-190538.160272.log' Switched to a charm directory and was able to successfully run charmcraft clean. Switched back to the bundle directory then: $ charmcraft revisions juju-qa-bundle-test Revision Version Created at Status 2 2 2021-03-26T19:22:11Z released 1 1 2021-03-22T17:57:22Z approved

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed stale Closed without a code fix after the intermittent Charmhub lookup error could not be reproduced under Charmcraft 3; maintainers suspected a server-side glitch.
stealth/space-bunny-alpha — closed stale No code fix was made: the intermittent Charmhub “not found” response disappeared, and the error could not be reproduced under Charmcraft 3; #851 was closed pending a new reproducer.
qwen3.6-35b-a3b-mtp-q6 — — Closed as a transient Charmhub service glitch. The error resolved spontaneously and could not be reproduced in Charmcraft 3. Issue remains closed pending a new reproducer if the behavior persists.
qwen/qwen3.6-35b-a3b — — Closed as a transient Charmhub API glitch. Maintainers confirmed the command queries the store directly and cannot reproduce it in Charmcraft 3. No code changes were made; closed pending a Charmcraft 3 reproducer if it persists.
qwen3.6-35b-a3b-mtp-q6 — — Closed as unreplicable. Maintainers attributed the transient error to a Charmhub service glitch. The issue was closed after failing to reproduce in Charmcraft 3, with a request to reopen if it persists with a new reproducer.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#2233 charmcraft should complain if the charm contains a bundle charmcraft open Feature request: charmcraft pack should error/warn when the produced charm contains a bundle.yaml, since juju deploy then deploys the bundle instead of the charm. Clear repro, but no maintainer triage or labels.
70%