Project

General

Profile

Bug #15607

Ownership of run dir, pid file and asok file not set when deferring permissions drop

Added by Anonymous about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

If a daemon requests to defer permissions drop (as is the case with radosgw), we need to take care of properly chown()'ing the run directory, pid file and admin socket (asok) file.


Related issues

Duplicated by Ceph - Bug #15892: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred Duplicate 05/16/2016
Copied to Ceph - Backport #15608: jewel: Ownership of run dir, pid file and asok file not set when deferring permissions drop Resolved

History

#1 Updated by Anonymous about 4 years ago

  • Status changed from New to Pending Backport
  • Backport set to jewel

#2 Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #15608: jewel: Ownership of run dir, pid file and asok file not set when deferring permissions drop added

#4 Updated by Nathan Cutler about 4 years ago

  • Project changed from devops to Ceph

#5 Updated by Nathan Cutler about 4 years ago

  • Related to Bug #15892: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred added

#6 Updated by Nathan Cutler about 4 years ago

  • Related to deleted (Bug #15892: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred)

#7 Updated by Nathan Cutler about 4 years ago

  • Duplicated by Bug #15892: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred added

#9 Updated by Loic Dachary about 4 years ago

  • Copied to Backport #15608: jewel: Ownership of run dir, pid file and asok file not set when deferring permissions drop added

#10 Updated by Loic Dachary about 4 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF