Hi yes, on the resource-agents side the commit is sufficient. Steps to repoduce:
install ubuntu 22.04 with pacemaker, corosync, nfs-kernel-server and resource-agents. configure a ocf:heartbeat:nfsserver resource _with_ nfs_shared_infodir parameter. start an the try to stop the resource. after a successful stop you will still se a mounted /var/lib/nfs. if your nfs_shared_infodir path is on a mounted resource itself, this resource cannot be stopped, since it is still mounted. for testing purpose its sufficient to check is the mount still is there. you most likely see a pacemaker-execd[]: notice: nfs_daemon_stop_0[65992] error output [ umount: /var/lib/nfs: target is busy. ] line in the log although the resource is considered stopped without error. Kind regards Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
