Foreman » SELinux

From downstream:

vrempet@li-lc-1017 ~
$ grep -c /etc/selinux/targeted/contexts/files/file_contexts /var/log/messages
512

vrempet@li-lc-1017 ~
$ grep /etc/selinux/targeted/contexts/files/file_contexts /var/log/messages | tail -n 5
Oct 5 12:45:11 li-lc-1017 puppet-master⁹⁰²⁶: /etc/selinux/targeted/contexts/files/file_contexts: invalid context system_u:object_r:puppet_etc_t:s0
Oct 5 12:45:38 li-lc-1017 puppet-master⁹⁰⁴⁶: /etc/selinux/targeted/contexts/files/file_contexts: invalid context system_u:object_r:puppet_etc_t:s0
Oct 5 12:45:38 li-lc-1017 puppet-master⁹⁰⁴⁶: /etc/selinux/targeted/contexts/files/file_contexts: invalid context system_u:object_r:puppet_etc_t:s0
Oct 5 12:45:38 li-lc-1017 puppet-master⁹⁰⁴⁶: /etc/selinux/targeted/contexts/files/file_contexts: invalid context system_u:object_r:puppet_etc_t:s0
Oct 5 12:45:38 li-lc-1017 puppet-master⁹⁰⁴⁶: /etc/selinux/targeted/contexts/files/file_contexts: invalid context system_u:object_r:puppet_etc_t:s0

vrempet@li-lc-1017 ~
$ uptime
12:55:58 up 13 min, 1 user, load average: 0.01, 0.51, 0.65

Does the execution of node.rb outside of the puppet-master process work or fail? If it fails, please provide the Foreman logs.

Are there any AVC denials? I'm unsure that those log messages are relevant or show anything relating to the issue description.

The logs don't appear to come from the same host, are these definitely demonstrating the same underlying bug?

We have been able to track the issue down with help of SELinux team. It's a long story, I will provide patch soon. For more details see:

https://bugzilla.redhat.com/show_bug.cgi?id=1202924

Applied in changeset 31ebc8e73a03dfc32aed8a9c6929404b00fa4f50.