Bug 788452

Summary: Java issue on updated packages from condor-7.6.3-0.3 to condor-7.6.5-0.11
Product: Red Hat Enterprise MRG Reporter: Petra Svobodová <psvobodo>
Component: condorAssignee: Timothy St. Clair <tstclair>
Status: CLOSED ERRATA QA Contact: Petra Svobodová <psvobodo>
Severity: low Docs Contact:
Priority: low    
Version: DevelopmentCC: esammons, matt, mkudlej, tstclair
Target Milestone: 2.3   
Target Release: ---   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: condor-7.8.2-0.3 Doc Type: Bug Fix
Doc Text:
C: Upgrading a windows condor install from 7.6.3-0.3 to 7.6.5-0.11. C: Condors Java detection is broken from the previous install. F: On upgrade the installer will correct the previous versions config file. R: Condors Java detection should work as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-06 18:41:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 773597, 825819    
Bug Blocks:    

Description Petra Svobodová 2012-02-08 08:54:33 UTC
Description of problem:
On updated packages from last release version using installation wizard (without previous uninstallation) there is an error report in the Starter log: 

"JavaDetect: failure status 1 when executing C:\PROGRA~2\Java\jre6\bin\java.exe -classpath C:\condor/bin:C:\condor/bin/scimark2lib.jar:. CondorJavaInfo old 2"

Java should be detected after update as well as after new installation.

Version-Release number of selected component (if applicable):
condor-7.6.5-0.11.msi

How reproducible:
100%

Steps to Reproduce:
1. Install condor-7.6.3-0.3.msi and restart your computer
2. Update condor by condor 7.6.5-0.11.msi using installation wizard and restart the computer again
3. See the StarterLog
  
Actual results:
The StarterLog contains an error message.

Expected results:
The StarterLog should contain no error message.


Additional info:
This may be associated with https://bugzilla.redhat.com/show_bug.cgi?id=748339

Comment 1 Timothy St. Clair 2012-02-14 19:44:13 UTC
The configs are preserved and not overwritten.  The old config had an issue and was subsequently fixed.  I'm uncertain whether we should create a software mod for this or update a FAQ.  b/c the updated installer will drop a correct config if one is not presently there.  

I think parsing the existing config to try to correct is the wrong choice, because it is actually broken from the original installation.  

thoughts?

Comment 2 Martin Kudlej 2012-02-15 14:14:47 UTC
I think this should be fixed somehow. I see two options:
1) you will introduce way how to update/rewrite old configuration values in default configuration files. This is not problem because I expect that users use remote configuration for configuration nodes.
2) write it into documentation that old configuration in default configuration files are not changed by update

Comment 3 Timothy St. Clair 2012-02-15 17:41:25 UTC
The installer will now read the existing config and *only* update the original config if 

JAVA_CLASSPATH_SEPARATOR = :

Comment 6 Timothy St. Clair 2012-03-19 18:31:50 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
C: Upgrading a windows condor install from 7.6.3-0.3 to 7.6.5-0.11.
C: Condors Java detection is broken from the previous install.
F: On upgrade the installer will correct the previous versions config file.
R: Condors Java detection should work as expected.

Comment 8 Petra Svobodová 2012-05-28 15:01:30 UTC
Upgrading condor-7.6.3-0.3 to 7.6.8-0.3 was successful on all supported platforms and no java failures were detected in log files.

But upgrading condor-7.6.5-11 to 7.6.8-0.3 failed; see https://bugzilla.redhat.com/show_bug.cgi?id=825819 (added to dependencies), so this bug cannot be verified at this time.

Comment 9 Petra Svobodová 2012-06-04 08:20:05 UTC
Upgrades condor-7.6.3-0.3 to condor-7.6.8-0.4 and condor-7.6.5-0.11 to 7.6.8-0.4 were successful on all supported Windows platforms:
- Windows XP-x86
- Windows 7-x86 and x64
- Windows Server2003-x86 and x64
- Windows Server2008-x86 and x64
- Windows Server2008R2

Verified on packages condor-7.6.8-0.4.msi.

--> VERIFIED

Comment 12 Petra Svobodová 2013-01-31 12:49:01 UTC
Retested on update condor-7.6.5-0.21 to condor-win-7.8.8-0.4. The issue did not appear yet.

--> VERIFIED

Comment 14 errata-xmlrpc 2013-03-06 18:41:42 UTC
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.

http://rhn.redhat.com/errata/RHSA-2013-0564.html