{"action":"opened","issue":{"url":"https://api.github.com/repos/roboconf/roboconf-platform/issues/360","labels_url":"https://api.github.com/repos/roboconf/roboconf-platform/issues/360/labels{/name}","comments_url":"https://api.github.com/repos/roboconf/roboconf-platform/issues/360/comments","events_url":"https://api.github.com/repos/roboconf/roboconf-platform/issues/360/events","html_url":"https://github.com/roboconf/roboconf-platform/issues/360","id":91267549,"number":360,"title":"Messaging in agent is never configured on IaaS VMs (user-data not propagated)","user":{"login":"gibello","id":1230975,"avatar_url":"https://avatars.githubusercontent.com/u/1230975?v=3","gravatar_id":"","url":"https://api.github.com/users/gibello","html_url":"https://github.com/gibello","followers_url":"https://api.github.com/users/gibello/followers","following_url":"https://api.github.com/users/gibello/following{/other_user}","gists_url":"https://api.github.com/users/gibello/gists{/gist_id}","starred_url":"https://api.github.com/users/gibello/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gibello/subscriptions","organizations_url":"https://api.github.com/users/gibello/orgs","repos_url":"https://api.github.com/users/gibello/repos","events_url":"https://api.github.com/users/gibello/events{/privacy}","received_events_url":"https://api.github.com/users/gibello/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/roboconf/roboconf-platform/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-06-26T14:36:35Z","updated_at":"2015-06-26T14:36:35Z","closed_at":null,"body":"When the DM deploys a new VM on a IaaS (eg. EC2), it passes configuration information across user-data. These informations should be used to configure the agent's messaging... but they are not, and the messaging points to localhost (default) although the user-data are properly updated (on EC2, can be checked by browsing http://169.254.169.254/latest/user-data on the VM).\r\nAs a consequence, the VM never gets in deployed/started state on the DM side (and remains \"being deployed\" forever), because no message arrives."}}