Duplicate architecture options in DOCA release catalog
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Open frontend-v2/src/components/settings/BluefieldImages.tsx around line 520 and inspect the architecture options in the Add DOCA Release form. Compare them with the amd64-to-x86_64 mapping at line 129; done means the dropdown shows only the canonical amd64 and arm64 values.
Written by the indexing model from the issue text.
Description
Description
The "Add DOCA Release" form in Catalog > DOCA Releases lists four architecture options: arm64, amd64, aarch64, x86_64. However, amd64 and x86_64 refer to the same architecture (as do arm64 and aarch64) — they are just different naming conventions
(Debian/Docker vs Red Hat/kernel).
Location
frontend-v2/src/components/settings/BluefieldImages.tsx, line 520:
{['arm64', 'amd64', 'aarch64', 'x86_64'].map((arch) => (
Impact
- Users can create duplicate DOCA release entries that differ only by arch naming convention
- The unique constraint (uq_doca_release on doca_version, host_os, host_os_version, host_arch) treats amd64 and x86_64 as distinct, allowing silent duplicates
- The URL generation logic at line 129 already maps amd64 → x86_64 for RPM paths, confirming they are equivalent
Expected behavior
The dropdown should only show two canonical values: amd64 and arm64 (matching Docker/Debian convention used throughout the codebase — Dockerfile, module code, etc.).
Fix
Change line 520 to:
{['arm64', 'amd64'].map((arch) => (
---
<sub>Migrated from `sp-prod-field/bnk-forge` **#407** (opened 2026-07-14; original labels: none). That repository is archived and read-only.
Bare `#NNN` references in the text above refer to issues and PRs in the **original** repository, not to numbering here.</sub>- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 19h 7m
- Merged PRs (30d)
- 43
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from f5devcentral/bnk-forge
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
f5devcentral/bnk-forge#218 ·
-
Document dpus/hosts kubernetes_cluster_id overloading: deploy-registration vs BNK membership (S4) Openbare-metal documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
f5devcentral/bnk-forge#117 ·
-
catalog enhancement frontend
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
f5devcentral/bnk-forge#88 ·
-
documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
f5devcentral/bnk-forge#86 ·
-
ci documentation enhancement verified
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
f5devcentral/bnk-forge#85 · 1 comment ·
All issues in f5devcentral/bnk-forge
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100