Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

When one promotes a Docker Repository from Archive to Library, the tags are not getting cleared out while the Manifests are.

1) Sync busybox (you should see around 75 tags and over 130 manifests)
2) Create a Content View pointing to this Busybox repo
3) Publish the CV
4) Goto Version 1.0 -> Docker Repositories
you should see Tag count for Library and Archive repo at 75. 
5) Now create a docker filter that says "Include only glibc"
6) Publish this Content View again
7) Goto Version 2.0 -> Docker Repositories
Note the Tag count for the archive version says 4 tags while the library version still says 75

Which probably implies that promotion didn't really do its job of clearing tags in library version before copying new stuff.

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

Upstream bug assigned to None

Upstream bug assigned to paji

Upstream bug assigned to paji

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

Connecting redmine issue http://projects.theforeman.org/issues/22157 from this bug

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

Created attachment 1452841 [details]
verification screenshot

Verified on Satellite 6.4 snap 7, see the attached 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:2927