On ti, 14 helmi 2017, Nuno Higgs wrote:
It worked perfecty.
I am wondering why this just popped up now with this patch update. Almost
none of our containers hosts (and by inherence the containers) have SELINUX
enabled for they are primary for testing, and they are on a secure network.
With this version of ipa-client, the host has to have SE enabled for the
container to inherit the definitions and policies of it?
As I said, this was an update in SELinux-related libraries and change of
behavior there, not in SSSD. It is reproducible in other environments as
well, see, f.e. https://bugzilla.redhat.com/show_bug.cgi?id=1415167
The workaround is to disable selinux provider in the environment where
SELinux is not used until SELinux libraries are fixed.
/ Alexander Bokovoy
Manage your subscription for the Freeipa-users mailing list:
Go to http://freeipa.org for more info on the project