{"action":"opened","issue":{"url":"https://api.github.com/repos/projectcalico/calico-containers/issues/920","repository_url":"https://api.github.com/repos/projectcalico/calico-containers","labels_url":"https://api.github.com/repos/projectcalico/calico-containers/issues/920/labels{/name}","comments_url":"https://api.github.com/repos/projectcalico/calico-containers/issues/920/comments","events_url":"https://api.github.com/repos/projectcalico/calico-containers/issues/920/events","html_url":"https://github.com/projectcalico/calico-containers/issues/920","id":148148632,"number":920,"title":"Failed calico-node start exits with success status ","user":{"login":"djosborne","id":3444362,"avatar_url":"https://avatars.githubusercontent.com/u/3444362?v=3","gravatar_id":"","url":"https://api.github.com/users/djosborne","html_url":"https://github.com/djosborne","followers_url":"https://api.github.com/users/djosborne/followers","following_url":"https://api.github.com/users/djosborne/following{/other_user}","gists_url":"https://api.github.com/users/djosborne/gists{/gist_id}","starred_url":"https://api.github.com/users/djosborne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/djosborne/subscriptions","organizations_url":"https://api.github.com/users/djosborne/orgs","repos_url":"https://api.github.com/users/djosborne/repos","events_url":"https://api.github.com/users/djosborne/events{/privacy}","received_events_url":"https://api.github.com/users/djosborne/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-13T18:44:49Z","updated_at":"2016-04-13T18:44:49Z","closed_at":null,"body":"I'm launching calico-node using calicoctl in mesos. My tasks fail because they're binding to an IP which is already in use by Calico (which is a mesos problem that I'll need to resolve seperately myself).\r\n\r\nHowever, calicoctl is exiting with status code 0 when this happens, instead of an error. This is bug.\r\n\r\nThe implications of this is that my mesos tasks think they've completed successfully and reporting that they've `FINISHED` instead of `FAILED`:\r\n```\r\nsh -c './calicoctl node --detach=false'\r\nForked command at 4309\r\nRunning Docker container with the following command:\r\n\r\ndocker run --restart=always --net=host --privileged --name=calico-node -e HOSTNAME=djo-dcos-agent-3.gulfstream.datcon.co.uk -e IP= -e IP6= -e CALICO_NETWORKING=true -e AS= -e NO_DEFAULT_POOLS= -e ETCD_AUTHORITY=127.0.0.1:2379 -e ETCD_SCHEME=http -v /var/log/calico:/var/log/calico -v /var/run/calico:/var/run/calico calico/node:v0.18.0\r\n\r\nCalico node is running with id: b0c21b9831319d2ea7f0a6c26cfd262760f8241a847c81053eb10f9654d4f013\r\nWaiting for successful startup\r\nNo IP provided. Using detected IP: 198.51.100.3\r\nERROR: IP address 198.51.100.3 is already in use by host djo-dcos-agent-2.gulfstream.datcon.co.uk. Calico requires each compute host to have a unique IP. If this is your first time running the Calico node on this host, ensure that another host is not already using the same IP address.\r\nCalico node failed to start\r\nCommand exited with status 0 (pid: 4309)\r\n```\r\n\r\n"}}