We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
The output from subctl diagnose for a failed connect shows:
subctl diagnose
✗ Checking route agent connections ✗ Connection to cluster "ocp-dr-mz" is not established. Connection details: { "status": "error", "statusMessage": "Failed to successfully ping the remote endpoint IP \"242.1.255.244\"", ... } }
However, there can be many route-agents so it's useful to see which route-agent it's referring to.
I propose:
✓ Retrieving route agents ✓ Checking connections for route agent "worker1" ✗ Checking connections for route agent "worker2" ✗ Connection to cluster "ocp-dr-mz" is not established. Connection details: { "status": "error", "statusMessage": "Failed to successfully ping the remote endpoint IP \"242.1.255.244\"", ... } }
The text was updated successfully, but these errors were encountered:
Identify the RouteAgent instance when logging connections for diagnose
c9bfd87
New output when connections are established: ✓ Retrieving route agent connections ✓ Checking remote connections for route agent "worker1" ✓ Checking remote connections for route agent "worker2" Output when a connection failed: ✓ Retrieving route agent connections ✗ Checking remote connections for route agent "worker1" ✗ IPv4 connection to cluster "west" is not established. Connection details: { "status": "error", "statusMessage": "no initial handshake", ... } Fixes submariner-io#1334 Signed-off-by: Tom Pantelis <[email protected]>
c5ac6f3
tpantelis
Successfully merging a pull request may close this issue.
The output from
subctl diagnose
for a failed connect shows:However, there can be many route-agents so it's useful to see which route-agent it's referring to.
I propose:
The text was updated successfully, but these errors were encountered: