{"action":"opened","issue":{"url":"https://api.github.com/repos/smdahlen/vagrant-digitalocean/issues/213","labels_url":"https://api.github.com/repos/smdahlen/vagrant-digitalocean/issues/213/labels{/name}","comments_url":"https://api.github.com/repos/smdahlen/vagrant-digitalocean/issues/213/comments","events_url":"https://api.github.com/repos/smdahlen/vagrant-digitalocean/issues/213/events","html_url":"https://github.com/smdahlen/vagrant-digitalocean/issues/213","id":108359656,"number":213,"title":"Re-creating the droplet fails if vagrant up is called immediately vagrant destroy","user":{"login":"viktorbenei","id":430618,"avatar_url":"https://avatars.githubusercontent.com/u/430618?v=3","gravatar_id":"","url":"https://api.github.com/users/viktorbenei","html_url":"https://github.com/viktorbenei","followers_url":"https://api.github.com/users/viktorbenei/followers","following_url":"https://api.github.com/users/viktorbenei/following{/other_user}","gists_url":"https://api.github.com/users/viktorbenei/gists{/gist_id}","starred_url":"https://api.github.com/users/viktorbenei/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/viktorbenei/subscriptions","organizations_url":"https://api.github.com/users/viktorbenei/orgs","repos_url":"https://api.github.com/users/viktorbenei/repos","events_url":"https://api.github.com/users/viktorbenei/events{/privacy}","received_events_url":"https://api.github.com/users/viktorbenei/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-25T16:34:01Z","updated_at":"2015-09-25T16:34:01Z","closed_at":null,"body":"The problem seems to be that the plugin doesn't wait for the droplet to be fully deleted.\r\n\r\nThis causes that if you call `vagrant destroy -f` and then immediately after it finishes you call `vagrant up` it'll tell you that the droplet is already created. If you call `vagrant up` again in like 10 seconds it'll properly start creating the droplet.\r\n\r\nA suggestion for the solution: after `vagrant destroy` this plugin should generate a new ID for the next `vagrant create`, so that if the previous droplet still under destroy it would be able to create a new droplet, with a new name/id immediately.\r\n\r\nRelated question: is it possible to manually set a name/ID? We could use that as a workaround in a similar way as I described above."}}