Some Kraken issues with vagrant when run on a local machine instead of in AWS

trying-to-ssh-in.log

yazz@kraken:~/kraken/terraform/local$ vagrant global-status
id       name            provider   state    directory
---------------------------------------------------------------------------------
a86df0f  etcd            virtualbox running  /opt/kraken/terraform/local
52be29e  master          virtualbox running  /opt/kraken/terraform/local
900bed6  apiserver-001   virtualbox running  /opt/kraken/terraform/local
a4d7427  node-001        virtualbox running  /opt/kraken/terraform/local
ed142a4  node-002        virtualbox running  /opt/kraken/terraform/local
9b514ab  node-003        virtualbox running  /opt/kraken/terraform/local

The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date. To interact with any of the machines, you can go to
that directory and run Vagrant, or you can use the ID directly
with Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"
yazz@kraken:~/kraken/terraform/local$ vagrant ssh a86df0f
/home/yazz/kraken/terraform/local/kraken_helpers.rb:10: warning: already initialized constant VAGRANTFILE_API_VERSION
/opt/kraken/terraform/local/kraken_helpers.rb:10: warning: previous definition of VAGRANTFILE_API_VERSION was here
/opt/vagrant/embedded/lib/ruby/2.2.0/ipaddr.rb:559:in `in6_addr': invalid address (IPAddr::InvalidAddressError)
	from /opt/vagrant/embedded/lib/ruby/2.2.0/ipaddr.rb:496:in `initialize'
	from /opt/kraken/terraform/local/kraken_helpers.rb:62:in `new'
	from /opt/kraken/terraform/local/kraken_helpers.rb:62:in `base_ip_address'
	from /opt/kraken/terraform/local/Vagrantfile:75:in `block (3 levels) in <top (required)>'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/v2/loader.rb:37:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/v2/loader.rb:37:in `load'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/loader.rb:113:in `block (2 levels) in load'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/loader.rb:107:in `each'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/loader.rb:107:in `block in load'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/loader.rb:104:in `each'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/loader.rb:104:in `load'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/vagrantfile.rb:153:in `machine_config'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/vagrantfile.rb:45:in `machine'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:663:in `machine'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/plugin/v2/command.rb:147:in `block in with_target_vms'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/plugin/v2/command.rb:201:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/plugin/v2/command.rb:201:in `block in with_target_vms'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/plugin/v2/command.rb:183:in `each'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/plugin/v2/command.rb:183:in `with_target_vms'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/commands/ssh/command.rb:41:in `execute'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/cli.rb:42:in `execute'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:302:in `cli'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/bin/vagrant:174:in `<main>'