History

Martin Sehnoutka d975effc42 improve vagrant test and its documentation RPM packages are now kept in output directory after build so that we know exactly which packages to copy to the test. The test directory now contains special directory for RPMs. Fedora developer portal is referenced from README file.		2019-07-25 12:46:53 +02:00
..
testing-rpms	improve vagrant test and its documentation	2019-07-25 12:46:53 +02:00
.gitignore	introduce testing script	2019-07-09 10:29:48 +02:00
1-create-base.json	osbuild-run: generate /etc/pki/tls/certs/ca-bundle.crt	2019-07-19 13:31:49 +02:00
2-configure-web-server.json	test and samples: don't include /etc/grub.d from the host	2019-07-19 13:31:49 +02:00
3-compose-qcow2.json	test and samples: don't include /etc/grub.d from the host	2019-07-19 13:31:49 +02:00
4-all.json	osbuild-run: generate /etc/pki/tls/certs/ca-bundle.crt	2019-07-19 13:31:49 +02:00
Makefile	introduce spec file and related build scripts	2019-07-23 15:22:40 +02:00
README.md	improve vagrant test and its documentation	2019-07-25 12:46:53 +02:00
run-tests.py	enable running osbuild test from local checkout	2019-07-23 00:06:31 +02:00
Vagrantfile	improve vagrant test and its documentation	2019-07-25 12:46:53 +02:00
variables	introduce testing script	2019-07-09 10:29:48 +02:00

README.md

Setup

To run the tests in vagrant virtual machine, please follow this tutorial: https://developer.fedoraproject.org/tools/vagrant/vagrant-libvirt.html

(run also sudo systemctl start libvirtd)

Using Vagrant

To start a Vagrant box by hand, run vagrant up in this directory. To stop and remove all volumes run vagrant destroy again in this directory.

Troubleshooting

In case you accidentally deleted .vagrant directory, you can use some of these commands in order to get rid of running instance:

$ virsh list # this should display test_default
$ virsh managedsave-remove test_default
$ virsh undefine test_default
# or using vagrant cli tool
$ vagrant global-status
$ vagrant destroy <id>
$ vagrant global-status --prune