Actions
Bug #53788
closedradosgw should reopen ops log file on SIGHUP
% Done:
100%
Source:
Backport:
pacific quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
v17.0.0-11011-g7eaed47aa6
Released In:
v18.2.0~2592
Upkeep Timestamp:
2025-07-14T15:48:48+00:00
Description
In order to ensure that ops logs files can be rotated without possible loss of log lines, radosgw should reopen ops logs files when it receives a SIGHUP.
Updated by Casey Bodley about 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 44488
thanks Cory, the PR #44488 merged to master. if this needs backports, can you please add backport tags and set status to Pending Backport? otherwise you can move to Resolved
Updated by Cory Snyder almost 4 years ago
hey Casey, this one slipped through the cracks until I just realized that it had never been backported. It doesn't look like I have the ability to change the 'Status' field?
Updated by Cory Snyder almost 4 years ago
- Backport changed from quincy,pacific to pacific
Updated by Casey Bodley almost 4 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport changed from pacific to pacific quincy
Updated by Upkeep Bot almost 4 years ago
- Copied to Backport #55996: pacific: radosgw should reopen ops log file on SIGHUP added
Updated by Upkeep Bot almost 4 years ago
- Copied to Backport #55997: quincy: radosgw should reopen ops log file on SIGHUP added
Updated by Konstantin Shalygin over 3 years ago
- Tracker changed from Feature to Bug
- Status changed from Pending Backport to Resolved
- % Done changed from 0 to 100
- Regression set to No
- Severity set to 3 - minor
Updated by Upkeep Bot 8 months ago
- Merge Commit set to 7eaed47aa60aea004d16cbba6b57309de6dbc66e
- Fixed In set to v17.0.0-11011-g7eaed47aa6
- Released In set to v18.2.0~2592
- Upkeep Timestamp set to 2025-07-14T15:48:48+00:00
Actions