one more thing to note. If I turn off all the evironments, restart puppetmaster and then everything works fine; and just one more clairification it's only "new" modules being created that have the problem.
On Feb 10, 10:23 am, trey85stang <trey85st...@gmail.com> wrote: > Hey all, Im still new to puppet so I may be doing something wrong. > The problem I am having is I have setup multiple environments. Going > from one environment. > > To get started with testing that I copied my manifests directory and > modules dirctories into a handful of different directories to setup > the environments. > > The I made the changes to my puppet.conf which is below: > [main] > vardir = /var/lib/puppet > logdir = /var/log/puppet > rundir = /var/run/puppet > ssldir = $vardir/ssl > manifest = /etc/puppet/environments/production/manifests/site.pp > modulepath = /etc/puppet/environments/production/modules > external_nodes = /etc/puppet/ext_node.sh > node_terminus = exec > > [agent] > classfile = $vardir/classes.txt > localconfig = $vardir/localconfig > [master] > environments=production,development,testing,beta,pilot > [production] > manifest = /etc/puppet/environements/production/manifests/site.pp > modulepath = /etc/puppet/environments/production/modules > [development] > manifest = /etc/puppet/environments/development/manifests/site.pp > modulepath = /etc/puppet/environments/development/modules > [testing] > manifest = /etc/puppet/environments/testing/manifests/site.pp > modulepath = /etc/puppet/environments/testing/modules > [beta] > manifest = /etc/puppet/environments/beta/manifests/site.pp > modulepath = /etc/puppet/environments/beta/modules > [pilot] > manifest = /etc/puppet/environments/pilot/manifests/site.pp > modulepath = /etc/puppet/environments/pilot/modules > > This all works perfectly, until I add a new module to one of the > environemtns to push a file out, after which my clients will receive > the following message: > Feb 10 10:06:31 mynode1 puppet-agent[28932]: (/Stage[main]/Environment/ > File[/etc/pupdev]) Could not evaluate: Error 400 on SERVER: Not > authorized to call find on /file_metadata/environment/pupdev Could not > retrieve file metadata for puppet:///environment/pupdev: Error 400 on > SERVER: Not authorized to call find on /file_metadata/environment/ > pupdev at /etc/puppet/environments/development/modules/environment/ > manifests/init.pp:7 > > The message on the server is: > Feb 10 10:05:02 puppetserver puppet-master[5377]: Not authorized to > call find on /file_metadata/environment/pupdev > > I've seen a few posts mentioning that the fileserver.conf file needs > to be updated. I have added allow * to it as suggested in a few > other palces but all that does is keeps puppetmaster from restarting. > > Does anyone have any ideas as to what the problem is? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
