Bug 1196574

Summary: OSCAP UI banner should have the recommended location for placing openscap content on hosts end
Product: Red Hat Satellite Reporter: Kedar Bidarkar <kbidarka>
Component: WebUIAssignee: Shlomi Zadok <szadok>
WebUI sub component: Foreman QA Contact: Kedar Bidarkar <kbidarka>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: bkearney, jmontleo, omaciel, slukasik, szadok
Version: 6.1.0   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/9785
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 05:27:34 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:
Description Flags
UI banner on creating a policy
none
OSCAP content_path location in the UI is fixed now none

Description Kedar Bidarkar 2015-02-26 10:20:30 UTC 
Description of problem:
OSCAP UI banner should have the recommended location for placing openscap content on hosts end

Version-Release number of selected component (if applicable):
sat6 beta snap4

How reproducible:
when creating oscap-content and oscap policy

Steps to Reproduce:
1. observe the UI banner for oscap-content and oscap policy 
2. IT should also specify the recommended path as to where the oscap content needs to be placed.
3.

Actual results:
currently no information as to where to place the openscap content after downloading it from the UI on the Hosts end.

Expected results:
UI banner should specify, the recommended location as to where to place the open-scap content on the Hosts end.

This becomes also important because the puppet-module configures the 

file /etc/foreman_scap_client/config.yaml with content_path as /var/lib/openscap/content/*.xml'.

Additional info:
Comment 1 Shlomi Zadok 2015-02-26 17:15:22 UTC 
proposed upstream fix: https://github.com/OpenSCAP/foreman_openscap/pull/85
Comment 3 Šimon Lukašík 2015-03-01 22:46:42 UTC 
Merged upstream as https://github.com/shlomizadok/foreman_openscap/commit/e101ea5140bb52c41807bb4363aad00372023df0
Comment 6 Kedar Bidarkar 2015-03-09 10:30:20 UTC 
Currently the UI banner is visible only after trying to edit the openscap policy and moving to the 'openscap content" tab.

I believe while creation also, we need to display this information.
Comment 7 Shlomi Zadok 2015-03-09 11:00:11 UTC 
Created attachment 999500 [details]
UI banner on creating a policy

The UI banner is also available when creating openscap policy
Comment 9 Shlomi Zadok 2015-03-16 13:44:43 UTC 
Created redmine issue http://projects.theforeman.org/issues/9785 from this bug
Comment 10 Shlomi Zadok 2015-03-16 13:48:26 UTC 
Proposed fix on upstream: https://github.com/OpenSCAP/foreman_openscap/pull/94
Comment 12 Shlomi Zadok 2015-03-19 09:44:44 UTC 
Upstream merged. slukasik is releasing a new version.
Comment 14 Kedar Bidarkar 2015-05-06 15:45:59 UTC 
Created attachment 1022724 [details]
OSCAP content_path location in the UI is fixed now

VERIFIED with Sat6.1-GA-SNAP2
Comment 15 Bryan Kearney 2015-08-11 13:30:28 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 16 errata-xmlrpc 2015-08-12 05:27:34 UTC 
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