Actions
Bug #11159
closedinit-radosgw.sysv (installed as init.d/ceph-radosgw) won't start instances with no socket path
Status:
Resolved
Priority:
Urgent
Assignee:
-
Target version:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
1 - critical
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
init-radosgw.sysv ignores instances of radosgw with a zero-length socket path, but that's exactly how you need to configure it to use TCP sockets.
The stanza starting at line 62 that checks rgw socket path for -z should be removed.
(Tamil encountered the problem, I diagnosed it)
Updated by Sage Weil about 9 years ago
- Status changed from New to Pending Backport
Updated by Sage Weil about 9 years ago
- Status changed from Pending Backport to Resolved
Updated by Ken Dreyer about 9 years ago
For clarificaton:
The fix for this was cherry-picked to the firefly branch as commit https://github.com/ceph/ceph/commit/3160e8d6918a04d1fec9fdccbc30bf007c7940c6 , which went in after 0.80.9 was tagged.
In other words, this landed after v0.80.9, and the earliest tagged version it will be in is (a yet-to-be-released) v0.80.10.
Updated by John Spray over 6 years ago
- Project changed from Ceph to rgw
- Category deleted (
22)
Bulk reassign of radosgw category to RGW project.
Actions