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:
No package or package groups or module_streams visible in contents count of products package, only errata's are visible. 


Version-Release number of selected component (if applicable):
Satellite 7.0.0 Snap 3.0

How reproducible:
Always

Steps to Reproduce:
1. Add custom repos under any products or enable CDN repos
2. Navigate to Content -> Products -> Select Product -> Select from Content column or select repo and check content counts column

Actual results:
No package or package groups or module_streams are visible 

Expected results:
Packages or package groups or module_streams should be visible 

Additional info:

Hi Guarav, 

Were the repositories synced or content uploaded to them?

Thanks!

Closing this BZ as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2042848 which is being tracked for 7.0.

*** This bug has been marked as a duplicate of bug 2042848 ***