{"action":"created","issue":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/6248","labels_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6248/labels{/name}","comments_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6248/comments","events_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6248/events","html_url":"https://github.com/mitchellh/vagrant/issues/6248","id":105382391,"number":6248,"title":"Interrupting vagrant during operation doesn't trap signal correctly","user":{"login":"madAndroid","id":1321437,"avatar_url":"https://avatars.githubusercontent.com/u/1321437?v=3","gravatar_id":"","url":"https://api.github.com/users/madAndroid","html_url":"https://github.com/madAndroid","followers_url":"https://api.github.com/users/madAndroid/followers","following_url":"https://api.github.com/users/madAndroid/following{/other_user}","gists_url":"https://api.github.com/users/madAndroid/gists{/gist_id}","starred_url":"https://api.github.com/users/madAndroid/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/madAndroid/subscriptions","organizations_url":"https://api.github.com/users/madAndroid/orgs","repos_url":"https://api.github.com/users/madAndroid/repos","events_url":"https://api.github.com/users/madAndroid/events{/privacy}","received_events_url":"https://api.github.com/users/madAndroid/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-09-08T13:40:36Z","updated_at":"2015-10-20T08:27:24Z","closed_at":null,"body":"Prior to upgrading to `1.7.4`, when I `ctrl-c` to interrupt a vagrant operation, the process would catch the signal correctly, issue a message stating:\r\n```\r\nWaiting for cleanup before exiting...\r\n```\r\nand then allow me to stop the process by hitting `ctrl-c` again, after which the following is shown:\r\n```\r\nExiting immediately, without cleanup!\r\n```\r\n\r\nAfter upgrading to `1.7.4`, I can no longer do this cleanly - after hitting `ctrl-c`, I get returned to my shell prompt, and the command is sent to the background, and continues to execute, with the output entering the current shell session when it continues. After some time, the expected message of:\r\n```\r\nVagrant exited after cleanup due to external interrupt.\r\n```\r\n... is shown, and the process list shows that vagrant is no longer running.\r\n\r\nI have no idea why this is happening - I've tried without any luck to track it down. It's happening to another colleague as well, I'm just not sure how many other users this is affecting, and whether it's possibly my shell environment that's responsible; when I downgrade to `1.7.2`, the problem goes away.\r\n"},"comment":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/comments/149475857","html_url":"https://github.com/mitchellh/vagrant/issues/6248#issuecomment-149475857","issue_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6248","id":149475857,"user":{"login":"madAndroid","id":1321437,"avatar_url":"https://avatars.githubusercontent.com/u/1321437?v=3","gravatar_id":"","url":"https://api.github.com/users/madAndroid","html_url":"https://github.com/madAndroid","followers_url":"https://api.github.com/users/madAndroid/followers","following_url":"https://api.github.com/users/madAndroid/following{/other_user}","gists_url":"https://api.github.com/users/madAndroid/gists{/gist_id}","starred_url":"https://api.github.com/users/madAndroid/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/madAndroid/subscriptions","organizations_url":"https://api.github.com/users/madAndroid/orgs","repos_url":"https://api.github.com/users/madAndroid/repos","events_url":"https://api.github.com/users/madAndroid/events{/privacy}","received_events_url":"https://api.github.com/users/madAndroid/received_events","type":"User","site_admin":false},"created_at":"2015-10-20T08:27:24Z","updated_at":"2015-10-20T08:27:24Z","body":"> 1.7.3 introduced bundler env jailbreaks, configurable sudo and ssh for machine etc which could do something like this as a side-effect, but I couldn't pinpoint it either.\r\n\r\nYep, there were quite a few changes that could have caused this. BTW @tuminoid - are you also using zsh?\r\n\r\nI have a feeling it may be down to this commit: https://github.com/mitchellh/vagrant/commit/3b8bc2a433c14a1c8ce159f034a457180683b788 but I've not been able to prove this conclusively\r\n"}}