Status: New
Owner: ----
New issue 1051 by [email protected]: gnt-cluister (and watcher?) return
errors when run on non-masters
https://code.google.com/p/ganeti/issues/detail?id=1051
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
$ /usr/sbin/gnt-cluster --version
gnt-cluster (ganeti v2.12.0) 2.12.0
$ sudo gnt-cluster version
Software version: 2.12.0
Internode protocol: 2120000
Configuration format: 2120000
OS api version: 20
Export interface: 0
VCS version: (ganeti) version v2.12.0
$ hspace --version
hspace (ganeti) version v2.12.0
compiled with ghc 7.6
running on linux x86_64
What distribution are you using?
Debian jessie/testing.
What steps will reproduce the problem?
1. Run gnt-cluster version on a non-master
What is the expected output? What do you see instead?
We should get a message telling us that gnt-cluster should only be run on
the master.
We actually get:
Timeout while talking to the master daemon. Jobs might have been submitted
and will continue to run even if the call timed out. Useful commands in
this situation are "gnt-job list", "gnt-job cancel" and "gnt-job watch".
Error:
Connect timed out
which is unhelpful for the new user, who suspects that something is
misconfigured.
Please provide any additional information below.
This may be effectively the same bug that I reported to Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781084
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
