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.

Bug 1043234

Summary: Section 6.2 Define the Satellite Server and Satellite Node clearly to avoid confusion
Product: Red Hat Satellite Reporter: Jakub Bittner <j.bittner>
Component: Docs Install GuideAssignee: Athene Chan <achan>
Status: CLOSED CURRENTRELEASE QA Contact: Megan Lewis <melewis>
Severity: medium Docs Contact:
Priority: unspecified    
Version: NightlyCC: cwelton, mmccune, mmurray
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 14370, Installation Guide-6.0-1 Build Date: 11-11-2013 14:07:51 Topic ID: 24317-552708 [Latest]
Last Closed: 2014-07-02 14:06:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jakub Bittner 2013-12-15 09:30:18 UTC
Title: Configuring a Satellite Node

Describe the issue:
In 6.2. Configuring a Satellite Node it is not easy to understand which commands has to be run on Satellite server and which on Satellite node. 
In section 6.2.5 there is sentence "Run the following commands as the root user on the Satellite server". Are you absolutely sure?

In section 6.2.4 satellite server is referred as "sat6host". I would suggest to unite reference on satellite server as satellite.examle.com and node as satellitenode.example.com across all documentation.

It is very easy to get lost in section 6.2 of Installation guide.

Comment 1 RHEL Program Management 2013-12-15 09:54:12 UTC
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.

Comment 3 Athene Chan 2013-12-23 20:53:20 UTC
Hello Jakub,

Thank you for your feedback! We'll re-evaluate the section for Satellite nodes and implement changes in the documentation on the next MDP release. I'll update this ticket once the changes have been made.

Cheers,
Athene

Comment 8 Bryan Kearney 2014-07-02 14:06:38 UTC
This was delivered with 6.0.3, which is the Satellite 6 Beta.