Bug 1122614

Summary: adding 2 new storage nodes simultaneously does not work correctly
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: Storage NodeAssignee: Michael Burman <miburman>
Status: CLOSED EOL QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.3.0CC: fbrychta, mfoley
Target Milestone: ---   
Target Release: JON 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-05 15:00:28 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: 1120418    
Bug Blocks:    
Attachments:
Description Flags
server.log none

Description Armine Hovsepyan 2014-07-23 15:40:38 UTC 
Description of problem:
adding 2 new storage nodes simultaneously does not work correctly

Version-Release number of selected component (if applicable):
JON 3.2.0 and later

How reproducible:
always

Steps to Reproduce:
1. install jon with rhqctl install --start command
2. install 2 new storage simultaneously with agent connected to jon server from step1


Actual results:
After step2. New installed nodes cannot see each other and cannot see any other node but node installed on the same box with server


Expected results:
all nodes should see each other, thus, should have each others hostnames in rhq-server-home/rhq-storage/conf/rhq-storage-auth.conf file

Additional info:
In my env there was an additional node, which failed install, after step2 that node cannot be got back.
server.log is attached
Comment 1 Armine Hovsepyan 2014-07-23 15:44:34 UTC 
Created attachment 920260 [details]
server.log
Comment 2 John Sanda 2014-08-29 12:17:53 UTC 
Bumping the target release due to time constraints. Work has been started though in the storage_workflow branch.
Comment 5 Filip Brychta 2019-08-05 15:00:28 UTC 
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.