Thanks - I tried the bundle on Local and AWS – but I get similar errors on both - hook failed: "etcd-relation-changed"
Local - unit-kubernetes-0[895]: 2016-02-17 05:56:46 INFO unit.kubernetes/0.etcd-relation-joined logger.go:40 subprocess.CalledProcessError: Command '['scripts/bootstrap_docker.sh', 'http://10.0.3.56:4001']' returned non-zero exit status 125 unit-kubernetes-0[895]: 2016-02-17 05:56:46 ERROR juju.worker.uniter.operation runhook.go:107 hook "etcd-relation-joined" failed: exit status 1 AWS - unit-kubernetes-0[3008]: 2016-02-17 06:30:32 INFO unit.kubernetes/0.etcd-relation-changed logger.go:40 subprocess.CalledProcessError: Command '['scripts/bootstrap_docker.sh', 'http://172.x.x.x:4001']' returned non-zero exit status 125 unit-kubernetes-0[3008]: 2016-02-17 06:30:32 ERROR juju.worker.uniter.operation runhook.go:107 hook "etcd-relation-changed" failed: exit status 1 From: Charles Butler <[email protected]<mailto:[email protected]>> Date: Tuesday, February 16, 2016 at 6:23 AM To: Akhil Arora <[email protected]<mailto:[email protected]>> Cc: juju <[email protected]<mailto:[email protected]>> Subject: Re: error bootstrapping kubernetes Greetings Akhil, This is an unfortunate issue. This looks like its affecting the older work we've published upstream into the kubernetes repository. Are you working on developing Kubernetes core and would like to use juju to stand that up? If not I would like to recommend you take a look at our newer work surrounding Kubernetes - (link forthcoming) This bundle will deploy the same solution in a slightly different configuration. Namely we're leveraging hyperkube to deliver the kubernetes application. https://jujucharms.com/u/kubernetes/kubernetes-cluster/bundle/18 All the best, Charles Butler <[email protected]<mailto:[email protected]>> - Juju Charmer Come see the future of modeling your datacenter: http://jujucharms.com<http://jujucharms.com/> On Fri, Feb 12, 2016 at 4:28 PM, Akhil Arora (akhiaror) <[email protected]<mailto:[email protected]>> wrote: Hi I was trying to bootstrap kubernetes (current master) on AWS using juju - KUBERNETES_PROVIDER=juju cluster/kube-up.sh But it fails at this step - 2016-02-12 10:29:18 Using deployment kubernetes-local 2016-02-12 10:29:18 Starting deployment of kubernetes-local 2016-02-12 10:29:18 Deploying services... 2016-02-12 10:30:27 Config specifies num units for subordinate: flannel-docker 2016-02-12 10:31:30 Config specifies num units for subordinate: kubernetes 2016-02-12 10:31:31 The following units had errors: unit: docker/1: machine: 2 agent-state: error details: hook failed: "config-changed" unit: docker/0: machine: 1 agent-state: error details: hook failed: "config-changed" 2016-02-12 10:31:31 Deployment stopped. run time: 133.01 Juju debug-log -n 10 shows unit-docker-1[2985]: 2016-02-12 21:24:06 INFO unit.docker/1.config-changed logger.go:40 subprocess.CalledProcessError: Command '['ansible-playbook', '-c', 'local', '-v', 'playbooks/site.yaml', '--tags', 'config-changed', '--module-path=/var/lib/juju/agents/unit-docker-1/charm/modules']' returned non-zero exit status 2 unit-docker-1[2985]: 2016-02-12 21:24:06 ERROR juju.worker.uniter.operation runhook.go:107 hook "config-changed" failed: exit status 1 Any ideas? Should I be using a specific kube release? Thanks in advance -- Juju mailing list [email protected]<mailto:[email protected]> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
