Skip to content

server: the "gossip" status API endpoint should work with secondary tenants with sufficient capability #110022

@knz

Description

@knz

Found while investigating #110001.

Describe the problem

When TestStatusGossipJson in server/storage_api is modified to point to a secondary tenant (e.g. via #110008), the test starts failing when accessing the /_status/gossip endpoint:

    gossip_test.go:36: status: 501 Not Implemented, content-type: application/json, body: {
          "error": "method Gossip not implemented",
          "code": 12,
          "message": "method Gossip not implemented",
          "details": [
          ]

How to reproduce

from #110008 reset DefaultTestTenant in TestStatusGossipJson, 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. It should retrieve the gossip info over the KV tenant connector over the network.

Epic CRDB-38968

Jira issue: CRDB-31227

Metadata

Metadata

Labels

A-cluster-observabilityRelated to cluster observabilityA-multitenancyRelated to multi-tenancyC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-db-serverv25.2.0-prerelease

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions