Skip to content

spanconfig: automatically drop clearly invalid PTS records instead of failing #156380

New issue
New issue
Open
Bug
Open
spanconfig: automatically drop clearly invalid PTS records instead of failing#156380
Bug
Assignees
kev-cao
Labels
A-disaster-recoveryC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.P-2Issues/test failures with a fix SLA of 3 monthsT-disaster-recoverybranch-masterFailures and bugs on the master branch.branch-release-24.3Used to mark GA and release blockers, technical advisories, and bugs for 24.3branch-release-25.2branch-release-25.3Used to mark GA and release blockers and technical advisories for 25.3branch-release-25.4Used to mark GA and release blockers and technical advisories for 25.4
@kev-cao

Description

@kev-cao
kev-cao
opened on Oct 28, 2025

As an additional follow-up item for #155444, we should update the AUTO SPAN CONFIG RECONCILIATION job to automatically drop clearly invalid configurations (e.g a secondary tenant intending to apply a PTS on another tenant) instead of failing.

Jira issue: CRDB-55976

Metadata

Metadata

Assignees

Labels

A-disaster-recoveryC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.P-2Issues/test failures with a fix SLA of 3 monthsT-disaster-recoverybranch-masterFailures and bugs on the master branch.branch-release-24.3Used to mark GA and release blockers, technical advisories, and bugs for 24.3branch-release-25.2branch-release-25.3Used to mark GA and release blockers and technical advisories for 25.3branch-release-25.4Used to mark GA and release blockers and technical advisories for 25.4

Type

Bug

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions