Actions
Bug #10698
closedrgw: not failing POST requests if keystone not configured
Status:
Resolved
Priority:
Urgent
Assignee:
-
Target version:
-
% Done:
0%
Source:
Community (user)
Tags:
Backport:
giant, firefly
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
It will most likely fail later on due to access permissions on the bucket, unless bucket has a public write permission set (in which case it will behave similar to the anonymous user). This is a recent regression, introduced at commit:8b3dfc9472022ea45ad24e02e0aa21dfdad798f8.
Updated by Yehuda Sadeh about 9 years ago
- Source changed from other to Community (user)
Updated by Yehuda Sadeh about 9 years ago
- Status changed from 12 to Fix Under Review
Updated by Yehuda Sadeh about 9 years ago
- Status changed from Fix Under Review to Resolved
Updated by Yehuda Sadeh about 9 years ago
- Status changed from Resolved to Pending Backport
- Backport set to giant, firefly
Updated by Loïc Dachary about 9 years ago
The code in firefly looks quite different and rgw: fail s3 POST auth if keystone not configured may not be necessary. If this is confirmed firefly can be removed from the Backport field.
Updated by Valery Tschopp about 9 years ago
Not from what I've experienced, and the patch is required for firefly too.
Here at SWITCH, we apply the patch directly in debian firefly trusty source package, rebuilt it and install it. We have to do this because our customers need the S3 browser POST functionality.
Updated by Sage Weil about 9 years ago
- Status changed from Pending Backport to Resolved
Actions