I found the issue. It turns out to be related to the use of Rack on the Puppet Master.
I'll document the issue so the mailing list archive can help others. Tom On Tue, Oct 22, 2013 at 12:20 AM, Tom Limoncelli <t...@whatexit.org> wrote: > I upgraded to puppet 3.3.1 and my clients can no longer access custom > facts or types. pluginsync = true in [main] for both clients and the > server. I suspect a problem with pluginsync because the master is > able to load the custom facts. > > I looked at syslog on both machines and didn't find any error or > warning messages; just the usual messages minus the ones about loading > custom facts. > > The first run after the upgrade resulted in messages about deleting > the custom facts (filebucketing them). That makes me suspect > fileserver.conf. According to our git repo, none of the *.conf files > changed. Did their interpretation change? > > "puppet agent -t -d -v" doesn't show anything unusual (except the > missing lines about syncing) > > Where should I start looking to debug this? > > Thanks, > Tom > P.S. I'm using CentOS6.4. > > -- > Email: t...@whatexit.org Work: tlimonce...@stackoverflow.com > Skype: YesThatTom > Blog: http://EverythingSysadmin.com -- Email: t...@whatexit.org Work: tlimonce...@stackoverflow.com Skype: YesThatTom Blog: http://EverythingSysadmin.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
