On Wednesday, August 7, 2013 6:03:17 PM UTC-5, Dan M wrote: > > I think I have found the fix... and it looks a little bit magical... Ruby > made... > > I was able to solve the problem by removing */etc/puppet/manifests * > folder. > It was empty at the moment of removal, but later on gets recreated by > puppet. > Anyway - Agent finally works as expected. >
If that was the key thing that solved the problem then very likely it had something to do with the permissions or SELinux context of that directory, but see also below. > > Also I have commented out *hiera_config* variable. > There is a significant possibility that this was actually the key change. Puppet 3 performs a hiera lookup for each parameter of each parameterized class declared for your node, and despite my continuing efforts, the world seems unable to get enough of class parameterization. I don't have to look to be confident that the classes of the puppetlabs-apache module are parameterized, especially the top-level "apache" class. An issue related to hiera configuration makes sense as a reason for Puppet to fail when you 'include' a class, but succeed when you don't. John -- 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.
