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:

I was running through the following instructions:

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/Installation_Guide/Adding_Environments_to_a_Satellite_Node.html

specifically section 5.4. I missed this part:

" Log in to the Satellite Server CLI as root.
Choose the desired Red Hat Satellite Capsule Server from the list and take note of its id:

# hammer capsule list
"

I was trying to run hammer on the Capsule vs Satellite. 

Thought I would would be good to more clearly state that hammer commands are to be run on the Satellite Server. Possibly a boldface comment or more clearly stated as a note, 

Note: All of the following hammer commands are run on the Satellite Server, not the Satellite Capsule Server.

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.

Hi Shannon,

Thanks for the feedback. I put in "step 1" to make it clear that it was on the Sat Server instead of the Capsule but if that is being skipped and a more visible statement needs to be made, I might add a "note" or "important" to that section to make it clearer. 

Does that work for you?

Cheers,
Athene

This was delivered with Satellite 6.0 which was released on 10 September 2014.