I want to check in and see if this is a known issue before I open a bug. I'm
seeing a particular issue where after a manifest change, the first run with the
newly compiled catalog will not report the changes made to the system.
For example,
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
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.
Does anyone know if this problem has already been fixed or not, or should I
report it as a new bug?
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source and other
randomness
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
