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-us...@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.
