Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OC Cluster never goes up Error: timed out waiting for the condition #23840

Open
stramzik opened this issue Sep 23, 2019 · 2 comments

Comments

@stramzik
Copy link

commented Sep 23, 2019

HI All,

When ever i try to get the cluster up using "oc cluster up"
Below is the error I get

[mano@mano ~]$ 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 ...
I0923 13:40:32.364326   15396 config.go:40] Running "create-master-config"
I0923 13:40:59.938492   15396 config.go:46] Running "create-node-config"
I0923 13:41:10.721711   15396 flags.go:30] Running "create-kubelet-flags"
I0923 13:41:18.241285   15396 run_kubelet.go:49] Running "start-kubelet"
I0923 13:41:23.016238   15396 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0923 13:46:23.023479   15396 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

Found few article but cant find a solution please guide me if there is a solution for the issue

Version

OC version

[mano@mano` ~]$ oc version
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Additional Information
[Note] Determining if client configuration exists for client/cluster diagnostics
[Note] No client configuration specified; skipping client and cluster diagnostics.

ERROR: [CED3001 from controller openshift/origin/pkg/oc/cli/admin/diagnostics/util/util.go]
       Encountered fatal error while building diagnostics: Requested diagnostic(s) skipped; nothing to run. See --help and consider setting flags or providing config to enable running.
       
[Note] Summary of diagnostics execution (version v3.11.0+0cbc58b):
[Note] Errors seen: 1
[mano@mano ~]$ 
@rniksch

This comment has been minimized.

Copy link

commented Sep 24, 2019

oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Seeing same issue on centos 7

@stramzik

This comment has been minimized.

Copy link
Author

commented Sep 27, 2019

Can someone please help me with this please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.