Solved, it was affecting both hosts and it related to an overriding
preference I had defined in site.pp (I''d borrowed from the best
practise
guide and not updated) :
filebucket { main: server => puppet }
robl wrote:> Hi,
>
> I''m having a problem with templates and a remote node. I have a
working
> puppetserver and and puppet client (on the same server) which
> successfully runs my manifest(s) and now I''m trying to add a new
client
> on a separate server. It all seems to work except for when I try to use
> templates. For example :
>
> file {
> "/etc/apt/sources.list":
> content => template("apt/sources.list.erb");
> }
>
> fails with :
>
> err:
>
//basenode/default/base/webserver/webserver-apache2/a.example.com/core-apt/File[/etc/cron-apt/config]/source:
> change from {md5}da3d5245761eaf447c7f7c04b8574dcd to
> puppet://ops.rattleresearch.com/files/cron-apt/config failed: Could not
> find server puppet
>
> I have defined the ''server'' parameter in my puppetd.conf
on the new
> client and it successfully transfers files when using :
>
> file { "/etc/cron-apt/config":
> source => "puppet://$puppet_server/files/cron-apt/config"
> }
>
> Seems strange it works on one client but not this one, can anybody
> suggest a reason why ?
>
> Thanks,
>
> Rob
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users
>