Error during vagrant up
cccabot opened this issue · 9 comments
It looks like something from ansible:
==> default: Configuring cache buckets...
==> default: Running provisioner: ansible...
PYTHONUNBUFFERED=1 ANSIBLE_FORCE_COLOR=true ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o ControlMaster=auto -o ControlPersist=60s' ansible-playbook --private-key=/home/ccabot/stucco/dev-setup/.vagrant/machines/default/virtualbox/private_key --user=vagrant --connection=ssh --limit='default' --inventory-file=/home/ccabot/stucco/dev-setup/.vagrant/provisioners/ansible/inventory --extra-vars={"ansible_ssh_user":"vagrant","rexster_host":"10.10.10.100"} provisioning/site.yml
PLAY [all] ********************************************************************
GATHERING FACTS ***************************************************************
failed: [default] => {"cmd": "/usr/bin/facter --puppet --json", "failed": true, "rc": 2}
msg: [Errno 2] No such file or directory
TASK: [jgoodall.common | install common packages (build-essential, git, mercurial, supervisor, unzip, rsync, curl, wget)] ***
FATAL: no hosts matched or all hosts have already failed -- aborting
PLAY RECAP ********************************************************************
to retry, use: --limit @/home/ccabot/site.retry
default : ok=0 changed=0 unreachable=0 failed=1
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
The issue was a name mismatch between /usr/bin/ruby (attempted) and /usr/bin/ruby1.9.1 (present on vm). I manually added a symbolic link between the two and that worked around it.
I havent seen this error before. In the vagrant instance, or on the host OS?
In the vagrant instance.
/usr/bin/ruby should point to /usr/local/rvm/rubies/ruby-1.9.3-p547/bin/ruby. Do you not have an rvm ruby in /usr/local?
Ok - I pointed it there instead. I do have an rvm there. The issue was that /usr/bin/ruby for some reason didn't originally exist.
I cannot reproduce. Can you start with a fresh instance? We made some changes to the processing code in the past day, and updated master of this repo.
With the new code I ran into this error:
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'puphpet/ubuntu1404-x64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: 1.2
==> default: Loading metadata for box 'puphpet/ubuntu1404-x64'
default: URL: https://atlas.hashicorp.com/puphpet/ubuntu1404-x64
The box you're attempting to add has no available version that
matches the constraints you requested. Please double-check your
settings. Also verify that if you specified version constraints,
that the provider you wish to use is available for these constriants.
Box: puphpet/ubuntu1404-x64
Address: https://atlas.hashicorp.com/puphpet/ubuntu1404-x64
Constraints: 1.2
Available versions: 2.0
I did a bit of digging and it appears that version 1.2 has been revoked from the puphpet website.
Thank you, I will look for a different base box and update here.
Ok, now using hashicorp/precise64 base box. Please let us know if there are any more issues.