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 1332911 - Installation and Configuration steps contradicting and confusing
Summary: Installation and Configuration steps contradicting and confusing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: Allison Heslin
QA Contact: Brandi Munilla
URL:
Whiteboard:
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2016-05-04 10:57 UTC by Peter Vreman
Modified: 2019-09-25 20:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-30 09:22:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1333067 0 high CLOSED TFTP is not configured by the scenario katello as promised in documentation 2021-02-22 00:41:40 UTC

Internal Links: 1333067

Description Peter Vreman 2016-05-04 10:57:24 UTC
Description of problem:
The intallation manaual of Sat6.2Beta is consuing:
In step 3.1.4 you already install and configure the Satellite with the foreman installater:

---
3.1.4. Installing Satellite Server

    Install the installation package.

    # yum install satellite

    Run Foreman installer.

    # foreman-installer --scenario katello
---

In step 3.3 there is mentioned there is a manual intallation and automatic installation
---
3.3. Performing the Initial Configuration
     Manual Configuration - Satellite Server has default initial configuration options that prepare the server for use. You can override these settings depending on your environment’s requirements. You can run the command as often as needed to configure any necessary options.
    Automatic Configuration - You can automate most of the installation and configuration by using an answer file. 
---

The step 3.3 is therefor being seen after already an 'automatic' installation with default (maybe unwished!) values is done. This is especially made clear in step 3.3.2 with the remark that the Default Location cannot be deleted afterwards:

---
3.3.2. Performing the Initial Configuration Manually

The initial configuration creates an organization, location, username, and password. After the initial configuration, you can create additional organizations and locations. You can rename the default organization or location and you can delete the default organization, but you cannot delete the default location. 
---



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Follow the installation manual
2.
3.

Actual results:
Satellite is already with defaults before you see step 3.3


Expected results:
Initial configuration and foreman-installer are discussed together. Moving the foreman-installer command to section 3.3 might already help.

Alternative is to improve section 3.1.4 to make clear that you can do an express installation with default values or go to section 3.3 to do a manual controleld installation with e.g. custom certs.


Additional info:


Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

Comment 1 Peter Vreman 2016-05-04 15:00:47 UTC
Another unlogical place is that location of the --help option, this is hidden in the section 3.4.2 where DNS and DHCP is configured

---
3.4.2. Configuring DNS and DHCP on Satellite Server
You can configure DNS and DHCP on Satellite Server. TFTP is automatically configured.
If you want to configure external services, see Configuring Satellite Server with External Services for
more information.
To view a complete list of configurable options, run the foreman-installer --help command.
----

Also note here the text in the paragraph mentioning 'TFTP', this comes out of the blue.

Comment 2 Peter Vreman 2016-05-04 15:54:27 UTC
It is also related to the overall issue with Installation Manaul that it is unclear what is 'Satellite Server' and 'Capsule Server'. Does 'Satellite Server' include an internal Capsule or not?
E.g. Do i need to run both 'foreman-installer --scenario=katello' and 'foreman-installer --scenario=capsule' on a single server?

Recommend is have have scenarios base on different deployment architectures:
- satellite-server-without-capsule
- satellite-server-with-capsule
- capsule-server

Comment 3 Andrew Dahms 2016-05-05 13:56:44 UTC
Assigning to Ali for review.

Comment 4 Allison Heslin 2016-05-26 17:52:36 UTC
I removed the mention of running foreman-installer in section 3.1.4 because there are so many options and it was confusing.

I added instances of the foreman-installer --help so that it was more visible to the user. The TFTP issue has been updated per bz1333067.

Comment 5 Allison Heslin 2016-05-26 18:03:02 UTC
(In reply to Peter Vreman from comment #2)
> It is also related to the overall issue with Installation Manaul that it is
> unclear what is 'Satellite Server' and 'Capsule Server'. Does 'Satellite
> Server' include an internal Capsule or not?
> E.g. Do i need to run both 'foreman-installer --scenario=katello' and
> 'foreman-installer --scenario=capsule' on a single server?
> 
> Recommend is have have scenarios base on different deployment architectures:
> - satellite-server-without-capsule
> - satellite-server-with-capsule
> - capsule-server

I copied and pasted this comment into bz1332972 since it fits with that section and can be better addressed there.

Comment 6 Andrew Dahms 2016-05-30 09:22:34 UTC
This content is now live on the Customer Portal.

Closing.


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