Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 876573

Summary: Condor packages are able to be installed, but the condor service could not run
Product: Red Hat Enterprise MRG Reporter: Petra Svobodová <psvobodo>
Component: condorAssignee: Timothy St. Clair <tstclair>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Kudlej <mkudlej>
Severity: high Docs Contact:
Priority: high    
Version: DevelopmentCC: crolke, iboverma, ltoscano, matt, mkudlej, pbelanyi, tstclair
Target Milestone: 2.3   
Target Release: ---   
Hardware: All   
OS: Windows   
Whiteboard:
Fixed In Version: condor-7.8.7-0.6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-19 16:38:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 752732    

Description Petra Svobodová 2012-11-14 13:55:48 UTC
Description of problem:

The condor packages could be installed via wizard and also via command line, but the condor service is not started and cannot be started manually after restart the computer. Starting fails with error message: 

"Windows could not start the condor service on Local Computer.
Error 1067: The process terminated unexpectedly."


Version-Release number of selected component (if applicable):

condor-win-7.8.7-0.4


How reproducible:
100%


Steps to Reproduce:
1. Install the condor packages via installation wizard.
2. Restart the computer.
3. Try to run the condor service from the Services Management Console.

  
Actual results:
The condor is not started automatically and its manual starting fails.

Expected results:
The condor should start automatically and should be able to be started manually.

Comment 1 Timothy St. Clair 2012-11-14 14:41:40 UTC
Please attach the logs.

Comment 6 Timothy St. Clair 2012-11-28 18:06:57 UTC
This particular issue was due to upstream changing service names(condor->HTCondor) and it caused breakage in several places.  

Fix was to retain condor service name, but keep all the branding changes.

Comment 7 Martin Kudlej 2012-12-10 08:53:43 UTC
Tested on all supported Windows versions with condor-7.8.7-0.6.msi and it works. --> VERIFIED