1:06 p.m.
OK, I finally found the time to revisit this issue. Indeed, it appears the SELinux policy
was not sufficient to allow access to the filesystem. I have posted the relevant output on
the github. Here is it, in case someone else is having similar issues:
module ganesha-extra 1.0;
require {
type ipmi_device_t;
type user_home_dir_t;
type unlabeled_t;
type ganesha_t;
type fuse_device_t;
type efivarfs_t;
type dosfs_t;
type var_t;
type tracefs_t;
type device_t;
type home_root_t;
class dir { getattr read };
class file getattr;
class blk_file getattr;
class chr_file getattr;
class filesystem getattr;
}
#============= ganesha_t ==============
allow ganesha_t device_t:blk_file getattr;
allow ganesha_t dosfs_t:dir getattr;
allow ganesha_t dosfs_t:filesystem getattr;
allow ganesha_t efivarfs_t:dir getattr;
allow ganesha_t efivarfs_t:filesystem getattr;
allow ganesha_t fuse_device_t:chr_file getattr;
allow ganesha_t home_root_t:dir read;
allow ganesha_t ipmi_device_t:chr_file getattr;
allow ganesha_t tracefs_t:dir getattr;
allow ganesha_t tracefs_t:filesystem getattr;
allow ganesha_t unlabeled_t:dir getattr;
allow ganesha_t unlabeled_t:file getattr;
allow ganesha_t user_home_dir_t:dir getattr;
allow ganesha_t var_t:dir read;