Bug 815965

Summary:	[eap6] cannot create deployment on server group
Product:	[Other] RHQ Project	Reporter:	Libor Zoubek <lzoubek>
Component:	Agent	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	4.4	CC:	hrupp, theute
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-09-02 07:15:17 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:	707223

Description Libor Zoubek 2012-04-24 22:08:21 UTC

Description of problem: WAR deployment child resource could not be created on server group level.


Version-Release number of selected component (if applicable):
Version: 4.4.0-SNAPSHOT
Build Number: 5ffafd2
EAP6 ER5

How reproducible:always


Steps to Reproduce:
1.import EAP6 in domain mode
2.navigate to main-server-group
3.create deployment child
  
Actual results:creation fails
java.lang.IllegalArgumentException: Management host cannot be null.
	at org.rhq.modules.plugins.jbossas7.ASUploadConnection.<init>(ASUploadConnection.java:68)
	at org.rhq.modules.plugins.jbossas7.BaseComponent.deployContent(BaseComponent.java:365)
	at org.rhq.modules.plugins.jbossas7.BaseComponent.createResource(BaseComponent.java:319




Expected results:deployment is created on server group


Additional info:

Comment 1 Heiko W. Rupp 2012-04-30 08:51:31 UTC

No real blocker, as the deployment can be created on domain level and then promoted to a server group

Comment 2 Heiko W. Rupp 2012-05-02 09:48:45 UTC

What exactly were you doing (describe the steps). I have just gone to the main-server-group, inventory tab and was very well able to deploy a war file there.

Comment 3 Libor Zoubek 2012-05-02 13:47:40 UTC

Version: 4.4.0-SNAPSHOT Build Number: 2484565

I just did the same (and I did the same when reproduced this BZ) and I see no issue here anymore

Comment 4 Heiko W. Rupp 2013-09-02 07:15:17 UTC

Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.