← Back to issue list

The Status command confuses branches between architectures

View original Github issue

Metadata

Project
charmcraft
Number
#834
Type
issue
State
closed
Author
facundobatista
Labels
—
Created
Updated
Closed

Current evaluation

Closed as a Charmhub backend issue. The status command incorrectly duplicates branch entries across architectures due to server-side data handling. No charmcraft fix was implemented; the team deferred resolution to the upstream server bug.

Suggested action: —

No scores available.

Issue body

When the charm is multi-architecture, and a branch is created, e.g. ``` charmcraft release testfacu-charm -r 1 --channel=edge/branch123 ``` ...there will be a branch for each architecture. Example of the channel map (after also releasing just to `edge`): ``` $ env/bin/python -m charmcraft status testfacu-charm Track Base Channel Version Revision Expires at latest ubuntu 18.04 (amd64) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (arm64) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (armhf) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (i386) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (powerpc) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (ppc64el) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (riscv64) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (s390x) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ``` However, Charmcraft is confused because Charmhub returns the 7 releases to branches (one for each architecture) and when building the map that architecture is not verified and then all 7 releases appear for each architecture. This is what is currently producing (wrong!): ``` Track Base Channel Version Revision Expires at latest ubuntu 18.04 (amd64) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (arm64) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (armhf) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (i386) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (powerpc) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (ppc64el) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (riscv64) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ubuntu 18.04 (s390x) stable - - candidate - - beta - - edge 1 1 edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z edge/branch123 1 1 2022-09-17T00:00:00Z ```

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6 — — Closed as a Charmhub backend issue. The status command incorrectly duplicates branch entries across architectures due to server-side data handling. No charmcraft fix was implemented; the team deferred resolution to the upstream server bug.
qwen/qwen3.6-35b-a3b — — Closed as an upstream Charmhub API bug. The status command duplicated branch entries across architectures due to unfiltered API data. No client-side fix was applied; resolution depends on upstream correction.
qwen3.6-35b-a3b-mtp-q6 — — Closed as a Charmhub backend bug. The status command incorrectly duplicates branch releases across architectures by failing to filter by base. No charmcraft-side fix was applied; resolution requires backend remediation.
qwen3.6-35b-a3b-mtp-q6 — — Closed as a Charmhub backend issue. The status command duplicates branch entries across architectures due to unfiltered API responses. Reported upstream and deferred pending a Charmhub fix or charmcraft workaround.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#2007 `status` command has wrong headers charmcraft open charmcraft status command displays 'Channel' header instead of 'Risk' and omits a Branch column when branch releases exist. Reported by a maintainer, synced to Jira (CRAFT-3717), but no fix has landed in the codebase as of the latest commit.
75%
#915 (charmhub) Don't show repeated branches in Status command results (CRAFT-1270). charmcraft merged Merged fix that removes duplicate branches from charmhub Status command output. Resolves #834 and CRAFT-1270. Approved by one reviewer, changing two files with 55 additions and 2 deletions.
72%