Created attachment 911791 [details] deploy_verioned Description of problem: Problem when discovering multiple versions of the same Deployment: when multiple versions of the same deployment war is deployed to eap, rhq treats it as the same war -> causing endless loop of changing version of the app Version-Release number of selected component (if applicable): rhq master How reproducible: always Steps to Reproduce: 1. install rhq server, agent and storage 2. install eap 6.0 next to agent 3. deploy helloworld.war app to eap server 4. deploy 2.0 version of helloworld.war to the same eap server 5. deploy 2.1 version of helloworld.war to the same eap server Actual results: sysem discovers 3 versions of the same app, which step on each other causing an endless loop in server.log (version 2.0 is discovered and reporting to rhq server) fragment from server.log -> name=helloworld.war, parent=EAP (0.0.0.0:10190)]] changed its version from [] to [2.0] Expected results: no engless logs only one app is discovered (latest) and reporting to server OR block/warn user not to deploy different versions of the same app next to each other Additional info: screen-shot of server.log attached
master commit dec8bae46446d4cde46fe13ed76585c2cfc164b8 Author: Jay Shaughnessy <jshaughn> Date: Fri Jun 27 16:18:35 2014 -0400 Adding one more thing to this feature, prevent discovery of siblings resolving to the same resource key. In the somewhat unlikely case that two distinct sibling deployments resolve down to the same logical deployment, don't let it get past discovery. For example, if the user has app-1.0.war and app-2.0.war and these are *really* different apps (and they would probably have to be since EAP would stop deployment if they had the same context). In this case both would be seen as app.war, and that is a problem on the RHQ side. In this situation generate an agent log warning that hopefully helps a user resolve the issue. Note that resource upgrade already prevents an upgrade of siblings with the same key, so this is an analogous change.
verified on master (will close as soon as 3.3 ER01 is created)
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
Created attachment 923287 [details] duplicate-deploy
verified in jon 3.3 DR1