Bug 1418852
| Summary: | scap cron schedule change is not getting updated to client | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Manikandan Somasundaram <msomasun> |
| Component: | SCAP Plugin | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Shimon Shtein <sshtein> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.5 | CC: | bbuckingham, hmore, jcallaha, mhulan, nshaik, oprazak, sjagtap, sshtein, szadok |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-21 16:54:17 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: | |||
|
Comment 2
Ondřej Pražák
2017-02-22 15:37:32 UTC
This might get fixed by BZ 1349082 which changes the way we configure the scap scanner triggering. Moving to ON_QA, please verify the described process when testing the linked BZ. We no longer use cron resource for the configuration but rather we manage /etc/cron.d/foreman_scap_client_cron file. 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-2018:0336
|