Here is the output of the init: [root@dn183 ~]# cdsw init Using user-specified config file: /etc/cdsw/config/cdsw.conf Prechecking OS Version........[OK] Prechecking scaling limits for processes........[OK] Prechecking scaling limits for open files........[OK] Prechecking that iptables are not configured........[OK] Prechecking that SELinux is disabled........[OK] Prechecking configured block devices and mountpoints........[OK] Prechecking kernel parameters........[OK] Prechecking that docker block devices are of adequate size........[OK] Prechecking that application block devices are of adequate size........[OK] Prechecking size of root volume........[OK] Prechecking that CDH gateway roles are configured........[OK] Prechecking that /etc/krb5 file is not a placeholder........ WARNING: The Kerberos configuration file [/etc/krb5.conf] seems to be a placeholder. If your CDH cluster is Kerberized, please copy /etc/krb5.conf to these Cloudera Data Science Workbench nodes. Press enter to continue. Prechecking parcel paths........[OK] Prechecking CDH client configurations........[OK] Prechecking Java version........[OK] Prechecking Java distribution........[OK] Creating docker thinpool if it does not exist Volume group "docker" not found Cannot process volume group docker Unmounting /dev/sdb umount: /dev/sdb: not mounted Removing Docker volume groups. Volume group "docker" not found Cannot process volume group docker Volume group "docker" not found Cannot process volume group docker Cleaning up docker directories... Physical volume "/dev/sdb" successfully created Volume group "docker" successfully created WARNING: xfs signature detected on /dev/docker/thinpool at offset 0. Wipe it? [y/n]: y Wiping xfs signature on /dev/docker/thinpool. Logical volume "thinpool" created. Logical volume "thinpoolmeta" created. WARNING: Converting logical volume docker/thinpool and docker/thinpoolmeta to pool's data and metadata volumes. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) Converted docker/thinpool to thin pool. Logical volume "thinpool" changed. Initialize application storage at /var/lib/cdsw [/dev/sdc] is formatted as [] and not ext4, hence needs to be formatted. WARNING: Formatting will erase all project files and data! Are you sure? y Starting rpc-statd... Enabling rpc-statd... Starting nfs-idmapd... Enabling nfs-idmapd... Starting rpcbind... Enabling rpcbind... Starting nfs-server... Enabling nfs-server... Proceeding to create storage for application... mke2fs 1.42.9 (28-Dec-2013) /dev/sdc is entire device, not just one partition! Proceed anyway? (y,n) y Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 73228288 inodes, 292896768 blocks 14644838 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=2441084928 8939 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done Enabling node with IP [192.168.239.183]... Node [192.168.239.183] added to nfs export list successfully. Starting rpc-statd... Enabling rpc-statd... Starting nfs-idmapd... Enabling nfs-idmapd... Starting rpcbind... Enabling rpcbind... Starting nfs-server... Enabling nfs-server... Starting docker... Enabling docker... Starting ntpd... Enabling ntpd... Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /etc/systemd/system/kubelet.service. Initializing cluster... Running pre-flight checks <master/tokens> generated token: "afde63.f3bb72d9a16f9a74" <master/pki> generated Certificate Authority key and certificate: Issuer: CN=kubernetes | Subject: CN=kubernetes | CA: true Not before: 2017-05-19 08:43:05 +0000 UTC Not After: 2027-05-17 08:43:05 +0000 UTC Public: /etc/kubernetes/pki/ca-pub.pem Private: /etc/kubernetes/pki/ca-key.pem Cert: /etc/kubernetes/pki/ca.pem <master/pki> generated API Server key and certificate: Issuer: CN=kubernetes | Subject: CN=kube-apiserver | CA: false Not before: 2017-05-19 08:43:05 +0000 UTC Not After: 2018-05-19 08:43:06 +0000 UTC Alternate Names: [192.168.239.183 100.77.0.1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] Public: /etc/kubernetes/pki/apiserver-pub.pem Private: /etc/kubernetes/pki/apiserver-key.pem Cert: /etc/kubernetes/pki/apiserver.pem <master/pki> generated Service Account Signing keys: Public: /etc/kubernetes/pki/sa-pub.pem Private: /etc/kubernetes/pki/sa-key.pem <master/pki> created keys and certificates in "/etc/kubernetes/pki" <util/kubeconfig> created "/etc/kubernetes/kubelet.conf" <util/kubeconfig> created "/etc/kubernetes/admin.conf" <master/apiclient> created API client configuration <master/apiclient> created API client, waiting for the control plane to become ready <master/apiclient> all control plane components are healthy after 42.548542 seconds <master/apiclient> waiting for at least one node to register and become ready <master/apiclient> first node is ready after 4.002406 seconds <master/apiclient> attempting a test deployment <master/apiclient> test deployment succeeded <master/discovery> created essential addon: kube-discovery, waiting for it to become ready <master/discovery> kube-discovery is ready after 24.002057 seconds <master/addons> created essential addon: kube-proxy <master/addons> created essential addon: kube-dns Kubernetes master initialised successfully! You can now join any number of machines by running the following on each node: kubeadm join --token=afde63.f3bb72d9a16f9a74 192.168.239.183 Added bootstrap token KUBE_TOKEN to /etc/cdsw/config/cdsw.conf node "dn183.pf4h.local" tainted daemonset "weave-net" created Waiting for kube-system cluster to come up. This could take a few minutes... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. ... ... ... Waiting for 10 seconds before checking again... ERROR:: Unable to bring up kube-system cluster.: 1 ERROR:: Unable to start clusters: 1 ... View more

We upgraded ou cluster to CDH 5.1.1 and the problem disappeared.So currently I cannot reproduce the problem. Thanks for the tip with webhdfs. ... View more