-
Bug
-
Resolution: Done
-
Critical
-
None
-
6.4
1. Proposed title of this feature request
Failed openscap reports are always shown as severity ERROR.
The severity of a failed scap report should be configurable as ERROR, WARNING or NOTICE.
3. What is the nature and description of the request?
For this customer, failed scap reports are not critical and the failed scap scans reported
as ERROR will hide other more relevant issues in the "Hosts => All Hosts" overview.
4. Why does the customer need this? (List the business requirements here)
ERRORs from scap scans are "hiding" othe more relevant issues for a host in "Hosts => All Hosts".
5. How would the customer like to achieve this? (List the functional requirements here)
The severity of the incoming scap reporst should be configurable in
Administer => Settings => Compliance
with a severity of ERROR, WARNING or NOTICE with the default configuration as ERROR.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
- When configured as ERROR, an in-compliant system should be reported with an ERROR on the host
- When configured as WARNING, an in-compliant system should be reported with an WARNING on the host
- When configured as NOTICE, an in-compliant system should be reported as in-compliant, but not with
a visible warning or error message
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Satellite 6.4
9. Is the sales team involved in this request and do they have any additional input?
No
10. List any affected packages or components.
- tfm-rubygem-foreman_openscap
11. Would the customer be able to assist in testing this functionality if implemented?
Yes
- external trackers