Issue #6111 has been updated by James Turnbull. Target version changed from 2.6.6 to 2.6.x
---------------------------------------- Bug #6111: Should be able to audit Host resources https://projects.puppetlabs.com/issues/6111 Author: Jeff McCune Status: Accepted Priority: Normal Assignee: Category: auditing/compliance Target version: 2.6.x Affected Puppet version: development Keywords: audit, inspect, Branch: 2.6.next ## Overview ## Using the audit meta-parameter with a host resource does not appear to audit the "ip" parameter. I'm not sure if the this parameter is a property or not, but puppet resource is able to sort out the value correctly: ## Impact Data ## This is relatively low impact, but the ability to audit entries in /etc/hosts is important as they have a high impact if they're not in the correct state. For example, applications will fail to start entirely. ## Steps to Reproduce ## Manifest: host { $fqdn: ensure => present, ip => $iptouseinetchost, alias => $hostname, audit => ip, } ## Expected Results ## Note, I would expect to see something like: ...Host[seed.puppetlabs.vm]/ip audit change: Previously recorded value 192.168.69.139 has been changed to 192.168.69.138. I also expect the IP value to show up in Puppet inspection reports and they do not. ## Actual Results ## In a noop run, the previous value is shown in the log messages but does not show up in the log messages related to audit change events. The IP values also do not show up in inspect reports. ## Steps to Reproduce ## Given the above manifest and the following Puppet Run. $ envpuppet puppet agent --test --server autoserver --noop info: Caching catalog for seed.puppetlabs.vm info: Applying configuration version '1296657013' notice: /Stage[main]/Resolver_test/Host[seed.puppetlabs.vm]/ip: current_value 192.168.69.138, should be 192.168.69.141 (noop) (previously recorded value was 192.168.69.139) notice: Finished catalog run in 0.11 seconds Notice there is no "audit change:" message like there are for File resources. You'll need to obtain the catalog once with a noop run, then manually change the /etc/hosts file and perform a noop run again to see if the IP property is audited as expected. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
