Ticket #2569: Submit event not written for spooled jobs when running as root

When a job is submitted with a user log and spooled input files to a schedd running as root, the schedd fails to write the submit event to the user log (in the spool directory). The schedd writes to the user log as the job owner. When it writes the submit event, the spool directory (if there is one) is owned by condor, so the write fails.

We can either chown the spool directory just before writing the submit event (at transaction commit time), or write the submit event as condor if the user log is in the spool directory.

This wasn't detected in previous changes in how the submit event is logged because testing was done with personal Condors (i.e. non-root).

[Append remarks]

Remarks:

2011-Oct-21 14:44:07 by jfrey:
I've attached a patch for this bug. If the schedd fails to open the user log as the user and the log is in the job's spool directory, the schedd will then try to open the log as user condor.


2011-Oct-21 16:17:22 by zmiller:
PATCH REVIEWED, LOOKS GOOD
[Append remarks]

Properties:

Type: defect           Last Change: 2011-Oct-24 13:06
Status: resolved          Created: 2011-Oct-21 13:51
Fixed Version: v070605           Broken Version: v070600 
Priority:          Subsystem: Daemons 
Assigned To: jfrey           Derived From: #1985
Creator: jfrey  Rust:  
Customer Group: other  Visibility: public 
Notify:   Due Date:  

Related Check-ins:

2011-Oct-21 16:10   Check-in [27942]: Fix typo in previous commit for submit event logging bugfix. #2569 (By Jaime Frey )
2011-Oct-21 16:00   Check-in [27941]: Submit event not written for spooled jobs when running as root #2569 When a job's files are first spooled to the schedd, they are owned by the condor user. Since the user log is usually written to as the user, logging of the submit event fails when files are spooled. [...] (By Jaime Frey )

Attachments: