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.
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?
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.
Hi Tom, is this expected behavior for manifest deletion?
Moving 6.2 bugs out to sat-backlog.
Connecting redmine issue http://projects.theforeman.org/issues/17607 from this bug
associated w/ upstream issue
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17607 has been resolved.
*** Bug 1466425 has been marked as a duplicate of this bug. ***
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.
Created attachment 1311901 [details] verification screenshot
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
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