Red Hat Bugzilla – Bug 1256329
JON upgrade from 3.3.2 to JON 3.3.3 does not remove files introduced with JON 3.3.0 upgrade 02
Last modified: 2015-10-28 10:37:25 EDT
Description of problem:
are introduced with JON 3.3.0 update 02 but are not needed in JON 3.3.0 update 03. However, above files are not removed when update is done via JON 3.3.2 (JON 3.3.0 -> JON 3.3.2 -> JON 3.3.3) and because of that, after JON Storage node is restarted, JON Server does not change it's status from MAINTENANCE to NORMAL. Also, because of this JON Agent does not reconnect to the JON Server.
Version-Release number of selected component (if applicable):
JON 3.3.2 -> JON 3.3.3
Steps to Reproduce:
1. Install JON 3.3.0;
2. Upgrade JON 3.3.0 to JON 3.3.2;
3. Upgrade JON 3.3.2 to JON 3.3.3;
4. Stop JON Storage Node (./rhqctl stop --storage);
5. Confirm that JON Server is in `MAINTENANCE` mode;
6. Wait until JON Agent is backfilled and then start JON Storage node;
JON Server is still in `MAINTENANCE` mode and JON Agent cannot register with the JON Server.
Restart of the JON Storage Node changes status of the JON Server to `NORMAL` and JON Agent is able to register with the JON Server.
When direct upgrade is done (from JON 3.3.0 to JON 3.3.3), this issue does not exist.
To fix this, change the upgrade script (JON 3.3.0 upgrade 03) to remove above files if they exist.
This if fixed with commit: 03525f95970 to jon.git.
Moving to MODIFIED for inclusion with next brew build.
Moving to ON_QA as available to test with new build:
*Note: jon-server-patch-3.3.0.GA.zip maps to DR01 build of jon-server-3.3.0.GA-update-04.zip.
3.3.0.GA Update 04
Build Number :
However there are other files which are not removed - captured here bz1263742
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.