Bug 1919321 - Satellite doesn't treat enabled RH repositories as enabled when they have a wrong arch set
Summary: Satellite doesn't treat enabled RH repositories as enabled when they have a w...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Cole Higgins
URL:
Whiteboard:
: 2118248 (view as bug list)
Depends On:
Blocks: 1907978
TreeView+ depends on / blocked
 
Reported: 2021-01-22 15:27 UTC by Evgeni Golov
Modified: 2023-07-31 17:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-06 11:22:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
redhat repositories page showing the issue (175.96 KB, image/png)
2021-01-22 15:27 UTC, Evgeni Golov
no flags Details

Description Evgeni Golov 2021-01-22 15:27:11 UTC
Created attachment 1749823 [details]
redhat repositories page showing the issue

Description of problem:
Red Hat repositories (on the CDN) have "substitutions" (usually basearch and releasever) to allow one repository URL definition to cover multiple versions of the product.
Some products only use a subset of these substitutions: e.g. RHEL8 uses releasever but not basearch.

Katello before 3.16 (Satellite 6.8) used to still set basearch=x86_64 on RHEL8 repositories. This was fixed in https://projects.theforeman.org/issues/28644, but there was no cleanup of old data done. Thus there are users who have enabled such repositories with the old (wrong) set of substitutions.

This is technically not bad, Katello/Pulp still can sync those just fine and serve them to clients.

However, those repos aren't marked as "enabled" when you pull the repository_sets/:id/available_repositories API endpoint, as e.g. done by the /redhat_repositories page or the redhat.satellite.repository_set Ansible module.

In both cases the user is led to believe that the repository is not yet enabled and will receive an error (from Pulp: "Relative URL [ORG/Library/content/dist/rhel8/8/x86_64/baseos/os] for repository [5f6c44b3-bde6-4e63-ab62-1ad877206480] conflicts with existing relative URL [ORG/Library/content/dist/rhel8/8/x86_64/baseos/os] for repository [18b0c24f-ae48-41b0-8157-997af90694a6]") when trying to enable it.

I think the data needs some cleanup, correcting the arch and name of the root repository to match.

Version-Release number of selected component (if applicable):
6.7.5, 6.8.2, 6.9.0 snaps.


How reproducible:
100%

Steps to Reproduce:
1. install 6.7.x
2. enable RHEL8 basos repo
3. 

Actual results:
see baseos repo still under "available" (and under enabled)

Expected results:
baseos repo is ONLY shown under enabled


Additional info:
this might be related to BZ#1316167 and BZ#1724807

Comment 1 Evgeni Golov 2021-01-22 15:31:31 UTC
in https://projects.theforeman.org/issues/28555 we initially discussed there is no migration needed -- I am not that sure anymore :)

Comment 2 Brad Buckingham 2023-02-01 19:24:14 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 3 Brad Buckingham 2023-03-06 11:22:23 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 4 Eric Helms 2023-07-31 17:24:03 UTC
*** Bug 2118248 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.