-
Notifications
You must be signed in to change notification settings - Fork 4.1k
server: the "ranges" status API endpoint should work with secondary tenants with sufficient capability #110019
Copy link
Copy link
Closed
Labels
A-multitenancyRelated to multi-tenancyRelated to multi-tenancyC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-db-server
Description
Found while investigating #110001.
This is a variant of #110018.
Describe the problem
When TestRangesResponse in server/storage_api is modified to point to a secondary tenant (e.g. via #110008), the test starts failing when accessing the /_status/ranges (NB: not range) endpoint:
=== RUN TestRangesResponse/test_ranges_response
ranges_test.go:47: status: 501 Not Implemented, content-type: application/json, body: {
"error": "method Ranges not implemented",
"code": 12,
"message": "method Ranges not implemented",
"details": [
]
}, error: <nil>
How to reproduce
from #110008 reset DefaultTestTenant in TestRangesResponse, run the test with a test tenant and observe the failure.
Expected behavior
Once the tenant is granted a suitable capability, the endpoint should work properly.
Epic CRDB-38968
Jira issue: CRDB-31225
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-multitenancyRelated to multi-tenancyRelated to multi-tenancyC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-db-server