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.

Bug 1257660

Summary: OpenSCAP UI still informs user to distribute SCAP content, when it is no longer required.
Product: Red Hat Satellite Reporter: Rich Jerrido <rjerrido>
Component: SCAP PluginAssignee: Shlomi Zadok <szadok>
Status: CLOSED ERRATA QA Contact: Kedar Bidarkar <kbidarka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bbuckingham, cwelton, kbidarka
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/11604
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:18:15 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:
Attachments:
Description Flags
Image illustrating the notice none

Description Rich Jerrido 2015-08-27 14:46:36 UTC
Created attachment 1067784 [details]
Image illustrating the notice

Description of problem:

When creating a new OpenSCAP policy, the user is informed to 'Ensure the selected SCAP content exists on your hosts' . However, the content, if not present on the host, in downloaded via the Satellite/Capsule. 

The UI needs to be updated to remove this statement. 

Version-Release number of selected component (if applicable):
openscap-1.2.4-1.el7sat.x86_64
openscap-scanner-1.2.4-1.el7sat.x86_64
puppet-foreman_scap_client-0.3.3-9.el7sat.noarch
puppetlabs-stdlib-4.2.1-1.20140510git08b00d9.el7sat.noarch
ruby193-rubygem-foreman_openscap-0.3.2.10-1.el7sat.noarch
ruby193-rubygem-openscap-0.4.2-2.el7sat.noarch
ruby193-rubygem-scaptimony-0.3.0.1-1.el7sat.noarch
rubygem-smart_proxy_openscap-0.3.0.9-1.el7sat.noarch
scap-security-guide-0.1.19-2.el7.noarch


How reproducible:
100%

Steps to Reproduce:
1. Create a new SCAP policy via Hosts->Policies
2. On Step 2 (SCAP Content), the Notice is displayed
3.

Actual results:
Satellite states that they user needs to distribute content


Expected results:
Satellite does not state that the user needs to distribute content.

Additional info:

Comment 1 Bryan Kearney 2015-08-28 17:36:08 UTC
Created redmine issue http://projects.theforeman.org/issues/11604 from this bug

Comment 2 Bryan Kearney 2015-08-28 17:51:03 UTC
Upstream bug component is SCAP Plugin

Comment 3 Bryan Kearney 2015-09-12 16:04:21 UTC
Upstream bug assigned to szadok

Comment 4 Bryan Kearney 2015-09-17 16:04:49 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/11604 has been closed

Comment 8 Kedar Bidarkar 2016-03-31 19:36:07 UTC
VERIFIED with sat62-snap6

This message is no longer displayed.

Comment 10 errata-xmlrpc 2016-07-27 09:18:15 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/RHBA-2016:1501