IBM Support

Installation of IBM InfoSphere Information Server Enterprise Search fails as kubeadm initialization fails

Troubleshooting


Problem

Installation of Information Server Enterprise Search fails as kubeadm initialization fails

Symptom

The installation fails.

Cause

The hostname value for the Information Server Enterprise Search host was returned as a short name.

Environment

Information Server Enterprise Search installation

Diagnosing The Problem

In /tmp examine the iiskubedeploy_<yyyy_MM_dd_hh_mm_ss>.log. Check whether it contains the error message

`TASK [setup.master : Run kubeadm init] *****************************************
fatal: [9.20.91.42]: FAILED! => {"changed": true, "cmd": "kubeadm init --config /opt/IBM/UGinstall/selfextract.TTMVCR.2018_07_23_09_18_22/kubeadm.conf && touch /tmp/kubeadm_join.txt", "delta": "0:02:28.328239", "end": "2018-07-23 11:24:43.581875", "failed": true, "msg": "non-zero return code", "rc": 1, "start": "2018-07-23 11:22:15.253636", "stderr": "\t[WARNING FileExisting-crictl]: crictl not found in system path\nerror marking master: timed out waiting for the condition", "stderr_lines": ["\t[WARNING FileExisting-crictl]: crictl not found in system path", "error marking master: timed out waiting for the condition"], "stdout": "[init] Using Kubernetes version: v1.9.7\n[init] Using Authorization modes: [Node RBAC]\n[preflight] Running pre-flight checks.\n[certificates] Generated ca certificate and key.\n[certificates] Generated apiserver certificate and key.\n[certificates] apiserver serving cert is signed for DNS names [9.20.91.42 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 9.20.91.42]\n[certificates] Generated apiserver-kubelet-client certificate and key.\n[certificates] Generated sa key and public key.\n[certificates] Generated front-proxy-ca certificate and key.\n[certificates] Generated front-proxy-client certificate and key.\n[certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki"\n[kubeconfig] Wrote KubeConfig file to disk: "admin.conf"\n[kubeconfig] Wrote KubeConfig file to disk: "kubelet.conf"\n[kubeconfig] Wrote KubeConfig file to disk: "controller-manager.conf"\n[kubeconfig] Wrote KubeConfig file to disk: "scheduler.conf"\n[controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"\n[controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"\n[controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"\n[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"\n[init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests".\n[init] This might take a minute or longer if the control plane images have to be pulled.\n[apiclient] All control plane components are healthy after 23.502135 seconds\n[uploadconfig] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace\n[markmaster] Will mark node 9.20.91.42 as master by adding a label and a taint", "stdout_lines": ["[init] Using Kubernetes version: v1.9.7", "[init] Using Authorization modes: [Node RBAC]", "[preflight] Running pre-flight checks.", "[certificates] Generated ca certificate and key.", "[certificates] Generated apiserver certificate and key.", "[certificates] apiserver serving cert is signed for DNS names [9.20.91.42 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 9.20.91.42]", "[certificates] Generated apiserver-kubelet-client certificate and key.", "[certificates] Generated sa key and public key.", "[certificates] Generated front-proxy-ca certificate and key.", "[certificates] Generated front-proxy-client certificate and key.", "[certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki"", "[kubeconfig] Wrote KubeConfig file to disk: "admin.conf"", "[kubeconfig] Wrote KubeConfig file to disk: "kubelet.conf"", "[kubeconfig] Wrote KubeConfig file to disk: "controller-manager.conf"", "[kubeconfig] Wrote KubeConfig file to disk: "scheduler.conf"", "[controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"", "[controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"", "[controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"", "[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"", "[init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests".", "[init] This might take a minute or longer if the control plane images have to be pulled.", "[apiclient] All control plane components are healthy after 23.502135 seconds", "[uploadconfig] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace", "[markmaster] Will mark node 9.20.91.42 as master by adding a label and a taint"]}
to retry, use: --limit @/opt/IBM/UGinstall/selfextract.TTMVCR.2018_07_23_09_18_22/ansible/playbooks/initSingle.retry

Resolving The Problem

1. Login to the ISES host
2. Update  the /etc/hostname file replacing short host name entries with long host name (fqdn)
3. Restart the ISES host
4. In /tmp/uginfo.rsp replace short host name entries with long host name (fqdn)
5. Rerun the bsx installer using the following command
    /tmp/kubeselfextract.bsx

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSZJPZ","label":"IBM InfoSphere Information Server"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"11.7.0.2;11.7.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
28 March 2019

UID

ibm10735089