Jira (PUP-9601) mount resource should trigger 'systemctl daemon-reload'

[Gheorghe Popescu (JIRA)]

Title: Message Title

Gheorghe Popescu commented on PUP-9601   Re: mount resource should trigger 'systemctl daemon-reload' Hi Adam Winberg After looking more in-depth into this issue i believe this can be solved using a notify to 'systemctl daemon-reload' and the service created by systemd. For example: $mount_name="test"   mount {"/mnt/${mount_name}": ensure => 'present', device => "fs_server:/opt/${mount_name}", fstype => 'nfs', options => 'noauto,x-systemd.automount,x-systemd.device-timeout=10,x-systemd.mount-timeout=30,x-systemd.idle-timeout=60,_netdev', notify => [Exec['systemctl daemon-reload'], Service["mnt-${mount_name}.mount"]] }   exec {'systemctl daemon-reload': refreshonly => true, path => ['/usr/bin', '/usr/sbin',] }   service { "mnt-${mount_name}.mount": ensure => running, } In your example you are adding "noauto". With this option, the mount unit will not be added as a dependency for local-fs.target or remote-fs.target, so a refresh to this services is not needed. The intent of "present" in the puppet mount resource is to add the information to fstab but not change mount/unmount status - this should not throw any mount errors. In your case the actual mount process is handled by systemd. Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302969.1554289295000.28997.1557415860223%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.