Skip to content

Identify the RouteAgent instance when logging failed connections for diagnose #1334

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

Closed
tpantelis opened this issue Mar 7, 2025 · 0 comments · Fixed by #1390
Closed

Identify the RouteAgent instance when logging failed connections for diagnose #1334

tpantelis opened this issue Mar 7, 2025 · 0 comments · Fixed by #1390
Assignees
Labels
enhancement New feature or request

Comments

@tpantelis
Copy link
Contributor

The output from subctl diagnose for a failed connect shows:

✗ 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\"",
  ...
  }
}
@tpantelis tpantelis added the bug Something isn't working label Mar 7, 2025
@tpantelis tpantelis self-assigned this Mar 7, 2025
@tpantelis tpantelis added this to Backlog Mar 7, 2025
@github-project-automation github-project-automation bot moved this to Backlog in Backlog Mar 7, 2025
@tpantelis tpantelis moved this from Backlog to Next Version Candidate in Backlog Mar 7, 2025
@tpantelis tpantelis added enhancement New feature or request and removed bug Something isn't working labels Mar 8, 2025
@maayanf24 maayanf24 removed this from Backlog Mar 11, 2025
@maayanf24 maayanf24 moved this to Todo in Submariner 0.21 Mar 11, 2025
tpantelis added a commit to tpantelis/subctl that referenced this issue May 6, 2025
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]>
@tpantelis tpantelis moved this from Todo to In Review in Submariner 0.21 May 6, 2025
@github-project-automation github-project-automation bot moved this from In Review to Done in Submariner 0.21 May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant