{"action":"opened","issue":{"url":"https://api.github.com/repos/edurange/edurange/issues/3","labels_url":"https://api.github.com/repos/edurange/edurange/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/edurange/edurange/issues/3/comments","events_url":"https://api.github.com/repos/edurange/edurange/issues/3/events","html_url":"https://github.com/edurange/edurange/issues/3","id":59598755,"number":3,"title":"Cloud Fails to Boot","user":{"login":"NickStephens","id":1915867,"avatar_url":"https://avatars.githubusercontent.com/u/1915867?v=3","gravatar_id":"","url":"https://api.github.com/users/NickStephens","html_url":"https://github.com/NickStephens","followers_url":"https://api.github.com/users/NickStephens/followers","following_url":"https://api.github.com/users/NickStephens/following{/other_user}","gists_url":"https://api.github.com/users/NickStephens/gists{/gist_id}","starred_url":"https://api.github.com/users/NickStephens/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/NickStephens/subscriptions","organizations_url":"https://api.github.com/users/NickStephens/orgs","repos_url":"https://api.github.com/users/NickStephens/repos","events_url":"https://api.github.com/users/NickStephens/events{/privacy}","received_events_url":"https://api.github.com/users/NickStephens/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-03T05:54:57Z","updated_at":"2015-03-03T05:54:57Z","closed_at":null,"body":"While testing a scenario on cloud.edurange.org. I continued to get the Runtime Error 'clouds failed to boot'. I was testing the new scenario 'ROP'. I was able to boot it once successfully, after that I destroyed the scenario without unbooting it. I then tried to boot ROP once more after making changes to its YML file. I got the error 'clouds failed to boot'. I then went into the EC2 console and manually terminated the instance I forgot to unboot and released the Elastic IP addresses which were bound to the old instance. This seemed to yield no results and new ROP scenarios continually fail to boot with the same error message. Why does this happen? This seems like a bug."}}