Bug 1973329

Summary:	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
Product:	Red Hat Satellite	Reporter:	Taft Sanders <tasander>
Component:	Content Views	Assignee:	Ryan Verdile <rverdile>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.9.0	CC:	ahumbe, bfinger, iballou, jsherril, osousa, paji, pdwyer, rverdile, sadas, saydas
Target Milestone:	6.12.0	Keywords:	PrioBumpGSS, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2103123 (view as bug list)		Environment:
Last Closed:	2022-11-16 13:32:43 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 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