Issue #3648 has been updated by Daniel Pittman.

Target version changed from 2.7.x to 2.7.12


----------------------------------------
Bug #3648: autorequire failure with subdirectory inside recursive file resource
https://projects.puppetlabs.com/issues/3648#change-57166

Author: Alan Barrett
Status: Closed
Priority: Normal
Assignee: 
Category: file
Target version: 2.7.12
Affected Puppet version: 0.25.4
Keywords: 
Branch: 


If you have a file resource that recursively creates a directory hierarchy, and 
another file resource that stores a file somewhere in that directory hierarchy, 
then the two resources may be evaluated in the wrong order.  The autorequire 
handling, which usually causes a file to require its parent directory, doesn't 
work in this case.

<pre>
class myclass {
    file { "/topdir/subdir/filename":
        ensure => file,
        content => "testing",
        # autorequires File["/topdir/subdir"], but doesn't notice
        # that /topdir/subdir is actually created by recursion in
        # the File["/topdir"] resource.
    }
    file { "/topdir":
        ensure => directory,
        recurse => inf,
        source => "puppet:///myclass/topdir",
        # assuming <modulepath>/myclass/files/topdir exists
        # on the puppetmaster, and assuming it contains
        # the "subdir" subdirectory, this resource
        # will create "/topdir/subdir" on the client,
        # but this sometimes happens too late for files
        # that should live in that subdirectory.
    }
}
</pre>


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

Reply via email to