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.

Document URL: 

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Prerequisites.html#sect-Red_Hat_Satellite-Installation_Guide-Prerequisites-Base_Operating_System

Section Number and Name: 

1.4.1. Base Operating System

Describe the issue: 

The command

# ping -c1 `hostname -s` # my_system

does not really make much sense. With myhostname nss plugin, only the FQDN will be resolved, and my test shows that that is enough for Satellite to install. Also, the sentence above that example says

  Full forward and reverse DNS resolution using a fully qualified domain name. Ensure that hostname and localhost resolve correctly, using the following commands:

so it correctly only talks about FQDN, not short name.

Suggestions for improvement: 

Remove that ping -c1 `hostname -s` # my_system line.

Additional information:

(In reply to Stephen Wadeley from comment #3)
> Hello
> 
> 
> --------------
> 
> One could suggest to the Content Strategist making a proper procedure for
> preparing a RHEL base system in a separate file and then using an Xinclude
> to include it in both chapters, for reader convenience, or just link to it
> the second time. 

This was my original thought, just link to the earlier chapter. Do you think I can find the email where I originally asked about it? Nooooo :-(

Thanks for acking the bug.

D.

Scheduled for release with async #2.