Bug #9769
closedforeman_scap_client config file does'nt get configured with policy unless policy is assigned at host level
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1200015
Description of problem:
foreman_scap_client config file doesn't get configured with policy unless it is assigned at host level.
1) Create a OSCAP policy and assign it to Host-Group.
2) Register a client/host with the sat6 as puppet client. [ requires 'puppet agent -t' run for this Host to be visible under satellite6. ]
3) After the HOST is visible, Now we need to update the Host, with
a) a Host-Group
b) Puppet-Environment
4) Now running the 'puppet agent -t' on the Host, configures the foreman_scap_client config file with port and server info only,
5) but not the policy info unless we assign the policy to the "Hosts" using the "Select Action" button and choosing the "Assign Compliance policy" option.
6) Having associated OSCAP policy to Host-group, step 5) shouldn't be required.
Version-Release number of selected component (if applicable):
sat6.1 beta snap5
How reproducible:
Steps to Reproduce:
1. as mentioned in description.
2.
3.
Actual results:
policy info doesn't get configured for foreman_scap_client config file unless we assign the oscap policy to the "Hosts" using the "Select Action" button and choosing the "Assign Compliance policy" option.
Expected results:
Assigning the oscap policy to Host-Group and assigning Host-group to Host, should be enough.
Additional info:
Updated by Shlomi Zadok over 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/OpenSCAP/foreman_openscap/pull/93 added
- Pull request deleted (
)
Updated by Shlomi Zadok over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100