Bug 1272266

Summary: Spinner spins forever while viewing Utilization graphs for DB tables
Product: Red Hat CloudForms Management Engine Reporter: Nandini Chandra <nachandr>
Component: UI - OPSAssignee: Martin Povolny <mpovolny>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: high Docs Contact:
Priority: high    
Version: 5.5.0CC: dclarizi, hkataria, jhardy, jprause, mfeifer, mpovolny, obarenbo, tcarlin
Target Milestone: GAKeywords: ZStream
Target Release: 5.5.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: appliance:database:spinner
Fixed In Version: 5.5.3.2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-13 18:39:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nandini Chandra 2015-10-15 22:43:55 UTC
Description of problem:
------------------------


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


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


Steps to Reproduce:
------------------
1.Navigate to Configure->Configuration
2.From the Database accordion,click any table.
3.On the right,click the utilization tab.


Actual results:
---------------
Spinner spins forever while viewing Utilization graphs for DB tables.


Expected results:
-----------------
Utilization graphs should be rendered.


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

Comment 3 Martin Povolny 2015-11-25 09:33:44 UTC
upstream PR: https://github.com/ManageIQ/manageiq/pull/5595

Comment 4 CFME Bot 2015-12-08 23:47:09 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/0da543c2ca7fbbe524a2ea91868f3a335390c60e

commit 0da543c2ca7fbbe524a2ea91868f3a335390c60e
Author:     Martin Povolny <mpovolny>
AuthorDate: Wed Nov 25 10:31:26 2015 +0100
Commit:     Martin Povolny <mpovolny>
CommitDate: Wed Nov 25 10:32:11 2015 +0100

    Add missing option for ajax call in settings/configuration/databases.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1272266

 app/controllers/ops_controller.rb | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

Comment 7 CFME Bot 2015-12-21 20:40:26 UTC
New commit detected on cfme/5.5.z:
https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=27902059086c071c4364b57144aeffcd3740f5e9

commit 27902059086c071c4364b57144aeffcd3740f5e9
Author:     Martin Povolny <mpovolny>
AuthorDate: Wed Nov 25 10:31:26 2015 +0100
Commit:     Martin Povolny <mpovolny>
CommitDate: Mon Dec 21 17:19:12 2015 +0100

    Add missing option for ajax call in settings/configuration/databases.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1272266

 app/controllers/ops_controller.rb | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

Comment 8 CFME Bot 2015-12-21 20:40:32 UTC
New commit detected on cfme/5.5.z:
https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=585e17d31350c6ac9b6a1d9fc779d67b45f2517c

commit 585e17d31350c6ac9b6a1d9fc779d67b45f2517c
Merge: bbd2dc8 2790205
Author:     Dan Clarizio <dclarizi>
AuthorDate: Mon Dec 21 15:37:18 2015 -0500
Commit:     Dan Clarizio <dclarizi>
CommitDate: Mon Dec 21 15:37:18 2015 -0500

    Merge branch 'cherry_5595' into '5.5.z'
    
    Add missing option for ajax call in settings/configuration/databases.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1272266
    
    clean cherry-pick from https://github.com/ManageIQ/manageiq/pull/5595
    
    upstream commit # 0da543c2ca7fbbe524a2ea91868f3a335390c60e
    
    See merge request !651

 app/controllers/ops_controller.rb | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

Comment 12 Nandini Chandra 2016-02-16 14:30:47 UTC
Verified that this issue is fixed in 5.5.2.4.

Comment 14 errata-xmlrpc 2016-04-13 18:39:16 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:0616