Bug 1505241 - Global Region Widget doesn't have data
Summary: Global Region Widget doesn't have data
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Replication
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.9.0
Assignee: Gregg Tanzillo
QA Contact: Alex Newman
URL:
Whiteboard:
Depends On:
Blocks: 1509008
TreeView+ depends on / blocked
 
Reported: 2017-10-23 06:31 UTC by tachoi
Modified: 2021-03-11 16:03 UTC (History)
9 users (show)

Fixed In Version: 5.9.0.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1509008 (view as bug list)
Environment:
Last Closed: 2018-03-06 14:55:48 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description tachoi 2017-10-23 06:31:47 UTC
Description of problem:
Muti-region configuration, global region, 2 remote regions
External LDAP login service to login 
If customer login from remote region ui, they can see Widget info without issue.
However, if customer login global region with same account, no data available.
- No Data found(please see attached file)
This happens to all users from global region ui.
Only Widget info available for "super_administrator" account only
CFME 5.8.1.5
No change has been made
Customer informed that this seems like never worked since they have been deployed

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
No Data available

Expected results:
Global region user should be able to see same Widget info from Regional 

Additional info:
No Change has been made, Checked from global db Widget data is only available for remote region miq_group_id not global miq_group_id 

This is show stopper in releasing Single Pane of Glass to end user

Comment 4 Gregg Tanzillo 2017-10-23 13:32:07 UTC
Was the widget(s) in question created in the remote region of in the global?

Comment 5 tachoi 2017-10-23 22:28:33 UTC
Hi Greg 

Here is the info from customer.
############################
We are using custom widgets in remote and "Default" dashboard widgets in Global. We did not go further of creating widgets in Global as given even the "Default" does not work

Thanks
Taeho

Comment 6 tachoi 2017-10-24 22:13:26 UTC
Hi Greg T

Do you have any update on this 
Customer is requesting update on this.

Regards,
Taeho

Comment 7 Gregg Tanzillo 2017-10-26 01:10:35 UTC
Taeho,

I was unable to recreate this issue locally using the database for authentication. I did the following -

1. Setup 2 regions, global and remote
2. Created user with the same name in both regions
3. Loaded the default dashboard in both regions

Both dashboards displayed data and were identical.

It's not obvious whether the fact that they are using external authentication would be related to the issue so I have some questions -

1. Are the user names in both regions identical?
2. Are both regions connecting to the same LDAP directory?
3. What is role does this user have?
4. Does this user have any RBAC filters configured on his group?
5. Can we get a screenshot of the user's dashboard on the remote region where the data is populated?
6. Would it be possible to try this with authentication in the DB (not external auth with LDAP)?

Also, from the screenshot, it look like these widgets were never run for this user. See the text at the bottom of each widget - "Update Never | Next ...". Some additional questions based on this -

7. Can you confirm from the logs that widget generation is actually running? 
8. Did the user wait long enough - it could be several minutes - for the widgets to generate the first time?

Thanks

Comment 10 Gregg Tanzillo 2017-10-26 01:50:07 UTC
You should see messages like this -

[----] I, [2017-10-25T18:00:04.819920 #50325:99514c]  INFO -- : MIQ(MiqSchedule#action_generate_widget) Action [rss_newest_vms] has been run for target type: [MiqWidget] with name: [EVM: Recently Discovered VMs]
[----] I, [2017-10-25T18:00:09.899292 #50392:99514c]  INFO -- : MIQ(MiqWidget#generate_one_content_for_group) Widget: [EVM: Recently Discovered VMs] ID: [99000000000020] for [MiqGroup] [Group1]...
[----] I, [2017-10-25T18:00:10.016236 #50392:99514c]  INFO -- : MIQ(MiqWidget#generate_one_content_for_group) Widget: [EVM: Recently Discovered VMs] ID: [99000000000020] for [MiqGroup] [Group1]...Complete
[----] I, [2017-10-25T18:00:10.154264 #50392:99514c]  INFO -- : MIQ(MiqWidget#generate_one_content_for_group) Widget: [EVM: Recently Discovered VMs] ID: [99000000000020] for [MiqGroup] [EvmGroup-super_administrator]...
[----] I, [2017-10-25T18:00:10.272286 #50392:99514c]  INFO -- : MIQ(MiqWidget#generate_one_content_for_group) Widget: [EVM: Recently Discovered VMs] ID: [99000000000020] for [MiqGroup] [EvmGroup-super_administrator]...Complete

Specifically, messages referencing the group that the user "ntdm_admin" is in

Comment 19 CFME Bot 2017-10-31 01:32:25 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/73a3edefab1affa5316e0a6332990f94abbab7e5

commit 73a3edefab1affa5316e0a6332990f94abbab7e5
Author:     Jillian Tullo <jtullo>
AuthorDate: Mon Oct 30 18:05:40 2017 -0400
Commit:     Jillian Tullo <jtullo>
CommitDate: Mon Oct 30 18:05:40 2017 -0400

    Use in_my_region when looking up group during widget content generation
    
    Ensure that when an miq group is looked up by its description during widget content generation that in_my_region is used. Currently it is causing an error when generating content for a user because it sets the correct user but with a group in another zone, causing it to be unviewable.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1505241

 app/models/miq_widget.rb                         |  2 +-
 app/models/miq_widget/content_generator.rb       |  2 +-
 spec/models/miq_widget/content_generator_spec.rb | 11 +++++++----
 spec/models/miq_widget_spec.rb                   |  7 +++++++
 4 files changed, 16 insertions(+), 6 deletions(-)

Comment 27 Marianne Feifer 2017-11-28 19:12:30 UTC
Alex, did you see GT's note above?


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