This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1467146 - Unable to view Reports if a member has a custom Role - indefinite spinning wheel
Unable to view Reports if a member has a custom Role - indefinite spinning w...
Status: ON_QA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS (Show other bugs)
Unspecified Unspecified
urgent Severity high
: GA
: 5.9.0
Assigned To: Martin Hradil
Niyaz Akhtar Ansari
: TestOnly, ZStream
Depends On:
Blocks: 1468336
  Show dependency treegraph
Reported: 2017-07-03 00:35 EDT by tachoi
Modified: 2017-10-05 21:59 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1468336 (view as bug list)
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: Bug
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core

Attachments (Terms of Use)
custom role (67.41 KB, image/png)
2017-07-03 00:35 EDT, tachoi
no flags Details
spinning wheel view (268.75 KB, image/png)
2017-07-03 00:46 EDT, tachoi
no flags Details

  None (edit)
Description tachoi 2017-07-03 00:35:34 EDT
Created attachment 1293727 [details]
custom role

Description of problem:
Having different Roles for our customers. However when we give them view permission to Reports, they are just getting a loading with "Spinning wheel" indefinitely.

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

How reproducible:

Steps to Reproduce:
1.Create Custom Role with attached screenshot permission list
2.Create Custom group with assigning this Custom Role
3.Create new user with assigning this custom group
4.Login with new created user and navigate to built-in reports accordion

Actual results:
Only see spinning wheel indefinitely

Expected results:
Navigate Reports menu based on permission

Additional info:
Able to observe "ERROR -- : An unauthorized connection attempt was rejected" from production.log
Comment 3 tachoi 2017-07-03 00:46 EDT
Created attachment 1293729 [details]
spinning wheel view
Comment 7 CFME Bot 2017-07-06 12:28:45 EDT
New commit detected on ManageIQ/manageiq-ui-classic/master:

commit 5d36640dacc79b2aa3ac3978ddc34de37d74575c
Author:     Martin Hradil <>
AuthorDate: Thu Jul 6 15:37:08 2017 +0000
Commit:     Martin Hradil <>
CommitDate: Thu Jul 6 15:37:08 2017 +0000

    Don't x_node_set on a tree which doesn't exist
    Calling `x_node_set` when a tree doesn't exist works, but actually creates the entry that `tree_exists?` checks to see if such a tree exists.
    When the user doesn't have the right to see such a tree, that's problematic, since it breaks the assumption that `tree_exists?` returns true only for trees that were actually initialized.
    The leads to the calling `lock_tree` on a nonexistent tree, leading to a JS exceptions ("No element has been found").
    This makes us actually check if the tree already exists before calling `x_node_set` on it.
    (Would prefer to fix `x_node_set` instead, but.. this is a bugfix, and I really don't want to introduce more bugs. :))

 app/controllers/report_controller.rb | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

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