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.
DescriptionJaroslav Henner
2017-02-09 15:16:26 UTC
Description of problem:
The deployments of router on opensift-3.4 started failing. I found this in
# oc describe pods router-1-deploy
...
1m 1m 1 {kubelet ose3-master-828ml.828ml...} Warning FailedSync Error syncing pod, skipping: failed to "SetupNetwork" for "router-1-deploy_default" with SetupNetworkError: "Failed to setup network for pod \"router-1-deploy_default(7e333bd8-eecb-11e6-802a-fa163eb77bb0)\" using network plugins \"cni\": failed to Statfs \"/proc/49939/ns/net\": no such file or directory; Skipping pod"
It smelled like a selinux issue and it seems it is.
# sudo setenforce 0
Fixed it:
3s 3s 1 {kubelet ose3-master-828ml.828ml...} spec.containers{deployment} Normal Created Created container with docker id 626b82664835; Security:[seccomp=unconfined]
3s 3s 1 {kubelet ose3-master-828ml.828ml.cmqe...} spec.containers{deployment} Normal Started Started container with docker id 626b82664835
Version-Release number of selected component (if applicable):
atomic-openshift-sdn-ovs-3.4.0.40-1.git.0.787e974.el7.x86_64
docker-1.12.6-2.el7.x86_64
selinux-policy-targeted-3.13.1-60.el7.noarch
container-selinux-2.7-1.el7.noarch
How reproducible:
Always
Steps to Reproduce:
1. Try deploying openshift with openshift-ansible
2. It will fail, so does manual issuing the command to create router
# oadm router jhenner-router --replicas=1 --service-account=router
[root@ose3-master-th4j5 cloud-user]# sudo audit2allow -a
#============= svirt_lxc_net_t ==============
allow svirt_lxc_net_t unconfined_service_t:process sigchld;
#============= unconfined_service_t ==============
allow unconfined_service_t svirt_lxc_net_t:process transition;
these rules seem to help.
Actual results:
router (and registry) pod failing to spawn.
type=AVC msg=audit(1486651160.007:6487): avc: denied { transition } for pid=111533 comm="exe" path="/usr/bin/pod" dev="dm-2" ino=33601336 scontext=system_u:system_r:unconfined_service_t:s0 tcontext=system_u:system_r:svirt_lxc_net_t:s0:c0,c1 tclass=process
type=AVC msg=audit(1486651206.979:6537): avc: denied { sigchld } for pid=112095 comm="docker-containe" scontext=system_u:system_r:svirt_lxc_net_t:s0:c4,c7 tcontext=system_u:system_r:unconfined_service_t:s0 tclass=process
Expected results:
Additional info:
Maybe it is needed to issue these commands to get the whole thing working:
# oadm policy add-scc-to-user privileged -z router
# oc deploy --cancel jhenner-router
# oc deploy --retry jhenner-router
Note that I am not sure is this the proper place to report this bug. It also may be the case there is some problem with the router image which showed up as selinux denials. Maybe the code is now doing something it shouldn't do. I didn't check that. I just needed the system working and found that the two rules seems to help. I didn't pay any attention to security implications of them!
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://rhn.redhat.com/errata/RHEA-2017-0416.html
Description of problem: The deployments of router on opensift-3.4 started failing. I found this in # oc describe pods router-1-deploy ... 1m 1m 1 {kubelet ose3-master-828ml.828ml...} Warning FailedSync Error syncing pod, skipping: failed to "SetupNetwork" for "router-1-deploy_default" with SetupNetworkError: "Failed to setup network for pod \"router-1-deploy_default(7e333bd8-eecb-11e6-802a-fa163eb77bb0)\" using network plugins \"cni\": failed to Statfs \"/proc/49939/ns/net\": no such file or directory; Skipping pod" It smelled like a selinux issue and it seems it is. # sudo setenforce 0 Fixed it: 3s 3s 1 {kubelet ose3-master-828ml.828ml...} spec.containers{deployment} Normal Created Created container with docker id 626b82664835; Security:[seccomp=unconfined] 3s 3s 1 {kubelet ose3-master-828ml.828ml.cmqe...} spec.containers{deployment} Normal Started Started container with docker id 626b82664835 Version-Release number of selected component (if applicable): atomic-openshift-sdn-ovs-3.4.0.40-1.git.0.787e974.el7.x86_64 docker-1.12.6-2.el7.x86_64 selinux-policy-targeted-3.13.1-60.el7.noarch container-selinux-2.7-1.el7.noarch How reproducible: Always Steps to Reproduce: 1. Try deploying openshift with openshift-ansible 2. It will fail, so does manual issuing the command to create router # oadm router jhenner-router --replicas=1 --service-account=router [root@ose3-master-th4j5 cloud-user]# sudo audit2allow -a #============= svirt_lxc_net_t ============== allow svirt_lxc_net_t unconfined_service_t:process sigchld; #============= unconfined_service_t ============== allow unconfined_service_t svirt_lxc_net_t:process transition; these rules seem to help. Actual results: router (and registry) pod failing to spawn. type=AVC msg=audit(1486651160.007:6487): avc: denied { transition } for pid=111533 comm="exe" path="/usr/bin/pod" dev="dm-2" ino=33601336 scontext=system_u:system_r:unconfined_service_t:s0 tcontext=system_u:system_r:svirt_lxc_net_t:s0:c0,c1 tclass=process type=AVC msg=audit(1486651206.979:6537): avc: denied { sigchld } for pid=112095 comm="docker-containe" scontext=system_u:system_r:svirt_lxc_net_t:s0:c4,c7 tcontext=system_u:system_r:unconfined_service_t:s0 tclass=process Expected results: Additional info: Maybe it is needed to issue these commands to get the whole thing working: # oadm policy add-scc-to-user privileged -z router # oc deploy --cancel jhenner-router # oc deploy --retry jhenner-router