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.

Description of problem:
Sometimes the metadata and # of packages in the DB are not matching, once this is not expected, Satellite should be alerting about this somehow.

Version-Release number of selected component (if applicable):


How reproducible:
trying to reproduce this behavior, but we can see it in the customer environment.

Steps to Reproduce:
1. 
2.
3.

Actual results:
Repos with metadata and # of packages are different and no alert at all.

Expected results:
Satellite should be sending notification and/or presenting in the webUI this behavior.

Additional info:

Hello

Closing once there is no issue at the end of the day.

Thank you!!