{"action":"created","issue":{"url":"https://api.github.com/repos/projectcalico/calico/issues/1013","repository_url":"https://api.github.com/repos/projectcalico/calico","labels_url":"https://api.github.com/repos/projectcalico/calico/issues/1013/labels{/name}","comments_url":"https://api.github.com/repos/projectcalico/calico/issues/1013/comments","events_url":"https://api.github.com/repos/projectcalico/calico/issues/1013/events","html_url":"https://github.com/projectcalico/calico/issues/1013","id":249200415,"number":1013,"title":"Calico doesn't start correctly on minikube","user":{"login":"ceridwen","id":8268008,"avatar_url":"https://avatars1.githubusercontent.com/u/8268008?v=4","gravatar_id":"","url":"https://api.github.com/users/ceridwen","html_url":"https://github.com/ceridwen","followers_url":"https://api.github.com/users/ceridwen/followers","following_url":"https://api.github.com/users/ceridwen/following{/other_user}","gists_url":"https://api.github.com/users/ceridwen/gists{/gist_id}","starred_url":"https://api.github.com/users/ceridwen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ceridwen/subscriptions","organizations_url":"https://api.github.com/users/ceridwen/orgs","repos_url":"https://api.github.com/users/ceridwen/repos","events_url":"https://api.github.com/users/ceridwen/events{/privacy}","received_events_url":"https://api.github.com/users/ceridwen/received_events","type":"User","site_admin":false},"labels":[{"id":443863604,"url":"https://api.github.com/repos/projectcalico/calico/labels/priority/P2","name":"priority/P2","color":"fbca04","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/projectcalico/calico/milestones/14","html_url":"https://github.com/projectcalico/calico/milestone/14","labels_url":"https://api.github.com/repos/projectcalico/calico/milestones/14/labels","id":2686370,"number":14,"title":"Calico v2.6.0","description":"Issues and PRs being considered for Calico v2.5.0","creator":{"login":"caseydavenport","id":1944093,"avatar_url":"https://avatars3.githubusercontent.com/u/1944093?v=4","gravatar_id":"","url":"https://api.github.com/users/caseydavenport","html_url":"https://github.com/caseydavenport","followers_url":"https://api.github.com/users/caseydavenport/followers","following_url":"https://api.github.com/users/caseydavenport/following{/other_user}","gists_url":"https://api.github.com/users/caseydavenport/gists{/gist_id}","starred_url":"https://api.github.com/users/caseydavenport/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/caseydavenport/subscriptions","organizations_url":"https://api.github.com/users/caseydavenport/orgs","repos_url":"https://api.github.com/users/caseydavenport/repos","events_url":"https://api.github.com/users/caseydavenport/events{/privacy}","received_events_url":"https://api.github.com/users/caseydavenport/received_events","type":"User","site_admin":false},"open_issues":17,"closed_issues":2,"state":"open","created_at":"2017-08-07T18:55:27Z","updated_at":"2017-08-15T22:36:35Z","due_on":null,"closed_at":null},"comments":10,"created_at":"2017-08-10T00:35:18Z","updated_at":"2017-08-17T14:39:09Z","closed_at":"2017-08-14T15:53:55Z","body":"## Expected Behavior\r\n\r\nInstalling Calico on minikube should start both containers in the calico-node pod.\r\n\r\n## Current Behavior\r\n\r\nI recently upgraded minikube to 0.21, which means deleting the cluster and reinstalling it.  When I tried to reinstall Calico, the calico-node container in the calico node pod never comes up, and networking is broken.\r\n\r\nI'm running minikube with `minikube start --network-plugin=cni --host-only-cidr=192.168.0.0/16`, using virtualbox as the driver.\r\n\r\nThe logs for calico-node contain entries like:\r\n\r\n```\r\n2017-08-10 00:28:51.825 [PANIC][2269] ipsets.go 283: Failed to update IP sets after mutliple retries. family=\"inet\"\r\npanic: (*logrus.Entry) (0x16df120,0xc4204744b0)\r\ngithub.com/projectcalico/felix/vendor/github.com/sirupsen/logrus.(*Entry).Panic(0xc42041a870, 0xc4208d5ee0, 0x1, 0x1)\r\n```\r\n\r\n```\r\n2017-08-10 00:29:15.131 [WARNING][2972] ipsets.go 271: Failed to update IP sets. Marking dataplane for resync. error=exit status 1 family=\"inet\"\r\n2017-08-10 00:29:15.270 [WARNING][2972] ipsets.go 621: Failed to complete ipset restore, IP sets may be out-of-sync. closeErr=<nil> commitErr=<nil> family=\"inet\" flushErr=<nil> input=\"create cali4tall-hosts hash:ip family inet maxelem 1048576\\nadd cali4tall-hosts 10.1.0.1\\nswap cali4-all-hosts cali4tall-hosts\\ndestroy cali4tall-hosts\\ncreate cali4-all-ipam-pools hash:net family inet maxelem 1048576\\ncreate cali4tall-ipam-pools hash:net family inet maxelem 1048576\\nadd cali4tall-ipam-pools 192.168.0.0/16\\nswap cali4-all-ipam-pools cali4tall-ipam-pools\\ndestroy cali4tall-ipam-pools\\ncreate cali4-masq-ipam-pools hash:net family inet maxelem 1048576\\ncreate cali4tmasq-ipam-pools hash:net family inet maxelem 1048576\\nadd cali4tmasq-ipam-pools 192.168.0.0/16\\nswap cali4-masq-ipam-pools cali4tmasq-ipam-pools\\ndestroy cali4tmasq-ipam-pools\\nCOMMIT\\n\" processErr=exit status 1 stderr=\"ipset v6.32: Error in line 5: Kernel error received: set type not supported\\n\" stdout=\"\" writeErr=<nil>\r\n2017-08-10 00:29:15.270 [WARNING][2972] ipsets.go 271: Failed to update IP sets. Marking dataplane for resync. error=exit status 1 family=\"inet\"\r\n```\r\n\r\n## Steps to Reproduce (for bugs)\r\n\r\n1. Install minikube with homebrew (https://github.com/kubernetes/minikube).\r\n2. Install Virtualbox (https://www.virtualbox.org/wiki/Downloads).\r\n<!--- Provide a link to a live example, or an unambiguous set of steps to -->\r\n<!--- reproduce this bug. Include code to reproduce, if relevant -->\r\n3. Start minikube with `minikube start --network-plugin=cni --host-only-cidr=192.168.0.0/16`\r\n4. Install calico with `kubectl apply -f https://docs.projectcalico.org/v2.4/getting-started/kubernetes/installation/hosted/kubernetes-datastore/calico-networking/1.6/calico.yaml`\r\n\r\n## Context\r\n\r\nI'm trying to create a working development environment for testing network policy on my local machine so I don't have to depend on a remote cluster for doing development work.  I know this is beta software, but it *was* working so I suspect that a change in Calico or minikube is responsible.\r\n\r\n## Your Environment\r\n\r\nCalico: v2.4\r\nminikube:  v0.21.0, Kubernetes version 1.7.0\r\nOS: Mac OS X 10.12.6\r\n"},"comment":{"url":"https://api.github.com/repos/projectcalico/calico/issues/comments/323093271","html_url":"https://github.com/projectcalico/calico/issues/1013#issuecomment-323093271","issue_url":"https://api.github.com/repos/projectcalico/calico/issues/1013","id":323093271,"user":{"login":"tmjd","id":14025438,"avatar_url":"https://avatars3.githubusercontent.com/u/14025438?v=4","gravatar_id":"","url":"https://api.github.com/users/tmjd","html_url":"https://github.com/tmjd","followers_url":"https://api.github.com/users/tmjd/followers","following_url":"https://api.github.com/users/tmjd/following{/other_user}","gists_url":"https://api.github.com/users/tmjd/gists{/gist_id}","starred_url":"https://api.github.com/users/tmjd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tmjd/subscriptions","organizations_url":"https://api.github.com/users/tmjd/orgs","repos_url":"https://api.github.com/users/tmjd/repos","events_url":"https://api.github.com/users/tmjd/events{/privacy}","received_events_url":"https://api.github.com/users/tmjd/received_events","type":"User","site_admin":false},"created_at":"2017-08-17T14:39:08Z","updated_at":"2017-08-17T14:39:08Z","body":"@gtirloni You might need to add a `--host-only-cidr 172.17.17.1/24` to the args @sbueringer has suggested.  The `--host-only-cidr` is the address and CIDR that will be used for the vboxnet interface on your host machine that will be connected to the minikube VM (that's the behavior I see).\r\nI'm suggesting you need that because I'm assuming your `kubectl get nodes` is running on your host and if it is trying to hit the VM at 192.168.99.100 and you have a ClusterCIDR of 192.168.0.0/16, I would expect things to not play nicely.\r\n\r\nTBH, I'm not sure that what I've described is your problem though, unless those connection refused messages line up with those localkube/kubelet panics.  You don't happen to have multiple VMs running that have that 192.168.99.100 address do you?  That kind of intermittent behavior makes me think of issues I've had when I've tried to bring up multiple instances of vagrant machines all trying to use the same IP address."}}
{"actor":{"display_login":"tmjd"}}