Fix credential refresh race during worker activation#567
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Context
In the 24-client same-org burst QA, several clients failed with:
same-tenant takeover requires newer owner epoch 1 (current N)During burst activation, worker rows become org-bound before the first ActivateTenant RPC completes and before s3_credentials_expires_at is stamped. The refresh scheduler treated those NULL-expiry reserved/activating rows as immediately due, bumped owner_epoch, and could race the original activation.
Tests
go test ./tests/configstore -run 'TestListWorkersDueForCredentialRefresh|TestMarkCredentialsRefreshed'go test -tags kubernetes ./controlplane -run 'TestCredentialRefreshScheduler|TestK8sPoolActivateReservedWorker|TestSharedWorkerActivator'