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:

compliance reports from a particular org should be visible when org context is set. Currently Compliance reports are not visible unless "Any Organization" is set.

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

How reproducible:


Steps to Reproduce:
1. Run "foreman_scap_client <policy_id>" on the client
2. See that the compliance reports are visible only under "any organization" context.
3.

Actual results:
compliance reports are visible only under "any organization" context.

Expected results:
compliance reports should be  visible under their respective ORganization context.

Additional info:

I believe the reports organization are coupled with their respective host's organization. Can you please verify that the host belongs to an organization?

Yes the hosts do belong to "Default Organization", but still we cannot see the reports unless we set "Any org" as the Org context.

Created redmine issue http://projects.theforeman.org/issues/14446 from this bug

Please note that http://projects.theforeman.org/issues/14458 solves the issue.

please cherrypick the fix from http://projects.theforeman.org/issues/14458, it will also find its way to upstream 1.11.1.

VERIFIED with sat62-snap8.1

I had set the org-context, "Default Organization", "any ORg", "kbidarka_org".
Depending upon the org context the compliance reports were visible,

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501