Issue #5015 has been updated by Stefan Schulte.
Hi Nigel, I sent a patch to the dev list including a test. I'm still new to git, the development cycle and puppet internals so please let me know if anything is missing or could have be done better. I also updated my gitrepo: https://github.com/stschulte/puppet/tree/feature/master/5015 https://github.com/stschulte/puppet/commit/d110ce62c578129513b40b6f693a61d318b4df01 ---------------------------------------- Feature #5015: mount should autorequire mountpoint https://projects.puppetlabs.com/issues/5015 Author: Stefan Schulte Status: Investigating Priority: Normal Assignee: Nigel Kersten Category: mount Target version: Affected Puppet version: Keywords: Branch: If we define a mount resource and the mountpoint as a file resource, puppet doesnt make sure that the mountpoint exists before actually mounting file {'/mnt/test': ensure => directory} mount {'/mnt/test': ensure => mounted } You have to explicitly set mount {'/mnt/test': require => File['/mnt/test'], ensure => mounted } I would like to have puppet generate an autorequire. But beware that if you try to fill a mountpoint like mount { '/mnt/test': ensure => mounted # we assume this always works (so /mnt/test has to be present) } file { '/mnt/test': source => ... recurse => true } you will have to set an explicit require in file resource to overwrite this new autorequire (because you will not see your data when puppet mounts after copying the whole directory). -- 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.
