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 1220262 - unable to upload oscap content
Summary: unable to upload oscap content
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Šimon Lukašík
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On:
Blocks: 1047797
TreeView+ depends on / blocked
 
Reported: 2015-05-11 06:49 UTC by Kedar Bidarkar
Modified: 2017-02-23 20:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:59:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
unable to upload oscap content (75.02 KB, image/png)
2015-05-11 06:49 UTC, Kedar Bidarkar 		no flags Details
rhel6 scap security guide (2.74 MB, application/xml)
2015-05-11 12:16 UTC, Kedar Bidarkar 		no flags Details
View All

Description Kedar Bidarkar 2015-05-11 06:49:00 UTC 
Created attachment 1024103 [details]
unable to upload oscap content

Description of problem:

Unable to upload OSCAP content (ds.xml file)

Unable to save
Invalid SCAP Source Datastream (1.2) content in NONEXISTENT. [oscap_source.c:205] NONEXISTENT:8755: Element '{http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}filepath': This element is not expected. Expected is ( {http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}epoch ). NONEXISTENT:11334: Element '{http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}filepath': This element is not expected. Expected is ( {http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}epoch ). NONEXISTENT:11340: Element '{http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}filepath': This element is not expected. Expected is ( {http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}epoch ). NONEXISTENT:11346: Element '{http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}filepath': This element is not expected. Expected is ( {http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}epoch ). NONEXISTENT:40256: Element '{http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}filepath': This element is not expected. Expected is ( {http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}epoch ). NONEXISTENT:42835: Element '{http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}filepath': This element is not expected. Expected is ( {http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}epoch ). NONEXISTENT:42841: Element '{http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}filepath': This element is not expected. Expected is ( {http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}epoch ). NONEXISTENT:42847: Element '{http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}filepath': This element is not expected. Expected is ( {http://oval.mitre.org/XMLSchema/oval-definitions-5#linux}epoch ). 



Version-Release number of selected component (if applicable):
sat61-GA-SNAP3

How reproducible:


Steps to Reproduce:
1.while trying to upload the oscap content
2.
3.

Actual results:
unable to upload OSCAP content.

Expected results:
Should be able to upload OSCAP content.

Additional info:
Comment 2 Kedar Bidarkar 2015-05-11 07:14:02 UTC 
uploading "ssg-rhel7-ds.xml" is successful but uploading "ssg-rhel6-ds.xml" fails with the above mentioned error.

[root@xyzabc ~]# rpm -qav | grep -i openscap
rubygem-smart_proxy_openscap-0.3.0.4-1.el7sat.noarch
ruby193-rubygem-openscap-0.4.2-2.el7sat.noarch
openscap-1.2.3-0.1.el7sat.x86_64
ruby193-rubygem-foreman_openscap-0.3.2.8-1.el7sat.noarch
Comment 3 Shlomi Zadok 2015-05-11 09:59:51 UTC 
Not sure it's a bug. Maybe an issue with the ssg-rhel6-ds.xml?
Comment 4 Šimon Lukašík 2015-05-11 11:45:30 UTC 
Yes, it seems to be problem with the content itself.

Kedar, can you please attach the problematic file? Thanks!
Comment 5 Kedar Bidarkar 2015-05-11 12:16:12 UTC 
Created attachment 1024202 [details]
rhel6 scap security guide

I have been using this same rhel6-ds.xml file since a long time.

I just wonder if it has something to do with the updated openscap-1.2.3 version.
Comment 6 Šimon Lukašík 2015-05-11 12:52:42 UTC 
Bug in upstream (Mitre's) OVAL-5.11 schema. It is not backward compatible. We should be able to patch this in OpenSCAP.
Comment 7 Šimon Lukašík 2015-05-12 08:33:25 UTC 
Proposed fix upstream: https://github.com/OpenSCAP/openscap/pull/76

Can you backport this single fix? Or do you prefer stock upstream release (may take couple hours).
Comment 8 Mike McCune 2015-05-13 04:00:25 UTC 
took the stock upstream 1.2-maint branch and built it.
Comment 10 Kedar Bidarkar 2015-05-13 13:55:13 UTC 
VERIFIED this by just updating the openscap-RPM on SAT6 and CAPSULE which was on SNAP3.

with openscap-1.2.3-1.1.el7sat.x86_64  should be able to upload ssg-rhel6-ds.xml
Comment 11 Bryan Kearney 2015-08-11 13:25:05 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 12 Bryan Kearney 2015-08-12 13:59:49 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.