Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Version-Release number of selected component (if applicable):
Satellite snap6
How reproducible:
Always
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
Actual results:
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
Expected results:
Foreman_scap_client should be configured and installed successfully
Additional info:
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.
Verified
- verified with
Satellite 6.6.0 snap 11
tfm-rubygem-foreman_openscap-1.0.4-1.el7sat.noarch
Test steps:
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.
Observation:
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.
https://access.redhat.com/errata/RHSA-2019:3172