Red Hat Bugzilla – Bug 1197090
foreman_scap_client config file gets configured with port 8443
Last modified: 2017-02-23 15:25:18 EST
Description of problem: foreman_scap_client config file gets configured with port 8443 For satellite6 foreman-proxy port is 9090 Version-Release number of selected component (if applicable): sat6 Beta snap4 How reproducible: Steps to Reproduce: 1. after running 'puppet agent -t' with foreman_scap_client puppet-class configured 2. check for the port_number in /etc/foreman_scap_client/config.yaml 3. Actual results: port number is currently 8443 Expected results: port number should be 9090 Additional info:
Never heard about that. Why does the downstream differs in this? We need to push down the port number from foreman_openscap like https://github.com/isimluk/foreman_openscap/commit/ec403e0d19d4205da73133a7876ba876694948e2 it should then propagate to puppet-foreman_scap_client. I have not tested that yet.
Actually not. This commit configures only the server, not the port. Please see PR: https://github.com/OpenSCAP/foreman_openscap/pull/86 @slukasik, please review. thx
Merged upstream: puppet-foreman_scap_client patch: https://github.com/OpenSCAP/puppet-foreman_scap_client/commit/84b92f8da6459a9220b6f20dd5b791280d324588 foreman_openscap patch https://github.com/OpenSCAP/foreman_openscap/commit/cc1db34f86a99b1df2faae6df8e092fa5169f336
foreman_scap_client config file now gets configured with satellite6 capsule port: 9090 VERIFIED with sat6.1 beta snap5
This bug is slated to be released with Satellite 6.1.
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-2015:1592