Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

cli failed to connect

See original GitHub issue

I was trying the getting start guide. I can see the pod using kubectl.

But

katib-cli -s gke-test-katib-default-pool-b88188d2-jnvp:30678 Getstudies
2018/05/09 11:38:13 connecting gke-test-katib-default-pool-b88188d2-jnvp:30678
2018/05/09 11:38:14 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp: lookup gke-test-katib-default-pool-b88188d2-jnvp on 127.0.0.1:53: no such host"; Reconnecting to {gke-test-katib-default-pool-b88188d2-jnvp:30678 <nil>}
2018/05/09 11:38:14 GetStudy failed: rpc error: code = 14 desc = grpc: the connection is unavailable

11:38:14lunkai@None:katib$ katib-cli
2018/05/09 11:38:34 connecting 127.0.0.1:6789
2018/05/09 11:38:34 Method not found:

Do we need to configure cli somehow?

Issue Analytics

State:
Created 5 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

lluunncommented, May 24, 2018

Working now, thank you! I will sent out a PR to fix getting-started.md

0reactions

YujiOshimacommented, May 24, 2018

You failed to resolve the name gke-test-katib-default-pool-b88188d2-jnvp. Try to use the IP address of the node. And in GKE, you should add a firewall rule to accessing to port 30678. e.g. gcloud compute firewall-rules create katibservice --allow tcp:30678