Description of problem: Updating nfs-ganesha using puddles gives error "Boolean rpcd_use_fusefs is not defined" Version-Release number of selected component (if applicable): nfs-ganesha-2.3.1-6 How reproducible: Always Steps to Reproduce: Try updating to the latest nfs-ganesha-2.3.1-6 rpm's using latest puddles provided and while upgrade following error is observed "ValueError: Boolean rpcd_use_fusefs is not defined", however nfs-ganesha gets updated without any issues (see as below): ------------------------------------------------------------------------------------ [root@dhcp37-44 yum.repos.d]# yum update nfs-ganesha* . . . Dependencies Resolved =================================================================================== Package Arch Version Repository Size =================================================================================== Updating: nfs-ganesha x86_64 2.3.1-6.el7rhgs External-Server-RH-Gluster-3-NFS-Repository-2 548 k nfs-ganesha-gluster x86_64 2.3.1-6.el7rhgs External-Server-RH-Gluster-3-NFS-Repository-2 34 k Installing for dependencies: libntirpc x86_64 1.3.1-1.el7rhgs External-Server-RH-Gluster-3-NFS-Repository-2 119 k Updating for dependencies: selinux-policy noarch 3.13.1-60.el7_2.4 External-Server-RH-Gluster-3-NFS-Repository-2 375 k selinux-policy-targeted noarch 3.13.1-60.el7_2.4 External-Server-RH-Gluster-3-NFS-Repository-2 3.9 M . . . Running transaction Updating :y-3.13.1-60. selinux-policel7_2.4.noarch 1/9 Installing : libntirpc-1.3.1-1.el7rhgs.x86_64 2/9 Updating : nfs-ganesha-2.3.1-6.el7rhgs.x86_64 3/9 ValueError: Boolean rpcd_use_fusefs is not defined success Updating : nfs-ganesha-gluster-2.3.1-6.el7rhgs.x86_64 4/9 Updating : selinux-policy-targeted-3.13.1-60.el7_2.4.noarch 5/9 Cleanup : selinux-policy-targeted-3.13.1-60.el7_2.3.noarch 6/9 Cleanup : nfs-ganesha-gluster-2.2.0-12.el7rhgs.x86_64 7/9 Cleanup : selinux-policy-3.13.1-60.el7_2.3.noarch 8/9 Cleanup : nfs-ganesha-2.2.0-12.el7rhgs.x86_64 9/9 Verifying : selinux-policy-targeted-3.13.1-60.el7_2.4.noarch 1/9 Verifying : libntirpc-1.3.1-1.el7rhgs.x86_64 2/9 Verifying : selinux-policy-3.13.1-60.el7_2.4.noarch 3/9 Verifying : nfs-ganesha-gluster-2.3.1-6.el7rhgs.x86_64 4/9 Verifying : nfs-ganesha-2.3.1-6.el7rhgs.x86_64 5/9 Verifying : nfs-ganesha-2.2.0-12.el7rhgs.x86_64 6/9 Verifying : selinux-policy-targeted-3.13.1-60.el7_2.3.noarch 7/9 Verifying : selinux-policy-3.13.1-60.el7_2.3.noarch 8/9 Verifying : nfs-ganesha-gluster-2.2.0-12.el7rhgs.x86_64 9/9 Dependency Installed: libntirpc.x86_64 0:1.3.1-1.el7rhgs Updated: nfs-ganesha.x86_64 0:2.3.1-6.el7rhgs nfs-ganesha-gluster.x86_64 0:2.3.1-6.el7rhgs Dependency Updated: selinux-policy.noarch 0:3.13.1-60.el7_2.4 selinux-policy-targeted.noarch 0:3.13.1-60.el7_2.4 Complete! [root@dhcp37-44 yum.repos.d]# ------------------------------------------------------------------------------------ and after setting up ganesha on the cluster and trying to restart nfs-ganesha-lock fails with below messages [root@dhcp37-44 ~]# service nfs-ganesha-lock status -l Redirecting to /bin/systemctl status -l nfs-ganesha-lock.service ● nfs-ganesha-lock.service - NFS status monitor for NFSv2/3 locking. Loaded: loaded (/usr/lib/systemd/system/nfs-ganesha-lock.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2016-05-16 03:57:59 IST; 9min ago Process: 7512 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=1/FAILURE) May 16 03:57:59 dhcp37-44.lab.eng.blr.redhat.com systemd[1]: Starting NFS status monitor for NFSv2/3 locking.... May 16 03:57:59 dhcp37-44.lab.eng.blr.redhat.com rpc.statd[7513]: Version 1.3.0 starting May 16 03:57:59 dhcp37-44.lab.eng.blr.redhat.com rpc.statd[7513]: Flags: TI-RPC May 16 03:57:59 dhcp37-44.lab.eng.blr.redhat.com rpc.statd[7513]: Failed to open directory sm: Permission denied May 16 03:57:59 dhcp37-44.lab.eng.blr.redhat.com rpc.statd[7513]: Failed to open /var/lib/nfs/statd/state: Permission denied May 16 03:57:59 dhcp37-44.lab.eng.blr.redhat.com systemd[1]: nfs-ganesha-lock.service: control process exited, code=exited status=1 May 16 03:57:59 dhcp37-44.lab.eng.blr.redhat.com systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking.. May 16 03:57:59 dhcp37-44.lab.eng.blr.redhat.com systemd[1]: Unit nfs-ganesha-lock.service entered failed state. May 16 03:57:59 dhcp37-44.lab.eng.blr.redhat.com systemd[1]: nfs-ganesha-lock.service failed. and following AVC's are seen in audit.log type=AVC msg=audit(1463351279.650:3838): avc: denied { read } for pid=7513 comm="rpc.statd" name="state" dev="fuse" ino=10644141316059799961 scontext=system_u:system_r:rpcd_t:s0 tcontext=system_u:object_r:fusefs_t:s0 tclass=file type=AVC msg=audit(1463351279.642:3837): avc: denied { read } for pid=7513 comm="rpc.statd" name="sm" dev="fuse" ino=10192728428274752403 scontext=system_u:system_r:rpcd_t:s0 tcontext=system_u:object_r:fusefs_t:s0 tclass=dir ******************************************************************************************************************** Try updating another system with selinux-policy updated before nfs-ganesha and it works fine (See below): Total size: 1.6 M Is this ok [y/d/N]: y Downloading packages: Running transaction check Running transaction test Transaction test succeeded Running transaction Updating : nfs-ganesha-2.3.1-6.el7rhgs.x86_64 1/4 success Updating : nfs-ganesha-gluster-2.3.1-6.el7rhgs.x86_64 2/4 Cleanup : nfs-ganesha-gluster-2.2.0-12.el7rhgs.x86_64 3/4 Cleanup : nfs-ganesha-2.2.0-12.el7rhgs.x86_64 4/4 Verifying : nfs-ganesha-gluster-2.3.1-6.el7rhgs.x86_64 1/4 Verifying : nfs-ganesha-2.3.1-6.el7rhgs.x86_64 2/4 Verifying : nfs-ganesha-2.2.0-12.el7rhgs.x86_64 3/4 Verifying : nfs-ganesha-gluster-2.2.0-12.el7rhgs.x86_64 *********************************************************************************************************************** So this seems to be an issue where if nfs-ganesha gets updated before selinux-policy-targeted, it cannot set this particular boolean value. We need to confirm that selinux-policy-targeted is indeed required before we try to upgrade nfs-ganesha? and if that is the case, we need to mark it also as a dependent package for nfs-ganesha Actual results: Updating nfs-ganesha using puddles gives error "Boolean rpcd_use_fusefs is not defined" Expected results: There should not be any failures while updating nfs-ganesha Additional info:
We didn't see this error when we installed selinux-policy and the matching dependency selinux-policy-targeted by hand, before installing rhgs. We appear to need a Requires: selinux-policy-targeted >= 3.13.1-60.el7_2.4 to match the current Requires: selinux-policy >= 3.13.1-60.el7_2.4 To ensure that selinux-policy-targeted is installed before nfs-ganesha. One, or the other, or both?
Looks like just have a single Requires: selinux-policy-targeted >= 3.13.1-60.el7_2.4 line will suffice.
Yes, selinux-policy-targeted must be updated before nfs-ganesha package.
Verified this bug with the latest generated puddles and during nfs-ganesha update, its fetching the required dependent selinux packages: [root@dhcp46-247 yum.repos.d]# yum update nfs-ganesha* . . . Dependencies Resolved =================================================================================== Package Arch Version Repository Size =================================================================================== Updating: nfs-ganesha x86_64 2.3.1-7.el7rhgs External-Server-RH-Gluster-3-NFS-Repository-2 548 k nfs-ganesha-gluster x86_64 2.3.1-7.el7rhgs External-Server-RH-Gluster-3-NFS-Repository-2 35 k Updating for dependencies: selinux-policy noarch 3.13.1-60.el7_2.4 External-Server-RH-Gluster-3-NFS-Repository-2 375 k selinux-policy-targeted noarch 3.13.1-60.el7_2.4 External-Server-RH-Gluster-3-NFS-Repository-2 3.9 M The update is successful and didn't observe the earlier "boolean is not defined" issue. Running transaction Updating : selinux-policy-3.13.1-60.el7_2.4.noarch 1/8 Updating : selinux-policy-targeted-3.13.1-60.el7_2.4.noarch 2/8 Updating : nfs-ganesha-2.3.1-7.el7rhgs.x86_64 3/8 success Updating : nfs-ganesha-gluster-2.3.1-7.el7rhgs.x86_64 4/8 Cleanup : selinux-policy-targeted-3.13.1-60.el7_2.3.noarch 5/8 Cleanup : nfs-ganesha-gluster-2.3.1-4.el7rhgs.x86_64 6/8 Cleanup : selinux-policy-3.13.1-60.el7_2.3.noarch 7/8 Cleanup : nfs-ganesha-2.3.1-4.el7rhgs.x86_64 8/8 success Verifying : nfs-ganesha-gluster-2.3.1-7.el7rhgs.x86_64 1/8 Verifying : selinux-policy-targeted-3.13.1-60.el7_2.4.noarch 2/8 Verifying : selinux-policy-3.13.1-60.el7_2.4.noarch 3/8 Verifying : nfs-ganesha-2.3.1-7.el7rhgs.x86_64 4/8 Verifying : nfs-ganesha-gluster-2.3.1-4.el7rhgs.x86_64 5/8 Verifying : selinux-policy-3.13.1-60.el7_2.3.noarch 6/8 Verifying : selinux-policy-targeted-3.13.1-60.el7_2.3.noarch 7/8 Verifying : nfs-ganesha-2.3.1-4.el7rhgs.x86_64 8/8 Updated: nfs-ganesha.x86_64 0:2.3.1-7.el7rhgs nfs-ganesha-gluster.x86_64 0:2.3.1-7.el7rhgs Dependency Updated: selinux-policy.noarch 0:3.13.1-60.el7_2.4 selinux-policy-targeted.noarch 0:3.13.1-60.el7_2.4 Complete! Based on the above observation, marking this bug as Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2016:1247