Bug 975585

Summary:	Manually typed Resource name in the "Resource Metric Graph" portlet breaks Dashboards (Globally uncaught exception)
Product:	[JBoss] JBoss Operations Network	Reporter:	Heiko W. Rupp <hrupp>
Component:	UI	Assignee:	Heiko W. Rupp <hrupp>
Status:	CLOSED DUPLICATE	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	JON 3.1.2	CC:	hrupp, ud1bugzilla
Target Milestone:	---
Target Release:	JON 3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	918051	Environment:
Last Closed:	2013-08-09 16:22:51 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:	918051
Bug Blocks:

Description Heiko W. Rupp 2013-06-18 20:16:30 UTC

+++ This bug was initially created as a clone of Bug #918051 +++

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).

--- Additional comment from Heiko W. Rupp on 2013-06-18 16:00:17 EDT ---

This is still true with RHQ 4.7 and current master

--- Additional comment from Heiko W. Rupp on 2013-06-18 16:13:42 EDT ---

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

Comment 1 Heiko W. Rupp 2013-07-02 10:58:11 UTC

This was solved in master and is part of RHQ 4.8, so will be in JON 3.2

Comment 2 Heiko W. Rupp 2013-08-09 16:22:51 UTC

Turns out this is a dup of 846818

*** This bug has been marked as a duplicate of bug 846818 ***