https://bugzilla.suse.com/show_bug.cgi?id=1231510 https://bugzilla.suse.com/show_bug.cgi?id=1231510#c4 Cathy Hu <cathy.hu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[Build 20241008-SELinux] |[Build 20241008-SELinux] |openQA test fails in |yast2-nfs-client: openQA |yast2_nfs_client: can not |test fails in |start rpcbind service |yast2_nfs_client: can not | |start rpcbind service Assignee|cathy.hu@suse.com |mvidner@suse.com CC| |cathy.hu@suse.com --- Comment #4 from Cathy Hu <cathy.hu@suse.com> --- Hi Martin, I assigned this bug to you because you are the maintainer for yast2-nfs-client. Please let me know if you are the wrong person to ask :) I was wondering if we could also clean up the /run/rpcbind.lock file with the incorrect selinux label after the "killall rpcbind" here: https://github.com/yast/yast-nfs-client/blob/master/src/modules/Nfs.rb#L681 for example, I tested this on my local machine and that fixes the issue: Yast::Execute.locally.stdout("rm", "/run/rpcbind.lock") This way the lock file will be recreated by the rpcbind systemd service in the call afterwards and has the correct label. What do you think? -- You are receiving this mail because: You are on the CC list for the bug.