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:
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.
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:
Bug details:
Teleport version: 12.0.x (tested on v12.0.1 and v12.0.4)
Recreation steps:
Add 2 Ubuntu 20.04 to your Teleport Cluster with the same node name
Attempt to download a file from any of the nodes
Debug logs: failed connecting to node ninja-node4. err-node-is-ambiguous
The text was updated successfully, but these errors were encountered:
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.
@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 👍
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.
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:
Bug details:
failed connecting to node ninja-node4. err-node-is-ambiguous
The text was updated successfully, but these errors were encountered: