Bug 1344391

Summary: Unable to disable orphaned repositories
Product: Red Hat Satellite Reporter: jcallaha
Component: RepositoriesAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, dmoessne, greartes, jcallaha, jentrena, mdekan, mmccune, oshtaier, pierre-yves.goubet, tomckay
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: 2018-02-21 16:46:52 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:
Attachments:
Description Flags
Red Hat Products
none
verification screenshot none

Description jcallaha 2016-06-09 14:33:25 UTC
Created attachment 1166332 [details]
Red Hat Products

Description of problem:
After deleting a manifest (or allowing subscriptions to expire), any orphaned RH repositories can no longer be disabled. See attached image.

Version-Release number of selected component (if applicable):
Satellite 6.2 Beta Snap 15

How reproducible:
Always

Steps to Reproduce:
1. Upload a manifest that provides at least one RH product/repo.
2. (Optional) Synchronize the product/repo.
3. Delete the manifest.
4. Attempt to disable the repository.

Actual results:
There is no way to disable an orphaned product/repo.

Expected results:
At least one method is provided to disable the orphaned product/repo.

Comment 1 Brad Buckingham 2016-06-10 14:21:54 UTC
Hi Jake, after deleting the manifest, did you still see the product and repository listed on Content -> Products?

If so, was the repository published in any content views?

Comment 2 jcallaha 2016-06-13 18:06:36 UTC
Brad,

  I do still see the products and repos listed under products. All products were in content views, but have since been removed and those republished.

Comment 3 Brad Buckingham 2016-06-20 21:16:28 UTC
Hi Tom,  is this expected behavior for manifest deletion?

Comment 4 Bryan Kearney 2016-07-26 18:56:04 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 5 Tom McKay 2016-12-12 13:24:54 UTC
Connecting redmine issue http://projects.theforeman.org/issues/17607 from this bug

Comment 6 Tom McKay 2016-12-12 13:25:41 UTC
associated w/ upstream issue

Comment 9 Satellite Program 2017-01-14 01:01:30 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17607 has been resolved.

Comment 13 jcallaha 2017-06-30 19:45:59 UTC
*** Bug 1466425 has been marked as a duplicate of this bug. ***

Comment 14 jcallaha 2017-08-10 20:14:25 UTC
Verified in Satellite 6.3 Snap 10.

After I removed the manifest, that provided the repos, and removed the content view they were published to; I was able to disable the no-orphaned repos. Before the content view was removed, the repos were grayed out, and could not be disabled. See attached screenshot for verification.

Comment 15 jcallaha 2017-08-10 20:15:06 UTC
Created attachment 1311901 [details]
verification screenshot

Comment 17 Bryan Kearney 2018-02-21 16:42:44 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, 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-2018:0336

Comment 18 Bryan Kearney 2018-02-21 16:46:52 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, 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-2018:0336

Comment 19 Satellite Program 2018-02-21 16:51:07 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, 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-2018:0336