Bug 852321

Summary:	Missing SPOOL settings in HAScheduler feature
Product:	Red Hat Enterprise MRG	Reporter:	Lubos Trilety <ltrilety>
Component:	condor-wallaby-base-db	Assignee:	Robert Rati <rrati>
Status:	CLOSED ERRATA	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.2	CC:	iboverma, jneedle, matt, mkudlej, rrati
Target Milestone:	2.2	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	condor-wallaby-base-db-1.23-1	Doc Type:	Bug Fix
Doc Text:	C: Using Remote Configuration to configure a High Availablity Scheduler with the HAScheduler feature C: The shadow could fail to start with the error: ERROR "According to /var/lib/condor/spool/spool_version, the SPOOL directory is written in spool version 0, but I only support versions back to 1 F: Added parameters to point the shadow at the same spool location used by the HAScheduler feature R: The shadow will run jobs as usual using the spool pointed to by the node with the HAScheduler feature installed	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-19 17:45:33 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:	828434

Description Lubos Trilety 2012-08-28 07:58:54 UTC

Description of problem:
Feature HAScheduler contains SCHEDD.SPOOL but that's not enough, the condor needs to set SPOOL for all daemons or at least for Shadow. This setting leads to error on Shadow daemon.
ERROR "According to /var/lib/condor/spool/spool_version, the SPOOL directory is written in spool version 0, but I only support versions back to 1.
" at line 67 in file /builddir/build/BUILD/condor-7.6.4/src/condor_utils/spool_version.cpp

Probably there should be set parameter SPOOL not SCHED.SPOOL in HAScheduler feature, like it was in previous version.

Version-Release number of selected component (if applicable):
condor-wallaby-base-db-1.22-5

How reproducible:
100%

Steps to Reproduce:
1. Set HAScheduler on some machines
2. Submit some jobs, see shadow log

  
Actual results:
error about spool version

Expected results:
no error, condor work correctly

Additional info:

Comment 2 Jeff Needle 2012-08-29 11:47:46 UTC


*** This bug has been marked as a duplicate of bug 852537 ***

Comment 3 Jeff Needle 2012-08-29 11:53:51 UTC

Incorrectly marked as a dup.  Reopening.

Comment 4 Robert Rati 2012-08-30 17:11:09 UTC

Added GRIDMANAGER.SPOOL and SHADOW.SPOOL to the SharedJobQueueLocation feature.  This resolves this issue for the shadow and gridmanager.

Fixed on upstream on:
master

Comment 5 Robert Rati 2012-08-30 17:17:09 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: Using Remote Configuration to configure a High Availablity Scheduler with the HAScheduler feature
C: The shadow could fail to start with the error:
ERROR "According to /var/lib/condor/spool/spool_version, the SPOOL directory is written in spool version 0, but I only support versions back to 1
F: Added parameters to point the shadow at the same spool location used by the HAScheduler feature
R: The shadow will run jobs as usual using the spool pointed to by the node with the HAScheduler feature installed

Comment 7 Lubos Trilety 2012-08-31 14:32:50 UTC

Tested with:
condor-wallaby-base-db-1.23-1

Tested on:
RHEL5 x86_64,i386
RHEL6 x86_64,i386

# wallaby show-feature SharedJobQueueLocation
Console Connection Established...
SharedJobQueueLocation
  name:  "SharedJobQueueLocation"
  params:  {"SHADOW.SPOOL"=>"$(SCHEDD.SPOOL)", "GRIDMANAGER.SPOOL"=>"$(SCHEDD.SPOOL)", "SCHEDD.HISTORY"=>"$(SCHEDD.SPOOL)/history", "SCHEDD.SPOOL"=>""}
  depends:  []
  conflicts:  []
  included_features:  []


All jobs run correctly, no error in logs.

>>> VERIFIED

Comment 9 errata-xmlrpc 2012-09-19 17:45:33 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-2012-1278.html