Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have a host , configure puppet and scap
2. Deploy a scap policy on the host
3. Do a puppet agent -t to configure foreman_scap_client on host
root@fred-yocham ~]# puppet agent -t
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Class[Foreman_scap_client]:
expects a value for parameter 'server'
expects a value for parameter 'port' on node fred-yocham
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Foreman_scap_client should be configured and installed successfully
I found the cause: foreman_scap_client puppet class was assigned to hostgroup and inherited by host while openscap proxy was assigned to host directly. Apparently, we do not modify inherited class params when openscap proxy changes.
Valid bug, but I do not think this is a regression.
Workaround: make sure openscap proxy and puppet class are both assigned directly to the same entity, do not use inheritance for one and direct assignment for the other.
Created redmine issue https://projects.theforeman.org/issues/27095 from this bug
Upstream bug assigned to email@example.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27095 has been resolved.
- verified with
Satellite 6.6.0 snap 11
1. Create host group, assign foreman_scap_client puppet class to host group.
(don't assign openscap capsule to host group)
2. Create host using host group created earlier, also assign
openscap capsule while creating host.
3. Assign scap policy to host.
4. Run puppet agent -t to configure foreman_scap_client on host.
Foreman_scap_client configured and installed successfully.
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.