Cluster wont start
scotty-c opened this issue · 7 comments
I am having issues with the cluster starting with the following error
etcd cluster:
Error: cannot sync with the cluster using endpoints http://172.17.15.101:2379
fleetctl list-machines:
MACHINE IP METADATA
dce67a8c... 172.17.15.101 role=control
Installing fleet units from '~/coreos-k8s-cluster/fleet' folder:
Triggered global unit kube-kubelet.service start
Triggered global unit kube-proxy.service start
Unit kube-controller-manager.service launched
Unit kube-scheduler.service launched
Unit fleet-ui.service launched
Unit kube-apiserver.service launched on dce67a8c.../172.17.15.101
Finished installing fleet units
UNIT MACHINE ACTIVE SUB
fleet-ui.service dce67a8c.../172.17.15.101 activating start-pre
kube-apiserver.service dce67a8c.../172.17.15.101 active running
kube-controller-manager.service dce67a8c.../172.17.15.101 active running
kube-scheduler.service dce67a8c.../172.17.15.101 activating start-pre
~/coreos-k8s-cluster/bin/gen_kubeconfig: line 6: kubectl: command not found
~/coreos-k8s-cluster/bin/gen_kubeconfig: line 7: kubectl: command not found
~/coreos-k8s-cluster/bin/gen_kubeconfig: line 8: kubectl: command not found
Waiting for Kubernetes cluster to be ready. This can take a few minutes...
Any help would be greatly appriciated
I need more details from your Mac setup, can you post output of your env?
Good morning,
upgrade to 6.0 fixed the issue.
Hi,
I have the same issue with v0.6.1
- OSX 10.11.2
- Vagrant 1.8.1
Env
PATH=/Users/XXXXXXX/.rvm/gems/ruby-2.2.4/bin:/Users/XXXXXXX/.rvm/gems/ruby-2.2.4@global/bin:/Users/XXXXXXX/.rvm/rubies/ruby-2.2.4/bin:/Users/XXXXXXX/.rvm/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
TMPDIR=/var/folders/dy/bc4g214n7zj4ylmtcgzhzpvr0000gn/T/
LOGNAME=XXXXXXX
XPC_FLAGS=0x0
HOME=/Users/XXXXXXX
Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.Ij9V3h1whJ/Render
LANG=fr_FR.UTF-8
TERM=xterm-256color
USER=XXXXXXX
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.pxbrzoDMos/Listeners
ITERM_PROFILE=Default
TERM_PROGRAM=iTerm.app
XPC_SERVICE_NAME=0
SHELL=/bin/zsh
ITERM_SESSION_ID=w1t0p0
PWD=/Users/XXXXXXX
__CF_USER_TEXT_ENCODING=0x1F5:0x0:0x1
SHLVL=1
OLDPWD=/Users/XXXXXXX
ZSH=/Users/XXXXXXX/.oh-my-zsh
PAGER=less
LESS=-R
LSCOLORS=Gxfxcxdxbxegedabagacad
LC_CTYPE=fr_FR.UTF-8
DOCKER_TLS_VERIFY=1
DOCKER_HOST=tcp://192.168.99.100:2376
export=
DOCKER_CERT_PATH=/Users/XXXXXXX/.docker/machine/machines/default
DOCKER_MACHINE_NAME=default
rvm_prefix=/Users/davidterranova
rvm_path=/Users/XXXXXXX/.rvm
rvm_bin_path=/Users/XXXXXXX/.rvm/bin
_system_type=Darwin
_system_name=OSX
_system_version=10.11
_system_arch=x86_64
rvm_version=1.26.11 (master)
GEM_HOME=/Users/XXXXXXX/.rvm/gems/ruby-2.2.4
GEM_PATH=/Users/XXXXXXX/.rvm/gems/ruby-2.2.4:/Users/XXXXXXX/.rvm/gems/ruby-2.2.4@global
MY_RUBY_HOME=/Users/XXXXXXX/.rvm/rubies/ruby-2.2.4
IRBRC=/Users/XXXXXXX/.rvm/rubies/ruby-2.2.4/.irbrc
RUBY_VERSION=ruby-2.2.4
_=/usr/bin/env
Regards
it will not work as your env does not have App's preset environment to master VM's fleet and k8s.
I see you are using zsh, the App uses bash
Yes, a simple PATH update in my .zshrc fixed the problem, just wanted to report the problem in case you want to fix it.
@davidterranova can you provide the fix you did, please? so I can include it to the readme
First option is to update the PATH and will allow you to access all the tools located in this directory
# ~/.zshrc
PATH=$PATH:~/coreos-k8s-cluster/binThe second option is to create a symlink for each tools you want
ln -s ~/coreos-k8s-cluster/bin/kubectl /usr/local/bin/kubectlRegards