search

solo-io / gloo

The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy
https://docs.solo.io/
Apache License 2.0
4.09k stars 441 forks source link

Malformed glooctl command produces strange errors #8496

Open jameshbarton opened 1 year ago

jameshbarton commented 1 year ago

Gloo Edge Version

1.14.x (latest stable)

Kubernetes Version

None

Describe the bug

A Gloo Edge enterprise customer reports strange errors. They tried to run the command glooctl get proxy url which is actually the wrong command to get the gateway proxy url (the correct command is glooctl proxy url). But instead of giving them a useful error message, instead they got the feedback below — which left them confused until they realized the mistake.

% glooctl get proxy url
Error: timed out trying to connect to localhost during port-forward, errors: 117 errors occurred:
    * rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:36575: connect: connection refused"
    * rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:36575: connect: connection refused"
    * rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:36575: connect: connection refused"
    * rpc error: code = Unknown desc = gloo-system.url does not exist
    * rpc error: code = Unknown desc = gloo-system.url does not exist
    * rpc error: code = Unknown desc = gloo-system.url does not exist
    * rpc error: code = Unknown desc = gloo-system.url does not exist
    * rpc error: code = Unknown desc = gloo-system.url does not exist
    * rpc error: code = Unknown desc = gloo-system.url does not exist
... repeated many more times ...

Steps to reproduce the bug

  1. Run glooctl get proxy url against a Gloo Edge 1.14 installation.

Expected Behavior

A clean, malformed command error should be reported by the glooctl CLI.

Additional Context

Internal reference: https://solo-io.slack.com/archives/C03146E7TEZ/p1689943890673179

github-actions[bot] commented 4 months ago

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.