Bug 751013

Summary: Job receive twice signal SIGCONT after condor_continue command.
Product: Red Hat Enterprise MRG Reporter: Daniel Horák <dahorak>
Component: condorAssignee: Timothy St. Clair <tstclair>
Status: CLOSED ERRATA QA Contact: Daniel Horák <dahorak>
Severity: low Docs Contact:
Priority: low    
Version: 2.1CC: esammons, iboverma, ltoscano, matt, mkudlej, tstclair
Target Milestone: 2.3Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: condor-7.8.2-0.1 Doc Type: Bug Fix
Doc Text:
C: Continuing a job after it had been suspended. C: The job would receive SIGCONT twice. F: Update logic to ensure that SIGCONT can only be sent once. R: A job which is continued after it has been suspended will only receive SIGCONT once.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-06 18:39:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Daniel Horák 2011-11-03 08:49:39 UTC 
Description of problem:
If job is continued via command condor_continue, they receive twice signal SIGCONT.
When is it (suspended and) continued because of expression (SUSPEND) CONTINUE, they receive SIGCONT only once.


Version-Release number of selected component (if applicable):
condor-classads-7.6.5-0.5
condor-7.6.5-0.5


How reproducible:
100%


Steps to Reproduce:
1. Default configuration of condor (expression SUSPEND and CONTINUE set to FALSE).
2. Submit job (execution script is from bug 635012, comment 18):
  # cat /tmp/test.job 
    universe = vanilla
    cmd = /tmp/bz635012.py
    output = /tmp/job_$(cluster).$(process).output
    error = /tmp/job_$(cluster).$(process).error
    Log = /tmp/job_$(cluster).$(process).log
    queue 1

  # runuser -s /bin/bash -l condor -c "condor_submit /tmp/test.job"

3. When job is running, suspend and continue him via condor_suspend and condor_continue command.

4. Look to output file:
  # cat /tmp/job_1.0.output
    [11:05:26]+0.8911 - Run '/tmp/bz635012.py' with pid: 5778
    [11:05:26]+0.8911 - 0
    [11:05:27]+0.9203 - 1
    . . .
    [11:05:40]+0.9533 - 14
    [11:05:41]+0.9533 - 15
    [11:06:02]+0.4006 - caught signal - sig_num: 18 ('SIGCONT')
    [11:06:02]+0.4008 - 16
    [11:06:02]+0.4738 - caught signal - sig_num: 18 ('SIGCONT')
    [11:06:02]+0.4740 - 17
    [11:06:03]+0.4788 - 18
    . . .

  
Additional info:
Found on verification of bug 635012.
Comment 2 Timothy St. Clair 2012-03-19 17:58:49 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: Continuing a job after it had been suspended.
C: The job would receive SIGCONT twice.
F: Update logic to ensure that SIGCONT can only be sent once.
R: A job which is continued after it has been suspended will only receive SIGCONT once.
Comment 10 Daniel Horák 2013-01-22 15:30:39 UTC 
Tested and verified via automatic test on RHEL 5.9,6.4 - i386,x86_64 with condor-7.8.8-0.3.

>>> VERIFIED
Comment 13 errata-xmlrpc 2013-03-06 18:39:35 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