Issue #17967 has been updated by Charlie Sharpsteen.

This is probably a duplicate of #16568 and I've bisected the behavior down to 
commit [242692e](https://github.com/puppetlabs/puppet/commit/242692e).

In a nutshell, that commit causes the Puppet master to internally cache classes 
that were missing during compilation runs. The master then skips looking for 
those classes during subsequent compilations. As noted in the commit message, 
this achieves a 30% speedup in some situations---but at the cost of setting up 
a confusing situation for people who forgot to install modules required by 
their node definition, or had a broken module as in this case.

----------------------------------------
Bug #17967: puppetmaster caches empty directory even if usecacheonfailure=false
https://projects.puppetlabs.com/issues/17967#change-89142

* Author: L Harris
* Status: Needs More Information
* Priority: Normal
* Assignee: L Harris
* Category: 
* Target version: 
* Affected Puppet version: 
* Keywords: 
* Branch: 
----------------------------------------
So on both the puppet and puppetmaster I have usecacheonfailure = false in 
/etc/puppet/puppet.conf

Unfortunately I had an empty directory for one of my modules 
(/etc/puppet/modules/rhn_register). The agent checked in and gave the error:

err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find 
declared class rhn_register at /etc/puppet/modules/base/manifests/init.pp:46 on 
node test-vbox-rh6.
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

Ok so far that's fine and expected.  I put the files and subdirectories into 
/etc/puppet/modules/rhn_register and have the agent check in.  Unfortunately it 
gave the same error. That wasn't at all fine or expected.

The only two solutions were to wait (30min-1hr) or restart apache.  Seems like 
somewhere it is caching the fact that the directory was empty.

Using puppet 3.0.1 


-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to