On Sat, Feb 25, 2012 at 2:06 AM, jcbollinger <john.bollin...@stjude.org>wrote:
> > I have not noticed this behavior, but you're a little vague. Yes, I guess I wasn't sure what I could provide in terms of detail so your questions help! When you say that the Mount resources are not applied, what exactly does > that > mean? Is /etc/fstab not modified? Is fstab modified but the filesystem is > not mounted? /etc/fstab is not modified at all. I rebooted the server and made it rebuild again and this time Puppet ran fine and all the mounts were applied correctly. > Either way, does the mount point exist (and is it a directory) before the > Mount is applied? What shows up in > the client log? Can you provide a simple manifest that exhibits the > behavior you describe (even if only intermitently)? > I have a define that creates the directory and then mounts it. Nothing in the client log indicating an error with the mounts. Unfortunately I don't have a simple manifest that shows this behaviour. I was hoping someone would say "oh yeah, seen that happen" based on my description, as it's not something I can easily show in a manifest. It happens occasionally too making the troubleshooting effort even harder. If I run Puppet again right after the first run, it gets all the mounts done correctly. Most of the time the first run is enough to get the entire catalog applied including mounts. - Gonzalo -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
