Puppet users - Sep 2009 - Running puppet as non-root => getting rid of all those ownership warnings

I''m using puppet to manage configs on machines where I don''t
have root
access.  Whenever I use a File resource where the source is a puppet://
resource, I get tons of warnings when I run puppet that look like:

Cannot manage ownership unless running as root

True enough, I''m not running as root, but I also didn''t
specifically
mention a "owner" parameter on my file resource.  This only seems to
happen to File resources that I populate using a "source" parameter.

These warnings tend to pile up and make it difficult to see more
informative messages from puppet about what has actually changed when
updating.  Is there some way of disabling these messages?

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Brian Ferris wrote:
> I''m using puppet to manage configs on machines where I
don''t have root
> access.  Whenever I use a File resource where the source is a puppet://
> resource, I get tons of warnings when I run puppet that look like:
>
> Cannot manage ownership unless running as root
>
> True enough, I''m not running as root, but I also didn''t
specifically
> mention a "owner" parameter on my file resource.  This only seems
to
> happen to File resources that I populate using a "source"
parameter.
>
> These warnings tend to pile up and make it difficult to see more
> informative messages from puppet about what has actually changed when
> updating.  Is there some way of disabling these messages?
>   
If you omit the owner and group parameters from the file resource then
puppet helpfully tries to set them to the owner/group of the source file
from your puppetmaster.

If you specify the owner/group to be the ones you are running puppetd as
then I think the warnings should go away.

-- 

Trevor Hemsley
Infrastructure Engineer
.................................................
* C A L Y P S O
* Brighton, UK   

OFFICE 	+44 (0) 1273 666 350
FAX 	+44 (0) 1273 666 351

.................................................
www.calypso.com

This electronic-mail might contain confidential information intended
only for the use by the entity named. If the reader of this message is
not the intended recipient, the reader is hereby notified that any
dissemination, distribution or copying is strictly prohibited.

* P * /*/ Please consider the environment before printing this e-mail /*/


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Trevor Hemsley wrote:
> Brian Ferris wrote:
>> I''m using puppet to manage configs on machines where I
don''t have root
>> access.  Whenever I use a File resource where the source is a puppet://
>> resource, I get tons of warnings when I run puppet that look like:
>>
>> Cannot manage ownership unless running as root
>>
>> True enough, I''m not running as root, but I also
didn''t specifically
>> mention a "owner" parameter on my file resource.  This only
seems to
>> happen to File resources that I populate using a "source"
parameter.
>>
>> These warnings tend to pile up and make it difficult to see more
>> informative messages from puppet about what has actually changed when
>> updating.  Is there some way of disabling these messages?
>>   
> If you omit the owner and group parameters from the file resource then
> puppet helpfully tries to set them to the owner/group of the source file
> from your puppetmaster.
> 
> If you specify the owner/group to be the ones you are running puppetd as
> then I think the warnings should go away.
I think Brian is referring to the messages, when puppet is trying to 
configure its runtime environment (config files, logging). There is 
syntax to do as you recommend in the config file too, but I would think 
that this should work by default, without useless noise in the log.


Regards, DavidS

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Just to elaborate, these warnings seem to appear whether I omit the owner
parameter or if I include the owner parameter, set to my current user
account.  I''m using something like:

file { "${my_target_directory}":
  ensure => directory,
  recurse => true,
  source => "puppet://$puppet_server/path/to/source/dir"
}

to recursively copy over a bunch of files and the warning is printed for
each file.  So I think this is more in line with Trevor''s description.
However, adding "owner => myUserId" doesn''t help.  Also,
I''ve confirmed that
file owner on the puppetmaster server already matches my user account.

I''m runnig 0.25.1rc1 btw, though these warnings also appeared under
0.24.8.

Any ideas?


On Wed, Sep 30, 2009 at 5:37 AM, David Schmitt <david@dasz.at> wrote:
>
> Trevor Hemsley wrote:
> > Brian Ferris wrote:
> >> I''m using puppet to manage configs on machines where I
don''t have root
> >> access.  Whenever I use a File resource where the source is a
puppet://
> >> resource, I get tons of warnings when I run puppet that look like:
> >>
> >> Cannot manage ownership unless running as root
> >>
> >> True enough, I''m not running as root, but I also
didn''t specifically
> >> mention a "owner" parameter on my file resource.  This
only seems to
> >> happen to File resources that I populate using a
"source" parameter.
> >>
> >> These warnings tend to pile up and make it difficult to see more
> >> informative messages from puppet about what has actually changed
when
> >> updating.  Is there some way of disabling these messages?
> >>
> > If you omit the owner and group parameters from the file resource then
> > puppet helpfully tries to set them to the owner/group of the source
file
> > from your puppetmaster.
> >
> > If you specify the owner/group to be the ones you are running puppetd
as
> > then I think the warnings should go away.
>
> I think Brian is referring to the messages, when puppet is trying to
> configure its runtime environment (config files, logging). There is
> syntax to do as you recommend in the config file too, but I would think
> that this should work by default, without useless noise in the log.
>
>
> Regards, DavidS
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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 30, 2009 at 8:35 AM, Brian Ferris <bdferris@gmail.com>
wrote:
> Just to elaborate, these warnings seem to appear whether I omit the owner
> parameter or if I include the owner parameter, set to my current user
> account.  I''m using something like:
>
> file { "${my_target_directory}":
>   ensure => directory,
>   recurse => true,
>   source => "puppet://$puppet_server/path/to/source/dir"
> }
>
> to recursively copy over a bunch of files and the warning is printed for
> each file.  So I think this is more in line with Trevor''s
description.
> However, adding "owner => myUserId" doesn''t help. 
Also, I''ve confirmed that
> file owner on the puppetmaster server already matches my user account.
>
> I''m runnig 0.25.1rc1 btw, though these warnings also appeared
under 0.24.8.
>
> Any ideas?

does owner => undef resolve it?

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Negative.  The warning is still present.


On Wed, Sep 30, 2009 at 8:42 AM, Nigel Kersten <nigelk@google.com> wrote:
>
> On Wed, Sep 30, 2009 at 8:35 AM, Brian Ferris <bdferris@gmail.com>
wrote:
> > Just to elaborate, these warnings seem to appear whether I omit the
owner
> > parameter or if I include the owner parameter, set to my current user
> > account.  I''m using something like:
> >
> > file { "${my_target_directory}":
> >   ensure => directory,
> >   recurse => true,
> >   source => "puppet://$puppet_server/path/to/source/dir"
> > }
> >
> > to recursively copy over a bunch of files and the warning is printed
for
> > each file.  So I think this is more in line with Trevor''s
description.
> > However, adding "owner => myUserId" doesn''t
help.  Also, I''ve confirmed
> that
> > file owner on the puppetmaster server already matches my user account.
> >
> > I''m runnig 0.25.1rc1 btw, though these warnings also appeared
under
> 0.24.8.
> >
> > Any ideas?
>
>
> does owner => undef resolve it?
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---