Bug 1193920 – Unable to create oscap policy

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1193920 - Unable to create oscap policy

Summary:	Unable to create oscap policy

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	WebUI (Show other bugs)
Sub Component:
Version:	6.1.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high (vote)
Target Milestone:	Unspecified
Target Release:	Unused
Assigned To:	Shlomi Zadok
QA Contact:	Kedar Bidarkar
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:	1047797
	Show dependency tree / graph

Reported:	2015-02-18 09:51 EST by Kedar Bidarkar
Modified:	2017-02-23 15:29 EST (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-08-12 01:25:03 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
foreman scap client could not be configured (37.92 KB, image/png) 2015-02-18 09:51 EST, Kedar Bidarkar	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2015:1592	normal	SHIPPED_LIVE	Important: Red Hat Satellite 6.1.1 on RHEL 6	2015-08-12 05:04:35 EDT

Groups: None (edit)

Description Kedar Bidarkar 2015-02-18 09:51:23 EST

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:

Comment 1 Shlomi Zadok 2015-02-18 11:42:31 EST

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

Comment 5 Kedar Bidarkar 2015-03-09 04:57:47 EDT

This issue is now fixed and VERIFIED with sat6.1 Beta Snap5.

Comment 6 Bryan Kearney 2015-08-11 09:34:49 EDT

This bug is slated to be released with Satellite 6.1.

Comment 7 errata-xmlrpc 2015-08-12 01:25:03 EDT

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

Note You need to log in before you can comment on or make changes to this bug.