Bug 918051

Summary:	Manually typed Resource name in the "Resource Metric Graph" portlet breaks Dashboards (Globally uncaught exception)
Product:	[Other] RHQ Project	Reporter:	ud1 <ud1bugzilla>
Component:	Core UI	Assignee:	Heiko W. Rupp <hrupp>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	hrupp
Target Milestone:	---
Target Release:	RHQ 4.8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	975585 (view as bug list)		Environment:
Last Closed:	2013-09-11 09:53:29 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:
Bug Depends On:
Bug Blocks:	975585

Description ud1 2013-03-05 11:45:59 UTC

Description of problem:
Dashboards become unavailable

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

Steps to Reproduce:
   1. Create new Dashboard
   2. Add "Resource Metric Graph" portlet
   3. Configure portlet, set Resource name from list to "C:\" and Metric to "Free Space", and after manually type "C:\test" into the Resource name. Save.
   4. Relogin.
  
   Dashboards would be unavailable.
   String value in the RHQ_CONFIG_PROPERTY with name "resourceId" for this portlet would be "C:\test", causing NumberFormatException error (is seems that it expected to be an integer number, not a string).

Comment 1 Heiko W. Rupp 2013-06-18 20:00:17 UTC

This is still true with RHQ 4.7 and current master

Comment 2 Heiko W. Rupp 2013-06-18 20:13:42 UTC

to get going again, the offending portlet currently needs to be manually removed from the rhq_dashboard_portlets page

Comment 3 Heiko W. Rupp 2013-06-19 04:03:35 UTC

master fe019d24ded5

Thanks for reporting this.

Comment 4 Heiko W. Rupp 2013-09-11 09:53:29 UTC

Bulk closing of old issues now that HRQ 4.9 is in front of the door.

If you think the issue has not been solved, then please open a new bug and mention this one in the description.