tree 7c8bccafbf5ce9cd46b89e370de82c1601b77156
parent 00bf4549a2b189a19b45db894f875714ee49f1f1
author Roger Luethi <roger@opennetworking.org> 1695208229 +0200
committer Roger Luethi <roger@opennetworking.org> 1695791370 +0200

Abort if voltctl cannot find etcd

The voltctl commands we used to set log levels return only a rather
unhelpful error message ("context deadline exceeded") if voltctl
is unable to connect to etcd. The exit status in that case is 0,
wrongly indicating success.

This happens quite easily if kubectl was configured to forward etcd to
a port other than the one expected by voltctl.

Using "voltctl log level list" as we do with this change has two effects
if voltctl cannot find etcd. First, it exits with status 1 which should
abort the pipeline, alerting the user to a configuration problem. Second,
it prints a more helpful error message:

  Is ETCD available at localhost:2379?

Signed-off-by: Roger Luethi <roger.luethi@bisdn.de>
Change-Id: I7c2b0fdd8a2028c4b85b1a9b81c35dd194de99ca