Bug 1193920
| Summary: | Unable to create oscap policy | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Kedar Bidarkar <kbidarka> | ||||
| Component: | WebUI | Assignee: | Shlomi Zadok <szadok> | ||||
| WebUI sub component: | Foreman | QA Contact: | Kedar Bidarkar <kbidarka> | ||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||
| Severity: | high | ||||||
| Priority: | unspecified | CC: | bbuckingham, cwelton, jmontleo, omaciel | ||||
| Version: | 6.1.0 | Keywords: | Triaged | ||||
| Target Milestone: | Unspecified | ||||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-08-12 05:25:03 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1047797 | ||||||
| Attachments: |
|
||||||
This happens because https://github.com/theforeman/foreman/pull/2080 was not backported to foreman-1.7 (the base for satellite 6.1). Can this PR be backported to Satellite? The hash for cherry-picking is e638fb38f35d6e4f3433691d94deb5cd724a2824 on https://github.com/theforeman/foreman/commit/e638fb38f35d6e4f3433691d94deb5cd724a2824 This issue is now fixed and VERIFIED with sat6.1 Beta Snap5. This bug is slated to be released with Satellite 6.1. 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: