+++ This bug was initially created as a clone of Bug #1420439 +++ Description of problem: Updating SCAP content on an existing Compliance Policy does not result in synchronization of the new SCAP content on subsequent puppet runs. Content hosts continue to run openscap scans using the previous outdated SCAP content. TRIAGE NOTES: This is request for 6.2 backport, we have both patches ready for backport. QA NOTES: See #1420439 for more info about how to reproduce.
Created attachment 1314648 [details] host YAML before
Created attachment 1314649 [details] host YAML after
Upstream bug assigned to oprazak
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17464 has been resolved.
UPGRADE NOTES: After applying the patch, the YAML output for host with a policy should change (classes -> foreman_scap_client -> policies -> download_path), see the attached screenshots. It is necessary to run puppet on the openscap clients so that config changes are propagated. The patch will not be active until the config is updated on clients. Steps to apply the patch: 1) apply patches for Satellite server, capsule(s) 2) restart Satellite, capsule(s) 3) run puppet on openscap clients Steps to verify the patch works: 1) set up a host with openscap, run foreman_scap_client on host 2) update host's policy with a new scap content 3) apply patches, restart Satellite server and capsule(s) 4) check the YAML output for host, download_path should end with a hash as a screenshots suggest 5) run puppet on a host 6) observe changes made to /etc/foreman_scap_client/config.yaml on host. They should correspond to what is in YAML output. 7) run foreman_scap_client, newly generated report should be based on updated scap content
I am closing this out as next release. The fix for this will be available in satellite 6.3. If you are running 6.3 and still seeing this issue, please feel free to re-open and provide additional information.