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.

Create an empty Organization context and navigate to "Monitor -> Dashboard"

You will see links near the bottom of the page that link to non-existent upstream pages:

"""
Import your data

Foreman comes with some importers to ease the burden of entering loads of data about your current installation. If you are already using puppet you should consider using some of the rake tasks that have been provided.

    Inventory browser - Importing Puppet Facts
    Puppet External Nodes - Importing Puppet classes and environments
    Reporting - Puppet Reports integration
"""

they each go to:

http://www.theforeman.org/manuals/1.6/index.html#3.5.5FactsandtheENC
http://theforeman.org/projects/foreman/wiki/External_Nodes
http://www.theforeman.org/manuals/1.6/index.html#3.5.4PuppetReports

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.

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