Issue #6633 has been reported by Paul Berry.
----------------------------------------
Bug #6633: Mount provider unmounts and tries to remount unsuccessfully when
unnecessary
https://projects.puppetlabs.com/issues/6633
Author: Paul Berry
Status: Accepted
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version: development
Keywords:
Branch:
I observed this behavior on Mac OS X. I suspect a similar bug exists on other
OSes.
Steps to reproduce:
* Execute the following manifest to create the mount point and fstab entry, but
not actually do the mount:
file { '/Volumes/NIKON_D40X': ensure => directory }
mount { '/Volumes/NIKON_D40X': ensure => present, device =>
"/dev/disk1s1", fstype => msdos, options => ro, require =>
File['/Volumes/NIKON_D40X'] }
* Mount the device using:
mount /dev/disk1s1
* Manually edit `/etc/fstab` to remove the newly created entry.
* Run the following manifest using `--debug`:
mount { '/Volumes/NIKON_D40X': ensure => mounted, device =>
"/dev/disk1s1", fstype => msdos, options => ro, require =>
File['/Volumes/NIKON_D40X'] }
* Expected behavior: Puppet rebuilds the missing fstab entry, but does not
mount or unmount the device (since it is already mounted, as desired).
* Observed behavior: Puppet rebuilds the missing fstab entry, then unmounts the
device using `umount`, then attempts to remount the device using `mount`, which
fails because the directory `/Volumes/NIKON_D40X` is now missing.
--
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.
