Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1928998

Summary: Getting "Repository not found" error when disabling RHEL 8 repositories on Satellite 6.8
Product: Red Hat Satellite Reporter: Hao Chang Yu <hyu>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: ajambhul, ankulkar, francesco.trentini, iballou, momran, pdwyer, saydas
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-04 21:29:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hao Chang Yu 2021-02-16 00:02:02 UTC
Description of problem:
Can't disable a rhel 8 repository on Satellite 6.8 if it was enabled on older Satellite version (Satellite 6.6 and older). This issue is caused by incorrect arch that Satellite uses to resolve all RHEL 8 repos. The database is storing "x86_64" but Satellite is looking for "noarch" when disabling the repository. Therefore, "Repository not found" error is raised. This is affecting the RHEL 8 repositories that were enabled on older Satellite version (Satellite 6.6 and older). When enabling a RHEL 8 repository, the older Satellite version will set its arch to "x86_64". However, Satellite 6.8 will set its arch to "noarch".

Steps to Reproduce:
1. Enable a rhel 8 repository on Satellite 6.6, such as rhel 8 baseos or appstreams
2. Upgrade the Satellite to 6.8
3. Disable the rhel 8 repository

Actual results:
Repository not found

Expected results:
Repository can be disabled successfully

Additional info:

This issue can be workaround by changing the root repo's arch from x86_64 to noarch.

foreman-rake console
Katello::RootRepository.where(name: ["Red Hat Enterprise Linux 8 for x86_64 - BaseOS RPMs x86_64 8", "Red Hat Enterprise Linux 8 for x86_64 - AppStream RPMs x86_64 8", "Red Hat Satellite Tools 6.7 for RHEL 8 x86_64 RPMs x86_64"]).update_all(arch: "noarch")
exit

Comment 1 Sayan Das 2022-03-16 12:18:57 UTC
This seems the same scenario as explained in 

1973329 – Provide upstream repository name value to allow a name change on the repository to not break Satellite if an enabled repository's name gets changed
https://bugzilla.redhat.com/show_bug.cgi?id=1973329


Hello Hao, Can you please check in https://bugzilla.redhat.com/show_bug.cgi?id=1973329#c4 and confirm the same ?


I guess, It would be best to have just one of the BZs alive and worked on if the end goal is the same.




-- Sayan

Comment 5 Brad Buckingham 2023-09-01 21:10:52 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 6 Brad Buckingham 2023-10-04 21:29:50 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 7 Red Hat Bugzilla 2024-02-02 04:25:02 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days