Bug 1248380

Summary:	oscap does not handle non-decimal version of OVAL
Product:	Red Hat Enterprise Linux 5	Reporter:	Ján Rusnačko <jrusnack>
Component:	openscap	Assignee:	Jan Černý <jcerny>
Status:	CLOSED DEFERRED	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.11	CC:	mhaicman, openscap-maint, qe-baseos-security, slukasik
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1248375	Environment:
Last Closed:	2019-09-05 10:01:25 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:	1202868, 1248375
Bug Blocks:	1248378

Description Ján Rusnačko 2015-07-30 08:02:59 UTC

+++ This bug was initially created as a clone of Bug #1248375 +++

Description of problem:
oscap does not handle the non-decimal version of OVAL XMLs (e.g. 5.10.1) well:

File '/home/jrusnack/workspace/tmp/result.xml' line 6: Element
'{http://oval.mitre.org/XMLSchema/oval-common-5}schema_version': '5.10.1' is not
a valid value of the atomic type 'xs:decimal'. 


Version-Release number of selected component (if applicable):
1.1.1

Steps to Reproduce:
$ oscap ds sds-compose source.xml result.xml 

where source.xml is OVAL XML with 5.10.1 version

Comment 1 Šimon Lukašík 2015-07-31 08:37:24 UTC

Fixed in upstream, easy to backport.

Relevant upstream change: https://github.com/OpenSCAP/openscap/commit/0aa1a0d02046f26935aa0f3833e7edf531662237

Comment 2 Mike McCune 2016-03-28 23:35:19 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 3 Marek Haicman 2019-09-05 10:01:25 UTC

Red Hat Enterprise Linux 5 is currently in Extended Life Cycle Support phase (https://access.redhat.com/articles/2986371), meaning only critical impact security and selected urgent priority bug fixes are eligible for fixing. This BZ is neither of those, thus closing as DEFERRED. This is fixed in RHEL6+