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.

1.  Create a product
2.  Create a repo with some errata that can be applicable
3.  Register a system and assign the product with errata, run sub-man refresh, yum repolist
4.  Notice errata are applicable
5.  re-register the client using 'subscription-manger register --force'
6.  Assign it to the same product
7.  run sub-man refresh adn yum repolist
8.  errata do not show up

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

Upstream bug assigned to jsherril

This is needed for 6.2.11 as it is exposed by https://bugzilla.redhat.com/show_bug.cgi?id=1445403

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

Verified in Satellite 6.2.11 Snap 1

I followed the steps outlined in the initial report. After the intial registration and errata applicability, the content host had a total of 387 errata install-able. After the force re-registration and subsequent errata process, the host still had all 387 available.

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/RHBA-2017:2466