Actions
Bug #19025
closedRGW health check errors out incorrectly
% Done:
0%
Source:
Tags:
Backport:
kraken,jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Looks like the config 'rgw_healthcheck_disabling_path' is checking for the presence of a path and if the path is accessible, the feature is supposed to return 503. Since access() returns zero upon success for the presence of a path with F_OK flag, the existing check returns 200 for such case.
Updated by Pavan Rallabhandi about 7 years ago
- Status changed from In Progress to Fix Under Review
Updated by Radoslaw Zarzynski about 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #19157: kraken: RGW health check errors out incorrectly added
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #19158: jewel: RGW health check errors out incorrectly added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions