issues running locally on Mac OSX
Closed this issue · 3 comments
First off, thanks so much for the blog posts and this project.
I just ran across your blog post and tried to set this up following your instructions. I;m running Mac OS X Yosemite and I downloaded Vagrant 1.7.2.
bundle install, ./bootstrap all seems to work fine however, when I try a vagrant up
I get an error
Bringing machine 'zookeeper1' up with 'virtualbox' provider...
Bringing machine 'nimbus1' up with 'virtualbox' provider...
Bringing machine 'supervisor1' up with 'virtualbox' provider...
Bringing machine 'supervisor2' up with 'virtualbox' provider...
==> zookeeper1: VirtualBox VM is already running.
==> nimbus1: Importing base box 'centos6-compatible'...
==> nimbus1: Matching MAC address for NAT networking...
==> nimbus1: Setting the name of the VM: wirbelsturm_nimbus1_1420863657770_80832
==> nimbus1: Fixed port collision for 22 => 2222. Now on port 2200.
==> nimbus1: Clearing any previously set network interfaces...
==> nimbus1: Preparing network interfaces based on configuration...
nimbus1: Adapter 1: nat
nimbus1: Adapter 2: hostonly
==> nimbus1: Forwarding ports...
nimbus1: 8080 => 28080 (adapter 1)
nimbus1: 22 => 2200 (adapter 1)
==> nimbus1: Running 'pre-boot' VM customizations...
==> nimbus1: Booting VM...
==> nimbus1: Waiting for machine to boot. This may take a few minutes...
nimbus1: SSH address: 127.0.0.1:2200
nimbus1: SSH username: vagrant
nimbus1: SSH auth method: private key
nimbus1: Warning: Connection timeout. Retrying...
nimbus1: Warning: Remote connection disconnect. Retrying...
nimbus1:
nimbus1: Vagrant insecure key detected. Vagrant will automatically replace
nimbus1: this with a newly generated keypair for better security.
nimbus1:
nimbus1: Inserting generated public key within guest...
nimbus1: Removing insecure key from the guest if its present...
nimbus1: Key inserted! Disconnecting and reconnecting using new SSH key...
==> nimbus1: Machine booted and ready!
==> nimbus1: Checking for guest additions in VM...
==> nimbus1: Setting hostname...
==> nimbus1: Configuring and enabling network interfaces...
==> nimbus1: Mounting shared folders...
nimbus1: /shared => /Users/spark/workspace/wirbelsturm/shared
nimbus1: /tmp/vagrant-puppet/modules-c119df1cc11c132dd5d64967542c94ee => /Users/spark/workspace/wirbelsturm/puppet/modules
nimbus1: /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3 => /Users/spark/workspace/wirbelsturm/puppet/manifests
==> nimbus1: Running provisioner: puppet...
==> nimbus1: Running Puppet with site.pp...
==> nimbus1: Notice: Scope(Class[main]): Deployment environment: 'default-environment'
==> nimbus1: Notice: Scope(Class[main]): I am running within a Vagrant-controlled environment
==> nimbus1: Notice: Scope(Class[main]): Disabling firewall...
==> nimbus1: Notice: Scope(Class[main]): I have been assigned the role 'storm_master'
==> nimbus1: Error: Could not find data item classes in any Hiera data file and no default supplied at /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3/site.pp:30 on node nimbus1.cable.rcn.com
==> nimbus1: Error: Could not find data item classes in any Hiera data file and no default supplied at /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3/site.pp:30 on node nimbus1.cable.rcn.com
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
At this point, the vagrant up command stops but the zookeeper service is up and running.
I'm very new to Vagrant and Puppet but have some experience with Ruby, Bundler, Gems but I"m a little stuck as to what the exact problem is.
Any thoughts on what I can try or look at to try and diagnose the problem?
Can you try to start from scratch? That is, re-clone Wirbelsturm to a new directory, run bootstrap, etc. Also, you may want to try with Vagrant 1.6.x -- Vagrant 1.7 was not tested yet.
==> nimbus1: Error: Could not find data item classes in any Hiera data file and no default supplied at /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3/site.pp:30 on node nimbus1.cable.rcn.com
==> nimbus1: Error: Could not find data item classes in any Hiera data file and no default supplied at /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3/site.pp:30 on node nimbus1.cable.rcn.com
I have not seen this error before (in this context), though it looks as if Puppet cannot find Hiera related data in the Puppet files that Vagrant has scp'd from your local host to the nimbus1 VM. So maybe these Puppet files (under /tmp/vagrant-puppet/* on the VM, see above) were not copied, or not all of them were copied, or they were missing on your local host in the first place (hence they could not get copied to the VM either).
Furthermore I notice this error/warning in the logs that I also haven't seen before:
nimbus1: Vagrant insecure key detected. Vagrant will automatically replace
nimbus1: this with a newly generated keypair for better security.
nimbus1:
nimbus1: Inserting generated public key within guest...
nimbus1: Removing insecure key from the guest if its present...
nimbus1: Key inserted! Disconnecting and reconnecting using new SSH key...
I just tried downgrading my vagrant from 1.7.2 to 1.6.5 and cleared my ~/.vagrant.d/ directory and it appears to be working. Thanks for the help.