Skip to content

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

Closed
@tpantelis

Description

@tpantelis

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\"",
  ...
  }
}

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions