Bug 1590404

Summary: Removing subscription from manifest still shows repos to enable
Product: Red Hat Satellite Reporter: Tom McKay <tomckay>
Component: RepositoriesAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: high Docs Contact:
Priority: unspecified    
Version: NightlyCC: cduryee, egolov, jsherril, pcreech
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.7.0.23-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:31:44 UTC Type: ---
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
verification screenshot none

Description Tom McKay 2018-06-12 14:50:45 UTC 
For my test:

+ import manifest w/ satellite subscription
+ enable and sync satellite rpms repo
+ refresh manifest from portal where satellite subscription had been removed
+ confirm that satellite repos are no longer listed to enable
+ confirm that the previously enabled repo is still present
+ confirm that the previously enabled repo is marked as "orphaned" in some way

These last three _confirm_ steps are broken.
Comment 1 Tom McKay 2018-06-12 14:50:48 UTC 
Created from redmine issue http://projects.theforeman.org/issues/23903
Comment 2 Tom McKay 2018-06-12 14:50:51 UTC 
Upstream bug assigned to None
Comment 4 Brad Buckingham 2018-06-12 17:05:14 UTC 
Note: from discussion in triage, it sounds like we should also confirm that user can 'disable' those repositories (if that was supported in previous versions).
Comment 5 Satellite Program 2018-07-18 16:24:05 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23903 has been resolved.
Comment 9 Peter Ondrejka 2018-08-13 08:29:11 UTC 
Sorry for delay (pto). Filing a separate bug for the hammer issue here https://bugzilla.redhat.com/show_bug.cgi?id=1615272

As per comments 6 and 8, moving this bz to assigned with a request to add an UI indication that a repository is "orphaned"

Cheers
Comment 11 Peter Ondrejka 2018-09-13 13:41:18 UTC 
Verification blocked on https://bugzilla.redhat.com/show_bug.cgi?id=1618485
Comment 12 Peter Ondrejka 2018-09-18 15:05:17 UTC 
Created attachment 1484409 [details]
verification screenshot
Comment 13 Peter Ondrejka 2018-09-18 15:05:50 UTC 
Verified on Sat 6.4 snap 22
Comment 14 Bryan Kearney 2018-10-16 19:31: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:2927