On (14/02/17 18:52), Lukas Slebodnik wrote: >On (14/02/17 18:28), Alexander Bokovoy wrote: >>On ti, 14 helmi 2017, Nuno Higgs wrote: >>> Hello, >>> >>> 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 >> >Sorry you are wrong. >This is a different bug. >https://bugzilla.redhat.com/show_bug.cgi?id=1412717 >which is unfortunatelly private. > I thought a little bit and I am not sure which bug is this case. What do "sestatus" inside container?
LS -- Manage your subscription for the Freeipa-users mailing list: https://www.redhat.com/mailman/listinfo/freeipa-users Go to http://freeipa.org for more info on the project