Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Comment 4Jan Pazdziora (Red Hat)
2017-05-16 11:01:36 UTC
Why is it failing now and was not failing in the past?
Are we able to minimize the reproducer, just running gssproxy in the container, or something similar?
Just added rules to container-selinux to allow container processes to set namespaced rpc and network sysctls.
commit 173862acc546c5e4e3c501f40611c02e016ad0e9
Author: Dan Walsh <dwalsh>
Date: Tue May 16 08:45:49 2017 -0400
Allow containers to be able to set namespaced SYCTLS
Currently containers have some namespaced sysctls, which the kernel has determined
to be safe for containers to use, this stops blocking these from an SELinux point
of view.
Also added missing container_runtime_t userns capabilities, so that policy will
compile on systems with expand-check=1
Signed-off-by: Dan Walsh <dwalsh>
Just added rules to container-selinux to allow container processes to set namespaced rpc and network sysctls.
commit 173862acc546c5e4e3c501f40611c02e016ad0e9
Author: Dan Walsh <dwalsh>
Date: Tue May 16 08:45:49 2017 -0400
Allow containers to be able to set namespaced SYCTLS
Currently containers have some namespaced sysctls, which the kernel has determined
to be safe for containers to use, this stops blocking these from an SELinux point
of view.
Also added missing container_runtime_t userns capabilities, so that policy will
compile on systems with expand-check=1
Signed-off-by: Dan Walsh <dwalsh>
It is failing now because beginning with FreeIPA 4.5 we leverage GSSProxy for IPA framework authentication and it took quite a lot of time for ipa-server RHEL 7.4 image to become Beaker test-ready.
It should be possible to prepare a minimal reproducer just from RHEL 7.4 base image running GSS-Proxy but I did not have time to prepare one.
This should be fine in
container-selinux-2.15-1.git583ca40.el7.noarch
docker-1.12.6-31.git3a6eaeb.el7.x86_64
# sesearch -T -s container_runtime_t -c process | grep spc_t
type_transition container_runtime_t container_share_t : process spc_t;
type_transition container_runtime_t svirt_sandbox_file_t : process spc_t;
type_transition container_runtime_t unlabeled_t : process spc_t;
type_transition container_runtime_t container_var_lib_t : process spc_t;
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:1626