Skip to content

Fix ClusterApiToken not persisted on secondary after initJoin#1851

Open
comerford wants to merge 1 commit intoTechnitiumSoftware:masterfrom
comerford:fix/cluster-api-token-not-synced
Open

Fix ClusterApiToken not persisted on secondary after initJoin#1851
comerford wants to merge 1 commit intoTechnitiumSoftware:masterfrom
comerford:fix/cluster-api-token-not-synced

Conversation

@comerford
Copy link
Copy Markdown

See: #1848

  • initJoin calls SyncConfigFromAsync → RestoreConfigAsync(isConfigTransfer: true)
  • The isConfigTransfer branch filters sessions to only ApiToken, dropping ClusterApiToken
  • Token lives in memory after join but is never written to auth.config on the secondary
  • On service restart, ClusterManager can't find the token so you get "No API token was found for the Cluster domain"

This is a simple fix to add the ClusterAPI token so it won't get filtered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant