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.

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.

Created from redmine issue http://projects.theforeman.org/issues/23903

Upstream bug assigned to None

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).

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23903 has been resolved.

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

Verification blocked on https://bugzilla.redhat.com/show_bug.cgi?id=1618485

Created attachment 1484409 [details]
verification screenshot

Verified on Sat 6.4 snap 22

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