Bug 538143

Summary: Error message needs to be more specific when you have an invalid location when you create new content provider
Product: [Other] RHQ Project Reporter: Preethi Thomas <pthomas>
Component: ContentAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Rajan Timaniya <rtimaniy>
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: cwelton, mfoley, whayutin
Target Milestone: ---Keywords: SubBug
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-27 19:14:41 UTC Type: ---
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: 565635, 565650    

Description Preethi Thomas 2009-11-17 18:23:39 UTC 
Description of problem:

Error message needs to be more specific when you have an invalid location when you create new content provider for RHN Hosted source.

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


How reproducible:


Steps to Reproduce:
1. Content->Content Providers->Create New
2. Select RHN Hosted Source
2. Edit the location to a bad value, i.e., "htp://"
3. Enter all the other required values
4. 
  
Actual results:
Error: Failed to start adapter for [ContentSource: id=[0], name=[test-negative2]]. Cause: org.rhq.enterprise.server.plugin.pc.content.InitializationException:java.lang.reflect.InvocationTargetException -> java.lang.reflect.InvocationTargetException:null -> java.lang.IllegalArgumentException:Invalid 'location' property

Expected results:

An error message that makes sense to the user. Saying that the Invalid location property

Additional info:
Comment 1 wes hayutin 2010-02-16 16:59:24 UTC 
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug
Comment 2 wes hayutin 2010-02-16 17:04:31 UTC 
making sure we're not missing any bugs in rhq_triage
Comment 3 Corey Welton 2010-12-16 14:05:06 UTC 
Rajan, see if this page still exists.  if not, close the bug
Comment 4 Mike Foley 2011-04-27 19:14:41 UTC 
page does not exist in RHQ 4.0 CR1.