Issue #16568 has been updated by wesoly romek.
I'm having the same problem on 3.1.1 version. After install some module from github resources puppet could not find it by class name contained in init.pp. My resolution is rename module folder name exactly like class name or in other way round the class name to module folder name (if syntax approves). IMHO puppet classloader could have some tracking module issue. Best Regards ---------------------------------------- Bug #16568: Modules added to modulepath aren't recognized until service restart https://projects.puppetlabs.com/issues/16568#change-93919 * Author: Ryan Coleman * Status: Merged - Pending Release * Priority: Normal * Assignee: Charlie Sharpsteen * Category: autoloader * Target version: 3.2.0 * Affected Puppet version: * Keywords: module class * Branch: https://github.com/puppetlabs/puppet/pull/1616 ---------------------------------------- Recreating my working environment (in this specific order): * Use CentOS 6.0 * Install puppet-server 3.0.0-rc7 from puppetlabs-devel yum repository on master, puppet 3.0.0-rc7 on agent * Install puppetdb module -- `puppet module install puppetlabs-puppetdb` * Start the puppetmaster service * Declare puppetdb & puppetdb::master::config class on master and run puppet) * Install mediawiki module -- `puppet module install martasd-mediawiki` Declare the mediawiki class for your agent node, <pre> class { 'mediawiki': server_name => 'wiki.puppetlabs.vm', admin_email => '[email protected]', db_root_password => 'really_long_password', doc_root => '/var/www', max_memory => '1024' } </pre> * Run Puppet on your agent I expect you'll run into the error I received. <pre> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class mediawiki at /etc/puppet/manifests/site.pp:9 on node wiki1.puppetlabs.vm Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run </pre> Additional info: <pre> [root@master modules]# puppet module list /etc/puppet/modules ├── cprice404-inifile (v0.0.3) ├── inkling-postgresql (v0.3.0) ├── mediawiki (???) ├── puppet-haproxy (v0.0.2) ├── puppetlabs-apache (v0.4.0) ├── puppetlabs-firewall (v0.0.4) ├── puppetlabs-mysql (v0.5.0) ├── puppetlabs-puppetdb (v1.0.3) ├── puppetlabs-stdlib (v3.0.1) ├── ripienaar-concat (v0.2.0) ├── saz-memcached (v2.0.2) └── stahnma-epel (v0.0.2) /usr/share/puppet/modules (no modules installed) [root@master modules]# puppet config print modulepath /etc/puppet/modules:/usr/share/puppet/modules </pre> Problem is resolved by restarting the puppetmaster service. No amount of waiting seems to resolve the issue. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
