Bug 645723 - Agent discovery command message shows resource id with comma [,]
Summary: Agent discovery command message shows resource id with comma [,]
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
low
medium vote
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq4
TreeView+ depends on / blocked
 
Reported: 2010-10-22 10:03 UTC by Rajan Timaniya
Modified: 2011-05-24 01:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-24 01:11:29 UTC


Attachments (Terms of Use)

Description Rajan Timaniya 2010-10-22 10:03:26 UTC
Description of problem:
Agent discovery command message shows resource id with comma [,]

> discovery --verbose --resourceId=10013
The given resource ID [10,013] does not match any resource in inventory.

Version-Release number of selected component (if applicable):
RHQ-Master build #442
http://hudson-qe.rhq.rdu.redhat.com:8080/view/RHQ/job/ci-rhq-master/442/

How reproducible:
Always

Steps to Reproduce:
1) Installed RHQ server and agent

2) Execute command on agent: discovery --verbose --resourceId=<INVALID_RESOURCE_ID>
  
Actual results:
Agent discovery command message shows resource id with comma [,]

Expected results:
Agent discovery command message should not show resource id with comma.
> discovery --verbose --resourceId=10013
The given resource ID [10013] does not match any resource in inventory.

Comment 1 John Mazzitelli 2011-02-18 16:01:08 UTC
fixed... commit 6f88237

Comment 2 Sunil Kondkar 2011-04-11 12:14:48 UTC
Verified on build#1140 (Version: 4.0.0-SNAPSHOT Build Number: 0589b9e)

Agent discovery command message does not display resource id with comma.

Marking as verified

Comment 3 Corey Welton 2011-05-24 01:11:29 UTC
Bookkeeping - closing bug - fixed in recent release.

Comment 4 Corey Welton 2011-05-24 01:11:29 UTC
Bookkeeping - closing bug - fixed in recent release.


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