Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem: In Satellite installation summary report, Satellite should be mentioned instead of foreman.
Version-Release number of selected component (if applicable):
6.8
How reproducible:
always
Steps to Reproduce:
1. Install satellite 6.8.
2. In the summary report, everywhere foreman mentioned instead of satellite.
# satellite-installer --scenario satellite
* Foreman is running at https://qesat68.xyz.com
Initial credentials are admin / ********
* To install an additional Foreman proxy on separate machine continue by running:
foreman-proxy-certs-generate --foreman-proxy-fqdn "$FOREMAN_PROXY" --certs-tar "/root/$FOREMAN_PROXY-certs.tar"
* Foreman Proxy is running at https://qesat68.xyz.com:9090
The full log is at /var/log/foreman-installer/satellite.log
Actual results:
In the summary report, everywhere foreman mentioned instead of satellite.
Expected results:
Use Satellite instead of foreman
Additional info:
Verified.
Version tested: Satellite 6.8.0 Snap 6.0
Package Version:
katello-3.16.0-0.3.rc3.el7sat.noarch
satellite-6.8.0-0.6.beta.el7sat.noarch
foreman-2.1.0-0.22.rc3.el7sat.noarch
pulp-server-2.21.2-1.el7sat.noarch
Steps:
1. Install satellite 6.8. ( #satellite-installer --scenario satellite )
Observation:
---output emitted---
Success!
* Satellite is running at https://satellite.example.com
Initial credentials are admin / ************
* 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.7 Capsule to 6.8:
Please see official documentation for steps and parameters to use when upgrading a 6.7 Capsule to 6.8.
* Capsule is running at https://satellite.example.com:9090
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 (Important: Satellite 6.8 release), 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-2020:4366