Bug #46667
mgr/dashboard: Handle buckets without a realm_id
% Done:
0%
Source:
Support
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
The dashboard should not fail hard or handle buckets without a set realm_id.
The API fails with something like this:
RGW REST API failed request with status code 400
(b'{
"Code":"InvalidLocationConstraint",
"Message":"The specified location-constr' b'aint is not valid",
"BucketName":"test",
"RequestId":"tx00000000000000001b64c-' b'005f16b722-137187-my-store",
"HostId":"137187-my-store-my-store"
}')
Related issues
History
#1 Updated by Stephan Müller about 2 years ago
- Description updated (diff)
#2 Updated by Stephan Müller about 2 years ago
- Description updated (diff)
#3 Updated by Sebastian Wagner about 2 years ago
- Related to Bug #44926: dashboard: creating a new bucket causes InvalidLocationConstraint added
#4 Updated by Sebastian Wagner about 2 years ago
duplicates #44926 ?
#5 Updated by Stephan Müller about 2 years ago
- Related to deleted (Bug #44926: dashboard: creating a new bucket causes InvalidLocationConstraint)
#6 Updated by Stephan Müller about 2 years ago
- Duplicates Bug #44926: dashboard: creating a new bucket causes InvalidLocationConstraint added
#7 Updated by Sebastian Wagner about 2 years ago
- Status changed from New to Resolved
#8 Updated by Ernesto Puerta over 1 year ago
- Tracker changed from Fix to Bug
- Project changed from mgr to Dashboard
- Category changed from 143 to Component - RGW
- Regression set to No
- Severity set to 3 - minor