Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1322938 - compliance reports from a particular org should be visible when org context is set
compliance reports from a particular org should be visible when org context i...
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: SCAP Plugin (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity high (vote)
: Beta
: Unused
Assigned To: Shlomi Zadok
Kedar Bidarkar
http://projects.theforeman.org/issues...
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-31 13:37 EDT by Kedar Bidarkar
Modified: 2016-07-27 05:29 EDT (History)
3 users (show)

See Also:
Fixed In Version: foreman-1.11.0.12-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-27 05:29:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 14458 None None None 2016-04-22 12:05 EDT
Red Hat Product Errata RHBA-2016:1501 normal SHIPPED_LIVE Red Hat Satellite 6.2 Capsule and Server 2016-07-27 08:28:58 EDT

  None (edit)
Description Kedar Bidarkar 2016-03-31 13:37:42 EDT
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:
Comment 2 Shlomi Zadok 2016-04-01 05:49:26 EDT
I believe the reports organization are coupled with their respective host's organization. Can you please verify that the host belongs to an organization?
Comment 3 Kedar Bidarkar 2016-04-01 11:18:28 EDT
Yes the hosts do belong to "Default Organization", but still we cannot see the reports unless we set "Any org" as the Org context.
Comment 4 Shlomi Zadok 2016-04-04 06:14:39 EDT
Created redmine issue http://projects.theforeman.org/issues/14446 from this bug
Comment 6 Shlomi Zadok 2016-04-06 04:11:51 EDT
Please note that http://projects.theforeman.org/issues/14458 solves the issue.
Comment 7 Ohad Levy 2016-04-06 04:37:19 EDT
please cherrypick the fix from http://projects.theforeman.org/issues/14458, it will also find its way to upstream 1.11.1.
Comment 9 Kedar Bidarkar 2016-04-15 11:27:44 EDT
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,
Comment 11 errata-xmlrpc 2016-07-27 05:29:50 EDT
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

Note You need to log in before you can comment on or make changes to this bug.