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 2103123 - 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
Summary: Provide upstream repository name value to allow a name change on the reposito...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.9.0
Hardware: x86_64
OS: Linux
high
unspecified
Target Milestone: 6.11.1
Assignee: Ryan Verdile
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-01 13:45 UTC by Odilon Sousa
Modified: 2024-12-20 21:41 UTC (History)
10 users (show)

Fixed In Version: tfm-rubygem-katello-4.3.0.43-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1973329
Environment:
Last Closed: 2022-07-27 17:27:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34490 0 Normal Closed Red Hat Repositories have weird behavior if arch setting is changed 2022-07-01 13:45:52 UTC
Red Hat Issue Tracker SAT-3843 0 None None None 2022-07-01 13:45:52 UTC
Red Hat Knowledge Base (Solution) 6301451 0 None None None 2022-07-01 13:45:52 UTC
Red Hat Product Errata RHBA-2022:5742 0 None None None 2022-07-27 17:27:22 UTC

Comment 1 Bryan Kearney 2022-07-01 16:05:31 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34490 has been resolved.
Comment 4 Lai 2022-07-14 18:32:20 UTC 
Steps to retest:

1. Upload manifest
2. On CLI, enable several repos with --basearch "x86_64"
3. Run db command to check the 'arch' of each enabled repo
4. Disabled and re-enabled the repos again on UI
5. Recheck db for the 'arch' column of each re-enabled repo

Expected:
Repos should still be able to be disabled and re-enabled without issues

Actual:
Repos are disabled and re-enabled on the UI without issues.  This is true even if it's x86_64 or has noarch.

I've tested this with both repos that has noarch and ones with x86_64 via both the CLI and UI and both can be disabled and re-enabled without issues.

Verified on 6.11.1 snap 1 with tfm-rubygem-katello-4.3.0.44-1.el7sat.noarch on rhel7 and rhel8
Comment 11 errata-xmlrpc 2022-07-27 17:27:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.11.1 Async Bug Fix Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:5742
Note You need to log in before you can comment on or make changes to this bug.