Bug 1418852 - scap cron schedule change is not getting updated to client
Summary: scap cron schedule change is not getting updated to client
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.2.5
Hardware: x86_64
OS: Linux
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Shimon Shtein
Depends On:
TreeView+ depends on / blocked
Reported: 2017-02-02 21:48 UTC by Manikandan Somasundaram
Modified: 2021-03-11 14:56 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18626 0 Normal Resolved scap cron schedule change is not getting updated to client 2020-04-10 11:26:33 UTC
Red Hat Bugzilla 1349082 1 None None None 2021-03-11 14:36:08 UTC

Internal Links: 1349082

Comment 2 Ondřej Pražák 2017-02-22 15:37:32 UTC
Created redmine issue http://projects.theforeman.org/issues/18626 from this bug

Comment 3 Marek Hulan 2017-05-31 11:37:30 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.

Comment 5 pm-sat@redhat.com 2018-02-21 16:54:17 UTC
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

Note You need to log in before you can comment on or make changes to this bug.