Bug 1397792 - Resource Usage page popup error
Summary: Resource Usage page popup error
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: RDO
Classification: Community
Component: openstack-horizon
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: trunk
Assignee: Radomir Dopieralski
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-23 11:11 UTC by Huang Shi Lin
Modified: 2018-08-21 12:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-21 12:25:04 UTC


Attachments (Terms of Use)
RDO Resource Usage Error screenshot (32.55 KB, image/png)
2016-11-23 11:11 UTC, Huang Shi Lin
no flags Details
Horizon access log file (5.73 KB, text/plain)
2016-11-24 08:32 UTC, Huang Shi Lin
no flags Details
Horizon error log file (1.28 KB, text/plain)
2016-11-24 08:33 UTC, Huang Shi Lin
no flags Details

Description Huang Shi Lin 2016-11-23 11:11:38 UTC
Created attachment 1223173 [details]
RDO Resource Usage Error screenshot

Description of problem:
Install RDO Newton version as all-in-one POC environment. After clean install, I just open dashboard and click each button and open each page to double check if everything works. When I navigate to "Admin->System->Resource Usage->Stats", ther is a popup message in the top right corner reads "Error: An error occurred, Please try again later." Since I did not configure/modify anthing yet, I'm nore sure where is the problem.

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

rdo-release-newton-4.noarch

How reproducible:


Steps to Reproduce:
1. Install all-in-one env following this link:https://www.rdoproject.org/install/quickstart/
2.Open dashboard: http://YOUR_IP/dashboard
3.Navigate to Admin->System->Resource Usage->Stats

Actual results:
Ther is a popup message in the top right corner reads "Error: An error occurred, Please try again later."

Expected results:
No error message show up.


Additional info:

Comment 1 Radomir Dopieralski 2016-11-23 12:10:14 UTC
Do you have Horizon's logs from the event?

Comment 2 Huang Shi Lin 2016-11-24 08:32:12 UTC
Created attachment 1223624 [details]
Horizon access log file

In the log file, 

GET /dashboard/admin/metering/?tab=ceilometer_overview__stats HTTP/1.1" 200 1048

Is the action I take to recreate this problem.

Comment 3 Huang Shi Lin 2016-11-24 08:33:32 UTC
Created attachment 1223626 [details]
Horizon error log file

I didn't see any error message in the log file related to this problem.

Comment 4 Utian Ayuba 2017-06-22 06:38:19 UTC
I still experience similar issue

Comment 5 Radomir Dopieralski 2017-06-22 07:55:13 UTC
Are there any errors in the browser's JavaScript console?

Comment 6 Utian Ayuba 2017-06-22 08:07:12 UTC
The JS console only say "Use of getPreventDefault() is deprecated.  Use defaultPrevented instead." on every menu link

And I can not found any error message on horizon and ceilometer httpd log

Comment 7 Radomir Dopieralski 2017-06-22 08:16:24 UTC
Thank you. We will try to reproduce it and figure out what is happening, but it may take some time.

Comment 8 Utian Ayuba 2017-06-22 08:25:12 UTC
Please take your time, Sir. Many thanks

Comment 9 Christopher Brown 2017-06-29 12:56:14 UTC
Just out of interest are you seeing this in Ocata also?

Thanks

Comment 10 Utian Ayuba 2017-07-02 08:28:38 UTC
I tried install the Ocata using packstack but the "Resource Usage" tab is not appear in Admin > System.

Is it related with gnocchi services that used as part of ceilometer services since Newton?

Comment 11 Radomir Dopieralski 2017-07-03 06:58:12 UTC
That panel is disabled by default for performance reasons. You can enable it by deleting the openstack_dashboard/enabled/_99_disable_metering_dashboard.py* files.

Comment 12 Radomir Dopieralski 2018-08-21 12:25:04 UTC
I'm closing this, because that view was disabled staring from Ocata, and completely removed in more recent releases, so there is no more anything to fix.


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