rsync with default chmod to 644
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-swift |
Fix Released
|
High
|
Emilien Macchi | ||
Icehouse |
Fix Released
|
High
|
David Moreau Simard | ||
Juno |
Fix Released
|
High
|
David Moreau Simard | ||
Kilo |
Fix Released
|
High
|
David Moreau Simard | ||
Mitaka |
Fix Released
|
High
|
Emilien Macchi |
Bug Description
This seems like a nasty bug, I'm surprised no one's bumped into it yet - I might just be crazy though, in which case, do let me know :)
Here's a snippet off of the rsyncd.conf file on a storage server:
====
# This file is being maintained by Puppet.
# DO NOT EDIT
[ object ]
path = /data/swift
read only = false
write only = no
list = yes
uid = swift
gid = swift
incoming chmod = 0644
outgoing chmod = 0644
max connections = 200
lock file = /var/lock/
====
I'd like to bring to your attention the default chmod values in there, brought about by these:
- https:/
- https:/
When I added some new devices today, I started seeing an anormal rise in the amount of permission denied errors for newly replicated partitions in the Swift logs (haven't quite noticed this before).
It turns out the files were in 644 (which is fine) but the folders were in 644 too, meaning the Swift user could not access them.
What we want for permissions is 755 for the folders and 644 for the files.
After doing some testing, what we want is the following incoming and outgoing chmod:
- incoming chmod = Du=rwx,
- outgoing chmod = Du=rwx,
Changed in puppet-swift: | |
assignee: | nobody → David Moreau Simard (dmsimard) |
status: | New → In Progress |
Changed in puppet-swift: | |
milestone: | none → 6.0.0 |
Changed in puppet-swift: | |
importance: | Undecided → High |
Changed in puppet-swift: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/165272
Review: https:/