Bug 760078

Summary: Failed to import "Process" resource
Product: [Other] RHQ Project Reporter: vlad crc <vlad.craciunoiu>
Component: InventoryAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2CC: hrupp, jshaughn
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-18 09:24:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 760116    
Attachments:
Description Flags
exception stacktrace in log file none

Description vlad crc 2011-12-05 11:57:06 UTC 
Created attachment 540817 [details]
exception stacktrace in log file

Description of problem:
I try to import a resource of type "Process", just like in this demo:
http://www.rhq-project.org/display/JOPR2/Demo-ProcessMonitoring
but I get the error: "Failed to manually import resource".


Version-Release number of selected component:
4.2


How reproducible:
RHQ server 4.2 is running on an Linux system, the monitored JBoss 4.2.3 and the RHQ agent are running on another Linux box.


Steps to Reproduce:
1. Go to "Inventory", select a platform, right-click on the platform.
2. Select "Import" -> "Process", "Resource import wizard" opens.
3. For "Type" select "Process query".
4. For "Piql" uncheck the "Unset?" check-box and in "Value" field enter this:
         process|basename|match=.*java.*,arg|*|match=org.jboss.Main
5. Click "Finish" button.
  

Actual results:
On the top banner I got an error message saying: "Failed to manually import resource".
In RHQ server log I have the error attached.


Expected results:
The process resource should be successfully imported and it should appear in inventory.
Comment 1 Jay Shaughnessy 2012-01-17 15:11:11 UTC 
These steps worked fine for me on Windows. I also tried it with the agent
down, but that resulted in a different, and expected, connection exception.

I suggest someone try this
Comment 2 Jay Shaughnessy 2012-01-17 17:20:07 UTC 
... I just tried this on Linux and it worked for me again.

So, I can't repro this.  Perhaps the agent was running as a user unable
to perform the process query?

Setting back to NEW
Comment 3 vlad crc 2012-01-18 09:24:24 UTC 
My bad, my test cases were wrong. I close the bug. Sorry for trouble...