{"action":"created","issue":{"url":"https://api.github.com/repos/pires/kubernetes-vagrant-coreos-cluster/issues/102","labels_url":"https://api.github.com/repos/pires/kubernetes-vagrant-coreos-cluster/issues/102/labels{/name}","comments_url":"https://api.github.com/repos/pires/kubernetes-vagrant-coreos-cluster/issues/102/comments","events_url":"https://api.github.com/repos/pires/kubernetes-vagrant-coreos-cluster/issues/102/events","html_url":"https://github.com/pires/kubernetes-vagrant-coreos-cluster/issues/102","id":80199917,"number":102,"title":"failure with vmware_fusion on OS X","user":{"login":"CaptTofu","id":106670,"avatar_url":"https://avatars.githubusercontent.com/u/106670?v=3","gravatar_id":"","url":"https://api.github.com/users/CaptTofu","html_url":"https://github.com/CaptTofu","followers_url":"https://api.github.com/users/CaptTofu/followers","following_url":"https://api.github.com/users/CaptTofu/following{/other_user}","gists_url":"https://api.github.com/users/CaptTofu/gists{/gist_id}","starred_url":"https://api.github.com/users/CaptTofu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CaptTofu/subscriptions","organizations_url":"https://api.github.com/users/CaptTofu/orgs","repos_url":"https://api.github.com/users/CaptTofu/repos","events_url":"https://api.github.com/users/CaptTofu/events{/privacy}","received_events_url":"https://api.github.com/users/CaptTofu/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-05-24T16:14:01Z","updated_at":"2015-05-25T16:59:15Z","closed_at":null,"body":"Hi there! I can't get this cluster working. It was working flawlessly last weekend. I'm not sure what changeset makes it fail.\r\n\r\nSometimes, it fails because the resolver isn't set up on any of the virtual machines so none of the services that rely on using wget to obtain binaries work. \r\n\r\nOther times, I get this failure with setup-network-service (a 403 from github/s3)\r\n\r\nPatricks-MacBook-Pro:kubernetes-vagrant-coreos-cluster patg$ vagrant ssh master\r\nCoreOS valpha (681.0.0)\r\nUpdate Strategy: No Reboots\r\nFailed Units: 1\r\n  setup-network-environment.service\r\n\r\n\r\ncore@master ~ $ systemctl status setup-network-environment.service\r\n● setup-network-environment.service - Setup Network Environment\r\n   Loaded: loaded (/etc/systemd/system/setup-network-environment.service; static; vendor preset: disabled)\r\n   Active: failed (Result: exit-code) since Sun 2015-05-24 16:10:05 ; 6s ago\r\n     Docs: https://github.com/kelseyhightower/setup-network-environment\r\n  Process: 2449 ExecStart=/opt/bin/setup-network-environment (code=exited, status=0/SUCCESS)\r\n  Process: 2445 ExecStartPre=/usr/bin/chmod +x /opt/bin/setup-network-environment (code=exited, status=0/SUCCESS)\r\n  Process: 2485 ExecStartPre=/usr/bin/wget -N -P /opt/bin https://github.com/kelseyhightower/setup-network-environment/releases/download/v1.0.0/setup-network-environment (code=exited, status=8)\r\n  Process: 2482 ExecStartPre=/usr/bin/mkdir -p /opt/bin (code=exited, status=0/SUCCESS)\r\n Main PID: 2449 (code=exited, status=0/SUCCESS)\r\n\r\nMay 24 16:10:05 master wget[2485]: Location: https://s3.amazonaws.com/github-cloud/releases/24030064/c925b05e-3c44-11e4-...\r\nMay 24 16:10:05 master wget[2485]: --2015-05-24 16:10:05--  https://s3.amazonaws.com/github-cloud/releases/24030064/c925...\r\nMay 24 16:10:05 master wget[2485]: Resolving s3.amazonaws.com... 54.231.14.72\r\nMay 24 16:10:05 master wget[2485]: Connecting to s3.amazonaws.com|54.231.14.72|:443... connected.\r\nMay 24 16:10:05 master wget[2485]: HTTP request sent, awaiting response... 403 Forbidden\r\nMay 24 16:10:05 master wget[2485]: 2015-05-24 16:10:05 ERROR 403: Forbidden.\r\nMay 24 16:10:05 master systemd[1]: setup-network-environment.service: control process exited, code=exited status=8\r\nMay 24 16:10:05 master systemd[1]: Failed to start Setup Network Environment.\r\nMay 24 16:10:05 master systemd[1]: Unit setup-network-environment.service entered failed state.\r\nMay 24 16:10:05 master systemd[1]: setup-network-environment.service failed.\r\nHint: Some lines were ellipsized, use -l to show in full.\r\n\r\n\r\n\r\ncore@master ~ $ /usr/bin/wget -N -P /opt/bin https://github.com/kelseyhightower/setup-network-environment/releases/download/v1.0.0/setup-network-environment\r\n--2015-05-24 16:11:33--  https://github.com/kelseyhightower/setup-network-environment/releases/download/v1.0.0/setup-network-environment\r\nResolving github.com... 192.30.252.131\r\nConnecting to github.com|192.30.252.131|:443... connected.\r\nHTTP request sent, awaiting response... 302 Found\r\nLocation: https://s3.amazonaws.com/github-cloud/releases/24030064/c925b05e-3c44-11e4-83a0-2e78b7fd556a?response-content-disposition=attachment%3B%20filename%3Dsetup-network-environment&response-content-type=application/octet-stream&AWSAccessKeyId=AKIAISTNZFOVBIJMK3TQ&Expires=1432483953&Signature=WNxk5676o6Vt7JKsebVmCYzbImw%3D [following]\r\n--2015-05-24 16:11:33--  https://s3.amazonaws.com/github-cloud/releases/24030064/c925b05e-3c44-11e4-83a0-2e78b7fd556a?response-content-disposition=attachment%3B%20filename%3Dsetup-network-environment&response-content-type=application/octet-stream&AWSAccessKeyId=AKIAISTNZFOVBIJMK3TQ&Expires=1432483953&Signature=WNxk5676o6Vt7JKsebVmCYzbImw%3D\r\nResolving s3.amazonaws.com... 54.231.96.120\r\nConnecting to s3.amazonaws.com|54.231.96.120|:443... connected.\r\nHTTP request sent, awaiting response... 403 Forbidden\r\n2015-05-24 16:11:33 ERROR 403: Forbidden.\r\n"},"comment":{"url":"https://api.github.com/repos/pires/kubernetes-vagrant-coreos-cluster/issues/comments/105270004","html_url":"https://github.com/pires/kubernetes-vagrant-coreos-cluster/issues/102#issuecomment-105270004","issue_url":"https://api.github.com/repos/pires/kubernetes-vagrant-coreos-cluster/issues/102","id":105270004,"user":{"login":"pires","id":1752631,"avatar_url":"https://avatars.githubusercontent.com/u/1752631?v=3","gravatar_id":"","url":"https://api.github.com/users/pires","html_url":"https://github.com/pires","followers_url":"https://api.github.com/users/pires/followers","following_url":"https://api.github.com/users/pires/following{/other_user}","gists_url":"https://api.github.com/users/pires/gists{/gist_id}","starred_url":"https://api.github.com/users/pires/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pires/subscriptions","organizations_url":"https://api.github.com/users/pires/orgs","repos_url":"https://api.github.com/users/pires/repos","events_url":"https://api.github.com/users/pires/events{/privacy}","received_events_url":"https://api.github.com/users/pires/received_events","type":"User","site_admin":false},"created_at":"2015-05-25T16:59:15Z","updated_at":"2015-05-25T16:59:15Z","body":"I use VirtualBox and I have no such issues.\r\n\r\n```\r\nlittlepires:kubernetes-vagrant-coreos-cluster pires$ NUM_INSTANCES=1 vagrant up\r\nBringing machine 'master' up with 'virtualbox' provider...\r\nBringing machine 'node-01' up with 'virtualbox' provider...\r\n==> master: Running triggers before up...\r\n==> master: Setting Kubernetes version 0.17.0\r\n==> master: Configuring Kubernetes cluster DNS...\r\n==> master: Importing base box 'coreos-alpha'...\r\n==> master: Matching MAC address for NAT networking...\r\n==> master: Checking if box 'coreos-alpha' is up to date...\r\n==> master: Setting the name of the VM: kubernetes-vagrant-coreos-cluster_master_1432567583441_13545\r\n==> master: Clearing any previously set network interfaces...\r\n==> master: Preparing network interfaces based on configuration...\r\n    master: Adapter 1: nat\r\n    master: Adapter 2: hostonly\r\n==> master: Forwarding ports...\r\n    master: 22 => 2222 (adapter 1)\r\n==> master: Running 'pre-boot' VM customizations...\r\n==> master: Booting VM...\r\n==> master: Waiting for machine to boot. This may take a few minutes...\r\n    master: SSH address: 127.0.0.1:2222\r\n    master: SSH username: core\r\n    master: SSH auth method: private key\r\n    master: Warning: Connection timeout. Retrying...\r\n==> master: Machine booted and ready!\r\n==> master: Setting hostname...\r\n==> master: Configuring and enabling network interfaces...\r\n==> master: Running provisioner: file...\r\n==> master: Running provisioner: shell...\r\n    master: Running: inline script\r\n==> master: Running triggers after up...\r\n==> master: Sanitizing stuff...\r\nIdentity added: /Users/pires/.vagrant.d/insecure_private_key (/Users/pires/.vagrant.d/insecure_private_key)\r\n==> master: Installing kubectl for the kubernetes version we just bootstrapped...\r\nDownloading and installing darwin version of 'kubectl' v0.17.0 into /usr/local/bin. This may take a couple minutes, depending on your internet speed..\r\nPassword:\r\nSetting environment variables..\r\n==> master: Waiting for Kubernetes master to become ready...\r\nreplicationcontrollers/kube-dns\r\nservices/kube-dns\r\n==> node-01: Importing base box 'coreos-alpha'...\r\n==> node-01: Matching MAC address for NAT networking...\r\n==> node-01: Checking if box 'coreos-alpha' is up to date...\r\n==> node-01: Setting the name of the VM: kubernetes-vagrant-coreos-cluster_node-01_1432567767447_54496\r\n==> node-01: Fixed port collision for 22 => 2222. Now on port 2200.\r\n==> node-01: Clearing any previously set network interfaces...\r\n==> node-01: Preparing network interfaces based on configuration...\r\n    node-01: Adapter 1: nat\r\n    node-01: Adapter 2: hostonly\r\n==> node-01: Forwarding ports...\r\n    node-01: 22 => 2200 (adapter 1)\r\n==> node-01: Running 'pre-boot' VM customizations...\r\n==> node-01: Booting VM...\r\n==> node-01: Waiting for machine to boot. This may take a few minutes...\r\n    node-01: SSH address: 127.0.0.1:2200\r\n    node-01: SSH username: core\r\n    node-01: SSH auth method: private key\r\n    node-01: Warning: Connection timeout. Retrying...\r\n==> node-01: Machine booted and ready!\r\n==> node-01: Setting hostname...\r\n==> node-01: Configuring and enabling network interfaces...\r\n==> node-01: Running provisioner: file...\r\n==> node-01: Running provisioner: shell...\r\n    node-01: Running: inline script\r\n==> node-01: Running triggers after up...\r\n==> node-01: Waiting for Kubernetes minion [node-01] to become ready...\r\nlittlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get minions\r\nNAME           LABELS        STATUS\r\n172.17.8.102   Schedulable   <none>    Ready\r\nlittlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get pods\r\nPOD              IP           CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED\r\nkube-dns-8x645   10.244.5.2   etcd           gcr.io/google_containers/etcd:2.0.9              172.17.8.102/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   About an hour\r\n                              kube2sky       gcr.io/google_containers/kube2sky:1.5\r\n                              skydns         gcr.io/google_containers/skydns:2015-03-11-001\r\n```"}}