← Back to issue list

[Documentation] What to do when api-error: Resource doesn't have a released revision on channel

View original Github issue

Metadata

Project
charmcraft
Number
#877
Type
issue
State
closed
Author
erik78se
Labels
—
Created
Updated
Closed

Current evaluation

Closed as expected behavior: every declared Charmhub resource must have a released revision. The maintainer annotated the docs and filed snapstore-server#1990845 to improve the unclear API error.

Resolution: closed not a bug

Reason: The closing maintainer comment clarified that resources are mandatory and that the release command must include the resource. It also linked the improved release-time resource documentation and upstream error-reporting bug snapstore-server#1990845.

Evaluated by: mr-cal-bot

No scores available.

Issue body

I was trying to release a charm to charmhub, but slammed into an error to which there is no clue on what I'm supposed to do. I'm just getting confused with this error. I would suggest provide details to a user as how to resolve this issue rather than leaving me in the dark. ![image](https://user-images.githubusercontent.com/850603/192086787-66afc596-20a9-4398-9d6e-8ef25d8b8dc2.png) What should a user do when hit with this error? There is no information in the docs about this situation either here: https://juju.is/docs/sdk/charmcraft-release

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed not a bug Closed as expected behavior: every declared Charmhub resource must have a released revision. The maintainer annotated the docs and filed snapstore-server#1990845 to improve the unclear API error.
stealth/space-bunny-alpha — closed not a bug Closed as working as designed: declared resources must be attached at release; docs were clarified and the unclear Charmhub error was tracked separately.
stealth/space-bunny-alpha — closed not a bug Closed as expected behavior: resources are mandatory. Maintainer facundobatista explained the error origin, filed snapstore-server bug #1990845 to improve the Charmhub error text, annotated the doc page, and closed the issue.
stealth/space-bunny-alpha — closed not a bug Closed as expected behavior: resources are mandatory. The maintainer clarified the release requirement, annotated the documentation, and filed Charmhub bug #1990845 for clearer errors.
stealth/space-bunny-alpha — closed not a bug Closed as expected behavior: charm metadata resources are mandatory. The resource-release documentation was updated, and Launchpad bug #1990845 was filed to improve Charmhub's error message.
stealth/space-bunny-alpha — closed not a bug Closed as expected behavior: metadata resources are mandatory, so a release needs a matching resource in that channel. Docs were updated, and snapstore-server#1990845 tracks better error messaging.
stealth/space-bunny-alpha — closed not a bug Documentation was updated to explain missing resources; the unclear Charmhub error was tracked upstream as Launchpad bug #1990845.
qwen3.6-35b-a3b-mtp-q6 — — Closed. Resources are mandatory in metadata; the error occurs when Charmhub cannot find a previously released resource. Documentation was updated to explain this, and an upstream bug was filed to improve the error message.
qwen/qwen3.6-35b-a3b — — Closed. Clarified that metadata resources are mandatory, and the error occurs when Charmhub lacks a previously released revision on the channel. Documentation was updated, and a separate issue was opened to improve the upstream error message.
qwen3.6-35b-a3b-mtp-q6 — — Closed. Clarified resources are mandatory if declared in metadata. The error occurs when Charmhub lacks a previously released revision. Documentation was updated, and an upstream issue was opened to improve the error message.

Update history

No update history recorded yet.

Related work

  • Related To: snapstore-server#1990845 (confidence 100%)

    Charmhub-side bug filed to improve the unclear missing-resource-revision API error.

Related issues

Issue Project State Summary Similarity
#2866 docs: Document that resources are bound to channels, not revisions. charmcraft open Docs request: clarify resources bind to channels, not revisions, since 'charmcraft release --resource' help text implies per-revision pinning. Behavior is correct; misleading docs/help only. No maintainer response yet.
71%