Error with ./hack/local-up-cluster.sh

2/15/2016

I have been trying to get my local cluster up with kubernetes. I have created the binaries and I am running the script by the name of ./hack/local-up-cluster.sh. When I run the script, I am getting this error:

root@ubuntu1604:~/kubernetes# ./hack/local-up-cluster.sh 
+++ [0215 00:22:00] Building go targets for linux/ppc64le:
    cmd/kube-apiserver
    cmd/kube-controller-manager
    cmd/kube-proxy
    cmd/kubectl
    cmd/kubelet
    plugin/cmd/kube-scheduler
+++ [0215 00:22:03] Placing binaries
curl: (7) Failed to connect to 127.0.0.1 port 8080: Connection refused
API SERVER port is free, proceeding...
Detected host and ready to start services.  Doing some housekeeping first...
Using GO_OUT /root/kubernetes/_output/local/bin/linux/ppc64le
Starting services now!
Starting etcd
etcd -data-dir /tmp/tmp.5C5e2WqxLN --bind-addr 127.0.0.1:4001 >/dev/null 2>/dev/null
Waiting for etcd to come up.
+++ [0215 00:22:03] On try 1, etcd: : 
{"action":"set","node":{"key":"/_test","value":"","modifiedIndex":3,"createdIndex":3}}
Waiting for apiserver to come up
!!! [0215 00:22:13] Timed out waiting for apiserver:  to answer at http://127.0.0.1:8080/api/v1/pods; tried 10 waiting 1 between each
Cleaning up...

Any idea how should I debug this?

-- Pensu
kubernetes

2 Answers

2/15/2016

It seems like your api-server is not working for some reason. Check for api-server logs at /tmp/kube-apiserver.log

-- Dimuthu
Source: StackOverflow

2/18/2016

Answering your question from the comments. There are 4 primary types of tests in the codebase:

  1. Unit tests (hack/test-go.sh): don't require local cluster to run; can be run while local cluster is running
  2. Integration tests (hack/test-integration.sh): local cluster must not be running while these tests are
  3. Command tests (hack/test-cmd.sh): local cluster must not be running while these tests are
  4. E2E tests (test/e2e/*.go): a cluster, local or remote is required for these tests
-- Paul Morie
Source: StackOverflow