lethal drum
When hitting the api/private/cli/cluster/ping-cluster endpoint (and passing the required node name) the cli_output is showing truncated data.
Here is what is returned from the api:
"cli_output": "Host is foo\nGetting addresses from network interface table...\nGetting addresses from sitelist...\nLocal = 169.254.163.55 169.254.158.212\nRemote = 169.254.202.95 169.254.178.116\nCluster Vserver Id = 12233242343\nPing status:\n.... \nBasic connectivity succeeds on 4 path(s)\nBasic connectivity fails on 0 path(s)\n.."
An example of what is returned when running cluster ping-cluster -node <node name> via CLI
Host is foo
Getting addresses from network interface table...
Getting addresses from sitelist...
Local = 169.254.163.55 169.254.158.212
Remote = 169.254.202.95 169.254.178.116
Cluster Vserver Id = 1231251235
Ping status:
....
Basic connectivity succeeds on 4 path(s)
Basic connectivity fails on 0 path(s)
................
Detected 9000 byte MTU on 4 path(s):
Local 169.254.158.212 to Remote 169.254.178.116
Local 169.254.158.212 to Remote 169.254.202.95
Local 169.254.163.55 to Remote 169.254.178.116
Local 169.254.163.55 to Remote 169.254.202.95
Larger than PMTU communication succeeds on 4 path(s)
RPC status:
2 paths up, 0 paths down (tcp check)
2 paths up, 0 paths down (udp check)
We're really hoping to be able to see all of the data including the RPC status.