Hey gang,
I'm using the latest Puppet/Augeas RPMs from EPEL testing:
puppet-0.24.8-1.el5.1
augeas-0.4.2-1.el5
augeas-libs-0.4.2-1.el5
I have the following in my Puppet manifest:
augeas { "rpm":
context => "/etc/logrotate.d/rpm",
changes => [ "set rule/create/mode 0640",
"set rule/create/owner root",
"set rule/create/group root" ],
}
This should add a "create 0640 root root" line to the
/etc/logrotate.d/rpm file.
Contents of the current /etc/logrotate.d/rpm file:
/var/log/rpmpkgs {
weekly
notifempty
missingok
}
(No create line in there)
I get the following in my puppetd debug trace:
debug: Augeas[rpm](provider=augeas): Opening augeas with root /, lens
path , flags 0
debug: Augeas[rpm](provider=augeas): Augeas version 0.4.2 is installed
debug: Augeas[rpm](provider=augeas): Will attempt to save and only run
if files changed
debug: Augeas[rpm](provider=augeas): sending command 'set' with params
["/etc/logrotate.d/rpm/rule/create/mode", "0640"]
debug: Augeas[rpm](provider=augeas): sending command 'set' with params
["/etc/logrotate.d/rpm/rule/create/owner", "root"]
debug: Augeas[rpm](provider=augeas): sending command 'set' with params
["/etc/logrotate.d/rpm/rule/create/group", "root"]
debug: Augeas[rpm](provider=augeas): Skipping becuase no files were changed
debug: Augeas[rpm](provider=augeas): Closed the augeas connection
So, for some reason Augeas doesn't see any changes being made to the
file by the set commands. If I run the set commands in augtool (in
exactly the same order) and then run "save", then I do get changes to my
file.
Is this a bug with the Puppet augeas type?
Thanks,
Avi
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
