Issue #1669 has been reported by ohookins.
----------------------------------------
Bug #1669: Mount parameter "dump" doesn't work
http://projects.reductivelabs.com/issues/show/1669
Author: ohookins
Status: Unreviewed
Priority: Normal
Assigned to:
Category: mount
Target version:
Complexity: Unknown
Affected version: 0.24.5
Keywords:
I can set "dump => 0" or leave it unset altogether to use the default value
(which is also 0), but Puppet seems to not actually make the change.
A manifest fragment:
<pre>
mount { "/tmp":
device => tmpfs,
fstype => tmpfs,
options => "defaults,size=${tmpfs_size},nosuid,nodev",
target => "/etc/fstab";
}
</pre>
The current line in /etc/fstab:
<pre>
tmpfs /tmp tmpfs defaults,size=500m,nosuid,nodev 1 0
</pre>
During the puppetd run (with debugging and verbose) it prints the following:
<pre>
notice: //Node[gage]/managed/fstab/Mount[/tmp]/dump: dump changed '1' to '0'
notice: //Node[gage]/managed/fstab/Mount[/tmp]: Refreshing self
</pre>
Yet the contents of that line are unchanged. Judging by the file's modification
timestamp, it doesn't look like Puppet has done anything to the file.
----------------------------------------
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://reductivelabs.com/redmine/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
-~----------~----~----~----~------~----~------~--~---
