{"action":"created","issue":{"url":"https://api.github.com/repos/aws/amazon-ecs-agent/issues/313","repository_url":"https://api.github.com/repos/aws/amazon-ecs-agent","labels_url":"https://api.github.com/repos/aws/amazon-ecs-agent/issues/313/labels{/name}","comments_url":"https://api.github.com/repos/aws/amazon-ecs-agent/issues/313/comments","events_url":"https://api.github.com/repos/aws/amazon-ecs-agent/issues/313/events","html_url":"https://github.com/aws/amazon-ecs-agent/issues/313","id":134065153,"number":313,"title":"AWS console way out of sync with instance state","user":{"login":"workybee","id":13958914,"avatar_url":"https://avatars.githubusercontent.com/u/13958914?v=3","gravatar_id":"","url":"https://api.github.com/users/workybee","html_url":"https://github.com/workybee","followers_url":"https://api.github.com/users/workybee/followers","following_url":"https://api.github.com/users/workybee/following{/other_user}","gists_url":"https://api.github.com/users/workybee/gists{/gist_id}","starred_url":"https://api.github.com/users/workybee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/workybee/subscriptions","organizations_url":"https://api.github.com/users/workybee/orgs","repos_url":"https://api.github.com/users/workybee/repos","events_url":"https://api.github.com/users/workybee/events{/privacy}","received_events_url":"https://api.github.com/users/workybee/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/aws/amazon-ecs-agent/labels/pending%20release","name":"pending release","color":"0052cc"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":28,"created_at":"2016-02-16T18:51:47Z","updated_at":"2016-02-24T14:19:44Z","closed_at":null,"body":"The AWS console \"Task\" tab shows ~48 tasks, but instances have only 3.\r\nMy naive understanding is that the ecs-agent is what the AWS console uses to know what is happening on the instances, hence the query here.\r\n\r\nA \"docker ps -a\" on all the instances shows nothing related to a task mentioned on the console.\r\n\r\nI am doing an hourly purge of meta-data ( i.e.: \"docker ps -a -q | xargs docker rm\" on each instance )to help keep the disk footprint low, prevent docker from locking up completely.\r\nI suspect this may be the causing the issue, but how to do that without the console (and hence AWS's notion of memory reservation etc. getting all messed up?\r\n\r\nAnd/Or how to re-sync things?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/aws/amazon-ecs-agent/issues/comments/188273668","html_url":"https://github.com/aws/amazon-ecs-agent/issues/313#issuecomment-188273668","issue_url":"https://api.github.com/repos/aws/amazon-ecs-agent/issues/313","id":188273668,"user":{"login":"CameronGo","id":14074983,"avatar_url":"https://avatars.githubusercontent.com/u/14074983?v=3","gravatar_id":"","url":"https://api.github.com/users/CameronGo","html_url":"https://github.com/CameronGo","followers_url":"https://api.github.com/users/CameronGo/followers","following_url":"https://api.github.com/users/CameronGo/following{/other_user}","gists_url":"https://api.github.com/users/CameronGo/gists{/gist_id}","starred_url":"https://api.github.com/users/CameronGo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CameronGo/subscriptions","organizations_url":"https://api.github.com/users/CameronGo/orgs","repos_url":"https://api.github.com/users/CameronGo/repos","events_url":"https://api.github.com/users/CameronGo/events{/privacy}","received_events_url":"https://api.github.com/users/CameronGo/received_events","type":"User","site_admin":false},"created_at":"2016-02-24T14:19:44Z","updated_at":"2016-02-24T14:19:44Z","body":"Question that is hopefully not out of line: In a case such as this where there is a major bug that disrupts core functionality, would it make sense to re-publish the previous version (v1.7.1 in this case) with the \"latest\" tag, so that launch configs and autoscaling groups that are not using version pinning remain in a functional state?"}}