← Back to issue list

Include charm revision for upload errors of type already exists in database

View original Github issue

Metadata

Project
charmcraft
Number
#826
Type
issue
State
open
Author
hemanthnakkina
Labels
Created
2022-08-11 09:20:17+00:00
Updated
2025-08-15 15:18:33+00:00
Closed

Current evaluation

No evaluation has been recorded for this issue yet.

Issue body

Is it possible to include charm revision as well if a charm upload fails with error message that says the package already exists in the database? Details: Uploaded a charm which resulted in Gateway Timeout ``` charmcraft upload --release latest/edge --name horizon-k8s horizon-k8s_ubuntu-20.04-amd64.charm Issue encountered while processing your request: [504] Gateway Time-out. Full execution log: '/home/hemanth/snap/charmcraft/common/cache/charmcraft/log/charmcraft-20220810-114700.938763.log' ``` Re-uploaded the charm which resulted in error with message package already exists. ``` charmcraft upload --release latest/edge --name horizon-k8s horizon-k8s_ubuntu-20.04-amd64.charm Upload failed with status 'rejected': - review-error: Cannot insert package. An upload with that digest (SHA3-384: '7058526548d07e54d68d8b19f23b89eb9697c3da543e4ab1f207e24f7399aeb214e0671086f9524730181844d993f6ba') already exists in the database. ``` Charmcraft CLI does not provide any mapping of charm revisions with the SHA. How to get the revision number of the charm that is just uploaded? Otherwise the simplest mechanism is to include the revision number in the error message that says 'already exist in the database'. Thoughts?

Evaluation history

No evaluation history available.