Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1354424 - [DOC] [RFE] Add a note about foreman-proxy-register-in-foreman
Summary: [DOC] [RFE] Add a note about foreman-proxy-register-in-foreman
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Docs Install Guide
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: Unspecified
Assignee: Stephen Wadeley
QA Contact: Melanie Corr
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-11 09:51 UTC by Lukas Zapletal
Modified: 2018-03-23 12:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-23 12:39:14 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Lukas Zapletal 2016-07-11 09:51:21 UTC
I'd also add info about --register-in-foreman option:

[root@ibm-x3655-04 ~]# satellite-installer -h | grep register
--foreman-proxy-register-in-foreman  Register proxy back in Foreman (default: true)

It is very useful to inform the user this can be optionally turned off in case Capsule can't (yet) reach Satellite and vice versa. Users very often hit this bug when installation seem to fail but it is only the registration step which fails (the puppet output is ugly and looks like its an installation error). In case network team did not yet setup firewall rules, user can still install Capsule. I'd make a subchapter called "Offline installation" describing this.

Low prio.


Note You need to log in before you can comment on or make changes to this bug.