Bug 1012083 - bundle deployment on Windows doesn't work
Summary: bundle deployment on Windows doesn't work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Core Server
Version: JON 3.2
Hardware: x86_64
OS: Windows
unspecified
urgent
Target Milestone: ER03
: JON 3.2.0
Assignee: Thomas Segismont
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 902347 jon32-Beta-Blockers-1006862
TreeView+ depends on / blocked
 
Reported: 2013-09-25 16:32 UTC by Armine Hovsepyan
Modified: 2015-09-03 00:02 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-10-01 09:57:10 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1012076 0 unspecified CLOSED impossible war deployment to EAP6 in Windows 2021-02-22 00:41:40 UTC

Internal Links: 1012076

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
Note You need to log in before you can comment on or make changes to this bug.