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

Bug 528067

Summary: Expected job lease duration != measured
Product: Red Hat Enterprise MRG Reporter: Timothy St. Clair <tstclair>
Component: condorAssignee: Timothy St. Clair <tstclair>
Status: CLOSED ERRATA QA Contact: Jiri Kolar <jkolar>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.1CC: freznice, jkolar, lbrindle, matt
Target Milestone: 1.2   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Grid bug fix C: The job_lease_duration period should be twenty minutes C: The actual job_lease_duration period is thirty minutes F: The startd & starters now respect the job lease duration if they were in the process of vacating. R: The job_lease_duration period can be effectively configured. The job_lease_duration period was not being adhered to. The startd and starters now respect the job lease duration if they were in the process of vacating.
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-03 09:19:21 UTC Type: ---
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: 527551    
Attachments:
Description Flags
Master Log from run w segfault
none
StartLog of run none

Description Timothy St. Clair 2009-10-08 19:54:55 UTC
The expected job_lease_duration from reading the manual was 20 minutes yet measured = 30 minutes.

To repro:

1.) Start up a couple of sleep jobs
2.) condor_off -master
3.) wait 30 minutes
4.) scan the master, and starter logs timestamps

= exactly 30 minutes.

nothing is special about condor_config or submission

2nd Verifications:
1.) Start up a couple of sleep jobs (set job_lease_duration = something small like 2 minutes = 120)
2.) condor_off -master
3.) wait 30 minutes
4.) scan the master, and starter logs timestamps

still takes 30 minutes

Sometimes the startd does not cleanly exit and segfaults too.  

http://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=826

Comment 1 Timothy St. Clair 2009-10-08 19:55:59 UTC
Created attachment 364174 [details]
Master Log from run w segfault

Comment 2 Timothy St. Clair 2009-10-08 19:56:28 UTC
Created attachment 364175 [details]
StartLog of run

Comment 3 Timothy St. Clair 2009-10-13 15:25:46 UTC
Update has been made upstream 
fix will be in 7.4.0-0.7

Comment 5 Irina Boverman 2009-10-29 14:30:06 UTC
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
please see bug summary.

Comment 6 Jiri Kolar 2009-11-04 14:28:19 UTC
Tested:
on condor 7.2.2-0.9.el5 bug aapears 
on  condor-7.4.1-0.2.el5 has been fixed

validated on RHEL5-Server-U4 for archs i386/x86_64 
packages:

# rpm -qa | grep -E '(qpid|openais|rhm|condor)' | sort -u

condor-7.4.1-0.2.el5
condor-qmf-plugins-7.4.1-0.2.el5
openais-0.80.6-8.el5_4.1
openais-debuginfo-0.80.6-8.el5_4.1
python-qpid-0.5.752581-4.el5
qpidc-0.5.752581-31.el5
qpidc-debuginfo-0.5.752581-30.el5
qpidc-devel-0.5.752581-31.el5
qpidc-perftest-0.5.752581-31.el5
qpidc-rdma-0.5.752581-31.el5
qpidc-ssl-0.5.752581-31.el5
qpidd-0.5.752581-31.el5
qpidd-acl-0.5.752581-31.el5
qpidd-cluster-0.5.752581-31.el5
qpidd-devel-0.5.752581-31.el5
qpid-dotnet-0.4.738274-2.el5
qpidd-rdma-0.5.752581-31.el5
qpidd-ssl-0.5.752581-31.el5
qpidd-xml-0.5.752581-31.el5
qpid-java-client-0.5.751061-9.el5
qpid-java-common-0.5.751061-9.el5
rhm-0.5.3206-21.el5
rhm-docs-0.5.756148-1.el5
rh-tests-distribution-MRG-Messaging-qpid_common-1.5-15


# rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u



->VERIFIED

Comment 7 Timothy St. Clair 2009-11-09 21:00:32 UTC
Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1 +1 @@
-please see bug summary.+The startd & starters now respect the job lease duration if they were in the process of vacating.

Comment 8 Lana Brindley 2009-11-11 21:16:11 UTC
Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1 +1,8 @@
-The startd & starters now respect the job lease duration if they were in the process of vacating.+Grid bug fix
+
+C: The job_lease_duration period should be twenty minutes
+C: The actual job_lease_duration period is thirty minutes
+F: The startd & starters now respect the job lease duration if they were in the process of vacating.
+R: The job_lease_duration period can be effectively configured.
+
+The job_lease_duration period was not being adhered to. The startd & starters now respect the job lease duration if they were in the process of vacating.

Comment 9 Lana Brindley 2009-11-11 21:16:50 UTC
Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -5,4 +5,4 @@
 F: The startd & starters now respect the job lease duration if they were in the process of vacating.
 R: The job_lease_duration period can be effectively configured.
 
-The job_lease_duration period was not being adhered to. The startd & starters now respect the job lease duration if they were in the process of vacating.+The job_lease_duration period was not being adhered to. The startd and starters now respect the job lease duration if they were in the process of vacating.

Comment 11 errata-xmlrpc 2009-12-03 09:19:21 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1633.html