Issue #1641 has been reported by luke.

----------------------------------------
Bug #1641: REST file recursion behaves differently on subsequent runs than on 
first run
http://projects.reductivelabs.com/issues/show/1641

Author: luke
Status: Accepted
Priority: Normal
Assigned to: luke
Category: fileserving
Target version: 0.25.0
Complexity: Medium
Affected version: 0.25.0
Keywords: 


This is a regression caused by the transition to REST fileserving.  It's a bit 
obscure to describe, so bear with me.

When file recursion happens, each of the recursively files should be managed no 
more than the top-level file -- that is, if you're managing the mode and only 
the mode of the top file, then only the mode should be managed on the lower 
files.  In addition, the properties you mention in the manifest should get 
preferentially merged with the properties of remote files (i.e., if you set the 
mode in the manifest, but not the owner, then the remote file's owner will be 
used but the manifest's mode will be used).

Previously, we tracked what was set in the manifest separately from what was 
set by remote files, but in the recent transition, that separate store was 
lost.  As a result, you get correct behaviour on the first run (mode comes from 
manifest, owner comes from remote file), but that information is cached in 
memory as though it all came from the manifest.  This means that on subsequent 
runs, even if the remote owner has changed, the cached value will take 
precedence.

The 'newchild' method needs to be extended to differentiate between property 
values that the resource was initialized with vs. those set through remote file 
comparison.


----------------------------------------
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to