{"action":"opened","issue":{"url":"https://api.github.com/repos/coreos/bugs/issues/1418","repository_url":"https://api.github.com/repos/coreos/bugs","labels_url":"https://api.github.com/repos/coreos/bugs/issues/1418/labels{/name}","comments_url":"https://api.github.com/repos/coreos/bugs/issues/1418/comments","events_url":"https://api.github.com/repos/coreos/bugs/issues/1418/events","html_url":"https://github.com/coreos/bugs/issues/1418","id":161551071,"number":1418,"title":"Server inaccessible after applying 1068.2.0 update","user":{"login":"egoldschmidt","id":931480,"avatar_url":"https://avatars.githubusercontent.com/u/931480?v=3","gravatar_id":"","url":"https://api.github.com/users/egoldschmidt","html_url":"https://github.com/egoldschmidt","followers_url":"https://api.github.com/users/egoldschmidt/followers","following_url":"https://api.github.com/users/egoldschmidt/following{/other_user}","gists_url":"https://api.github.com/users/egoldschmidt/gists{/gist_id}","starred_url":"https://api.github.com/users/egoldschmidt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/egoldschmidt/subscriptions","organizations_url":"https://api.github.com/users/egoldschmidt/orgs","repos_url":"https://api.github.com/users/egoldschmidt/repos","events_url":"https://api.github.com/users/egoldschmidt/events{/privacy}","received_events_url":"https://api.github.com/users/egoldschmidt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-06-21T22:07:29Z","updated_at":"2016-06-21T22:07:29Z","closed_at":null,"body":"# Issue Report #\r\n\r\n## Bug ##\r\n\r\n### CoreOS Version ###\r\n\r\n1068.2.0; I can't cat /etc/os-release as I can't SSH into the machines anymore...\r\n\r\n### Environment ###\r\n\r\nWhat hardware/cloud provider/hypervisor is being used to run CoreOS?\r\n\r\nAWS - instance types ranging from t2.small to m4.large\r\n\r\n### Expected Behavior ###\r\n\r\nServers restart with new release, bootstrap themselves into ECS cluster, etc.\r\n\r\n### Actual Behavior ###\r\n\r\nMy servers listening on the `beta` channel have applied CoreOS 1068.2.0 and restarted themselves this afternoon. They were previously running CoreOS 1010.4.0. After coming back up they are inaccessible via SSH. Connection hangs after:\r\n\r\n```\r\ndebug1: Connection established.\r\ndebug1: identity file...\r\ndebug1: Enabling compatibility mode for protocol 2.0\r\ndebug1: Local version string SSH-2.0-OpenSSH_6.2\r\n```\r\n\r\nFurther, they no longer appear to do any of the normal bootstrapping tasks: running monitoring agents (ECS, DataDog, Splunk), much less running our application servers. Each of the aforementioned agents are configured via unit files in cloud-init.yml.\r\n\r\nIf no one else is running into the same issue this is likely an artifact of our setup, but:\r\n\r\n1. This happened to a wide variety of machines at the same time, with none coming back successfully\r\n2. All previous updates for the past few months have been applied w/no problem using the same tooling\r\n\r\nWere there any changes to, for example, SSH configs, cloud-init, or bootstrapping workflows in the last release? The release notes are pretty thin on details.\r\n\r\n### Reproduction Steps ###\r\n\r\n  0. Run CoreOS 1010.4.0\r\n  1. Apply CoreOS 1068.2.0\r\n  2. Restart\r\n\r\n### Other Information ###\r\n"}}
{"actor":{"display_login":"egoldschmidt"}}