installcentos
installcentos copied to clipboard
gshipley
openshift install fails
I keep getting error messages on my installation. I am running centos 7 and the version of openshift I tried are 3.9, 3.10 and 3.11. I see the control plane pods created but they don't appear to be accessible or visible...(?)
FAILED - RETRYING: Wait for control plane pods to appear (4 retries left). FAILED - RETRYING: Wait for control plane pods to appear (3 retries left). FAILED - RETRYING: Wait for control plane pods to appear (2 retries left). FAILED - RETRYING: Wait for control plane pods to appear (1 retries left). failed: [10.25.75.210] (item=etcd) => {"attempts": 60, "changed": false, "item": "etcd", "msg": {"cmd": "/usr/bin/oc get pod master-etcd-ctrl.elab.local -o json -n kube-system", "results": [{}], "returncode": 1, "stderr": "Unable to connect to the server: Service Unavailable\n", "stdout": ""}} FAILED - RETRYING: Wait for control plane pods to appear (60 retries left). FAILED - RETRYING: Wait for control plane pods to appear (59 retries left). FAILED - RETRYING: Wait for control plane pods to appear (58 retries left). +++++ created volume 199 error: unable to recognize "oc_vol.yaml": Get https://ctrl.elab.local:8443/api?timeout=32s: Service Unavailable created volume 200
- Your console is https://console.elab.local:8080
- Your username is origin
- Your password is origin123
- Login using:
$ oc login -u origin -p origin123 https://console.elab.local:8080/
error: Service Unavailable [root@ctrl installcentos]#
[root@ctrl installcentos]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 536f8b015fa5 ff5dd2137a4f "/bin/sh -c '#!/bi..." 2 minutes ago Exited (1) 2 minutes ago k8s_etcd_master-etcd-ctrl.elab.local_kube-system_45cca627095658e26a83b307411535b0_11 932314d6d35b bbb653b4d998 "/bin/bash -c '#!/..." 8 minutes ago Up 8 minutes k8s_controllers_master-controllers-ctrl.elab.local_kube-system_65900fff2b6e1f76c768d747ff1e53f6_1 fc0f7bb6f2e3 bbb653b4d998 "/bin/bash -c '#!/..." 8 minutes ago Up 8 minutes k8s_api_master-api-ctrl.elab.local_kube-system_60f548cd1d82d290eb6882da121098d3_0 7a2ea4ba1b8a docker.io/openshift/origin-pod:v3.11.0 "/usr/bin/pod" 8 minutes ago Up 8 minutes k8s_POD_master-api-ctrl.elab.local_kube-system_60f548cd1d82d290eb6882da121098d3_0 2909496bf5b8 docker.io/openshift/origin-control-plane@sha256:db5dcd806d1a7228c8e4a7ee9a5ba19d93a85a06487d3b7bf2cac4776cb61b34 "/bin/bash -c '#!/..." 12 minutes ago Exited (255) 8 minutes ago k8s_controllers_master-controllers-ctrl.elab.local_kube-system_65900fff2b6e1f76c768d747ff1e53f6_0 4df9a39003f3 docker.io/openshift/origin-pod:v3.11.0 "/usr/bin/pod" 12 minutes ago Up 12 minutes k8s_POD_master-controllers-ctrl.elab.local_kube-system_65900fff2b6e1f76c768d747ff1e53f6_0 923de90bd762 docker.io/openshift/origin-pod:v3.11.0 "/usr/bin/pod" 12 minutes ago Up 12 minutes k8s_POD_master-etcd-ctrl.elab.local_kube-system_45cca627095658e26a83b307411535b0_0 [root@ctrl installcentos]#
I have also same issue, please help
Hello sivalanka, try to delete /etc/origin and rerun script with more cpu and memory it's good for me Regards
No idea if this is the same solution for the problem listed, but I had many similar problems for about a week trying to get Openshift to start up properly. In the end if I set the environment variable "export no_proxy='hostname'" (use backticks) before I ran the script , then it all seem to work. No idea, I don't have any proxy.
The below fixed my issue. I use a proxy in my environment
$ cat <<EOF > /etc/environment http_proxy=http://10.xx.xx.xx:8080 https_proxy=http://10.xx.xx.xx:8080 ftp_proxy=http://10.xx.xx.xx:8080 no_proxy=127.0.0.1,localhost,172.17.240.84,172.17.240.85,172.17.240.86,172.17.240.87,10.96.0.0/12,10.244.0.0/16,v-openshift1-lnx1,v-node01-lnx1,v-node02-lnx1,console,console.inet.co.za EOF
$ cat <<EOF > /etc/systemd/system/docker.service.d/no-proxy.conf [Service] Environment="NO_PROXY=artifactory-za.devel.iress.com.au, 172.30.9.71, 172.17.240.84, 172.17.240.85, 172.17.240.86, 172.17.240.87" Environment="HTTP_PROXY=http://10.xx.xx.xx:8080/" Environment="HTTPS_PROXY=http://10.xx.xx.xx:8080/" EOF
The below fixed my issue. I use a proxy in my environment
$ cat <<EOF > /etc/environment http_proxy=http://10.xx.xx.xx:8080 https_proxy=http://10.xx.xx.xx:8080 ftp_proxy=http://10.xx.xx.xx:8080 no_proxy=127.0.0.1,localhost,172.17.240.84,172.17.240.85,172.17.240.86,172.17.240.87,10.96.0.0/12,10.244.0.0/16,v-openshift1-lnx1,v-node01-lnx1,v-node02-lnx1,console,console.inet.co.za EOF
$ cat <<EOF > /etc/systemd/system/docker.service.d/no-proxy.conf [Service] Environment="NO_PROXY=artifactory-za.devel.iress.com.au, 172.30.9.71, 172.17.240.84, 172.17.240.85, 172.17.240.86, 172.17.240.87" Environment="HTTP_PROXY=http://10.xx.xx.xx:8080/" Environment="HTTPS_PROXY=http://10.xx.xx.xx:8080/" EOF