Bug 1040493

Summary: Incorrect interaction between deployments/ directory and CLI
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: dereed
Component: Domain ManagementAssignee: Emmanuel Hugonnet (ehsavoie) <ehugonne>
Status: CLOSED DUPLICATE QA Contact: Petr Kremensky <pkremens>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: brian.stansberry, emuckenh
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: 2014-05-07 12:55:53 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:

Description dereed 2013-12-11 14:14:57 UTC 
Description of problem:
Modifying the same deployment through the CLI and deployments/ can get the deployment into an incorrect state.

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

How reproducible:
Always

Steps to Reproduce:
1.  Put deployment (test.war) in deployments/ so it will be deployed
2.  "undeploy --keep-content test.war"
3.  "deploy --name=test.war"
4.  Restart EAP

Actual results:
test.war is not deployed because step 2 created test.war.undeployed, but step 3 did not remove it.

Expected results:
test.war is deployed

Additional info:

I also saw some other problems when modifying the same deployment through both deployments/ and the CLI, but haven't replicated them yet.
Comment 1 Alexey Loubyansky 2013-12-11 14:21:40 UTC 
AFAIK, deployments that are hot-deployed are not managed (by the means of the domain management api and tools based on it) deployments.
Comment 2 dereed 2013-12-11 14:48:24 UTC 
But the domain API does operate on the deployment and gets it into an incorrect state.

(note: I would be fine with the fix being that the API refuses to touch hot-deployed deployments, if that's the desired behavior)
Comment 5 Emmanuel Hugonnet (ehsavoie) 2014-05-07 12:55:53 UTC 

*** This bug has been marked as a duplicate of bug 1074999 ***