Actions
Bug #28555
openenabling a repository set without providing a basearch yields unexpected results
Status:
New
Priority:
Normal
Assignee:
-
Category:
API
Target version:
-
Description
PUT /katello/api/products/:product_id/repository_sets/:id/enable
does not mark basearch
as required, however, when one does enable a reposet without providing the basearch, the repo is displayed as "noarch" in /katello/sync_management
(see attached screenshot)
the same does not happen when you enable that repo via the UI, as the UI will force the basearch to be set, even if the repository does not provide it in its substitutions
I think instead of the UI doing the injection, the API/controller should do it.
Files
Updated by Evgeni Golov over 5 years ago
- Related to Bug #25224: Some repositories from the CDN no longer has variants and repository page shows "Unspecified" added
Updated by Evgeni Golov over 5 years ago
- Related to Bug #25901: [Subscription] - Not able to add RHEL8 repositories into Katello added
Updated by Evgeni Golov over 5 years ago
- Related to Tracker #27680: API bugs that need workarounds in foreman-ansible-modules added
Updated by Evgeni Golov over 5 years ago
- Related to Bug #28644: inconsistent repository enabled state for RHEL8 repository sets in the API added
Updated by Jonathon Turel over 5 years ago
- Target version set to Katello 3.15.0
- Triaged changed from No to Yes
Updated by Partha Aji about 5 years ago
- Target version changed from Katello 3.15.0 to Katello Backlog
Actions