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.

Description of problem:
When pressing the "puppet modules" tab of a content-view, the satellite UI will first show a message saying that there are no puppet modules in this content view and then, after a few seconds, it will suddenly list the modules. 
This message is highly confusing, a "Loading" message would be better

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

How reproducible:
Every time

Steps to Reproduce:
1. Go to https://satellite6ga.lab.arn.redhat.com/content_views/5/puppet_modules
2. Hit the "puppet modules" tab
3. See the confusing message that first tells you there are no modules. After a few seconds, the message goes away and instead lists the modules as expected.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Created redmine issue http://projects.theforeman.org/issues/7939 from this bug

PR:  https://github.com/Katello/katello/pull/4745

(In reply to Walden Raines from comment #4)
> PR:  https://github.com/Katello/katello/pull/4745

Reopened PR against bastion:  https://github.com/Katello/bastion/pull/16

Moving to POST since upstream bug http://projects.theforeman.org/issues/7939 has been closed
-------------
Walden Raines
Applied in changeset bastion:commit:bastion|ca275139e3bf15cf358be3723090604b7ceb3e60.

Created attachment 991274 [details]
the screenshot which shows now 'working' instead of the earlier message

VERIFIED with Satellite6.1 Beta SNAP2

This bug is slated to be released with Satellite 6.1.

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-2015:1592