Issue #1760 has been reported by wyvern.
----------------------------------------
Bug #1760: inconsistent reporting if client file is changed
http://projects.reductivelabs.com/issues/show/1760
Author: wyvern
Status: Unreviewed
Priority: Low
Assigned to:
Category:
Target version:
Complexity: Unknown
Affected version: 0.24.5
Keywords:
A bit of background:
- we have /etc/network/interfaces under puppet control (just as a template)
with a notify action to restart networking
However, sometimes we do this _manually_ (by running the appropriate changes
manually but still updating the template).
If I run puppetd --test --noop it returns:
<pre>
notice:
//Node[stickle.example.com]/basenode/network::network/File[/etc/network/interfaces]/checksum:
is {md5}67f14aec4e52b6a49ebecd8c167f88ff, should be md5 (noop)
info:
//Node[stickle.example.com]/basenode/network::network/File[/etc/network/interfaces]:
Scheduling refresh of Service[networking]
notice:
//Node[stickle.example.com]/basenode/network::network/Service[networking]:
Would have triggered refresh from 1 dependencies
</pre>
I have to edit /var/lib/puppet/state/state.yaml and update the md5 sum there
before puppet believes that the file is in sync.
puppet seems to compare template with stored md5 sum and say "it's different,
I'll need to change this". However if I _just_ edit the file on disk, puppet
(quite correctly) detects this change.
i.e. since puppet _always_ has to check the real md5sum of the destination
file, why bother storing it at all and comparing against that version?
To be honest, I can see that it would be handy if puppet reported "file changed
outside puppet control" (i.e. when the md5sum on disk changes) so storing it is
a good idea.
----------------------------------------
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://reductivelabs.com/redmine/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
-~----------~----~----~----~------~----~------~--~---
