Bug 1205492 - Spinner spins forever on Configure->Configuration->Diagnostics->Timelines tab
Summary: Spinner spins forever on Configure->Configuration->Diagnostics->Timelines tab
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Milan Zázrivec
QA Contact: Nandini Chandra
URL:
Whiteboard: timeline
Depends On:
Blocks: 1291696
TreeView+ depends on / blocked
 
Reported: 2015-03-25 03:48 UTC by Nandini Chandra
Modified: 2016-06-29 14:53 UTC (History)
9 users (show)

Fixed In Version: 5.6.0.7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1291696 (view as bug list)
Environment:
Last Closed: 2016-06-29 14:53:28 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Nandini Chandra 2015-03-25 03:48:17 UTC
Description of problem:
-----------------------
I ran into this issue while verifying bug 1154867.


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


How reproducible:
-----------------
Always


Steps to Reproduce:
------------------
1.Edit the CFME Server relationship for a CFME appliance
2.Navigate to configure->configuration;Select current server from the Diagnostics accordion;Click Utilization tab.
3.Move the cross-hair control over a data point on the C&U graph.
4.Left click the data point;Select 'Timeline';Select 'Daily events on this VM' or 'Hourly events on this VM'

Alternatively,follow this step after following step 1 to reproduce the issue.

2.Navigate to configure->configuration;Select current server from the Diagnostics accordion;Click Timelines tab.


Actual results:
----------------
Spinner spins forever.


Expected results:
----------------
Timeline events should be displayed.


Additional info:
---------------

Comment 3 Milan Zázrivec 2015-05-04 13:18:34 UTC
I cannot reproduce this problem on my CFME instance. Is there perhaps
a running instance or a database dump I could look into / use?

Thank you.

Comment 5 Milan Zázrivec 2015-05-25 15:00:58 UTC
https://github.com/ManageIQ/manageiq/pull/2990

Comment 6 CFME Bot 2015-06-04 23:11:07 UTC
New commit detected on manageiq/master:
https://github.com/ManageIQ/manageiq/commit/5fbe83d243f1da78605aae463e53e939907ad5a0

commit 5fbe83d243f1da78605aae463e53e939907ad5a0
Author:     Milan Zazrivec <mzazrivec>
AuthorDate: Mon May 25 16:57:17 2015 +0200
Commit:     Milan Zazrivec <mzazrivec>
CommitDate: Mon May 25 16:57:17 2015 +0200

    Fix timelines tab in diagnostics accordion
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1205492

 vmdb/app/views/layouts/_tl_options.html.haml            | 2 +-
 vmdb/app/views/ops/_diagnostics_timelines_tab.html.haml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Comment 12 Milan Zázrivec 2016-05-11 11:46:45 UTC
https://github.com/ManageIQ/manageiq/pull/8611

Comment 13 CFME Bot 2016-05-12 14:01:16 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/910a8a626ccf089719ea6e2bf7d1db75034909e9

commit 910a8a626ccf089719ea6e2bf7d1db75034909e9
Author:     Milan Zazrivec <mzazrivec>
AuthorDate: Wed May 11 13:44:55 2016 +0200
Commit:     Milan Zazrivec <mzazrivec>
CommitDate: Wed May 11 13:44:55 2016 +0200

    Fix javascript error in diagnostics timelines tab
    
    We're accessing a hash / object, not a variable.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1205492

 app/views/ops/_diagnostics_timelines_tab.html.haml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 15 Nandini Chandra 2016-05-26 16:57:18 UTC
Verified in 5.6.0.8

Comment 17 errata-xmlrpc 2016-06-29 14:53:28 UTC
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:1348


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