Error with trusted cluster prevents accessing

[stevenGravy]

Description

What happened:

Logging into the web shows the following error with no way of navigating into the cluster.

Removing and recreating the trusted clusters appeared to resolve the issue.

tsh access was still available.

What you expected to happen:

If there is an error with a particular cluster the individual cluster would indicate an error and the user can still navigate to clusters that are accessible.

How to reproduce it (as minimally and precisely as possible):

Create a configuration with two teleport clusters with one trusting the other. Stop both. Reset the root cluster /var/lib/teleport so it's CA changes. Restart. Attempt to login with the web.

Environment

• Teleport version (use teleport version): 4.3

• Tsh version (use tsh version): 4.3

• OS (e.g. from /etc/os-release): AWS linux 2

• Where are you running Teleport? (e.g. AWS, GCP, Dedicated Hardware): aws ec2

Browser environment

• Browser Version (for UI-related issues): Chrome 84

[russjones]

@stevenGravy Is this related to OTP?

[russjones]

Best: 1
Realistic: 2