I don't think we've seen this reported before. SELinux gets a hefty workout from Red Hat with their downstream ODF for OpenShift (Kubernetes), so it certainly works at a basic level. SELinux is a fussy beast though, so if you're eg mounting CephFS across RHEL nodes and invoking SELinux against it, any differences between those nodes (like differing UIDs, or probably lots of other bits) could result in it looking wrong to them. I'm not even close to an expert but IIUC, people generally turn off SELinux for their shared/distributed data. -Greg On Wed, Aug 2, 2023 at 5:53 AM Harry G Coin <hgcoin@gmail.com> wrote:

Hi! No matter what I try, using the latest cephfs on an all ceph-pacific setup, I've not been able to avoid this error message, always similar to this on RHEL family clients:

SELinux: inode=1099954719159 on dev=ceph was found to have an invalid context=system_u:object_r:unlabeled_t:s0. This indicates you may need to relabel the inode or the filesystem in question.

What's the answer?

Thanks

Harry Coin

_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io