Description of problem: The jbossews `control deploy` implementation uses a `mv` operation to relocate built artifacts from $OPENSHIFT_REPO_DIR to the live Tomcat deployments directory. During scale up events and scaled builds, only directories relative to $OPENSHIFT_REPO_DIR are synced. Scaled gears thus do not receive the built artifacts. Version-Release number of selected component (if applicable): How reproducible: Perform a build in a scalable jbossews application. Steps to Reproduce: 1. 2. 3. Actual results: Scaled up gears are missing built artifacts in ~/jbossews. Expected results: Scaled up gears should be in sync with the head gear's build output. Additional info:
https://github.com/openshift/origin-server/pull/3045
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/0becce09fd0ab8db5c7e2964c854f916682c32eb Bug 983216: Use rsync for jbossews deployments rather than mv
Checked on devenv_3482 with 3-gear scalable jbossews2.0 app. Placed a pre-built sample.war into the webapps/ and push the change. Found it using rsync instead of mv in the git push log. remote: + rsync -r --delete /var/lib/openshift/966457217098891931942912/app-root/runtime/repo//webapps/ /var/lib/openshift/966457217098891931942912/jbossews//webapps/ Check the web gears, the war exist for all gears. # rhc ssh jbews2s --gear "ls \$OPENSHIFT_JBOSSEWS_DIR/webapps/" === 999629402297430465052672 jbossews-2.0+haproxy-1.4 ROOT.war sample.war === 966457217098891931942912 jbossews-2.0+haproxy-1.4 ROOT.war sample.war === dda1e0c8ea0311e29af122000a8a0ade jbossews-2.0+haproxy-1.4 ROOT.war sample.war
*** Bug 983494 has been marked as a duplicate of this bug. ***