On Wed, Nov 24, 2010 at 05:03:45PM +0100, Arnau Bria wrote:
> On Wed, 24 Nov 2010 07:22:11 -0800 (PST)
> jcbollinger jcbollinger wrote:
> 
> 
> > On Nov 24, 6:17 am, Ohad Levy <ohadl...@gmail.com> wrote:
> Hi !
> 
> I'm getting a little crazy with this... I'll paste some code and see if
> you see what's happening...
> 
> > > You probably have a File statement somewhere (like site.pp) which
> > > has a default source or target attributes.
> 
> Nop, I'm not defining source/content default.
>  
> If I comment content line, all works fine:
> 
>         file {  'default_dns':
>                         name    => '/etc/resolv.conf',
> #                       content => "search pic.es nameserver 193.109.175.5 
> nameserver 193.109.172.144 nameserver 158.109.0.1 nameserver 84.88.0.5";
>         }
> 
> info: Applying configuration version '1290614540'
> info: FileBucket adding /etc/resolv.conf as 
> {md5}6607f03347a11c61819976c8e28483bf
> info: /Stage[main]/Common_system_defaults/File[default_dns]: Filebucketed 
> /etc/resolv.conf to puppet with sum 6607f03347a11c61819976c8e28483bf
> notice: /Stage[main]/Common_system_defaults/File[default_dns]/ensure: ensure 
> changed 'file' to 'link'
> notice: Finished catalog run in 0.37 seconds
> 

I dont think its working fine, when /etc/resolv.conf is now a link (ensure 
changed 'file' to 'link'). At first
* don't use name. If anything, use "path" but I recommend just declaring
  file {'/etc/resolv.conf': content => ...).
* If you still have strange results try to use an explicit ensure (you
  should always specfy one anyways. So use ensure => 'file' to make sure
  its a normal file
* If you still get strange results, test to set target => undef and
  source => undef. If this helps, you have set a default somewhere.
  But maybe there is just a missing bracket somewhere so puppet will try
  to parse different resource definitions as one

-Stefan

Attachment: pgpS88ksSKyMQ.pgp
Description: PGP signature

Reply via email to