You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior:
Self hosted Teleport Clusters configured with CockroachDB storage backend should operate without errors when restarted.
Current behavior:
A customer deployed Teleport across three regions (or Data Centers) using CockroachDB as the storage backend. While restarting the Auth Service in the Secondary or Tertiary region, they encountering the following timeout error when the Auth Service attempted to connect to the CockroachDB backend.
Important to note, this issue does not occur in the Primary region of our Teleport cluster. However, the error eventually resolves after multiple attempts, provided the Auth Service receives a response from CockroachDB within 5 seconds.
Bug details:
Teleport version
Issue observed with v16.4.6
Recreation steps
Error observed simply restarting their Auth servers.
Expected behavior:
Self hosted Teleport Clusters configured with CockroachDB storage backend should operate without errors when restarted.
Current behavior:
A customer deployed Teleport across three regions (or Data Centers) using CockroachDB as the storage backend. While restarting the Auth Service in the Secondary or Tertiary region, they encountering the following timeout error when the Auth Service attempted to connect to the CockroachDB backend.
Important to note, this issue does not occur in the Primary region of our Teleport cluster. However, the error eventually resolves after multiple attempts, provided the Auth Service receives a response from CockroachDB within 5 seconds.
Bug details:
Teleport version
Issue observed with v16.4.6
Recreation steps
Error observed simply restarting their Auth servers.
Auth Server Config
The text was updated successfully, but these errors were encountered: