Now that cucumber-puppet is a Puppet Labs project, I guess it is time to email questions about it here ;) I''m in the process of adding RoR environment support into my module tree, so instead of just having a single location for all modules, I now have several environments. Logically to test my different environments I''ll need to call cucumber-puppet once for each environment (and I guess it is possible I''ll need to change which tests I run in each). What mechanism is there (or is needed) in order to make cucumber-puppet aware of the environment (or at least modulepath) settings? -- 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.
Hi Oliver, try: http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environments On Sep 14, 2010, at 7:09 AM, Oliver <ohookins@gmail.com> wrote:> Now that cucumber-puppet is a Puppet Labs project, I guess it is time > to email questions about it here ;) > > I''m in the process of adding RoR environment support into my module > tree, so instead of just having a single location for all modules, I > now have several environments. Logically to test my different > environments I''ll need to call cucumber-puppet once for each > environment (and I guess it is possible I''ll need to change which > tests I run in each). > > What mechanism is there (or is needed) in order to make > cucumber-puppet aware of the environment (or at least modulepath) > settings? > > -- > 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. >-- 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.
Bruce Richardson
2010-Sep-14 13:28 UTC
Re: [Puppet Users] cucumber-puppet and environments
On Tue, Sep 14, 2010 at 08:34:00AM -0400, Ryan Coleman wrote:> Hi Oliver, try: > > http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_EnvironmentsI''ve never been fond of the way RoR treats environments (or, at least, the way RoR developers treat them). The thing I really don''t like about the way Puppet implements them is the fact that the *client* specifies which environment to use. This is just plain wrong. At the very least, the puppetmaster should be able to ignore or override the client''s idea of which environment to use on a per host basis. -- Bruce I see a mouse. Where? There, on the stair. And its clumsy wooden footwear makes it easy to trap and kill. -- Harry Hill
On Tue, Sep 14, 2010 at 6:28 AM, Bruce Richardson <itsbruce@workshy.org> wrote:> On Tue, Sep 14, 2010 at 08:34:00AM -0400, Ryan Coleman wrote: >> Hi Oliver, try: >> >> http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environments > > I''ve never been fond of the way RoR treats environments (or, at least, > the way RoR developers treat them). The thing I really don''t like about > the way Puppet implements them is the fact that the *client* specifies > which environment to use. This is just plain wrong. At the very least, > the puppetmaster should be able to ignore or override the client''s idea > of which environment to use on a per host basis.Bruce, we have some bugs in around this. The external node classifier should be able to set the environment, and should be able to do so without the client environment specification being consulted at all if that''s what you want. I''ll try and dig them up today, but from what I understand it''s not a simple fix.> > -- > Bruce > > I see a mouse. Where? There, on the stair. And its clumsy wooden > footwear makes it easy to trap and kill. -- Harry Hill > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkyPeJEACgkQtkVqYTMBSwExSwCeP/F7rMGXs9IQ7Ulz1gsGxD/9 > WTEAnRwgtxB46w6bq4Ft46DmhUMYw26q > =KRMp > -----END PGP SIGNATURE----- > >-- nigel -- 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.
On Tue, 14 Sep 2010, Bruce Richardson wrote:> On Tue, Sep 14, 2010 at 08:34:00AM -0400, Ryan Coleman wrote: > > Hi Oliver, try: > > > > http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environments > > I''ve never been fond of the way RoR treats environments (or, at least, > the way RoR developers treat them). The thing I really don''t like about > the way Puppet implements them is the fact that the *client* specifies > which environment to use. This is just plain wrong. At the very least, > the puppetmaster should be able to ignore or override the client''s idea > of which environment to use on a per host basis.The external node classifier can override the client''s idea of the environment. --apb (Alan Barrett) -- 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.
On Sep 15, 11:01 am, Alan Barrett <a...@cequrux.com> wrote:> On Tue, 14 Sep 2010, Bruce Richardson wrote: > > On Tue, Sep 14, 2010 at 08:34:00AM -0400, Ryan Coleman wrote: > > > Hi Oliver, try: > > > >http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environ... > > > I''ve never been fond of the way RoR treats environments (or, at least, > > the way RoR developers treat them). The thing I really don''t like about > > the way Puppet implements them is the fact that the *client* specifies > > which environment to use. This is just plain wrong. At the very least, > > the puppetmaster should be able to ignore or override the client''s idea > > of which environment to use on a per host basis. > > The external node classifier can override the client''s idea of the > environment.Hi all, thanks for the responses but they have nothing to do with the problem I have. The client/server interaction which determines environment is not the issue since cucumber-puppet calls the Puppet module directly, which makes it a lot more like using the standalone puppet utility. The question is, how to bend cucumber-puppet to recognise environments when there is no server to define what the module path is from a given environment setting from the client. It is possible to specify the module path (with some slightly nasty hacks) but I was looking for a way to reuse the concept of environments which I will be using everywhere else. -- 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.
On Wed, Sep 15, 2010 at 2:01 AM, Alan Barrett <apb@cequrux.com> wrote:> On Tue, 14 Sep 2010, Bruce Richardson wrote: >> On Tue, Sep 14, 2010 at 08:34:00AM -0400, Ryan Coleman wrote: >> > Hi Oliver, try: >> > >> > http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environments >> >> I''ve never been fond of the way RoR treats environments (or, at least, >> the way RoR developers treat them). The thing I really don''t like about >> the way Puppet implements them is the fact that the *client* specifies >> which environment to use. This is just plain wrong. At the very least, >> the puppetmaster should be able to ignore or override the client''s idea >> of which environment to use on a per host basis. > > The external node classifier can override the client''s idea of the > environment.It can''t really. http://projects.puppetlabs.com/issues/3910> > --apb (Alan Barrett) > > -- > 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. > >-- 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.
* Oliver [2010-09-14]:> What mechanism is there (or is needed) in order to make > cucumber-puppet aware of the environment (or at least modulepath) > settings?The environment is just another node fact. As long as you don''t use yaml node files, you can set it in hooks.rb or in a Given step: @facts[''environment''] = "test1" If you use yaml node files, you have to use different files for different environments. It is currently not possible to override the facts from node files. cheers, Nikolay -- 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.
On Wed, 15 Sep 2010, Nigel Kersten wrote:> > The external node classifier can override the client''s idea of the > > environment. > > It can''t really. > > http://projects.puppetlabs.com/issues/3910I didn''t know about that one; my bug in this area is #2834. I use an external node classifier purely for the purpose of setting the environment (and a parameter called $error_message or something, but not any classes). There are minor problems when the master and client disagree, but so far the problems have not been enough to prevent installing a puppet.conf from a template, to make the client specify the correct environment on the next run. --apb (Alan Barrett) -- 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.
On Wed, Sep 15, 2010 at 12:31 PM, Alan Barrett <apb@cequrux.com> wrote:> On Wed, 15 Sep 2010, Nigel Kersten wrote: >> > The external node classifier can override the client''s idea of the >> > environment. >> >> It can''t really. >> >> http://projects.puppetlabs.com/issues/3910 > > I didn''t know about that one; my bug in this area is #2834. > > I use an external node classifier purely for the purpose of setting > the environment (and a parameter called $error_message or something, > but not any classes). There are minor problems when the master and > client disagree, but so far the problems have not been enough to prevent > installing a puppet.conf from a template, to make the client specify the > correct environment on the next run.I wouldn''t class the situation as "minor problems" You''re getting classes from the server specified environment, but file resources from the client specified environment... Maybe your setup is different, but even if the client runs work in my setup, I know I''d be delivering inconsistent configurations.> > --apb (Alan Barrett) > > -- > 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 -- 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.
On Wed, 15 Sep 2010, Nigel Kersten wrote:> On Wed, Sep 15, 2010 at 12:31 PM, Alan Barrett <apb@cequrux.com> wrote: > > On Wed, 15 Sep 2010, Nigel Kersten wrote: > >> > The external node classifier can override the client''s idea of the > >> > environment. > >> > >> It can''t really. > >> > >> http://projects.puppetlabs.com/issues/3910 > > > > the environment (and a parameter called $error_message or something, > > but not any classes). =?0There are minor problems when the master and > > client disagree, but so far the problems have not been enough to prevent > > installing a puppet.conf from a template, to make the client specify the > > correct environment on the next run. > > I wouldn''t class the situation as "minor problems"I meant to say that the problems I have personally seen have been minor; I haven''t noticed the problem you describe, possibly because I deliberately run puppetd with a restrictive "tags" parameter when I know that the environment is not properly set, or possibly because any incorrect files would have been corrected on the next run, but I agree that issue #3910 is serious. --apb (Alan Barrett) -- 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.
On Wed, Sep 15, 2010 at 12:53 PM, Alan Barrett <apb@cequrux.com> wrote:> On Wed, 15 Sep 2010, Nigel Kersten wrote: >> On Wed, Sep 15, 2010 at 12:31 PM, Alan Barrett <apb@cequrux.com> wrote: >> > On Wed, 15 Sep 2010, Nigel Kersten wrote: >> >> > The external node classifier can override the client''s idea of the >> >> > environment. >> >> >> >> It can''t really. >> >> >> >> http://projects.puppetlabs.com/issues/3910 >> > >> > the environment (and a parameter called $error_message or something, >> > but not any classes). =?0There are minor problems when the master and >> > client disagree, but so far the problems have not been enough to prevent >> > installing a puppet.conf from a template, to make the client specify the >> > correct environment on the next run. >> >> I wouldn''t class the situation as "minor problems" > > I meant to say that the problems I have personally seen have been > minor; I haven''t noticed the problem you describe, possibly because I > deliberately run puppetd with a restrictive "tags" parameter when I > know that the environment is not properly set, or possibly because any > incorrect files would have been corrected on the next run, but I agree > that issue #3910 is serious.I think this is what worries me the most about this bug, that people may not realize it exists, because it many cases it''s invisible, no matter how you restrict the run with tags. As long as the files you refer to in the classes actually exist in the client-specified-environment, the puppet runs will cruise along happily until that one time when you make a change and it doesn''t go out to everyone. :( Multiple runs do mitigate it, but ... we shouldn''t have to do that.> > --apb (Alan Barrett) > > -- > 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 -- 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.
On Sep 15, 5:53 pm, Nikolay Sturm <goo...@erisiandiscord.de> wrote:> * Oliver [2010-09-14]: > > > What mechanism is there (or is needed) in order to make > > cucumber-puppet aware of the environment (or at least modulepath) > > settings? > > The environment is just another node fact. As long as you don''t use yaml > node files, you can set it in hooks.rb or in a Given step: > > @facts[''environment''] = "test1" > > If you use yaml node files, you have to use different files for > different environments. It is currently not possible to override the > facts from node files.OK, I was aware of being able to set the environment in this way, but didn''t realise that this would tie in with client-defined properties of that environment (e.g. the modulepath) but from what I''ve read from other posts in this thread, that seems to be possible (and the source of some confusion for the related bugs). So basically, it is a matter of using this variable plus defining the desired environments in some puppet.conf that cucumber-puppet pulls in. Thanks! -- 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.
Bruce Richardson
2010-Sep-16 08:15 UTC
Re: [Puppet Users] cucumber-puppet and environments
On Wed, Sep 15, 2010 at 09:31:19PM +0200, Alan Barrett wrote:> I use an external node classifier purely for the purpose of setting > the environment (and a parameter called $error_message or something, > but not any classes). There are minor problems when the master and > client disagree, but so far the problems have not been enough to prevent > installing a puppet.conf from a template, to make the client specify the > correct environment on the next run.You''re still trusting the client. It''s the wrong approach (I''m not criticising you personally, Puppet doesn''t leave you much choice if you want to use environments), it''s vulnerable to error, fragile and potentially insecure. -- Bruce I unfortunately do not know how to turn cheese into gold. -- 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.
On Thu, Sep 16, 2010 at 1:15 AM, Bruce Richardson <itsbruce@workshy.org> wrote:> On Wed, Sep 15, 2010 at 09:31:19PM +0200, Alan Barrett wrote: >> I use an external node classifier purely for the purpose of setting >> the environment (and a parameter called $error_message or something, >> but not any classes). There are minor problems when the master and >> client disagree, but so far the problems have not been enough to prevent >> installing a puppet.conf from a template, to make the client specify the >> correct environment on the next run. > > You''re still trusting the client. It''s the wrong approach (I''m not > criticising you personally, Puppet doesn''t leave you much choice if you > want to use environments), it''s vulnerable to error, fragile and > potentially insecure.The client is the only component that can be authoritative over the environment unfortunately. However we set it via a fact, and that hasn''t been fragile for us. YMMV.> > -- > Bruce > > I unfortunately do not know how to turn cheese into gold. > > -- > 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 -- 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.
On Thu, 16 Sep 2010, Bruce Richardson wrote:> On Wed, Sep 15, 2010 at 09:31:19PM +0200, Alan Barrett wrote: > > I use an external node classifier purely for the purpose of setting > > the environment [...] > You''re still trusting the client.Yes, for file serving, as I discovered a few messages earlier in this thread, and I don''t like that at all. But for compiling the catalog, I do not believe that I trust the client. I have tested with incorrect environments on the client''s command line or in the client''s puppet.conf, and the server correctly uses the environment from the external node classifier. --apb (Alan Barrett) -- 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.
On Fri, Sep 17, 2010 at 6:10 AM, Alan Barrett <apb@cequrux.com> wrote:> On Thu, 16 Sep 2010, Bruce Richardson wrote: >> On Wed, Sep 15, 2010 at 09:31:19PM +0200, Alan Barrett wrote: >> > I use an external node classifier purely for the purpose of setting >> > the environment [...] >> You''re still trusting the client. > > Yes, for file serving, as I discovered a few messages earlier in > this thread, and I don''t like that at all. But for compiling the > catalog, I do not believe that I trust the client. I have tested with > incorrect environments on the client''s command line or in the client''s > puppet.conf, and the server correctly uses the environment from the > external node classifier.Are you absolutely positive about this ? Because if you are, then the bug I referenced above is wrong, and I''d like to know :) http://projects.puppetlabs.com/issues/3910> > --apb (Alan Barrett) > > -- > 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. > >-- 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.
On Fri, 17 Sep 2010, Nigel Kersten wrote:> >> On Wed, Sep 15, 2010 at 09:31:19PM +0200, Alan Barrett wrote: > >> > I use an external node classifier purely for the purpose of > >> > setting the environment [...] > > I have tested with incorrect environments on the client''s command > > line or in the client''s puppet.conf, and the server correctly uses > > the environment from the external node classifier. > > Are you absolutely positive about this ?Yes, for puppet 0.25.5. I just ran "/usr/local/sbin/puppetd --onetime --test --noop --environment=WRONG --tags=notify", and I saw the client perform "GET /WRONG/catalog/host.domain.example?...", but it received the catalog for the correct environment (and stashed it in /var/puppet/client_yaml/catalog/host.domain.example), and it performed a "notify" whose text contains the correct environment name. I repeated the test three times, with (1) an environment that does not exist at all on the server, (2) an environment called "UNCONFIGURED", which is the default as far as puppetmasterd is concerned, and whose manifest contains not much more than a "fail" statement, and (3) a more normal environment that just happened to be incorrect for this client. I then repeated test (1) (but not the others) by specifying the incorrect environment in puppet.conf instead of on the command line. I received identical results every time. I also know that the server was not trying to trick me by substituting the correct $environment string into the notify message from the catalog for some incorrect environment, because all environments contain ''node default { fail "..." }'', and the fail as not triggered. Something that might be relevant here is that my external node classifier prints this sort of output: --- parameters: environment: FOO whereas somebody told me a few days ago that it''s supposed to put environment at the top level, not inside "parameters". --apb (Alan Barrett) -- 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.
On Fri, Sep 17, 2010 at 9:42 AM, Alan Barrett <apb@cequrux.com> wrote:> On Fri, 17 Sep 2010, Nigel Kersten wrote: >> >> On Wed, Sep 15, 2010 at 09:31:19PM +0200, Alan Barrett wrote: >> >> > I use an external node classifier purely for the purpose of >> >> > setting the environment [...] >> > I have tested with incorrect environments on the client''s command >> > line or in the client''s puppet.conf, and the server correctly uses >> > the environment from the external node classifier. >> >> Are you absolutely positive about this ? > > Yes, for puppet 0.25.5. > > I just ran "/usr/local/sbin/puppetd --onetime --test --noop > --environment=WRONG --tags=notify", and I saw the client perform > "GET /WRONG/catalog/host.domain.example?...", but it received > the catalog for the correct environment (and stashed it in > /var/puppet/client_yaml/catalog/host.domain.example), and it performed a > "notify" whose text contains the correct environment name. > > I repeated the test three times, with (1) an environment that does not > exist at all on the server, (2) an environment called "UNCONFIGURED", > which is the default as far as puppetmasterd is concerned, and whose > manifest contains not much more than a "fail" statement, and (3) a > more normal environment that just happened to be incorrect for this > client. I then repeated test (1) (but not the others) by specifying the > incorrect environment in puppet.conf instead of on the command line. I > received identical results every time.So you''re not seeing the mismatch between files and file metadata as described in the bug? Do you have a default modulepath defined that things are falling back to?> > I also know that the server was not trying to trick me by substituting > the correct $environment string into the notify message from the catalog > for some incorrect environment, because all environments contain ''node > default { fail "..." }'', and the fail as not triggered. > > Something that might be relevant here is that my external node > classifier prints this sort of output: > > --- > parameters: > environment: FOO > > whereas somebody told me a few days ago that it''s supposed to > put environment at the top level, not inside "parameters". > > --apb (Alan Barrett) > > -- > 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 -- 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.
On Fri, 17 Sep 2010, Nigel Kersten wrote:> > I just ran "/usr/local/sbin/puppetd --onetime --test --noop > > --environment=WRONG --tags=notify", and I saw the client perform > > "GET /WRONG/catalog/host.domain.example?...", but it received > > the catalog for the correct environment (and stashed it in > > /var/puppet/client_yaml/catalog/host.domain.example), and it performed a > > "notify" whose text contains the correct environment name. > > So you''re not seeing the mismatch between files and file metadata as > described in the bug? > > Do you have a default modulepath defined that things are falling back to?I haven''t tried replicating exactly whats in bug #3910. The tests that I have done so far would not expose the case of files being downloaded from a module in the wrong environment, though I think they would expose catalogs being compiled with a modulepath for the wrong environment. I don''t set modulepath at the top level or in the [puppetmasterd] section; it''s set only in the environment-specific sections of puppet.conf. --apb (Alan Barrett) -- 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.