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.

Created attachment 1150282 [details]
UI doesn't show the content count under content, immediately after publish/promote

Description of problem: I published a content-view with couple of custo and RHEL repos. However, UI doesn't show the content count under content, immediately after publish/promote contents.

If I navigate to other tab and come back, I can see the count.


Version-Release number of selected component (if applicable):
sat6.2 beta snap9.2

How reproducible:


Steps to Reproduce:
1. create a CV
2.  publish/promote
3.

Actual results:
UI doesn't show the content count under content, immediately after publish/promote contents. Content count shows only if user navigate to other page and come back on same page.

Expected results:
UI should show content count immediately after publish/promote

Additional info:

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