Virtual deepops failed with libvirt on Ubuntu 16.04

[bloodeagle40234]

Hello.
When I tried to setup deepops cluster with virtual mode for testing, it failed with libvirt provider at launching vagrant box. What I did is like

step1: clone deepops repository into local
step2: copy virtual/Vagrantfile-ubuntu to virtual/Vagrantfile
step3: run virtual/vagrant_startup.sh

It looks like the dependency packages are installed (e.g. host-manager plugin) successfully but the vagrant up failed. I paste the execution log since vagrant up called, here.

+ vagrant up --provider=libvirt
Bringing machine 'virtual-mgmt' up with 'libvirt' provider...
Bringing machine 'virtual-login' up with 'libvirt' provider...
Bringing machine 'virtual-gpu01' up with 'libvirt' provider...
==> virtual-mgmt: An error occurred. The error will be shown after all tasks complete.
==> virtual-gpu01: An error occurred. The error will be shown after all tasks complete.
==> virtual-login: An error occurred. The error will be shown after all tasks complete.
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.

An error occurred while executing the action on the 'virtual-mgmt'
machine. Please handle this error then try again:

There was error while creating libvirt storage pool: Call to virStoragePoolDefineXML failed: operation failed: Storage source conflict with pool: 'images'

An error occurred while executing the action on the 'virtual-login'
machine. Please handle this error then try again:

There was error while creating libvirt storage pool: Call to virStoragePoolDefineXML failed: operation failed: Storage source conflict with pool: 'images'

An error occurred while executing the action on the 'virtual-gpu01'
machine. Please handle this error then try again:

There was error while creating libvirt storage pool: Call to virStoragePoolDefineXML failed: operation failed: Storage source conflict with pool: 'images'

Any idea to fix this problem?

[michael-balint]

@bloodeagle40234 - It seems like you might have an existing storage pool. Can you check?

$ virsh pool-list --all
 Name                 State      Autostart 
-------------------------------------------
 default              active     no 

The name of the pool should be default. If yours is images instead, do the following...

$ virsh pool-destroy images
Pool images destroyed

$ virsh pool-undefine images
Pool images has been undefined

[michael-balint]

PS: if there is a reason why you need to keep the pool named images, you can reference that instead in the Vagrantfile...

Vagrant.configure("2") do |config|
  ...
  config.vm.provider :libvirt do |libvirt|
    libvirt.storage_pool_name = "images"
  end
  ...
end

[bloodeagle40234]

Thanks a lot! Actually,

$ virsh pool-undefine images
Pool images has been undefined

This resolved my problem, once I did just virsh pool-destroy images ever though.
The problem occurred even I just clean installed the libvirt tools via apt in Ubuntu 16.04 xenial so perhaps, images might be a default.

Anyway, it looks my vm launched successfully, thanks.