Hi there,

I'm using the puppet:/// protocol with the triple slash as described
in the advanced puppet recipe because I want to keep all my config
files on the puppet server that serves the puppet nodes and such:
http://reductivelabs.com/trac/puppet/wiki/AdvancedPuppetRecipe

In terms of connecting to the fileserver to describe the file and diff
the checksums, there are no problems and it will connect to the server
that the node is getting its configuration from.  It even shows the
correct diff that will be applied to the file if there are changes.
However, when it comes time to actually retrieve the file, the puppet
client seems to want the file from the server "puppet", instead of
the /etc/puppet/puppet.conf-specified server.  It is as if I had
written "puppet://puppet/module/myfile.conf" - but the problem only
applies in terms of file retrieval, not for diffing the file.

My current workaround is to just change /etc/hosts so that puppet
points to my puppet server, but doing this makes my clusters less
portable, and I'm pretty sure the point of the puppet:/// protocol was
to avoid this problem.

>From what I've searched online and in the group, someone had a similar
problem and workarounds at (http://osdir.com/ml/sysutils.puppet.user/
2006-09/msg00279.html), but I believe that was because he was using
"puppet://puppet/module/file", with only 2 slashes.  This is also not
a certificate/signing problem, which came up frequently when i
searched for the error "could not find server puppet".

Any suggestions or ideas (possibly for what I may be doing wrong)
would be greatly appreciated!
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+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to