search

eirc / puppet-account

Helpers for managing users and groups with puppet.
0 stars 1 forks source link

Invalid resource type account::group #3

Closed tlatsas closed 1 year ago

tlatsas commented 10 years ago

Hello, puppet fails to provision an Arch Linux machine through vagrant with the following error:

Invalid resource type account::group at /tmp/vagrant-puppet-2/modules-0/nefos/manifests/users.pp:4

I use puppet v5.3.1 with ruby 2.1.1 on the VM. Facter is on version 2.0.1 . For what is worth on my host machine I run ruby 2.1.2 and Vagrant 1.6.2

More detailed debug output:

Debug: importing '/tmp/vagrant-puppet-2/modules-0/nefos/manifests/init.pp' in environment production
Debug: Automatically imported nefos from nefos into production
Debug: importing '/tmp/vagrant-puppet-2/modules-0/nefos/manifests/common_packages.pp' in environment production
Debug: Automatically imported nefos::common_packages from nefos/common_packages into production
Debug: importing '/tmp/vagrant-puppet-2/modules-0/nefos/manifests/users.pp' in environment production
Debug: Automatically imported nefos::users from nefos/users into production

And the actual error:

Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type account::group at /tmp/vagrant-puppet-2/modules-0/nefos/manifests/users.pp:4 on node zen-tassadar-agent1.home.lan

Wrapped exception:
Invalid resource type account::group
Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type account::group at /tmp/vagrant-puppet-2/modules-0/nefos/manifests/users.pp:4 on node zen-tassadar-agent1.home.lan

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

FACTER_teamcity_own_address='192.168.0.10' FACTER_teamcity_own_port='9091' puppet apply --verbose --debug --modulepath '/tmp/vagrant-puppet-2/modules-0:/etc/puppet/modules' --manifestdir /tmp/vagrant-puppet-2/manifests --detailed-exitcodes /tmp/vagrant-puppet-2/manifests/site.pp
eirc commented 9 years ago

This has probably something to do with Vagrant not properly mounting the modules path or referencing it when running puppet and group.pp is not loaded. BTW there is no puppet v5.3.1. If you could provide a url for an Arch vagrant box (which I guess would include puppet?) I could check it too.

tlatsas commented 9 years ago

Sorry about that. I switched the major/minor numbers. Puppet is on v3.5.1