puppet - Vagrant heira_config error on vagrant up -
I am trying to confuse the box with config files created by puphpet - that works fine on my Yosemite 10.10 The MacBook Air has been for a few weeks - but after reloading the configuration to add the second vhost to Apache, I get the following error when I'm going passionately
==> default: Puppet Establishing Needs == & gt; Default: / tmp / vagrant-shell: Line 54: / usr / bin / gem: No such file or directory: == & gt; Default: Finish installing puppet requirements == & gt; Default: Installing paveting 3.4.3 ==> Default: / tmp / vagrant-shell: line 58: / usr / bin / gem: No such file or directory ==> Default: Install Muppet 3.4.3 == & gt; Default: Running Pravator: Puppet ... ==> Default: The puppet is running with the site.pp ... == & gt; Default: stdin: is not a tty ==> Default: Options could not be parsed: Invalid option: - The hiera_config SSH command responded with a non-zero exit status. Vagrantr believes that it means that the command failed. The output should be in the log above for this command. Please read the output to determine what went wrong.
I am using a hashicorp / exact 64
base box, and my puppet provision is:
Provision: Puppet: manifests_path: Puphpet / puppet manifest_file: site.pp module_path: puphpet / puppet / module options: - '--wrobows' -' --HIRA_config /vagrant/puphpet/puppet/hiera.yaml '-' --Parts Future '
Can anyone put a light on why I get this error suddenly? Check your logs with something like
VAGRANT_LOG = info vagrant up
.
In our case, an unsigned rvm
installation (> = 1.26), so we had to download the key in our init script, such as:
< Code> command-curl -sl https://rvm.io/mpapis.asc |
Comments
Post a Comment