Provisioning hangs on "Running puppet with site.pp"

[aphofstede]

I'm experimenting with vagrant-managed-servers for an older PuPHPet-based project and I can't seem to get past the puppet provisioning stage.
vagrant destroy demo -f && vagrant up demo --provider=managed && vagrant provision --debug
and then
ps axuww fills up with loads of these process pairs:

root     130956  0.0  0.0   9552  1152 ?        S    13:00   0:00 /bin/bash /usr/bin/puppet apply --verbose --hiera_config /vagrant/puphpet/puppet/hiera.yaml --parser future --modulepath /tmp/vagrant-puppet/modules-ca1d2e31b8e8c6e53179ceedf9c5cac0:/etc/puppet/modules --detailed-exitcodes --manifestdir /tmp/vagrant-puppet/manifests-893fcda21077f5a583c2dbbba8515c0a /tmp/vagrant-puppet/manifests-893fcda21077f5a583c2dbbba8515c0a/site.pp
root     131060  0.2  0.2  13680  5616 ?        S    13:00   0:00 bash /usr/local/rvm/bin/rvm ruby-2.1.10 do puppet apply --verbose --hiera_config /vagrant/puphpet/puppet/hiera.yaml --parser future --modulepath /tmp/vagrant-puppet/modules-ca1d2e31b8e8c6e53179ceedf9c5cac0:/etc/puppet/modules --detailed-exitcodes --manifestdir /tmp/vagrant-puppet/manifests-893fcda21077f5a583c2dbbba8515c0a /tmp/vagrant-puppet/manifests-893fcda21077f5a583c2dbbba8515c0a/site.pp

and then the provisioning fails with DEBUG ssh: stderr: /usr/local/rvm/scripts/set: fork: Cannot allocate memory

I tried increasing swap, but it just takes longer and runs out of memory anyway.

Please advise, why would it come in an endless loop?

Thanks,
Alex

[aphofstede]

@tknerr Any ideas on this one?

[tknerr]

Hi @aphofstede,

sorry for the late reply.

Hmmm... I have no idea to be honest :-/

I never used the vagrant puppet provisioner so far. Does that happen with a local box (e.g. when using VirtualBox provisioner) as well, or only when using vagrant-managed-servers?

Which vagrant version did you use? does updating to the latest version help?

Cheers,
Torben

[aphofstede]

Hi Torben, @tknerr,

Thanks for having a look. It's an existing Vagrant set-up I created a while ago using PuPHPeT. It runs fine on a local VM, though I did have to modify it to run with vagrant-manager-servers (mostly on content though, like the SSH port, some paths, etc.)

I'm using Vagrant 1.9.2, I could try 1.9.8 but I got a bit wary of upgrades ever since some breakage in the 1.8.x era.. Does it work with 2.0?

Cheers,
Alex

[tknerr]

Can you share with me a Vagrantfile / minimal repro case of your local setup?

If you have a local setup with the puppet provisioner that works, then you can add a second "managed_server" VM to the Vagrantfile that points to the local VM. Pretty much like in the example here:
https://github.com/tknerr/vagrant-managed-servers/blob/master/Vagrantfile

If that works as expected, then the odd behaviour seems to be triggered by the remote server you are actually provisioning. If you can reproduce the odd behaviour here, it's a bug in the vagrant-managed-servers plugin.

HTH, Torben

[tknerr]

P.S.: understand your reluctance to upgrade Vagrant, and haven't tested the plugin with 2.0 yet... so better stay with 1.9.x for for now... ;)