rancher: RHEL 7.7 with selinux enabled using RHEL docker on k8s 1.16 cluster fails to deploy

What kind of request is this (question/bug/enhancement/feature request): bug

Steps to reproduce (least amount of steps as possible): On a rancher:2.3.2-rc2 - deploy an RHEL 7.7 custom cluster - (3 etcd, 1 control plane, 3 worker nodes)

Docker - Native docker 1.13 Selinux - Enabled

Expected Result: The cluster should be deployed successfully

Actual Result: The cluster fails to deploy with error: Failed to get job complete status for job rke-network-plugin-deploy-job in namespace kube-system

Error in logs:

2019/10/24 19:16:59 [INFO] Removing container [rke-log-cleaner] on host [xxxx], try #1



















2019/10/24 19:16:59 [INFO] cluster [c-xcdfw] provisioning: [cleanup] Successfully started [rke-log-cleaner] container on host [xxxx]
2019/10/24 19:16:59 [INFO] cluster [c-xcdfw] provisioning: [cleanup] Successfully started [rke-log-cleaner] container on host [xxxx]
2019/10/24 19:16:59 [INFO] Removing container [rke-log-cleaner] on host [xxxx], try rancher/rancher#1
2019/10/24 19:16:59 [INFO] cluster [c-xcdfw] provisioning: [remove/rke-log-cleaner] Successfully removed container on host [xxxxx]
2019/10/24 19:16:59 [INFO] cluster [c-xcdfw] provisioning: [remove/rke-log-cleaner] Successfully removed container on host [xxxx]
2019/10/24 19:16:59 [INFO] cluster [c-xcdfw] provisioning: [remove/rke-log-cleaner] Successfully removed container on host [xxxx]
2019/10/24 19:16:59 [INFO] cluster [c-xcdfw] provisioning: [remove/rke-log-cleaner] Successfully removed container on host [xxxx]
2019/10/24 19:16:59 [INFO] cluster [c-xcdfw] provisioning: [sync] Syncing nodes Labels and Taints
2019/10/24 19:16:59 [INFO] cluster [c-xcdfw] provisioning: [sync] Successfully synced nodes Labels and Taints
2019/10/24 19:16:59 [INFO] cluster [c-xcdfw] provisioning: [network] Setting up network plugin: canal
2019/10/24 19:17:00 [INFO] cluster [c-xcdfw] provisioning: [addons] Saving ConfigMap for addon rke-network-plugin to Kubernetes
2019/10/24 19:17:00 [INFO] cluster [c-xcdfw] provisioning: [addons] Successfully saved ConfigMap for addon rke-network-plugin to Kubernetes
2019/10/24 19:17:00 [INFO] cluster [c-xcdfw] provisioning: [addons] Executing deploy job rke-network-plugin
2019/10/24 19:17:35 [ERROR] cluster [c-xcdfw] provisioning: Failed to get job complete status for job rke-network-plugin-deploy-job in namespace kube-system
2019/10/24 19:17:35 [INFO] kontainerdriver rancherkubernetesengine stopped
2019/10/24 19:17:35 [ERROR] ClusterController c-xcdfw [cluster-provisioner-controller] failed with : Failed to get job complete status for job rke-network-plugin-deploy-job in namespace kube-system

Other details that may be helpful:

Environment information

  • Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.3.2-rc2
  • Installation option (single install/HA): HA

Cluster information

  • Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom - rhel 7.7
  • Kubernetes version (use kubectl version):
1.16.2-rancher1-1
  • Docker version (use docker version):
native docker - docker 1.13 (native)

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 25 (15 by maintainers)

Most upvoted comments

Available in rancher/rancher:v2.3.6-rc6

verified on 2.3.5-rc2, On k8s version 1.16.6 and 1.17.2, cluster does not come up. On K8s version 1.15.9 --> Works fine

cluster spec:

deploy an RHEL 7.7 custom cluster - (1 etcd, 1 control plane, 3 worker nodes) 
Docker - Native docker 1.13
Selinux - Enabled

Error:

2020/01/23 18:38:23 [INFO] kontainerdriver rancherkubernetesengine stopped
2020/01/23 18:38:23 [ERROR] ClusterController c-8klsx [cluster-provisioner-controller] failed with : Failed to get job complete status for job rke-network-plugin-deploy-job in namespace kube-system

@fmunteanu K8s version 16.6 should be already available to you on a fresh install of v2.3.4. If you are using an already deployed rancher-server with v2.3.4 you would have to refresh kubernetes metadata (Tools-> Refresh Kubernetes Metadata) if you dont see these new versions already.