Bug 971825

Summary: Storage node auto-import - Agent platform having no storage node is being auto-imported into inventory
Product: [Other] RHQ Project Reporter: Armine Hovsepyan <ahovsepy>
Component: Core UIAssignee: Jay Shaughnessy <jshaughn>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: hrupp, jshaughn, mfoley
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-07 16:13:20 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:    
Bug Blocks: 951619    

Description Armine Hovsepyan 2013-06-07 10:51:29 UTC 
Description of problem:
 Agent platform having no storage node is being auto-imported into inventory

Version-Release number of selected component (if applicable):
RHQ 4.8 build:bf44b14

How reproducible:
always

Steps to Reproduce:
1. Server with rhq storage installed (ip1)
2. agent installed and connected to server (ip1)
3. agent installed and connected to server (ip2)


Actual results:
both ip1 and ip2 platforms inventoried bypassing discovery queue

Expected results:
only ip1 platform is inventoried bypassing discovery queue

Additional info:
ip1: 10.16.23.133
ip2: 10.16.23.140
Comment 1 Jay Shaughnessy 2013-06-07 15:17:26 UTC 
I was unable to reproduce this using Armine's environment. Although, there was something odd to start with. I was unable to uninventory the agent platform until I uninventoried the children first.  I can't explain that.

But, afterwards things worked as expected.  I don't think there is an issue with the autocommit as it explicitly works with only the parent platform of the StorageNode resource.

Unless we can recreate the issue again, I will say that this was a transient environmental issue. But, we need to keep an eye out for anything else odd in this area, that may support evidence of some kind of issue.
Comment 2 Armine Hovsepyan 2013-06-07 16:13:20 UTC 
Re-tested with new environment:
10.16.23.63 server
10.16.23.63, 10.16.23.106, 10.16.23.198 agents

It must have been an environment issue. Marking bug as not-bug.