Issue #9685 has been updated by James Turnbull. Status changed from Unreviewed to Needs More Information Assignee set to Jo Rhett
Jo - just so I make sure I get this - it changes it BOTH times and only reports it once? And you're running --test the first time and --verbose the second? What happens if you run --verbose first? ---------------------------------------- Bug #9685: first run with the newly compiled catalog will not report the changes made to the system. https://projects.puppetlabs.com/issues/9685 Author: Jo Rhett Status: Needs More Information Priority: Normal Assignee: Jo Rhett Category: agent Target version: Affected Puppet version: 2.6.6 Keywords: Branch: For example, <pre> 1. I edited a manifest to change the ntp servers. 2. I run "puppet agent --test" (which includes verbose) and it reports the new catalog timestamp, but shows no changes info: Caching catalog for changes.for.me info: Applying configuration version '1316827173' notice: Finished catalog run in 248.13 seconds 3. I confirm that the ntp.conf was in fact changed as per the new catalog 4. Reverse the ntp.conf edit by hand 5. Re-run "puppet agent --verbose" and it shows the changes being made info: Caching catalog for changes.for.me info: Applying configuration version '1316827173' --- /etc/ntp.conf 2011-09-21 05:27:43.000000000 +0000 +++ /tmp/puppet-file.8965.0 2011-09-23 06:08:12.000000000 +0000 @@ -43,7 +43,11 @@ # Specify the key identifier to use with the ntpq utility. #controlkey 8 +# Managed by Class['ntp'] -server 10.50.0.2 +server 10.50.0.1 info: FileBucket adding {md5}965a1ecdd47c86415ea2d0e52c632d99 info: /File[ntp.conf]: Filebucketed /etc/ntp.conf to puppet with sum 965a1ecdd47c86415ea2d0e52c632d99 notice: /File[ntp.conf]/content: content changed '{md5}965a1ecdd47c86415ea2d0e52c632d99' to '{md5}883cdb9b8c44718eaadf1d3cea6cff96' info: /File[ntp.conf]: Scheduling refresh of Service[ntpd] info: /File[ntp.conf]: Scheduling refresh of Service[ntpd] notice: /Stage[main]/Ntp/Service[ntpd]: Triggered 'refresh' from 2 events info: Creating state file /var/lib/puppet/state/state.yaml notice: Finished catalog run in 249.33 seconds </pre> In case you missed it, the same actions were taken by puppet client in steps 2 and 5, but it only outputs the changes to the terminal session in step 5. The catalog has not changed in between these steps. This is persistently repeatable on CentOS 5.6 using the EPEL 2.6.6 puppet RPMs. -- 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.
