Duplicate output when connecting to an ssh instance that is offline

[rosstimothy]

Expected behavior:

Current behavior:

tsh ssh root@facf33a6-2879-4505-a633-154b25e44ed7
ERROR: failed connecting to host facf33a6-2879-4505-a633-154b25e44ed7:0: failed to dial target host
	Teleport proxy failed to connect to "node" agent "@local-node" over reverse tunnel:

  no tunnel connection found: no node reverse tunnel for facf33a6-2879-4505-a633-154b25e44ed7.benchmark.cloud.gravitational.io found, error dialing peer proxies [a27fb30e-2895-40df-ba04-3e1addba72ea 5a93d274-7396-480b-9684-df30623c6e85]: error receiving dial response: Teleport proxy failed to connect to "node" agent "@local-node" over reverse tunnel:

  no tunnel connection found: no node reverse tunnel for facf33a6-2879-4505-a633-154b25e44ed7.benchmark.cloud.gravitational.io found

This usually means that the agent is offline or has disconnected. Check the
agent logs and, if the issue persists, try restarting it or re-registering it
with the cluster., error receiving dial response: Teleport proxy failed to connect to "node" agent "@local-node" over reverse tunnel:

  no tunnel connection found: no node reverse tunnel for facf33a6-2879-4505-a633-154b25e44ed7.benchmark.cloud.gravitational.io found

This usually means that the agent is offline or has disconnected. Check the
agent logs and, if the issue persists, try restarting it or re-registering it
with the cluster.

This usually means that the agent is offline or has disconnected. Check the
agent logs and, if the issue persists, try restarting it or re-registering it
with the cluster.

Bug details:

• Teleport version: v14.0.0-alpha.2
• Recreation steps:

1. Add a tunnel node
2. Stop the node
3. Try to connect to the node
4. Observe the duplicate message

[zmb3]

Should we close this one @rosstimothy? We've never reproduced it or seen any other reports.