Bug 1012083

Summary:	bundle deployment on Windows doesn't work
Product:	[JBoss] JBoss Operations Network	Reporter:	Armine Hovsepyan <ahovsepy>
Component:	Core Server	Assignee:	Thomas Segismont <tsegismo>
Status:	CLOSED NOTABUG	QA Contact:	Mike Foley <mfoley>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	hrupp, mfoley, myarboro, tsegismo
Target Milestone:	ER03
Target Release:	JON 3.2.0
Hardware:	x86_64
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-01 09:57:10 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:	902347, 1006862

Description Armine Hovsepyan 2013-09-25 16:32:59 UTC

Description of problem:
bundle deployment on Windows doesn't work

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

How reproducible:
always

Steps to Reproduce:
1. install jon server-agent-storage on windows
2. install jboss eap6.1.1 on windows (download dir http://download.devel.redhat.com/released/JBEAP-6/6.1.1/)
3. deploy a bundle using recipe and war from bug #902347

Actual results:
bundle deployment status is red
war not found

Expected results:
bundle deployed with corresponding version into correct deploy dir.

Additional info:
bundle status screenshot -> http://d.pr/i/3DvJ
directory where war should have been -> http://d.pr/i/aFr8

Seems file is broken for windows (interconnected bugs 1012040, 1012076)

Comment 1 Heiko W. Rupp 2013-09-30 14:27:21 UTC

What JDK was that on?

Comment 2 Armine Hovsepyan 2013-09-30 15:25:21 UTC

fragment from server log -> http://d.pr/f/UX6k
fragment from agent log -> http://d.pr/f/3xyN

Comment 3 Thomas Segismont 2013-09-30 16:09:05 UTC

This really looks like the same problem as in BZ1012076 (same error message). I will take care of this one too.

Comment 4 Armine Hovsepyan 2013-10-01 09:57:10 UTC

the issue was environmental -  please see comment from Thomas Segismont under bug #1012076 comment #6