Bug 1037751

Summary:	Install doc indicates to run node-install command on satellite server rather than satellite node
Product:	Red Hat Satellite	Reporter:	Eric Nothen <eric_nothen>
Component:	Docs Install Guide	Assignee:	Athene Chan <achan>
Status:	CLOSED NEXTRELEASE	QA Contact:	Dan Macpherson <dmacpher>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Nightly	CC:	cwelton, j.bittner, mlamouri, mmccune, mmurray
Target Milestone:	Unspecified	Keywords:	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-05-21 00:20:05 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:

Description Eric Nothen 2013-12-03 18:14:10 UTC

Title: Configuring a Satellite Node

Describe the issue:
Section "6.2. Configuring a Satellite Node", step #5, Options 1, 2 and 3 read "Run the following commands as the root user on the Satellite server". 

Suggestions for improvement:
Shouldn't that be run on the Satellite node instead? I followed the document the first time, and run the node-install command on the Satellite server, but it complains that "the pulp node can't be installed on a machine with Katello master". Running it on the actual node being configured works fine, but I first had to construct SATELLITE_6 and OAUTH_SECRET, since the node being configured doesn't have the file /etc/katello/oauth_token-file.

Additional information:

Comment 1 RHEL Program Management 2013-12-03 18:14:57 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 sachua 2013-12-05 05:47:55 UTC

Hi Eric,

Thanks for bringing this to our attention. We will make the amendment with the next doc update.

Regards,
Sarah

Comment 4 Mark Lamourine 2014-01-30 21:55:45 UTC

An additional alternate interpretation:

Option 3 in the MDS-2 document, section 6.2 gives a CLI example for an all-in-one (with the node on the Sat6/Forman server).  This example indicates to include pulp in the node-install.  The setup command seems to work on the Satellite host if the node-install arguments for pulp are left off:

sudo node-install -v   --parent-fqdn "${SATELLITE_6}"   \
  --dns true --dns-interface eth0 --dns-zone sat6.example.com \
  --dns-forwarders 192.168.1.1 --dns-forwarders 192.168.1.2 \
  --dhcp true --dhcp-interface eth0 \
  --tftp true --tftp-servername ${SATELLITE_6} \
  --puppet true --puppetca true   \
  --register-in-foreman true --foreman-oauth-secret "${OAUTH_SECRET}" \
  --pulp false

Comment 5 Athene Chan 2014-05-21 00:03:16 UTC

(In reply to Mark Lamourine from comment #4)
> An additional alternate interpretation:
> 
> Option 3 in the MDS-2 document, section 6.2 gives a CLI example for an
> all-in-one (with the node on the Sat6/Forman server).  This example
> indicates to include pulp in the node-install.  The setup command seems to
> work on the Satellite host if the node-install arguments for pulp are left
> off:
> 
> sudo node-install -v   --parent-fqdn "${SATELLITE_6}"   \
>   --dns true --dns-interface eth0 --dns-zone sat6.example.com \
>   --dns-forwarders 192.168.1.1 --dns-forwarders 192.168.1.2 \
>   --dhcp true --dhcp-interface eth0 \
>   --tftp true --tftp-servername ${SATELLITE_6} \
>   --puppet true --puppetca true   \
>   --register-in-foreman true --foreman-oauth-secret "${OAUTH_SECRET}" \
>   --pulp false

Hello Mark,

New commands have been added to the next version of the documentation for the next release. Thank you for your input on the subject!

Cheers,
Athene

Comment 6 Athene Chan 2014-05-21 00:18:29 UTC

Hello Eric and Mark,

Changes have been made to the new version of the book in the works, incorporating the feedback. I will be closing this ticket as resolved.

Should there be further issues in the new version, please do not hesitate to create another bug report or reopen this issue. We value your feedback!

Thank you and have a good day.

Cheers,
Athene