History

Lars Karlitski 2c73187046 assemblers/qcow2: Pass size explicitly Don't try to guess how much room the filesystem will take up. In practice, most people will want to specify a size anyway, depending on their use case. As is typical for osbuild, there are no convenience features for the pipeline (it's not meant to be written manually). `size` must be given in bytes and it must be a multiple of 512.		2019-09-01 23:04:25 +02:00
..
integration_tests	osbuild: allow additional an additional build-pipeline to be prepended	2019-08-30 12:00:47 +02:00
pipelines	assemblers/qcow2: Pass size explicitly	2019-09-01 23:04:25 +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
__init__.py	osbuild: add description() methods	2019-08-07 10:01:17 +02:00
__main__.py	osbuild: allow additional an additional build-pipeline to be prepended	2019-08-30 12:00:47 +02:00
Makefile	make vagrant-test idempotent	2019-07-25 15:47:53 +02:00
README.md	improve vagrant test and its documentation	2019-07-25 12:46:53 +02:00
test_osbuild.py	Pipeline: drop the build setter	2019-08-13 17:13:13 +02:00
Vagrantfile	make vagrant-test idempotent	2019-07-25 15:47:53 +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