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 the Satellite use case, the server.xml file for Tomcat is configured/managed via puppet.
I would like the sslProtocols & sslEnabledProtocols values to be exposed as puppet parameters so that I can override them with custom hiera.
Build: Satellite 6.3.1 snap1
grep candlepin /etc/foreman-installer/custom-hiera.yaml
candlepin::tls_versions: ['1.2', '1.3']
[root@sgi-uv20-01 ~]# grep /etc/
Display all 273 possibilities? (y or n)
[root@sgi-uv20-01 ~]# grep ssl /etc/tomcat/server.xml
sslProtocols="TLSv1.2"
sslEnabledProtocols="TLSv1.2"
[root@sgi-uv20-01 ~]# satellite-installer
Installing Done [100%] [................................................................................................................................]
Success!
* Satellite is running at https://sat-host
* 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.2 Capsule to 6.3:
Please see official documentation for steps and parameters to use when upgrading a 6.2 Capsule to 6.3.
The full log is at /var/log/foreman-installer/satellite.log
[root@sgi-uv20-01 ~]# grep ssl /etc/tomcat/server.xml
sslProtocols="TLSv1.2,TLSv1.3"
sslEnabledProtocols="TLSv1.2,TLSv1.3"
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/RHBA-2018:1126