Bug 1232194

Weird. Why we are seeing same issue again?

It should have been fixed by bug 1220262.

How we have get to the duplicate bug?

Analysis:
 * The fix for bug 1220262 has landed upstream after openscap 1.2.3 upstream release.
 * The bug 1220262 comment 7 contained important question that has not been answered.
 * The package openscap-1.2.3-1.1.el7sat (fix for bug 1220262) has not been based on upstream release (1.2.3). But some later commit.
 * The openscap-1.2.3-3.el6_6sat.x86_64 was again based on upstream release. (Not included the fix).

Moving to post, fixed upstream.

This issue is now also seen on RHEL7.

rhel71 ~]# foreman-rake db:seed
Seeding /usr/share/foreman/db/seeds.d/03-auth_sources.rb
Seeding /usr/share/foreman/db/seeds.d/03-permissions.rb
Seeding /usr/share/foreman/db/seeds.d/03-roles.rb
Seeding /usr/share/foreman/db/seeds.d/04-admin.rb
Seeding /usr/share/foreman/db/seeds.d/05-taxonomies.rb
Seeding /usr/share/foreman/db/seeds.d/06-architectures.rb
Seeding /usr/share/foreman/db/seeds.d/07-config_templates.rb
Seeding /usr/share/foreman/db/seeds.d/08-partition_tables.rb
Seeding /usr/share/foreman/db/seeds.d/10-installation_media.rb
Seeding /usr/share/foreman/db/seeds.d/11-smart_proxy_features.rb
Seeding /usr/share/foreman/db/seeds.d/13-compute_profiles.rb
Seeding /usr/share/foreman/db/seeds.d/15-bookmarks.rb
Seeding /usr/share/foreman/db/seeds.d/16-mail_notifications.rb
Seeding /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.12.8/db/seeds.d/20-foreman_tasks_permissions.rb
Seeding /opt/rh/ruby193/root/usr/share/gems/gems/foreman_bootdisk-4.0.2.13/db/seeds.d/50-bootdisk_templates.rb
Seeding /opt/rh/ruby193/root/usr/share/gems/gems/foreman_discovery-2.0.0.15/db/seeds.d/60_discovery_proxy_feature.rb
Seeding /opt/rh/ruby193/root/usr/share/gems/gems/foreman_openscap-0.3.2.10/db/seeds.d/openscap_feature.rb
Seeding /opt/rh/ruby193/root/usr/share/gems/gems/foreman_openscap-0.3.2.10/db/seeds.d/openscap_scap_default.rb
## SCAP content is invalid: Invalid SCAP Source Datastream (1.2) content in NONEXISTENT. [oscap_source.c:205]
NONEXISTENT:9896: 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:9902: 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:9908: 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:11812: 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:42817: 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:42823: 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:42829: 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:44733: 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 ).
 ##
Saved /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml as Red Hat rhel7 default content
All seed files executed

I'm going to temporarily roll back to openscap-1.2.3-1.1.el7sat until we can straighten this out.  This will get RHEL7 working.

What I think we want is either:

1) an upstream 1.2.4 release that includes all the fixes above rebuilt directly downstream

2) I keep openscap-1.2.3 and backport the patch:

https://github.com/OpenSCAP/openscap/pull/76

into openscap-1.2.3.X

Option (1) seems easier from a maint perspective for us but I don't know if we want to pull in all of the 1.2-maint code.

Thoughts?

My proposal is:
 * 1.2.4 will be soon released
 * RHEL-7.2 will be released with 1.2.4-1 package
 * Satellite can pick up 1.2.4 release early next week to the composes
 * Satellite can package it as 1.2.4-0.1. So it gets updated with RHEL-7.2 bits once they are released. (that has certain maintenance benefits going forward, i.e. if 1.2.4-1.el7 gets certified it will include Satellite customers).

VERIFIED with sat6.1.1 SNAP13-c1 build.

For sat6.1 running on RHEL66, make note that only RHEL6 OSCAP content would get created automatically.

But adding RHEL7 ds-stream.xml file manually does work fine.

This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.