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

SSH Nodes: Download Files Ambiguous Error #22507

Closed
Erick-Reyes opened this issue Mar 1, 2023 · 4 comments · Fixed by #23124
Closed

SSH Nodes: Download Files Ambiguous Error #22507

Erick-Reyes opened this issue Mar 1, 2023 · 4 comments · Fixed by #23124
Assignees
Labels
bug c-nt Internal Customer Reference scp ssh

Comments

@Erick-Reyes
Copy link
Contributor

Expected behavior:
When accessing a specific node in the Teleport UI, which shares a name with other nodes, it should allow you to download a file using the file transfer dialog without any issues.
Screenshot 2023-03-01 at 2 00 37 PM

Current behavior:
When starting a session through the Teleport UI to a specific node, which shares a name with other nodes, it fails to download any file using the file transfer dialog with the following error:
Screenshot 2023-03-01 at 2 00 25 PM

Bug details:

  • Teleport version: 12.0.x (tested on v12.0.1 and v12.0.4)
  • Recreation steps:
  1. Add 2 Ubuntu 20.04 to your Teleport Cluster with the same node name
  2. Attempt to download a file from any of the nodes
  • Debug logs: failed connecting to node ninja-node4. err-node-is-ambiguous
@Erick-Reyes Erick-Reyes added bug ssh c-nt Internal Customer Reference to-be-reviewed This issue needs to be reviewed by Engineering and Product labels Mar 1, 2023
@zmb3 zmb3 added the scp label Mar 1, 2023
@russjones
Copy link
Contributor

@avatus Can you fix this while you are working on moderated sessions downloads? We should connect/download via UUID instead of node name.

cc @zmb3

@avatus
Copy link
Contributor

avatus commented Mar 8, 2023

Sure thing!

@russjones russjones removed the to-be-reviewed This issue needs to be reviewed by Engineering and Product label Mar 8, 2023
@ravicious
Copy link
Member

I've addressed a similar issue in Connect a few weeks ago when I was working on removing the resource cache. We were using the hostname (which we had to get from the resource cache) while the UUID is available from the URIs used by Connect.

@avatus
Copy link
Contributor

avatus commented Mar 15, 2023

@ravicious basically same solution here. We already sent the serverID in the http request itself, so rather than searching for a hostname, I just passed in the serverID and all is well 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug c-nt Internal Customer Reference scp ssh
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants