During provisioning, I get this error:
==> printed.dev: Running provisioner: shell...
printed.dev: Running: /var/folders/d5/7mrv3fms2fgdvz7ghvtqlb600009zc/T/vagrant-shell20160701-921-1ahdiq4.sh
==> printed.dev: Pre-existing private key found at 'puphpet/files/dot/ssh/root_id_rsa'
==> printed.dev: Pre-existing private key found at 'puphpet/files/dot/ssh/id_rsa'
==> printed.dev: Adding generated root key to /root/.ssh/id_rsa
==> printed.dev: Adding generated root key to /root/.ssh/id_rsa.pub
==> printed.dev: Adding generated root key to /root/.ssh/authorized_keys
==> printed.dev: Adding generated key to /home/vagrant/.ssh/id_rsa
==> printed.dev: Adding generated key to /home/vagrant/.ssh/id_rsa.pub
==> printed.dev: Adding generated key to /home/vagrant/.ssh/authorized_keys
==> printed.dev: Running provisioner: shell...
printed.dev: Running: /var/folders/d5/7mrv3fms2fgdvz7ghvtqlb600009zc/T/vagrant-shell20160701-921-18fgvhl.sh
==> printed.dev: Running provisioner: shell...
printed.dev: Running: /var/folders/d5/7mrv3fms2fgdvz7ghvtqlb600009zc/T/vagrant-shell20160701-921-r3yc93.sh
==> printed.dev: ERROR: Error installing activesupport:
==> printed.dev: activesupport requires Ruby version >= 2.2.2.
==> printed.dev: Successfully installed deep_merge-1.0.1
==> printed.dev: Successfully installed vine-0.2
==> printed.dev: 2 gems installed
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.
It's already fixed in latest puphpet
@d-ph does that mean re-creating your zip file from the online GUI again? Or is there another way of updating the scripts?
Ah, I got it, just drag my config.yaml into the online puphpet configurator and it even asks me if I have this error! :)
xD
I should've probably left an information here about how to fix that without recreating the archive, for all these folks coming from google.com:
If you can't be bothered going through puphpet wizard again, then please find this file in your current puphpet directory: install-puppet.sh and change the line as shown is this diff: link. It's still advisable to have the latest puphpet archive, since there are more bug fixes there.
Most helpful comment
xD
I should've probably left an information here about how to fix that without recreating the archive, for all these folks coming from google.com:
If you can't be bothered going through puphpet wizard again, then please find this file in your current puphpet directory:
install-puppet.shand change the line as shown is this diff: link. It's still advisable to have the latest puphpet archive, since there are more bug fixes there.