trey85stang
2011-Feb-10 16:23 UTC
[Puppet Users] Problem with file serving and envrionments.
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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
trey85stang
2011-Feb-10 19:16 UTC
[Puppet Users] Re: Problem with file serving and envrionments.
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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
trey85stang
2011-Feb-11 18:30 UTC
[Puppet Users] Re: Problem with file serving and envrionments.
Finally figured it out, Maybe this is a bug I am not sure. But I was setting the environment only from the external_nodes script. I was not making any changes to the client config. When I add the environment to the puppet.conf on the client everything now works as expected. Not exactly the way it seems it should work, if you can specify the environment with ext_nodes then the client shouldn''t need to configured to point to it; should it? Thanks, Trey On Feb 10, 1:16 pm, trey85stang <trey85st...@gmail.com> wrote:> 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Daniel Pittman
2011-Feb-11 18:34 UTC
Re: [Puppet Users] Re: Problem with file serving and envrionments.
On Feb 11, 2011 10:30 AM, "trey85stang" <trey85stang@gmail.com> wrote:> > Finally figured it out, Maybe this is a bug I am not sure. But I was > setting the environment only from the external_nodes script. I was > not making any changes to the client config. When I add the > environment to the puppet.conf on the client everything now works as > expected.It isn''t clear what the right behaviour is - we argue about that internally, but it is clear that the current behaviour is a bug. You need to update the client environment, since currently catalogs use the ENC idea of environment, but files use the client idea of environment, which is a total mess. Sorry you got bitten by that too. Most people end up templating the client config, and make their environment value sticky through that. Regards, Daniel -- Puppet Labs Developer –http://puppetlabs.com Daniel Pittman <daniel@puppetlabs.com> Contact me via gtalk, email, or phone: +1 (877) 575-9775 Sent from a mobile device. Please forgive me if this is briefer than usual. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Nigel Kersten
2011-Feb-11 19:27 UTC
Re: [Puppet Users] Re: Problem with file serving and envrionments.
On Fri, Feb 11, 2011 at 10:30 AM, trey85stang <trey85stang@gmail.com> wrote:> Finally figured it out, Maybe this is a bug I am not sure. But I was > setting the environment only from the external_nodes script. I was > not making any changes to the client config. When I add the > environment to the puppet.conf on the client everything now works as > expected. > > Not exactly the way it seems it should work, if you can specify the > environment with ext_nodes then the client shouldn''t need to > configured to point to it; should it?Ah, you''re becoming familiar with 3910 my old dear friend. https://projects.puppetlabs.com/issues/3910 time to devote some more cycles to this one... -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
trey85stang
2011-Feb-11 20:13 UTC
[Puppet Users] Re: Problem with file serving and envrionments.
Thanks for the 411, Looks like I will just deal with the config file on the client. I can''t say that would be my preferred way but I can deal with that. Thanks for the reponses and it''s not a big deal. I can''t complain too much when my work load is going to be decreasing greatly when I get this deployed. On Feb 11, 1:27 pm, Nigel Kersten <ni...@puppetlabs.com> wrote:> On Fri, Feb 11, 2011 at 10:30 AM, trey85stang <trey85st...@gmail.com> wrote: > > Finally figured it out, Maybe this is a bug I am not sure. But I was > > setting the environment only from the external_nodes script. I was > > not making any changes to the client config. When I add the > > environment to the puppet.conf on the client everything now works as > > expected. > > > Not exactly the way it seems it should work, if you can specify the > > environment with ext_nodes then the client shouldn''t need to > > configured to point to it; should it? > > Ah, you''re becoming familiar with 3910 my old dear friend. > > https://projects.puppetlabs.com/issues/3910 > > time to devote some more cycles to this one...-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
trey85stang
2011-Feb-12 22:21 UTC
[Puppet Users] Re: Problem with file serving and envrionments.
One suggestion, if you two are still reading. First im not a developer, just a sys admin so if this suggestion is dumb just ignore but: Why not just add an override in the client config. env_defined_remote = true (or whatever), will tell the puppet client to grab the environment from the server, with the default being false and leaving the current functionality. And a server setting saying that the client will always specify the the environment? Or perhaps I am over simplifying this? -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.