Bug 1448570

Summary: [Ref-Arch] HA path to find admin_password
Product: Red Hat Satellite Reporter: Kenny Tordeurs <ktordeur>
Component: DocumentationAssignee: satellite-doc-list
Status: CLOSED CANTFIX QA Contact: satellite-doc-list
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2.9CC: adahms
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-23 05:22:35 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:
Bug Depends On:    
Bug Blocks: 1425213    

Description Kenny Tordeurs 2017-05-05 19:18:36 UTC
Document URL: 
https://access.redhat.com/sites/default/files/attachments/sat6ha-lb-refarch.pdf

Section Number and Name: 
4.1.3.3 Verify The Satellite Functionality
Invoke a browser, point the URL and login with information as mentioned in the output of
katello-installer script.
The password for the user (admin by default) can also be retrieved from the installer answer
file generated during install:
[root@satnode1 katello-installer]# grep admin_password \
/etc/katello-installer/answers.katello-installer.yaml | grep -v pulp
 admin_password: sybh5aCkwJCxKHGp

Describe the issue: Path to find the password has changed in more recent versions of satellite.

Suggestions for improvement: 
# grep admin_password /etc/foreman-installer/scenarios.d/satellite-answers.yaml | grep -v pulp

Additional information:

Comment 2 Andrew Dahms 2018-07-23 05:22:35 UTC
This bug was raised against the document "Deploying a Highly Available Red Hat Satellite Server 6 Environment", for which customers are now being asked to contact Red Hat (either their account team or consulting team) directly for assistance.

Because the product documentation team is unable to process this request, and in consultation with the Reference Architecture team, I am now closing this bug.

See the following article for more information -

https://access.redhat.com/solutions/1603283