Issue #6632 has been updated by Paul Berry. Status changed from Unreviewed to Accepted Affected Puppet version set to development
---------------------------------------- Bug #6632: Adding a new mount causes error with umount https://projects.puppetlabs.com/issues/6632 Author: Paul Berry Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: development Keywords: Branch: This behavior was observed on Mac OS X. I suspect it exists on other OSes. These repro steps are based on mounting a device `/dev/disk1s1` at a mount point called `/Volumes/NIKON_D40X`. It should be easy to adapt to other devices: * Ensure that `/dev/disk1s1` is not mounted, and is not mentioned in `/etc/fstab`. * Run the following manifest: file { '/Volumes/NIKON_D40X': ensure => directory } mount { '/Volumes/NIKON_D40X': ensure => mounted, device => "/dev/disk1s1", fstype => msdos, options => ro, require => File['/Volumes/NIKON_D40X'] } * Expected result: fstab entry created and device mounted. Observed result: fstab entry created, but Puppet generates this error: err: /Stage[main]//Mount[/Volumes/NIKON_D40X]: Failed to call refresh: Execution of '/sbin/umount /Volumes/NIKON_D40X' returned 1: umount: /Volumes/NIKON_D40X: not currently mounted -- 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.
