Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1351768

Summary: [GSS](6.4.z) CLI fails to find deployment artifact located in a Windows Share UNC path
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Taneem Ibrahim <tibrahim>
Component: CLIAssignee: Radovan Netuka <rnetuka>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: high Docs Contact:
Priority: high    
Version: 6.4.6CC: bmaxwell, brian.stansberry, dosoudil, jbilek, jboss-set, jtruhlar, msochure, rnetuka
Target Milestone: CR1Keywords: Regression
Target Release: EAP 6.4.10   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 13:01:34 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: 1339868    

Description Taneem Ibrahim 2016-06-30 18:56:52 UTC 
Description of problem:

This worked fine until CP06 release. If a WAR or EAR file path is an UNC windows share file path then the deployment fails with file not found error. In this scenario, CLI adds an extra "s" character in the deployment path. However, the same WAR/EAR deploys fine if the path is changed to a local path.

Example:

This deployment is successful:

1. jboss-cli.bat -c --controller=$mytestserver.dot.com:9999  --command="deploy "d:\Test\Drop732863\TEST.war" --server-groups=MyHA"

However, this one fails to find the WAR file even though it exists in the same folder as above but the path is an UNC one instead of the local one:

2. jboss-cli.bat -c --controller=$mytestserver.dot.com:9999  --command="deploy "\\stlmjbad001\Test\Drop732863\TEST.war" --server-groups=MyHA"

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

JBoss EAP 6.4 CP06


How reproducible:

Using a UNC path for the WAR file location on a Windows server consistently shows the same error.

Steps to Reproduce:
1. Deploy a WAR or an EAR file with a UNC path using the following CLI:

jboss-cli.bat -c --controller=$mytestserver.dot.com:9999  --command="deploy "\\stlmjbad001\Test\Drop732863\TEST.war" --server-groups=MyHA"


Actual results:

Path \\stlmjbad001\Test\Drop732863\TEST.war doesn't exist. 

Expected results:

It should deploy successfully since TEST.war exists. This worked fine until CP06 release. Same deployment when attempted on a EAP 6.4.0 CP05 instance it is successful.


Additional info:

This is preventing the customer from patching JBoss EAP 6.4.z. They have to use the Windows share paths for deployment from Jenkins.
Comment 1 Taneem Ibrahim 2016-06-30 19:20:35 UTC 
Just to clarify this does not work in JBoss EAP 6.4.6, 6.47, and 6.4.8 versions. It worked until 6.4.5 fine. So something between 6.4.5 and 6.4.6 caused this windows share UNC path based deployments to fail.

Also when the deployment fails it adds an extra "s" in the path:

Path \\sstlmjbad001\Test\Drop732863\TEST.war doesn't exist. 

In this case the actual path was \\stlmjbad001\Test\Drop732863\TEST.war .
Comment 2 Taneem Ibrahim 2016-07-01 18:38:17 UTC 
Windows UNC path - http://compnetworking.about.com/od/windowsnetworking/g/unc-name.htm
Comment 3 Taneem Ibrahim 2016-07-01 19:22:24 UTC 
Customer Environment info:

OS: Microsoft Windows Server 2012 R2 Standard - 64-bit

JDK: Oracle Java SE Development Kit 8 Update 51 (64-bit) 8.0.510.16
Comment 10 Radovan Netuka 2016-07-19 14:16:58 UTC 
No upstream fix is required.
Comment 12 Radovan Netuka 2016-07-20 11:34:08 UTC 
PR: https://github.com/jbossas/jboss-eap/pull/2809
Comment 14 Jiří Bílek 2016-08-29 15:24:11 UTC 
Verified with EAP 6.4.10.CP.CR2
Comment 15 Petr Penicka 2017-01-17 13:01:34 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.