Bug 1292622 - A SCAP Compliance Policy cannot be created with a space in its name
Summary: A SCAP Compliance Policy cannot be created with a space in its name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.1.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-17 23:16 UTC by Russell Dickenson
Modified: 2019-08-12 14:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
scap policy with space (18.69 KB, image/png)
2017-02-08 10:57 UTC, Sanket Jagtap 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12885 0 None None None 2016-04-22 15:56:39 UTC

Comment 1 Shlomi Zadok 2015-12-20 12:06:39 UTC 
Created redmine issue http://projects.theforeman.org/issues/12885 from this bug
Comment 2 Bryan Kearney 2016-05-24 12:11:49 UTC 
Upstream bug assigned to szadok
Comment 3 Bryan Kearney 2016-05-24 12:11:52 UTC 
Upstream bug assigned to szadok
Comment 4 Bryan Kearney 2016-07-26 19:08:04 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 7 Bryan Kearney 2016-08-23 08:11:21 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/12885 has been closed
Comment 8 Sanket Jagtap 2017-02-08 10:57:22 UTC 
Created attachment 1248586 [details]
scap policy with space

Build: Satellite 6.3.0 

Packages:rpm -qa | grep satellit
satellite-6.3.0-11.1.beta.el6sat.noarch
satellite-installer-6.3.0-3.el6sat.noarch
satellite-cli-6.3.0-11.1.beta.el6sat.noarch
tfm-rubygem-foreman_theme_satellite-1.0.1-2.el6sat.noarch

Verified, oscap policy was created successfully with space in it's name as "Test policy"
Comment 10 Satellite Program 2018-02-21 16:54:17 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-2018:0336
Note You need to log in before you can comment on or make changes to this bug.