Unable to run Cucumber tests against ADB and CDK using libvirt

[hferentschik]

Using something like

$ bundle exec rake features BOX=cdk,adb PROVIDER=libvirt 

fails, whereas

$ bundle exec rake features BOX=cdk,adb PROVIDER=virtualbox 

works.

The underlying problems is most likely somewhere in the underlying kvm/qemu which also caches virtual machines. The tests will alternate between adb and cdk boxes, but I think that on libvirt always the same box is used. We might need to clean kvm.qemu after each run.

[praveenkumar]

@hferentschik if these tests are running on the same setup then we have to clean vagrant box after each run.

[coolbrg]

@praveenkumar We are doing "vagrant destroy" on every cucumber file (.feature). These are happening automatically along with execution of acceptance test.
Also, there are CLI to clean the garbage.

[hferentschik]

if these tests are running on the same setup then we have to clean vagrant box after each run.

I think it is more kvm/qemu. I ran into this before and I seem to recall that someone (Dusty!?) wrote an email about it as well once. I just cannot remember the right commands atm.

[hferentschik]

See also vagrant-libvirt/vagrant-libvirt#85

[praveenkumar]

@hferentschik So what I usually end up doing is execute below commands in case of libvirt provider to get clean environment for next test.

# vagrant destroy -f && rm -fr .vagrant
# rm -fr /var/lib/libvirt/images/*_0.img && systemctl restart libvirtd

[dustymabe]

you need to have vagrant-libvirt in the plugins definition in the Gem file in order to load the libvirt plugin when running bundle exec vagrant.

see #335

[hferentschik]

you need to have vagrant-libvirt in the plugins definition in the Gem file in order to load the libvirt plugin when running bundle exec vagrant.

vagrant-libvirt is already added and the CentOS CI environment already runs against the libvirt provider. The problems lies somewhere else.