Issue #6645 has been updated by Paul Berry. Status changed from Accepted to Needs Decision Assignee set to Nigel Kersten
I was initially planning to perform extra tests to verify that this bug is real, but after reviewing the spec tests that led to its discovery, I don't think there is any need. We need to decide what the desired behavior of the mount provider is in this circumstance, and whether to target the fix for 2.6 or Statler. ---------------------------------------- Bug #6645: Suspected bug in mount provider when using ensure => present and mount point already mounted https://projects.puppetlabs.com/issues/6645 Author: Paul Berry Status: Needs Decision Priority: Normal Assignee: Nigel Kersten Category: Target version: Affected Puppet version: development Keywords: Branch: This is a placeholder for a bug that I'm fairly certain exists. I will replace this description with repro steps once I've confirmed it. When ensure => (defined or present), and there is not an fstab entry for the resource, but the mount point is mounted, and you change a mount option: The option change takes effect in /etc/fstab, but does not take effect on the already-mounted device. However, when the same conditions hold but there _is_ an fstab entry for the resource, the option change takes effect both in /etc/fstab and on the already-mounted device. I'm not sure which behavior is desired, but this seems really inconsistent. -- 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.
