M
> *To: *"Tancheff, Shaun" , "
> daniel.rodw...@anu.edu.au"
> *Cc: *"lustre-discuss@lists.lustre.org"
> *Subject: *Re: [lustre-discuss] Upgraded Lustre client now has SElinux
> failure
>
>
>
> Thanks, Shaun and Daniel for the heads up.
>
&g
> *Date: *Tuesday, August 4, 2020 at 1:02 PM
> *To: *"lustre-discuss@lists.lustre.org"
> *Subject: *[lustre-discuss] Upgraded Lustre client now has SElinux failure
> *Resent-From: *
> *Resent-Date: *Tuesday, August 4, 2020 at 1:02 PM
>
>
>
> Hi, I just upda
Hi Kevin
We've hit the same issue, and reported it up to Whamcloud support. It's being
actively worked on.
The public LU and patch is being tracked on LU-13742
(https://jira.whamcloud.com/browse/LU-13742).
Initially we bypassed the issue by setting SELinux to explicitly disabled to
get the cl
Hi, I just updated a RedHat machine from RHEL8.1 to RHEL8.2, and Lustre
from 2.12.4 to 2.12.5. I've built the lustre client from source, using
Mellanox OFED 5.0-2.1.8.0.
After the update, I can no longer mount my Lustre filesystem- I'm getting
the following error:
# mount /lustre
[ 1482.866631]
