Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tsh ssh with load all CAs does not work #31339

Open
atburke opened this issue Sep 1, 2023 · 2 comments
Open

tsh ssh with load all CAs does not work #31339

atburke opened this issue Sep 1, 2023 · 2 comments
Labels
bug test-plan-problem Issues which have been surfaced by running the manual release test plan

Comments

@atburke
Copy link
Contributor

atburke commented Sep 1, 2023

Expected behavior:
When logged in to the root cluster of a trusted cluster pair where auth_service.load_all_cas is true, tsh ssh <leaf-node-addr> should work.

Current behavior:
tsh ssh <leaf-node-addr> fails with error direct dialing to nodes not found in inventory is not supported.

Bug details:

  • Teleport version: v14.0.0-alpha.2
  • Recreation steps: Follow tsh CA loading section of testplan

#30323 removed support for direct dialing of nodes, which was the only case where load_all_cas applied. It may make sense to also deprecate loading all CAs for tsh ssh.

Edit: Works correctly when TELEPORT_UNSTABLE_UNLISTED_AGENT_DIALING=yes in the proxy's environment.

@atburke atburke added bug test-plan-problem Issues which have been surfaced by running the manual release test plan labels Sep 1, 2023
@zmb3
Copy link
Collaborator

zmb3 commented Sep 1, 2023

See also #31162

@galbeniluz
Copy link

Hi, we've recently upgraded our cluster to v14.0.3 and we are experiencing the same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug test-plan-problem Issues which have been surfaced by running the manual release test plan
Projects
None yet
Development

No branches or pull requests

3 participants