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 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
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
high
Target Milestone: 6.12.0
Assignee: Ryan Verdile
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-17 16:13 UTC by Taft Sanders
Modified: 2023-07-03 13:11 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2103123 (view as bug list)
Environment:
Last Closed: 2022-11-16 13:32:43 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-03-01 16:25:23 UTC
Red Hat Issue Tracker SAT-7991 0 None None None 2022-08-26 20:57:33 UTC
Red Hat Knowledge Base (Solution) 6301451 0 None None None 2021-09-22 09:22:42 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:32:52 UTC

Description Taft Sanders 2021-06-17 16:13:05 UTC 
Description of problem:
With a name change to a repository that is enabled on a Satellite comes a great number of issues like:
- Manual manifest refresh is needed for updated subscriptions
- Manual removal of the repository from all content views are needed
- Manual removal of the repository is needed
- Manual enablement and sync of the new repository
- Manual implementation to each content view where the repository was previously included
- Publish and promotion of each content view with a newly added repository name

Version-Release number of selected component (if applicable):
Red Hat Satellite 6

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Red Hat repository names/lables are not editable items on Satellite. Any name change to a repository that has a matching URL requires the process mentioned above.

Expected results:
Red Hat repository name changes should happen without interruption to the Satellite user.

Additional info:
Comment 1 Brad Buckingham 2021-06-18 13:32:14 UTC 
Moving from Pulp to Content Views component.  This may not be the best component; however, there really isn't one that will address all of the areas impacted.
Comment 9 Justin Sherrill 2022-02-23 18:47:50 UTC 
clearing need info as i think engineering has enough to fix, we are going to make sure a user can always disable these repos.
Comment 11 Brad Buckingham 2022-03-01 16:25:24 UTC 
Associating upstream redmine and moving to POST as the upstream PR is merged.
Comment 15 Lai 2022-07-22 18:36:38 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.12.0 snap 3
Comment 20 errata-xmlrpc 2022-11-16 13:32:43 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 (Important: Satellite 6.12 Release), 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/RHSA-2022:8506
Note You need to log in before you can comment on or make changes to this bug.