Issue #1534 has been updated by adam.
Jay's super terse bug report belies what could be a fairly serious thing. In talking with him about the behavior he's seeing on IRC, it sounds suspiciously like the sort of resource 'corruption' we were seeing with #1010. From the manifest and the attached YAML, it's hard to see how Puppet would ever decide that it should be recursively filebucketing that NFS mount - the resource itself only mentions the directory, no source lines, etc. I'm around on IRC most of the time, if anyone wants to talk a bit more about what this... although without an easily reproducable test case (or a system that can trigger the issue, as Fujin's did reliable back in the day) it may be difficul to track to the specific source. ---------------------------------------- Bug #1534: puppet clientbucketing when no config change has occured http://reductivelabs.com/redmine/issues/show/1534 Author: jay Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Complexity: Unknown Affected version: 0.24.4 Keywords: Once and a while we have a few nodes that decide to bucket an nfs share. This past weekend we had 4 nodes do this, out of 20 that have this configuration. ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
