Skip to content

multitenant: Tenants started with startTenant that fail during startup are not cleaned up immediately #98868

Closed
#100436
Closed
multitenant: Tenants started with startTenant that fail during startup are not cleaned up immediately#98868
#100436
Assignees
knz
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-multitenantIssues owned by the multi-tenant virtual teambranch-masterFailures and bugs on the master branch.branch-release-23.1Used to mark GA and release blockers, technical advisories, and bugs for 23.1
@ajstorm

Description

@ajstorm
ajstorm
opened on Mar 17, 2023

Describe the problem

It was notice in the course of multi-tenant upgrade testing that tenants which fail during startup don't return a stopper. At the same time, they don't immediately stop. The workaround for this is to supply a custom stopper, as is done in TestServerStartupGuardrails. We should investigate why this is occurring, and fix it.

To Reproduce

Remove the custom stopper added in #94998 and rerun the test.

Jira issue: CRDB-25558
Epic: CRDB-23559

Metadata

Metadata

Assignees

Labels

C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-multitenantIssues owned by the multi-tenant virtual teambranch-masterFailures and bugs on the master branch.branch-release-23.1Used to mark GA and release blockers, technical advisories, and bugs for 23.1

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions