{"action":"opened","issue":{"url":"https://api.github.com/repos/vagrant-libvirt/vagrant-libvirt/issues/658","repository_url":"https://api.github.com/repos/vagrant-libvirt/vagrant-libvirt","labels_url":"https://api.github.com/repos/vagrant-libvirt/vagrant-libvirt/issues/658/labels{/name}","comments_url":"https://api.github.com/repos/vagrant-libvirt/vagrant-libvirt/issues/658/comments","events_url":"https://api.github.com/repos/vagrant-libvirt/vagrant-libvirt/issues/658/events","html_url":"https://github.com/vagrant-libvirt/vagrant-libvirt/issues/658","id":179931655,"number":658,"title":"Can't vagrant up or destroy \"domain about to create is already taken\"","user":{"login":"ryanlerch","id":592259,"avatar_url":"https://avatars.githubusercontent.com/u/592259?v=3","gravatar_id":"","url":"https://api.github.com/users/ryanlerch","html_url":"https://github.com/ryanlerch","followers_url":"https://api.github.com/users/ryanlerch/followers","following_url":"https://api.github.com/users/ryanlerch/following{/other_user}","gists_url":"https://api.github.com/users/ryanlerch/gists{/gist_id}","starred_url":"https://api.github.com/users/ryanlerch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ryanlerch/subscriptions","organizations_url":"https://api.github.com/users/ryanlerch/orgs","repos_url":"https://api.github.com/users/ryanlerch/repos","events_url":"https://api.github.com/users/ryanlerch/events{/privacy}","received_events_url":"https://api.github.com/users/ryanlerch/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-29T01:32:19Z","updated_at":"2016-09-29T01:32:19Z","closed_at":null,"body":"In some cases, i have found that some of my vagrant-libvirt setups get into a state where i get the following message when trying to `vagrant destroy`\r\n\r\n    Name `vagrantbox_default` of domain about to create is already taken. Please try to run  `vagrant up` command again.\r\n\r\nAnd then get the same message when trying the recommendation of running `vagrant up`\r\n\r\nWhat usually has happened is that i have either removed the `.vagrant` directory, or interputed a `vagrant destroy` before it has fully completed.\r\n\r\nTo fix this, i just go into virt-manager, and remove the VM (domain) that still exists, in the above example, that would be:  `vagrantbox_default`\r\n\r\n### Steps to reproduce\r\n1. `vagrant up` to create and provision\r\n2. `rm -rf .vagrant`\r\n\r\n### Expected behaviour\r\nNot sure what the best solution is here -- maybe a better error message that there may be a VM still sticking around that vagrant-libvirt doesnt know about becuase the .vagrant directory is missing. Or maybe even providing an option when this happens to allow the user to delete the VM / domain.\r\n"}}
{"actor":{"display_login":"ryanlerch"}}