Bug 1029365

Summary:	Permission problems in /var/lock/condor/loca
Product:	[Fedora] Fedora	Reporter:	Bert DeKnuydt <Bert.Deknuydt>
Component:	condor	Assignee:	matt
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	19	CC:	bbockelm, matt, tomspur, tstclair
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-17 19:12:05 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:

Description Bert DeKnuydt 2013-11-12 09:33:40 UTC

Description of problem:

In HTCondor's Schedlog, one finds errors like:

11/11/13 19:28:04 Initializing a VANILLA shadow for job 10529.3
11/11/13 19:28:04 (10529.3) (23459): directory_util::rec_touch_file: Directory /var/lock/condor/local//16 cannot be created (Permission denied) 

This is due to incorrect permissions in the directory, set by
/etc/tmpfiles.d/condor.conf

Everything works correctly though, as HTCondor switches to using
a lock directory in /tmp/condorLocks

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

condor-8.1.1-0.3.fc19.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Install condor
2. Run a local or sched universe job, or a DAGman
3. Check in /var/log/condor/ShadowLog

Actual results:

See above.

Expected results:

Put the locks in the normal place, and don't complain.

Additional info:

Fix is to modify the last line of /etc/tmpfiles.d/condor.conf 
as shipped in the rpm:

---
d /var/lock/condor/local 0775 condor condor -
---

to

---
d /var/lock/condor/local 1777 condor condor -
---

This is because the these locks are written by the daemon condor_shadow,
which runs not as user 'condor' but as the user who submitted the job.

Comment 1 Fedora End Of Life 2015-01-09 20:33:54 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-02-17 19:12:05 UTC

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.