Bug 1197090
Summary: | foreman_scap_client config file gets configured with port 8443 | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Kedar Bidarkar <kbidarka> |
Component: | Other | Assignee: | Šimon Lukašík <slukasik> |
Status: | CLOSED ERRATA | QA Contact: | Kedar Bidarkar <kbidarka> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.1.0 | CC: | bbuckingham, bkearney, jmontleo, omaciel, slukasik |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-12 05:28:09 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: | 1047797 |
Description
Kedar Bidarkar
2015-02-27 13:35:17 UTC
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 |