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.

Description of problem:

Questions) When selecting in SCAP Content - XCCDF - "Default XCCDF profile", the
result is not selected, when we change to another option, like PCI, the
result works fine. 

Explanation) This is expected behavior. The default profile may contain rules.
However stock policies (from scap-security-guide package) never have
meaningful content.

Satellite presents default profile as an option for customers that
create their own policies, that can bring meaningful default profile.

We can improve UX and hide default profile if that option is not
meaningful given the content file. 

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


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:

No meaningful oscap default profile.

Expected results:

Should have a meaningful default profile.

Additional info:

This should be fixed in Proxy::OpenSCAP::ContentParser.extract_policies.

At that point we can tell, whether the 'default' profile is useful or not. We should perhaps implement that function (to query usefulness) in rubygem-openscap.

Moving 6.2 bugs out to sat-backlog.

Moving 6.2 bugs out to sat-backlog.

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.