Name XYZ of domain about to create is already taken. But no domain exists...

176 views
Skip to first unread message

Alfonso

unread,
Feb 7, 2019, 6:07:19 AM2/7/19
to Vagrant
Hi,

I am trying to run Jenkins via vagrant with CentOS7 environment and I have a problem with running 'vagrant up' command on Fedora 29.

The error says that "Name `cvjd` of domain about to create is already taken. Please try to run `vagrant up` command again.", but the problem is that there is no domain existing on my system.

The 'vagrant global-status' command returns: There are no active Vagrant environments on this computer and 'virsh list' command returns empty list.

I tried to reinstall the vagrant package with dnf command and also deleted user data via https://www.vagrantup.com/docs/installation/uninstallation.html, but it did not help. I also deleted all virtual connections previously made.

Has anyone seen this before?

Thank you for your help,
Alf

Brian Cain

unread,
Feb 8, 2019, 1:02:49 PM2/8/19
to vagra...@googlegroups.com
Hey there,

Do you have a link to a gist showing the full debug log from running vagrant up --debug? Also having a Vagrantfile would be helpful too, thanks!

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/4eba5020-2b07-47b9-9c11-d1622af14f5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
Brian Cain

Alfonso

unread,
Feb 12, 2019, 9:31:49 AM2/12/19
to Vagrant
Hi Brian,

sorry for the late response.

I managed to solve this issue by running virsh undefine <MACHINE> command. The <MACHINE> was listed in virsh list -all command.

Have a nice day,
Alf


Dne pátek 8. února 2019 19:02:49 UTC+1 Brian Cain napsal(a):
Reply all
Reply to author
Forward
0 new messages