Description of problem: rhq-server-env.sh.default should be backup of rhq-server-env.sh in new JON version. It works fine when first attempt to upgrade JON is successful. When there is some problem and upgrade process is rolled back, second try overwrites rhq-server-env.sh.default with rhq-server-env.sh from previous JON version. Version-Release number of selected component (if applicable): Version : 3.3.0.DR01 Build Number : 6468454:dda0a47 How reproducible: Always Steps to Reproduce: 1. install jon3.2.0 and add rhq-server-env.sh to JON_SERVER_HOME/bin 2. edit rhq-server-env.sh 3. start upgrade process to version 3.3.DR01 but cancel it (ctrl+c) during agent upgrade -> upgrade process should be rolled back 4. start the upgrade process again Actual results: rhq-server-env.sh.default is identical with rhq-server-env.sh from jon3.2.0 Expected results: rhq-server-env.sh.default should be identical with rhq-server-env.sh from newly unzipped jon3.3.DR01
Master commit 457b04a0083522ce5afebf037aa6af018573b582 Author: Jay Shaughnessy <jshaughn> Date: Wed Aug 20 17:47:30 2014 -0400 Add FileReverters for the -env files. So, on cancel the unmodified version of the file should be restored. Release/jon3.3.x commit 168d146857cd59cf7e2863df2348eb1521795fe3 Author: Jay Shaughnessy <jshaughn> Date: Wed Aug 20 17:49:22 2014 -0400 Cherry-pick master 457b04a0083522ce5afebf037aa6af018573b582
Moving to ON_QA as available for test with the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=381194
Verified on Version : 3.3.0.ER02 Build Number : 4fbb183:7da54e2