Hide Forgot
Description of problem: Missing admin credentials in satellite-installer output. Version-Release number of selected component (if applicable): @Satellite 6.6.0(Snap1) How reproducible: Always Steps to Reproduce: 1. Setup pre-requisite for satellite 6.6.0 installation. 2. Execute Satellite installer command(satellite-installer --scenario satellite) Actual results: # satellite-installer --scenario satellite Installing Done [100%] [................................................................................................................................] Success! * Satellite is running at https://hostname.example.com * To install an additional Capsule on separate machine continue by running: capsule-certs-generate --foreman-proxy-fqdn "$CAPSULE" --certs-tar "/root/$CAPSULE-certs.tar" * To upgrade an existing 6.4 Capsule to 6.5: Please see official documentation for steps and parameters to use when upgrading a 6.4 Capsule to 6.5. The full log is at /var/log/foreman-installer/satellite.log yum install -y -q rh-mongodb34-syspaths finished successfully! Expected results: # satellite-installer --scenario satellite Resetting puppet server version param... Installing Service[puppetserver] [86%] [............................................................................................................... ] Installing Done [100%] [................................................................................................................................] Success! * Satellite is running at https://hostname.example.com Initial credentials are admin / bdsbdksdsd * To install an additional Capsule on separate machine continue by running: capsule-certs-generate --foreman-proxy-fqdn "$CAPSULE" --certs-tar "/root/$CAPSULE-certs.tar" * To upgrade an existing 6.4 Capsule to 6.5: Please see official documentation for steps and parameters to use when upgrading a 6.4 Capsule to 6.5. The full log is at /var/log/foreman-installer/satellite.log yum install -y -q rh-mongodb34-syspaths finished successfully!
Created redmine issue https://projects.theforeman.org/issues/26745 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26745 has been resolved.
*** Bug 1710370 has been marked as a duplicate of this bug. ***
*** Bug 1711972 has been marked as a duplicate of this bug. ***
Verified @Satellite 6.6.0 snap 6 Steps: 1. Setup pre-requisite for satellite 6.6.0 installation. 2. Execute Satellite installer command(satellite-installer --scenario satellite) Observation: - satellite-installer prints initial credentials after satellite installation. # satellite-installer --scenario satellite Installing Done [100%] [...........................................................................] Success! * Satellite is running at https://hostname.example.com Initial credentials are admin / eLgDnWara4vWcCMX * To install an additional Capsule on separate machine continue by running: capsule-certs-generate --foreman-proxy-fqdn "$CAPSULE" --certs-tar "/root/$CAPSULE-certs.tar" * To upgrade an existing 6.5 Capsule to 6.6: Please see official documentation for steps and parameters to use when upgrading a 6.5 Capsule to 6.6. The full log is at /var/log/foreman-installer/satellite.log
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3172