+++ This bug was initially created as a clone of Bug #844217 +++ Description of problem: Deploy a bundle with a WAR archive to JBoss AS 7 standalone server leads to wrong directory. How reproducible: Steps to Reproduce: 1.Make an Ant bundle with a simple WAR archive within. 2.Update the bundle file to RHQ to create a new bundle. 3.New a group with JBoss AS 7 standalone server 4.Deploy the bundle to the created group. Actual results: The WAR is deployed correctly at <JBoss Standalone Server>/standalone/deployments/ Expected results: The WAR is deployed at <JBoss Standalone Server>/standalone/deployment/<Destination Directory> Additional info: This should be a typo. --- Additional comment from hrupp on 2012-07-30 10:24:52 EDT --- master 264bf23cb1
release/jon3.1.x branch commit: http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commit;h=bb1765a555263daa7a4185461ed3b730b2a5246e
JON 3.1.1 ER1 build is available. Moving to ON_QA. https://brewweb.devel.redhat.com/buildinfo?buildID=226942
reopened. EAP6 ER6 Jon-3.1.1-CR1 Deployment is still being done under EAP6/standalone/deployments
Armine, is this with a server you had already in inventory or with an as7 server, that you took into inventory after installing the cr1 ?
Hi Heiko, It's the old eap, but has been added into inventory after CR1 was installed. shall i install new eap?
I've verified that it works correctly with freshly imported as7 servers Now what happens is that servers in inventory have the old bad value set and this does not get overwritten by the update.
The value 'deployments' should not be hard-coded as this is a configurable option in EAP 6 and can change. Therefore, it needs to be a trait and re-discovered from time-to-time or obtained through some other method.
A new implementation using a trait is now pushed to master as 1ace95e The plugin config 'deployDir' has been removed, so on plugin upgrade users will get the correct setting. Todo QA: test deploying a bundle after plugin upgrade to a server that was in inventory before the upgrade. As well as deploy to a server that is new in inventory after the upgrade.
release-branch 09ac5f9a4c1d QA: also check for drift in the deploy dir.
Moving to ON_QA. The JON 3.1.1 ER3 build is available at https://brewweb.devel.redhat.com/buildinfo?buildID=230321.
reopen. 1. Installed JON 3.1.1 ER3 server/agent 2. Installed EAP plugin ER2 3. Inventoried EAP server 4. Deployed bundle 5. Uploaded EAP plugin ER3 jar 6. Updated plugins 7. Deployed bundle -------> incorrect directory 8. Reloaded EAP 9. Deployed bundle -------> incorrect directory 10. Restarted EAP 11. Deployed bundle -------> incorrect directory Clean installation worked correctly. Any deploy dir change is being detected and deployment in correct (new) directory is being done.
Armine, in step 7 did you deploy a new bundle version of the bundle you deployed in step 4 or did you deploy a completely new bundle? Did you check between steps 6 and 7 if/that the trait has been collected and shows the correct value?
Armine in step 7,9,11 -- what is the incorrect directory this writes to?
So I tried the following: * installed jon 311er3 server/agent, er2 eap7 plugin * inventoried eap6ga * deployed a bundle - worked correctly * updated plugin to er3 version of the plugin * deployed a bundle - worked correctly * trait is also collected with correct value
Hi Heiko, Did you do this for a changed deploy dir or it was for deployments dir? As it says in comment "Clean installation worked correctly. Any deploy dir change is being detected and deployment in correct (new) directory is being done." - deploy dir needs to be changed beforehand. Regards, Armine H
verified! Thanks heiko.