Adding one more point to it. There was a problem in one of the 'system' commands in Dockerfile causing connection timeouts.
"The problem is that each of the system statements in the Vagrantfile is executed in a separate subshell. This means that the environment variables are not being exported between calls, hence kubectl does not know the $KUBERNETES_MASTER address." This has been fixed in upstream repo with [1]. [1] https://github.com/pires/kubernetes-vagrant-coreos-cluster/pull/122/files On Fri, Jul 10, 2015 at 6:06 PM, Imesh Gunaratne <im...@apache.org> wrote: > Thanks Akila! I have now merged it. > > For others information, the problem was that when the internet connection > is slow, the Kubernetes installation process get restarted after reaching > the timeout. Now Akila has increased it to 400 seconds. > > On Fri, Jul 10, 2015 at 10:32 AM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi Kishanthan, >> >> Actually your master node has not been configured properly. See the logs >> at >> >> *==> master: Waiting for Kubernetes master to become ready...* >> >> The connection to the server localhost:8080 was refused - did you specify >> the right host or port? >> >> >> Also please check whether you are running on latest Vagrant version. >> >> @Imesh: this is a known issue and has been fixed in upstream repo. I've >> sent you a PR with the fix at [1]. >> >> [1] https://github.com/imesh/kubernetes-vagrant-setup/pull/1 >> >> Thanks. >> >> >> On Fri, Jul 10, 2015 at 9:29 AM, Imesh Gunaratne <im...@apache.org> >> wrote: >> >>> Hi Kishanthan, >>> >>> You could try to ssh into master and node-01 and execute journalctl -f >>> to view the log. Kubernetes installation may have failed in one of the >>> hosts. >>> >>> On Fri, Jul 10, 2015 at 9:07 AM, Kishanthan Thangarajah < >>> kshanth2...@gmail.com> wrote: >>> >>>> Hi Devs, >>>> >>>> I was trying out the steps provided in : >>>> https://gist.github.com/imesh/b8f81fac8de39183a504 >>>> >>>> I couldn't get the vagrant up and running with minions which fails with >>>> the error at the bottom. >>>> >>>> I assume node-01 here is one of the minion. From the logs, I think the >>>> master node is correctly configured, even with the version constraint. But >>>> the node-01 had failed on the version constraint while adding the core-os. >>>> Is this a known issue? Do I have to change/remove the version constraint in >>>> some config file? >>>> >>>> kubernetes-vagrant-setup kishanthan$ vagrant up >>>> >>>> Bringing machine 'master' up with 'virtualbox' provider... >>>> >>>> Bringing machine 'node-01' up with 'virtualbox' provider... >>>> >>>> Bringing machine 'node-02' up with 'virtualbox' provider... >>>> >>>> *==> master: Running triggers before up...* >>>> >>>> *==> master: Setting Kubernetes version 0.18.0* >>>> >>>> *==> master: Configuring Kubernetes cluster DNS...* >>>> >>>> *==> master: Box 'coreos-alpha' could not be found. Attempting to find >>>> and install...* >>>> >>>> master: Box Provider: virtualbox >>>> >>>> master: Box Version: >= 738.1.0 >>>> >>>> *==> master: Loading metadata for box >>>> 'http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vagrant.json >>>> <http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vagrant.json>'* >>>> >>>> master: URL: >>>> http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vagrant.json >>>> >>>> *==> master: Adding box 'coreos-alpha' (v738.1.0) for provider: >>>> virtualbox* >>>> >>>> master: Downloading: >>>> http://alpha.release.core-os.net/amd64-usr/738.1.0/coreos_production_vagrant.box >>>> >>>> master: Calculating and comparing box checksum... >>>> >>>> *==> master: Successfully added box 'coreos-alpha' (v738.1.0) for >>>> 'virtualbox'!* >>>> >>>> >>>> *-----------------------------------------------------------------------------------------------------------------------* >>>> >>>> *==> master: Waiting for Kubernetes master to become ready...* >>>> >>>> The connection to the server localhost:8080 was refused - did you >>>> specify the right host or port? >>>> >>>> The connection to the server localhost:8080 was refused - did you >>>> specify the right host or port? >>>> >>>> *==> node-01: Box 'coreos-alpha' could not be found. Attempting to find >>>> and install...* >>>> >>>> node-01: Box Provider: virtualbox >>>> >>>> node-01: Box Version: >= 738.1.0 >>>> >>>> You specified a box version constraint with a direct box file >>>> >>>> path. Box version constraints only work with boxes from Vagrant >>>> >>>> Cloud or a custom box host. Please remove the version constraint >>>> >>>> and try again. >>>> >>> >>> >>> >>> -- >>> Imesh Gunaratne >>> >>> Senior Technical Lead, WSO2 >>> Committer & PMC Member, Apache Stratos >>> >> >> >> >> -- >> Akila Ravihansa Perera >> Software Engineer, WSO2 >> >> Blog: http://ravihansa3000.blogspot.com >> > > > > -- > Imesh Gunaratne > > Senior Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- Akila Ravihansa Perera Software Engineer, WSO2 Blog: http://ravihansa3000.blogspot.com
