Bug 824502 - Update farmed Application Deployment (EAR/WAR) results in non-farmed deployment
Update farmed Application Deployment (EAR/WAR) results in non-farmed deployment
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 5 (Show other bugs)
JON 3.0.0
All All
unspecified Severity high
: ---
: JON 3.1.0
Assigned To: RHQ Project Maintainer
Mike Foley
: 824498 (view as bug list)
Depends On: EMBJOPR-366 820650
Blocks: jon30-bugs jon310-sprint11/rhq44-sprint11
  Show dependency treegraph
Reported: 2012-05-23 11:41 EDT by Stefan Negrea
Modified: 2013-09-11 06:58 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: EMBJOPR-366
JON 2.4 EAP 5.0.1 admin-console
Last Closed: 2013-09-11 06:58:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stefan Negrea 2012-05-23 11:41:07 EDT
+++ This bug was initially created as a clone of Bug #646631 +++

Description of problem:
If an application is deployed to an AS instance's farm directory and the Update Content operation is performed, application is no longer deployed to farm.

Version-Release number of selected component (if applicable):
RHQ 3.0.0
JON 2.4.0
Embedded JOPR (admin-console) with EAP 5.0.0, EAP 5.0.1

How reproducible:

Steps to Reproduce:
1. Setup a two node EAP cluster
2. Deploy an application (EAR/WAR) to node1's farm using admin-console
3. Verify application was deployed to both node1 and node2
4. Update the application using the same EAR/WAR (From admin-console, expand and select the deployed EAR/WAR and select it's Content tab and then click Update)

Actual results:
The updated deployed application is now only deployed to node1 in its deploy directory

Expected results:
The updated deployed application is deployed to node1 and node2 and appears in their farm directory

Additional info:
This is a result of the StandaloneManagedDeploymentComponent.deployPackages method invoking DeploymentUtils.deployArchive without a means of passing in whether to deploy farmed or not. Currently, the method appears to support a deployExploded boolean but no method of passing in whether it is farmed or not. The DeploymentUtils.deployArchive method should probably accept a deployFarmed boolean as well as the deployPackages method being updated to check to see if the updated deployment was farmed. Of course, this may be very error prone as this would be directly tied to a hard-coded path name. Maybe we should gather these options from ProfileService or Inventory before we remove the old deployment?
Comment 1 Stefan Negrea 2012-05-23 11:43:30 EDT
The AS5 deployer uses the file name as-is to determine the name of the app to be updated/deployed. Instead of adding the random UUID to the archive to be deployed, add the random UUID to a temp folder name and then download content there (leaving the file name unchanged). This issue has been fixed for both farmed and non-farmed deployments.

Another update was to switch to the farm version of the AS5 deployer prior to stopping and deleting existing content. The switch to a farm deployer was happening too late (prior to deployment) and was not stopping and removing the farmed application prior to the new deployment.

release/jon3.1.x branch commits:

Comment 2 Larry O'Leary 2012-05-23 11:45:20 EDT
*** Bug 824498 has been marked as a duplicate of this bug. ***
Comment 3 John Sanda 2012-06-05 10:35:59 EDT
Moving to ON_QA since this is included in the CR2 build.
Comment 4 Radim Hatlapatka 2013-03-01 09:31:40 EST
Verified against JON 3.1.2 GA and EAP 5.1.2 and EAP 5.2.0

Note You need to log in before you can comment on or make changes to this bug.