TheNewNormal / kube-cluster-osx

Local development multi node Kubernetes Cluster for macOS made very simple
Apache License 2.0
298 stars 26 forks source link

Node1 VM timeout during initial setup #98

Closed cgswong closed 8 years ago

cgswong commented 8 years ago

Getting the below when attempting initial setup:

$ /Applications/Kube-Cluster.app/Contents/Resources/first-init.command; exit;

Setting up Kubernetes Cluster for macOS

Reading ssh key from /Users/cgwong/.ssh/id_rsa.pub

/Users/cgwong/.ssh/id_rsa.pub found, updating configuration files ...

Set CoreOS Release Channel:
 1)  Alpha (may not always function properly)
 2)  Beta
 3)  Stable (recommended)

Select an option: 3

Please type Nodes RAM size in GBs followed by [ENTER]:
[default is 2]:
Changing Nodes RAM to 2GB...

Creating 5GB sparse disk (QCow2) for Master ...
-
Created 5GB Data disk for Master

Please type Nodes Data disk size in GBs followed by [ENTER]:
[default is 15]:

Creating 15GB sparse disk (QCow2) for Node1...
-
Created 15GB Data disk for Node1

Creating 15GB sparse disk (QCow2) for Node2...
-
Created 15GB Data disk for Node2

Starting k8smaster-01 VM ...
> booting k8smaster-01 (1/1)
---> 'k8smaster-01' started successfuly with address 192.168.64.3 and PID 77647
---> 'k8smaster-01' boot logs can be found at '/Users/cgwong/.coreos/running/7E79BC00-7E3C-4B19-9CDF-83F99FD73A23/log'
---> 'k8smaster-01' console can be found at '/Users/cgwong/.coreos/running/7E79BC00-7E3C-4B19-9CDF-83F99FD73A23/tty'

Starting k8snode-01 VM ...
> booting k8snode-01 (1/1)
[ERROR] Unable to grab VM's IP after 30s (!)... Aborted

Node1 VM has not booted, please check '~/kube-cluster/logs/node1_vm_up.log' and report the problem !!!

Press [Enter] key to continue...

Checked the master boot log:

tail -f ~/.coreos/running/7E79BC00-7E3C-4B19-9CDF-83F99FD73A23/log
SSH host key: SHA256:dVhd86dKSBRW/DYPIGwyOZasoQ7BZRt7rrfvKkR+tWc (RSA)
eth0: 192.168.64.3 fe80::dc1d:85ff:fe1f:cf32

k8smaster-01 login: core (automatic login)

CoreOS stable (1068.8.0)
Update Strategy: No Reboots
Failed Units: 1
  coreos-setup-environment.service
core@k8smaster-01 ~ $

Corectl: 0.2.4 Kube-Cluster: 0.4.9

Let me know if you need anything else as the log indicated has the same content as the screen. Any suggestions?

AntonioMeireles commented 8 years ago

@cgswong hi!

thanks for reporting! what's your hw specs and macOS version ?

cgswong commented 8 years ago

@AntonioMeireles macOS: OS X El Capitan, version 10.11.6 (15G31) HW Specs: MacBook Pro Retina (2.3 GHz Corei7; 16GB memory; Intel Iris Pro 1536 MB graphics; 512GB SSD of which 306GB are free)

rimusz commented 8 years ago

@cgswong have you tried to reboot your Mac, could be something messed up with your network e.g. by the VirtualBox

cgswong commented 8 years ago

I rebooted and got the same error. Sometimes my work network affects things so I'll try again when I'm at home later and update again.

cgswong commented 8 years ago

@AntonioMeireles Same error after rebooting and running from home.

AntonioMeireles commented 8 years ago

@cgswong could you please just ping me in kubernet's slack, in order to debug this ?...

cgswong commented 8 years ago

@AntonioMeireles Removed ~/.kube and redid the install from home and it worked (I did use coreos-kubernetes before but I doubt that had any effect). I'm closing the issue since issue is resolved. Thanks for the help.