Bug 1066550

Summary:	[eap6] Autostart is not working when adding a new managed server to domain controller
Product:	[Other] RHQ Project	Reporter:	Filip Brychta <fbrychta>
Component:	Plugins	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	hrupp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1070299 (view as bug list)		Environment:
Last Closed:		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:	1070299

Description Filip Brychta 2014-02-18 15:49:13 UTC

Description of problem:
Newly added managed server is not started event though the autostart option was enabled

Version-Release number of selected component (if applicable):
Version :	
4.10.0-SNAPSHOT
Build Number :	
c526922

Eap6.2.0

How reproducible:
Alwys

Steps to Reproduce:
1. go to EAP Domain Controller resource->Inventory->Create Child->Managed Server 
2. pick 'serverFour' as a name and press Next button
3. use 'master' host, 'main-server-group', 'full-sockets' binding, relevant port offset for your machine, enable 'Autostart' and press Finish button

Actual results:
Managed server is visible in the inventory but it is NOT available and process on target machine is NOT started (should be visible using: ps -ef | grep java | grep serverFour)

No exceptions in logs.

Expected results:
Managed server process is started and created resource is UP in the inventory.

Additional info:
Managed server can be started manually by scheduling operation 'start' and then everything works fine.