Jira (PUP-1828) mount fails, still configures dependant resources
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1828 mount fails, still configures dependant resources Change By: Moses Mendoza Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1828) mount fails, still configures dependant resources
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1828 mount fails, still configures dependant resources Change By: Nicholas Fagerlund Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1828) mount fails, still configures dependant resources
Title: Message Title Steven Post created an issue Puppet / PUP-1828 mount fails, still configures dependant resources Issue Type: Bug Affects Versions: 3.4.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 03/Mar/14 8:15 AM Environment: RedHat enterprise Linux 6.4 Priority: Normal Reporter: Steven Post Hi, We have several NAS mounts but also a restrictive firewall between the NFS client and server (no rejects, but drops). We use the 'bg' option on our NAS mounts not to let booting hang, this in turn causes mount to return code 0 when backgrounding. Puppet then does a remount to check, but since the volume isn't mounted, mount now returns code 32. Puppet however, happily considers the resource configured successfully, also configuring depending resources. The puppet agent return code in this case is 6, indicating a failure did happen. puppet agent --server puppet.ourdomain.net --test Info: Retrieving plugin ... Info: Caching catalog for hostname
