New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rgw: logfile does not get chowned properly #5233

Merged
1 commit merged into from Sep 2, 2015

Conversation

Projects
None yet
3 participants
@smithfarm
Contributor

smithfarm commented Jul 14, 2015

Unconditionally chown rados log file.
This fixes bnc#905047 (in a somewhat ad-hoc way). Sadly the log
file gets created from several places, so its existence does not
mean init-radosgw had actually run.

Signed-off-by: Thorsten Behrens <tbehrens@suse.com>
(cherry picked from commit 41611ea)

@smithfarm smithfarm self-assigned this Jul 14, 2015

@smithfarm smithfarm added this to the firefly milestone Jul 14, 2015

@smithfarm smithfarm added bug fix core build/ops and removed core labels Jul 14, 2015

ghost pushed a commit that referenced this pull request Sep 2, 2015

Loic Dachary
Merge pull request #5233 from SUSE/wip-12074-firefly
RGW logfile does not get chowned properly

Reviewed-by: Loic Dachary <ldachary@redhat.com>

@ghost ghost merged commit 7f8a397 into ceph:firefly Sep 2, 2015

@smithfarm smithfarm deleted the SUSE:wip-12074-firefly branch Sep 5, 2015

@ghost ghost changed the title from RGW logfile does not get chowned properly to rgw: logfile does not get chowned properly Oct 24, 2015

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment