kubernetes/cluster/vagrant
Filipe Brandenburger 86c1ddc121 Fix which salt-master warning in Vagrant startup
The `which` command in Fedora 20 (differently from the one in Debian)
prints to stderr when the binary is not found. Redirect both stdout and
stderr to /dev/null to prevent messages from being printed by `which`.

Check whether the binary exists or not by the exit status of `which`
(non-zero means the binary does not exist) instead of checking for empty
output.

Tested:
- Started a Vagrant cluster with `vagrant up` and confirmed these
  messages were gone. Checked master and minions for Kubernetes
  components using the systemd status commands.
- Confirmed that the same error message for salt-minion is also
  suppressed from the output with this patch.

Fixes: Issue #1079

Signed-off-by: Filipe Brandenburger <filbranden@google.com>
2014-08-27 23:15:08 -07:00
..
config-default.sh Fix logic errors in validate cluster and make it work for vagrant again 2014-08-21 10:58:09 -04:00
config-test.sh Initial vagrant setup and e2e testing support 2014-07-24 16:32:36 -04:00
pod-ip-test.sh add test to check minion to master reachability; logfiling and some cosmetification. 2014-08-26 12:52:02 -07:00
provision-config.sh apiserver listen on 0.0.0.0 in vagrant 2014-08-14 10:02:04 -04:00
provision-master.sh Fix which salt-master warning in Vagrant startup 2014-08-27 23:15:08 -07:00
provision-minion.sh Fix which salt-master warning in Vagrant startup 2014-08-27 23:15:08 -07:00
provision-network.sh add ip per pod across vagrant minions 2014-08-26 11:29:35 -07:00
util.sh Fix logic errors in validate cluster and make it work for vagrant again 2014-08-21 10:58:09 -04:00