Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fails to run puppet manifests #3

Open
jwjohns opened this issue Jul 1, 2014 · 3 comments
Open

fails to run puppet manifests #3

jwjohns opened this issue Jul 1, 2014 · 3 comments

Comments

@jwjohns
Copy link

jwjohns commented Jul 1, 2014

I get this everytime no matter what I try:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

puppet apply --modulepath '/tmp/vagrant-puppet-3/modules-0:/etc/puppet/modules' --manifestdir /tmp/vagrant-puppet-3/manifests --detailed-exitcodes /tmp/vagrant-puppet-3/manifests/init.pp

Stdout from the command:

Stderr from the command:

stdin: is not a tty
Could not parse for environment production: Could not match /usr/bin/, at /tmp/vagrant-puppet-3/manifests/init.pp:2 on node

@Silom
Copy link

Silom commented Jul 28, 2014

Same here

@mwillerich
Copy link

I had the same problem; it seems apt-get update isn't guaranteed to run before the packages are installed, causing a fail due to outdated packages. What works for me is to do a vagrant up and then run provisioning again (because apt-get update ran at some point, just not in the right order) with vagrant reload --provision. Ensuring the command is run first should solve the issue.

@mwillerich
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants