Hide Forgot
Description of problem: Dashboard - All widgets should honor selected org/loc context Version-Release number of selected component (if applicable): Satellite 6.2.0-beta-snap3 How reproducible: Always Steps to Reproduce: 1. Review the dashboard Actual results: The following widgets do not honor current org/loc context: - Current Subscription Totals - Task Status Expected results: the above mentioned widget should honor current org/loc context Additional info:
I looked into filtering tasks by organization and I am not sure if it's possible. There's no direct association between a task and an organization in the database. Some tasks have locks which in term point to resources (e.g. Organization, User, Repository) but the problem is that how you get from a resource to org varies depending on the resource.
I checked with Ivan on comment #3 and it looks like there is a method on Task that gets us most of what we want: for_resource. It looks like it doesn't pick up actions that fail during the plan phase but we can maybe write some middleware to get around this.
I created a separate bug for the task status widget: https://bugzilla.redhat.com/show_bug.cgi?id=1322566 Will address that separately since it's probably going to require some additional changes that I think will preclude it from being in 6.2.
Updating title to reflect the correct issue - the task widget has been split to a separate BZ1322566. The other widget, subscription total, seems to have been fixed upstream via fix for http://projects.theforeman.org/issues/16713 - updating status etc accordingly.
Steps to verify: # rpm -q satellite satellite-6.3.0-18.0.beta.el7sat.noarch 1. Create 2 organizations. One org with hosts and the other without any hosts 2. Subscription Status shows correct data for selected organization. I'm not testing "Task Status" widget as there is separate Bug 1322566 for this. VERIFIED
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/RHSA-2018:0336