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.
Created attachment 993141[details]
foreman scap client could not be configured
Description of problem:
currently unable to create oscap policy.
We get the message as shown in the attachement.
Completed 200 OK in 340ms (Views: 72.1ms | ActiveRecord: 242.4ms)
Processing by ScaptimonyPoliciesController#create as HTML
Parameters: {"utf8"=>"✓", "authenticity_token"=>"QLtMOslh6V76v9RoUO4aPr+qRnS/YQEWxIlZ39o9gJA=", "policy"=>{"current_step"=>"SCAP Content", "name"=>"nightly_test", "description"=>"", "scap_content_id"=>"1", "period"=>"", "weekday"=>"", "day_of_month"=>"", "cron_line"=>"", "location_ids"=>["", "2"], "organization_ids"=>["", "1"], "hostgroup_ids"=>[""]}, "commit"=>"Next"}
Failed to save: policies class parameter for class foreman_scap_client could not be configured.
Version-Release number of selected component (if applicable):
Satellite6.1 Beta snap3
How reproducible:
always
Steps to Reproduce:
1. while creating OSCAP policy
2.
3.
Actual results:
currently unable to create oscap policy.
Expected results:
should be able to create oscap policy.
Additional info:
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-2015:1592
Created attachment 993141 [details] foreman scap client could not be configured Description of problem: currently unable to create oscap policy. We get the message as shown in the attachement. Completed 200 OK in 340ms (Views: 72.1ms | ActiveRecord: 242.4ms) Processing by ScaptimonyPoliciesController#create as HTML Parameters: {"utf8"=>"✓", "authenticity_token"=>"QLtMOslh6V76v9RoUO4aPr+qRnS/YQEWxIlZ39o9gJA=", "policy"=>{"current_step"=>"SCAP Content", "name"=>"nightly_test", "description"=>"", "scap_content_id"=>"1", "period"=>"", "weekday"=>"", "day_of_month"=>"", "cron_line"=>"", "location_ids"=>["", "2"], "organization_ids"=>["", "1"], "hostgroup_ids"=>[""]}, "commit"=>"Next"} Failed to save: policies class parameter for class foreman_scap_client could not be configured. Version-Release number of selected component (if applicable): Satellite6.1 Beta snap3 How reproducible: always Steps to Reproduce: 1. while creating OSCAP policy 2. 3. Actual results: currently unable to create oscap policy. Expected results: should be able to create oscap policy. Additional info: