{"action":"closed","issue":{"url":"https://api.github.com/repos/coreos/bugs/issues/53","labels_url":"https://api.github.com/repos/coreos/bugs/issues/53/labels{/name}","comments_url":"https://api.github.com/repos/coreos/bugs/issues/53/comments","events_url":"https://api.github.com/repos/coreos/bugs/issues/53/events","html_url":"https://github.com/coreos/bugs/issues/53","id":35823062,"number":53,"title":"Fleet fails to schedule units","user":{"login":"BrianHicks","id":355401,"avatar_url":"https://avatars.githubusercontent.com/u/355401?v=3","gravatar_id":"","url":"https://api.github.com/users/BrianHicks","html_url":"https://github.com/BrianHicks","followers_url":"https://api.github.com/users/BrianHicks/followers","following_url":"https://api.github.com/users/BrianHicks/following{/other_user}","gists_url":"https://api.github.com/users/BrianHicks/gists{/gist_id}","starred_url":"https://api.github.com/users/BrianHicks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BrianHicks/subscriptions","organizations_url":"https://api.github.com/users/BrianHicks/orgs","repos_url":"https://api.github.com/users/BrianHicks/repos","events_url":"https://api.github.com/users/BrianHicks/events{/privacy}","received_events_url":"https://api.github.com/users/BrianHicks/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/coreos/bugs/labels/component/fleet","name":"component/fleet","color":"0052cc"},{"url":"https://api.github.com/repos/coreos/bugs/labels/kind/bug","name":"kind/bug","color":"FF0000"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":22,"created_at":"2014-06-16T18:29:24Z","updated_at":"2015-12-02T22:06:46Z","closed_at":"2015-12-02T22:06:46Z","body":"With the attached unit file and log, Fleet on EC2 (Beta channel) fails to start the unit file.\r\n\r\nhttps://gist.github.com/BrianHicks/8bd436bbce429d6ee5b7\r\n\r\n*Steps to reproduce:*\r\n\r\n 1. submit the attached unit file with `fleetctl start sample-1.unit.service`\r\n 2. check the status of the unit with `fleetctl list-units` - it will never start, just hang out as \"inactive\"\r\n 3. check the fleet logs with `journalctl -u fleet` and see the attached logging information."}}