oc cluster up result into an error
Error: timed out waiting for the condition
Mac OS: 10.14.1
docker version
Client:
Version: 18.06.1-ce
API version: 1.38
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:21:31 2018
OS/Arch: darwin/amd64
Experimental: false
Server:
Engine:
Version: 18.06.1-ce
API version: 1.38 (minimum version 1.12)
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:29:02 2018
OS/Arch: linux/amd64
Experimental: false
md5-29e2941133eec0c0bb3432cbd87b11e2
oc version
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth
md5-29e2941133eec0c0bb3432cbd87b11e2
docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
openshift/origin-node v3.11 48cb61702ea2 29 hours ago 1.16GB
openshift/origin-control-plane v3.11 fb643d7aeb7a 29 hours ago 818MB
openshift/origin-hypershift v3.11 92fdbc9dd636 29 hours ago 541MB
openshift/origin-hyperkube v3.11 6c60787c0d3e 29 hours ago 501MB
openshift/origin-cli v3.11 782540b81ca5 29 hours ago 376MB
openshift/origin-pod v3.10 61b86934f357 46 hours ago 224MB
openshift/origin-service-serving-cert-signer v3.11 47dadf9d43b6 2 weeks ago 276MB
md5-9c5446494438dce60ff3585000bfc318
oc cluster up
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Pulling image openshift/origin-control-plane:v3.11
Pulled 1/5 layers, 23% complete
Pulled 2/5 layers, 61% complete
Pulled 3/5 layers, 77% complete
Pulled 4/5 layers, 83% complete
Pulled 5/5 layers, 100% complete
Extracting
Image pull complete
Pulling image openshift/origin-cli:v3.11
Image pull complete
Pulling image openshift/origin-node:v3.11
Pulled 5/6 layers, 88% complete
Pulled 6/6 layers, 100% complete
Extracting
Image pull complete
Creating shared mount directory on the remote host ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking prerequisites for port forwarding ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I1103 16:06:53.568319 17438 flags.go:30] Running "create-kubelet-flags"
I1103 16:06:54.749134 17438 run_kubelet.go:49] Running "start-kubelet"
I1103 16:06:55.072466 17438 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
I1103 16:07:34.343218 17438 interface.go:26] Installing "kube-proxy" ...
I1103 16:07:34.343258 17438 interface.go:26] Installing "kube-dns" ...
I1103 16:07:34.343279 17438 interface.go:26] Installing "openshift-service-cert-signer-operator" ...
I1103 16:07:34.343293 17438 interface.go:26] Installing "openshift-apiserver" ...
I1103 16:07:34.343328 17438 apply_template.go:81] Installing "openshift-apiserver"
I1103 16:07:34.343352 17438 apply_template.go:81] Installing "kube-proxy"
I1103 16:07:34.343398 17438 apply_template.go:81] Installing "kube-dns"
I1103 16:07:34.343437 17438 apply_template.go:81] Installing "openshift-service-cert-signer-operator"
I1103 16:08:08.205618 17438 interface.go:41] Finished installing "kube-proxy" "kube-dns" "openshift-service-cert-signer-operator" "openshift-apiserver"
Error: timed out waiting for the condition
md5-71dd19dba2c4c17939d0f93bc254f7a8
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1ae0cac4567b openshift/origin-service-serving-cert-signer "service-serving-cer…" About a minute ago Up About a minute k8s_service-serving-cert-signer-controller_service-serving-cert-signer-668c45d5f-pxwqx_openshift-service-cert-signer_2a529539-cf8d-11e8-b78b-025000000001_0
e2e9ac3dae11 openshift/origin-service-serving-cert-signer "service-serving-cer…" About a minute ago Up About a minute k8s_operator_openshift-service-cert-signer-operator-6d477f986b-qqdzd_openshift-core-operators_0db6c342-cf8d-11e8-b78b-025000000001_0
511631535c11 openshift/origin-hypershift "hypershift openshif…" About a minute ago Up About a minute k8s_apiserver_openshift-apiserver-j2r72_openshift-apiserver_d10429eb-d3db-11e8-b8e9-025000000001_0
e2fb6a36000a openshift/origin-control-plane "openshift start net…" About a minute ago Up About a minute k8s_kube-proxy_kube-proxy-rg5mq_kube-proxy_0dc7cb92-cf8d-11e8-b78b-025000000001_0
61b476fdb48b openshift/origin-service-serving-cert-signer "service-serving-cer…" About a minute ago Up About a minute k8s_apiservice-cabundle-injector-controller_apiservice-cabundle-injector-8ffbbb6dc-6scp8_openshift-service-cert-signer_2b9fce4e-cf8d-11e8-b78b-025000000001_0
be52142fb105 openshift/origin-control-plane "openshift start net…" About a minute ago Up About a minute k8s_kube-dns_kube-dns-vdrf8_kube-dns_0dd32d8a-cf8d-11e8-b78b-025000000001_0
8d989e9845fb openshift/origin-node:v3.11 "hyperkube kubelet -…" 2 minutes ago Up 2 minutes origin
md5-29e2941133eec0c0bb3432cbd87b11e2
docker logs origin > origin.log 2>&1
docker logs be52142fb105 > kube-dns.log 2>&1
docker logs 61b476fdb48b > apiservice-cabundle-injector.log 2>&1
docker logs e2fb6a36000a > kube-proxy.log 2>&1
docker logs 511631535c11 > openshift-apiserver.log 2>&1
docker logs e2e9ac3dae11 > openshift-service-cert-signer-operator.log 2>&1
docker logs 1ae0cac4567b > service-serving-cert-signer-controller.log 2>&1
md5-01e5fc6702cea7e2ce66b4211ee198d8
mkdir -p "$HOME/.occluster"
oc cluster up --base-dir="$HOME/.occluster"
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Creating shared mount directory on the remote host ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking prerequisites for port forwarding ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I1103 16:23:02.811666 18115 config.go:40] Running "create-master-config"
I1103 16:23:05.446271 18115 config.go:46] Running "create-node-config"
I1103 16:23:07.135914 18115 flags.go:30] Running "create-kubelet-flags"
I1103 16:23:08.341419 18115 run_kubelet.go:49] Running "start-kubelet"
I1103 16:23:08.645223 18115 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
I1103 16:23:35.895717 18115 interface.go:26] Installing "kube-proxy" ...
I1103 16:23:35.895738 18115 interface.go:26] Installing "kube-dns" ...
I1103 16:23:35.895744 18115 interface.go:26] Installing "openshift-service-cert-signer-operator" ...
I1103 16:23:35.895750 18115 interface.go:26] Installing "openshift-apiserver" ...
I1103 16:23:35.895777 18115 apply_template.go:81] Installing "kube-proxy"
I1103 16:23:35.895778 18115 apply_template.go:81] Installing "openshift-apiserver"
I1103 16:23:35.895786 18115 apply_template.go:81] Installing "openshift-service-cert-signer-operator"
I1103 16:23:35.895777 18115 apply_template.go:81] Installing "kube-dns"
I1103 16:23:38.830911 18115 interface.go:41] Finished installing "kube-proxy" "kube-dns" "openshift-service-cert-signer-operator" "openshift-apiserver"
I1103 16:26:08.908169 18115 run_self_hosted.go:242] openshift-apiserver available
I1103 16:26:08.908200 18115 interface.go:26] Installing "openshift-controller-manager" ...
I1103 16:26:08.908218 18115 apply_template.go:81] Installing "openshift-controller-manager"
I1103 16:26:11.618352 18115 interface.go:41] Finished installing "openshift-controller-manager"
Adding default OAuthClient redirect URIs ...
Adding centos-imagestreams ...
Adding registry ...
Adding router ...
Adding sample-templates ...
Adding persistent-volumes ...
Adding web-console ...
I1103 16:26:11.641602 18115 interface.go:26] Installing "centos-imagestreams" ...
I1103 16:26:11.641623 18115 interface.go:26] Installing "openshift-image-registry" ...
I1103 16:26:11.641630 18115 interface.go:26] Installing "openshift-router" ...
I1103 16:26:11.641635 18115 interface.go:26] Installing "sample-templates" ...
I1103 16:26:11.641640 18115 interface.go:26] Installing "persistent-volumes" ...
I1103 16:26:11.641650 18115 interface.go:26] Installing "openshift-web-console-operator" ...
I1103 16:26:11.641778 18115 apply_list.go:67] Installing "centos-imagestreams"
I1103 16:26:11.641835 18115 interface.go:26] Installing "sample-templates/nodejs quickstart" ...
I1103 16:26:11.641854 18115 interface.go:26] Installing "sample-templates/rails quickstart" ...
I1103 16:26:11.641877 18115 interface.go:26] Installing "sample-templates/jenkins pipeline ephemeral" ...
I1103 16:26:11.641890 18115 interface.go:26] Installing "sample-templates/mongodb" ...
I1103 16:26:11.641902 18115 interface.go:26] Installing "sample-templates/mariadb" ...
I1103 16:26:11.641910 18115 interface.go:26] Installing "sample-templates/postgresql" ...
I1103 16:26:11.641919 18115 interface.go:26] Installing "sample-templates/cakephp quickstart" ...
I1103 16:26:11.641927 18115 interface.go:26] Installing "sample-templates/django quickstart" ...
I1103 16:26:11.641936 18115 interface.go:26] Installing "sample-templates/mysql" ...
I1103 16:26:11.641977 18115 apply_list.go:67] Installing "sample-templates/rails quickstart"
I1103 16:26:11.641987 18115 apply_list.go:67] Installing "sample-templates/nodejs quickstart"
I1103 16:26:11.642036 18115 apply_list.go:67] Installing "sample-templates/jenkins pipeline ephemeral"
I1103 16:26:11.642068 18115 apply_list.go:67] Installing "sample-templates/mysql"
I1103 16:26:11.642000 18115 interface.go:26] Installing "sample-templates/dancer quickstart" ...
I1103 16:26:11.642161 18115 interface.go:26] Installing "sample-templates/sample pipeline" ...
I1103 16:26:11.642249 18115 apply_list.go:67] Installing "sample-templates/sample pipeline"
I1103 16:26:11.642283 18115 apply_list.go:67] Installing "sample-templates/postgresql"
I1103 16:26:11.642381 18115 apply_list.go:67] Installing "sample-templates/cakephp quickstart"
I1103 16:26:11.642402 18115 apply_template.go:81] Installing "openshift-web-console-operator"
I1103 16:26:11.642439 18115 apply_list.go:67] Installing "sample-templates/dancer quickstart"
I1103 16:26:11.642460 18115 apply_list.go:67] Installing "sample-templates/mariadb"
I1103 16:26:11.642539 18115 apply_list.go:67] Installing "sample-templates/django quickstart"
I1103 16:26:11.643068 18115 apply_list.go:67] Installing "sample-templates/mongodb"
I1103 16:26:19.810920 18115 interface.go:41] Finished installing "sample-templates/nodejs quickstart" "sample-templates/rails quickstart" "sample-templates/jenkins pipeline ephemeral" "sample-templates/mongodb" "sample-templates/mariadb" "sample-templates/postgresql" "sample-templates/cakephp quickstart" "sample-templates/django quickstart" "sample-templates/mysql" "sample-templates/dancer quickstart" "sample-templates/sample pipeline"
I1103 16:26:53.420432 18115 interface.go:41] Finished installing "centos-imagestreams" "openshift-image-registry" "openshift-router" "sample-templates" "persistent-volumes" "openshift-web-console-operator"
Login to server ...
Creating initial project "myproject" ...
Server Information ...
OpenShift server started.
The server is accessible via web console at:
https://127.0.0.1:8443
You are logged in as:
User: developer
Password: <any value>
To login as administrator:
oc login -u system:admin
WARNING: An HTTP proxy (gateway.docker.internal:3128) is configured for the Docker daemon, but you did not specify one for cluster up
WARNING: An HTTPS proxy (gateway.docker.internal:3129) is configured for the Docker daemon, but you did not specify one for cluster up
WARNING: A proxy is configured for Docker, however 172.30.1.1 is not included in its NO_PROXY list.
172.30.1.1 needs to be included in the Docker daemon's NO_PROXY environment variable so pushes to the local OpenShift registry can succeed.
Same here. Workaround is not working instead.
i am also experiencing this issue with the 3.11 client downloaded from the releases page, my host is fedora 28.
worked on Fedora29, but the step in question took 2,5 min:
I1205 10:39:56.536312 10298 interface.go:41] Finished installing "kube-proxy" "kube-dns" "openshift-service-cert-signer-operator" "openshift-apiserver"
I1205 10:42:28.597603 10298 run_self_hosted.go:242] openshift-apiserver available
Seems it's the same complain as #20617
Just in case, do you face this problem too? https://github.com/minishift/minishift/issues/2809
Also facing this issue.
CentOS Linux release 7.6.1810 (Core)
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Checking type of volume mount ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking if required ports are available ...
W0201 21:39:11.125863 6514 up.go:765] Port 80 is already in use and may cause routing issues for applications.
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I0201 21:39:11.130934 6514 config.go:40] Running "create-master-config"
I0201 21:39:16.703581 6514 config.go:46] Running "create-node-config"
I0201 21:39:19.169849 6514 flags.go:30] Running "create-kubelet-flags"
I0201 21:39:20.384801 6514 run_kubelet.go:49] Running "start-kubelet"
I0201 21:39:20.975565 6514 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
I0201 21:39:43.993294 6514 interface.go:26] Installing "kube-proxy" ...
I0201 21:39:43.993328 6514 interface.go:26] Installing "kube-dns" ...
I0201 21:39:43.993342 6514 interface.go:26] Installing "openshift-service-cert-signer-operator" ...
I0201 21:39:43.993355 6514 interface.go:26] Installing "openshift-apiserver" ...
I0201 21:39:43.993370 6514 apply_template.go:81] Installing "kube-proxy"
I0201 21:39:43.993391 6514 apply_template.go:81] Installing "openshift-apiserver"
I0201 21:39:43.993433 6514 apply_template.go:81] Installing "kube-dns"
I0201 21:39:43.993488 6514 apply_template.go:81] Installing "openshift-service-cert-signer-operator"
I0201 21:39:47.867664 6514 interface.go:41] Finished installing "kube-proxy" "kube-dns" "openshift-service-cert-signer-operator" "openshift-apiserver"
Error: timed out waiting for the condition
despite the timeouts, containers are running.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
097ee7bd67db openshift/origin-control-plane "openshift start net…" 5 minutes ago Up 5 minutes k8s_kube-proxy_kube-proxy-nq5lv_kube-proxy_050eb454-266c-11e9-b93a-002655350488_0
d7cd274f52eb openshift/origin-control-plane "openshift start net…" 5 minutes ago Up 5 minutes k8s_kube-dns_kube-dns-jrxfk_kube-dns_05049b14-266c-11e9-b93a-002655350488_0
84c392433798 openshift/origin-service-serving-cert-signer "service-serving-cer…" 5 minutes ago Up 5 minutes k8s_operator_openshift-service-cert-signer-operator-6d477f986b-xhx7v_openshift-core-operators_04e28177-266c-11e9-b93a-002655350488_0
0b4b065eb78d openshift/origin-pod:v3.11 "/usr/bin/pod" 5 minutes ago Up 5 minutes k8s_POD_kube-proxy-nq5lv_kube-proxy_050eb454-266c-11e9-b93a-002655350488_0
67e41090aea2 openshift/origin-pod:v3.11 "/usr/bin/pod" 5 minutes ago Up 5 minutes k8s_POD_kube-dns-jrxfk_kube-dns_05049b14-266c-11e9-b93a-002655350488_0
6a88b7ac1bdc openshift/origin-pod:v3.11 "/usr/bin/pod" 5 minutes ago Up 5 minutes k8s_POD_openshift-service-cert-signer-operator-6d477f986b-xhx7v_openshift-core-operators_04e28177-266c-11e9-b93a-002655350488_0
36e854577ad2 openshift/origin-hyperkube "hyperkube kube-sche…" 6 minutes ago Up 6 minutes k8s_scheduler_kube-scheduler-localhost_kube-system_f7f0f3d2f7794c1aff29222d2fb8c76c_0
46f6fd838687 openshift/origin-hyperkube "hyperkube kube-cont…" 6 minutes ago Up 6 minutes k8s_controllers_kube-controller-manager-localhost_kube-system_7b5fcf36c36b6a2836943f66cba5410e_0
e7a875040bae openshift/origin-control-plane "/bin/bash -c '#!/bi…" 6 minutes ago Up 6 minutes k8s_etcd_master-etcd-localhost_kube-system_f7db0853936df2fc29525f0a40be4618_0
3b10cc9706a9 openshift/origin-hypershift "/bin/bash -c '#!/bi…" 6 minutes ago Up 6 minutes k8s_api_master-api-localhost_kube-system_48e2b84a9231f2308a7a00fb5541ad60_0
4541c51055cd openshift/origin-pod:v3.11 "/usr/bin/pod" 6 minutes ago Up 6 minutes k8s_POD_kube-scheduler-localhost_kube-system_f7f0f3d2f7794c1aff29222d2fb8c76c_0
1c8e5fdf67c1 openshift/origin-pod:v3.11 "/usr/bin/pod" 6 minutes ago Up 6 minutes k8s_POD_kube-controller-manager-localhost_kube-system_7b5fcf36c36b6a2836943f66cba5410e_0
b8fac228544b openshift/origin-pod:v3.11 "/usr/bin/pod" 6 minutes ago Up 6 minutes k8s_POD_master-etcd-localhost_kube-system_f7db0853936df2fc29525f0a40be4618_0
e8c033fc7931 openshift/origin-pod:v3.11 "/usr/bin/pod" 6 minutes ago Up 6 minutes k8s_POD_master-api-localhost_kube-system_48e2b84a9231f2308a7a00fb5541ad60_0
8370c1de0bee openshift/origin-node:v3.11 "hyperkube kubelet -…" 6 minutes ago Up 6 minutes origin
setting base dir workaround does not solve it.
Anyone found any other steps to troubleshoot?
I had the same issue on CentOS 7 and oc tools 3.11 but after adding a new firewalld zone as per documentation (https://github.com/openshift/origin/blob/release-3.11/docs/cluster_up_down.md#linux), everything worked fine.
firewall-cmd --permanent --new-zone dockerc
firewall-cmd --permanent --zone dockerc --add-source 172.17.0.0/16
firewall-cmd --permanent --zone dockerc --add-port 8443/tcp
firewall-cmd --permanent --zone dockerc --add-port 53/udp
firewall-cmd --permanent --zone dockerc --add-port 8053/udp
firewall-cmd --reload
@raven4ever worked like a charm! Thanks for that!
Really feel like that link should be better pointed to/reflected in these docs:
https://docs.okd.io/latest/install/prerequisites.html#install-config-network-using-firewalld
The prerequisites link on that page fails to point out those steps as it assumes you are using ansible for setup.
Will point that out on the docs repo.
Thanks again!
I had a similar issue starting minishift on Windows 10 using VirtualBox as the vm-driver however, running it as administrator fixed it
I have the same issue on ubunto 18.04 bionic with openshift 3.11 :(
Also tried starting the cluster up as root
oc cluster up --public-hostname=''
E0426 07:55:33.909661 20849 run_self_hosted.go:571] API server error: Get https://127.0.0.1:8443/healthz?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused ()
Error: timed out waiting for the condition
oc cluster up --public-hostname=xx.xxx.xx.xxx
where xx.xxx.xx.xxx is my public ip(returned by dig +short myip.opendns.com @resolver1.opendns.com) . This yields network unreachable
E0426 07:37:36.025451 19048 run_self_hosted.go:571] API server error: Get https://xx.xxx.xx.xxx:8443/healthz?timeout=32s: dial tcp xx.xxx.xx.xxx:8443: connect: network is unreachable ()
Error: timed out waiting for the condition
Did you confirm iptables/firewall settings? Worked for me.
@matthewmodestino Yep. Same timeout error. Perhaps something else for Ubuntu 18?
So for Ubuntu 18 bionic weaver, along with the firewall setup, I had to disable firewall with sudo ufw disable, deleted all log files and started up with a fresh install. Starting the cluster as root did not work. I am now able to start the cluster as non-root and cluster available at https://127.0.0.1:8443
@raven4ever Thank you for linking, that solved my issue on fedora 29!
@raven4ever it doesn't work for me, neither on a fresh Ubuntu 19.04 install in VirtualBox - even with firewalld installed and your commands executed, nor on a current Debian unstable. Both setups fail with
I0518 02:19:49.469907 29778 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0518 02:24:49.472960 29778 run_self_hosted.go:571] API server error: Get https://127.0.0.1:8443/healthz?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused ()
Error: timed out waiting for the condition
And I can understand a little: using netstat -anp --inet, there is nothing listening on port 8443 while it says "Waiting for the kube-apiserver...".
Workaround which has worked for me :
1) Using hyperv + oc 3.11 + minishift v1.34.1+c2ff9cb.
2) Problem only on not so good internet connections.
3) Once minishift start command fails for the first time, ssh into minishift vm. Run oc cluster down followed by oc cluster up (copy this from the logs). Repeat this down/up step till your cluster is up. It could be 10-20 times or more or less depending on the network maybe.
4) Once the cluster is up, run minishift stop/ start and then you will be ready.
Hope this helps
believeit or not, I solved this by add some mem to my vm from 8G to 10G ..
I've solved this issue by performing the following steps:
docker run -it --rm --privileged --pid=host justincormack/nsenter1 /bin/sh -c 'mkdir -p /var/lib/kubelet/device-plugins'oc cluster up --loglevel=5 --base-dir new-openshiftI've solved this issue reducing the amount of memory for the minishift Virtualbox Machine.
By default minishift uses 4GB of RAM, I opened Virtualbox and go to Machine configuration and set it to 2GB and now it works correctly.
My host is 6GB memory.
Tried the base-dir, the firewall settings, nothing is working for me. It started the first time and now not anymore after I tried to configure the domain name for the UI.
Could someone please help me fixing the issue please?
Centos7
Firewall configured as per this doc https://docs.okd.io/latest/install/prerequisites.html#install-config-network-using-firewalld
Yet I am still getting the below error please help :(
[root@sparky sparky]# oc cluster up
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Checking type of volume mount ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I0928 15:31:30.199575 18498 flags.go:30] Running "create-kubelet-flags"
I0928 15:31:35.772817 18498 run_kubelet.go:49] Running "start-kubelet"
I0928 15:31:38.843519 18498 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0928 15:36:38.893217 18498 run_self_hosted.go:571] API server error: Get https://127.0.0.1:8443/healthz?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused ()
Error: timed out waiting for the condition
@stramzik Try to follow this. Its shud work eventually
Once minishift start command fails for the first time, ssh into minishift vm. Run oc cluster down followed by oc cluster up (copy this from the logs). Repeat this down/up step till your cluster is up. It could be 10-20 times or more or less depending on the network maybe.
Once the cluster is up, run minishift stop/ start and then you will be ready.
Hope this helps
Instead of ssh step, you can also do minishift start several times.
Or connect your machine to a good internet connection. and do delete followed by start.
I have also been struggling for a while starting openshift on my Windows 10 laptop with VirtualBox, both with minishift and with vagrant. When I run minishift or vagrant however from a command prompt with administrator privileges openshift just starts fine.
I had the same issue on CentOS 7 and oc tools 3.11 but after adding a new firewalld zone as per documentation (https://github.com/openshift/origin/blob/release-3.11/docs/cluster_up_down.md#linux), everything worked fine.
firewall-cmd --permanent --new-zone dockerc firewall-cmd --permanent --zone dockerc --add-source 172.17.0.0/16 firewall-cmd --permanent --zone dockerc --add-port 8443/tcp firewall-cmd --permanent --zone dockerc --add-port 53/udp firewall-cmd --permanent --zone dockerc --add-port 8053/udp firewall-cmd --reload
after I added it, but still have error.
Finished installing "kube-proxy" "kube-dns" "openshift-service-cert-signer-operator" "openshift-apiserver"
Error: timed out waiting for the condition
I had the same issue on CentOS 7 and oc tools 3.11 but after adding a new firewalld zone as per documentation (https://github.com/openshift/origin/blob/release-3.11/docs/cluster_up_down.md#linux), everything worked fine.
firewall-cmd --permanent --new-zone dockerc firewall-cmd --permanent --zone dockerc --add-source 172.17.0.0/16 firewall-cmd --permanent --zone dockerc --add-port 8443/tcp firewall-cmd --permanent --zone dockerc --add-port 53/udp firewall-cmd --permanent --zone dockerc --add-port 8053/udp firewall-cmd --reloadafter I added it, but still have error.
Finished installing "kube-proxy" "kube-dns" "openshift-service-cert-signer-operator" "openshift-apiserver"
Error: timed out waiting for the condition
I am having the same issue as well.
I'm facing the Same Problem while running minishift start
Error:
I0103 13:20:27.344142 2549 interface.go:41] Finished installing "kube-proxy" "kube-dns" "openshift-service-cert-signer-operator" "openshift-apiserver"
Error: timed out waiting for the condition
Guy's If any one's Facing this Problem, It's a Internet Connection Problem, Kindly Go into minishift ssh and manually run what comman you're failing with.
Try to restart it by :
minishift stop then minishift start
it would solve half the Problems.
Good Luck With Minishift
Hi, I experienced this issue too and I've found some clues about how to fix it:
be sure that firewalld is running and to have configured it correctly as specified here.
Eventually, add a rule to expose the web console port too:
sudo firewall-cmd --zone=public --permanent --add-port=8443/tcp
If firewalld is NOT running, I systematically get the issue: running it (once configured) solved it for me.
Hello,
I had the same issue in centos 7, so i tried with this article:
https://medium.com/@fabiojose/working-with-oc-cluster-up-a052339ea219
and now it´s working, only change to more recently avilable version in the repo
It seems to be a matter of resources available (cpu/ram)
I increasing the number of cpu to 8 and using 10gb of RAM.
oc cluster up --public-host=myhost.mydomain.priv
I have same issue:
oc cluster up
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Checking type of volume mount ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I0718 16:14:57.974750 24870 config.go:40] Running "create-master-config"
I0718 16:15:01.495072 24870 config.go:46] Running "create-node-config"
I0718 16:15:03.260556 24870 flags.go:30] Running "create-kubelet-flags"
I0718 16:15:04.007884 24870 run_kubelet.go:49] Running "start-kubelet"
I0718 16:15:04.224262 24870 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0718 16:20:04.225876 24870 run_self_hosted.go:571] API server error: Get https://127.0.0.1:8443/healthz?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused ()
Error: timed out waiting for the condition
The firewalld settings do not work for me because I disabled the service firewalld already.
The cluster was up successfully finally, but I did nothing for it. Just tried 3 or 4 times with the command oc cluster up.
_I have tried everything suggested! Since the time I wanted to use minishift, I have keep on solving issue by issue but things are not working for me. I would be glad if you guys can help me out. Am using Fedora 32_
@raven4ever @niteshthakur @davi-romero @mdepa
minishift start
-- Starting profile 'minishift'
-- Check if deprecated options are used ... OK
-- Checking if https://github.com is reachable ... OK
-- Checking if requested OpenShift version 'v3.10.0' is valid ... OK
-- Checking if requested OpenShift version 'v3.10.0' is supported ... OK
-- Checking if requested hypervisor 'kvm' is supported on this platform ... OK
-- Checking if KVM driver is installed ...
Driver is available at /usr/local/bin/docker-machine-driver-kvm ...
Checking driver binary is executable ... OK
-- Checking if Libvirt is installed ... OK
-- Checking if Libvirt default network is present ... OK
-- Checking if Libvirt default network is active ... OK
-- Checking the ISO URL ... OK
-- Checking if provided oc flags are supported ... OK
-- Starting the OpenShift cluster using 'kvm' hypervisor ...
-- Starting Minishift VM ................. OK
-- Checking for IP address ... OK
-- Checking for nameservers ... OK
-- Checking if external host is reachable from the Minishift VM ...
Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ...
Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 30% used OK
-- Writing current configuration for static assignment of IP address ... WARN
-- OpenShift cluster will be configured with ...
Version: v3.10.0
-- Copying oc binary from the OpenShift container image to VM ... OK
-- Starting OpenShift cluster .....................................................................Error during 'cluster up' execution: Error starting the cluster. ssh command error:
command : /var/lib/minishift/bin/oc cluster up --public-hostname 192.168.42.50 --routing-suffix 192.168.42.50.nip.io --base-dir /var/lib/minishift/base --image 'openshift/origin-${component}:v3.10.0'
err : exit status 1
output : Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.10.0 is available ...
Checking type of volume mount ...
Determining server IP ...
Using public hostname IP 192.168.42.50 as the host IP
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.10.0 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.10.0 ...
I0915 20:26:37.652159 4434 flags.go:30] Running "create-kubelet-flags"
I0915 20:26:38.918623 4434 run_kubelet.go:48] Running "start-kubelet"
I0915 20:26:39.350952 4434 run_self_hosted.go:172] Waiting for the kube-apiserver to be ready ...
I0915 20:27:11.358343 4434 interface.go:26] Installing "kube-proxy" ...
I0915 20:27:11.359003 4434 interface.go:26] Installing "kube-dns" ...
I0915 20:27:11.359032 4434 interface.go:26] Installing "openshift-apiserver" ...
I0915 20:27:11.359087 4434 apply_template.go:83] Installing "openshift-apiserver"
I0915 20:27:11.360477 4434 apply_template.go:83] Installing "kube-proxy"
I0915 20:27:11.360903 4434 apply_template.go:83] Installing "kube-dns"
I0915 20:27:15.329461 4434 interface.go:41] Finished installing "kube-proxy" "kube-dns" "openshift-apiserver"
Error: timed out waiting for the condition
can we increase that timeout manually? Restarting brings back the same error.
Most helpful comment
I had the same issue on CentOS 7 and oc tools 3.11 but after adding a new firewalld zone as per documentation (https://github.com/openshift/origin/blob/release-3.11/docs/cluster_up_down.md#linux), everything worked fine.