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:
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:

proposed upstream fix: https://github.com/OpenSCAP/foreman_openscap/pull/85

Merged upstream as https://github.com/shlomizadok/foreman_openscap/commit/e101ea5140bb52c41807bb4363aad00372023df0

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.

Created attachment 999500 [details]
UI banner on creating a policy

The UI banner is also available when creating openscap policy

Created redmine issue http://projects.theforeman.org/issues/9785 from this bug

Proposed fix on upstream: https://github.com/OpenSCAP/foreman_openscap/pull/94

Upstream merged. slukasik is releasing a new version.

Created attachment 1022724 [details]
OSCAP content_path location in the UI is fixed now

VERIFIED with Sat6.1-GA-SNAP2

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