Bug 972771 - storage node table is not being updated when new storage is inventoried
Summary: storage node table is not being updated when new storage is inventoried
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Database
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER01
: JON 3.2.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 951619
TreeView+ depends on / blocked
 
Reported: 2013-06-10 14:42 UTC by Armine Hovsepyan
Modified: 2015-09-03 00:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-02 20:36:19 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
storage_node_datamodel (332.22 KB, image/png)
2013-06-27 10:48 UTC, Armine Hovsepyan 		no flags Details
View All

Description Armine Hovsepyan 2013-06-10 14:42:17 UTC 
Description of problem:
storage node table is not being updated when new storage is inventoried 

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


How reproducible:


Steps to Reproduce:
1. install rhq storage on ip1
2. install rhq server and agent on ip1
3. install rhq storage and agent on ip2 and connect to server in ip1

Actual results:
storage node table is not being updated when new storage is inventoried 

Expected results:
storage node table is updated when new storage is inventoried (new storage is visible in db)

Additional info:
http://d.pr/i/JOVB
Comment 1 John Sanda 2013-06-26 18:18:59 UTC 
Armine, can you retest this? The relevant code has undergone a few iterations since  you opened this bug, and a new storage node entity should get created when the corresponding resource is auto-imported into inventory.
Comment 2 Armine Hovsepyan 2013-06-27 10:48:07 UTC 
Created attachment 766055 [details]
storage_node_datamodel
Comment 3 Armine Hovsepyan 2013-06-27 12:59:09 UTC 
verified,

please get attached verification screen-shot.
Note You need to log in before you can comment on or make changes to this bug.