Bug 816235 - CLI - DiscoveryBoss.importResources(resources) fails when parent resources are not already in inventory.
Summary: CLI - DiscoveryBoss.importResources(resources) fails when parent resources ar...
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: CLI, Usability
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 743405
TreeView+ depends on / blocked
 
Reported: 2012-04-25 15:14 UTC by Filip Brychta
Modified: 2020-04-27 01:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Filip Brychta 2012-04-25 15:14:21 UTC
Description of problem:
DiscoveryBoss.importResources(resources) doesn't import related parent resources automatically. User is forced to import them manually otherwise importing fails. This could be really time-consuming activity for complex hierarchy. 

Version-Release number of selected component (if applicable):
Version: 4.4.0-SNAPSHOT
Build Number: ca5eecb

How reproducible:
Always

Steps to Reproduce:
1. uninventory all resources
2. use DiscoveryBoss.importResources(resources) to import JBossAS
  
Actual results:
Caused by: java.lang.IllegalStateException: [Warning] Cannot commit resource [Resource[id=25264, uuid=4bcd99f8-57ef-43a8-813f-e837ecfb0664, type={JBossAS5}JBossAS Server, key=/home/testuser/jboss-eap-5.1/jboss-as/server/default, name=EAP localhost:1099 default, parent=dhcp-27-145.brq.redhat.com, version=EAP 5.1.2]] to inventory, because its parent resource [Resource[id=25263, uuid=98c84f72-9252-46f8-b4e4-4fa520a4ab79, type={Platforms}Linux, key=dhcp-27-145.brq.redhat.com, name=dhcp-27-145.brq.redhat.com, parent=<null>, version=Linux 3.3.0-8.fc16.x86_64]] has not yet been committed.

Expected results:
JBossAS is imported

Comment 1 Mike Foley 2012-04-30 16:02:13 UTC
triaged 4/30/2012 by loleary, ccrouch, mfoley


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