Bug 795851

Summary: Redeployment of exploded archive using content system causes deployment to become zipped and unavailable on EAP 4.3
Product: [Other] RHQ Project Reporter: Libor Zoubek <lzoubek>
Component: ContentAssignee: Stefan Negrea <snegrea>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: urgent Docs Contact:
Priority: medium    
Version: 4.3CC: hrupp, theute
Target Milestone: ---   
Target Release: JON 3.1.0   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugzilla.redhat.com/show_bug.cgi?id=788762
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 799163 (view as bug list) Environment:
Last Closed: 2014-03-25 22:59:57 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 799163    

Description Libor Zoubek 2012-02-21 11:23:06 EST
Version-Release number of selected component (if applicable):
Version: 3.0.1.GA
Build Number: dd8a001:fbca611
EAP 4.3 CP10

How reproducible:always

Steps to Reproduce:
1. have EAP started in default profile inventoried in JON
2. deploy a hello.war (Create child in EAP's inventory tab, select archive to be exploded [Deploy zipped=No])
3. wait for deployment to appear among other EAP's children in inventory
4. ASSERT deployment is exploded on filesystem (in EAP deploy dir) and is reachable on EAP via HTTP
5. Navigate to hello.war resource, select Content tab
6. Click 'New' upload new version of war (some modified version)
Actual results:

- Deployment becomes unavailable on server (server returns 404)
- on file system it is no longer exploded, you'll find hello.war file
- after a while, deployment is detected as offline by JON 

This is what appears in EAP's log

15:43:05,282 INFO  [TomcatDeployer] deploy, ctxPath=/hello,
15:44:20,585 INFO  [TomcatDeployer] deploy, ctxPath=/hello,
15:44:20,946 INFO  [TomcatDeployer] undeploy, ctxPath=/hello,

Expected results:

- modified version of hello.war becomes available via HTTP
- on file system, deployment remains exploded

Additional info: setting severity to urgent, because it could be very common usecase
Comment 3 Stefan Negrea 2012-02-22 14:44:45 EST
The deployment code does not take into account current application state (zipped or exploded) and deploys everything as zipped. This is not a regression with respect to the content changes recently made. I tested with EAP 4.2 and 4.3 CP10 and deployments succeed regardless of existing deployment state (zipped or exploded).

Each application has a flag dedicated to this (if the current deployment is zipped or exploded) but is not properly used for content updates. This is not a regression but a fix can be placed in future releases to keep existing deployment configuration.
Comment 5 Mike Foley 2012-02-27 10:49:02 EST
triage to JON 3.1 mfoley,crouch
Comment 9 Stefan Negrea 2014-03-25 22:59:57 EDT
Blocking BZ fixed.