I made an adjustment to my puppet config for three systems today, which has the "remount" option set to true in the *.pp, and I see this in the logs on my systems: Execution of ''/bin/mount -o remount /home/directory'' returned 32: mount.nfs: Invalid argument "remount" is valid to the "mount" command, but not to the "mount.nfs" command on RHEL. I''m not really sure if this is important or how to get around this -- or if this is a bug. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
jcbollinger
2011-Aug-10 15:24 UTC
[Puppet Users] Re: RHEL 5.x "remount" an invalid option to NFS?
On Aug 9, 3:18 pm, Forrie <for...@gmail.com> wrote:> I made an adjustment to my puppet config for three systems today, > which has the "remount" option set to true in the *.pp, and I see this > in the logs on my systems: > > Execution of ''/bin/mount -o remount /home/directory'' returned 32: > mount.nfs: Invalid argument > > "remount" is valid to the "mount" command, but not to the "mount.nfs" > command on RHEL. > > I''m not really sure if this is important or how to get around this -- > or if this is a bug.The ''remount'' option is valid for all filesystem types. mount.nfs is complaining about the mount point argument -- this happens when an attempt is made to remount a file system that is listed in /etc/fstab but is not already mounted. I''d account it a Puppet bug. It appears related to http://projects.puppetlabs.com/issues/6027 and http://projects.puppetlabs.com/issues/6309, yet distinct from them. I suggest you file a ticket. Unless you''re interested in creating a local version of Puppet, the only general workaround I can see is to set remounts => false on your Mount resource. There may be something special about your manifests that triggers this bug, however, in which case there may be other workarounds available. If you do plan to file a ticket, then the requisite process of narrowing down the failure case should reveal any such special circumstances that may be contributing. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.