mirror of
https://github.com/virt-manager/virt-manager.git
synced 2024-12-23 17:34:21 +03:00
58ac786b6b
We have this option --dry-run that should run through the installation process but don't actually touch anything. Just pretend the installation. And we have a test that uses it heavily. However, the test is failing: Traceback (most recent call last): File "/home/zippy/work/virt-manager.git/tests/clitest.py", line 161, in _launch_command ret = virtconvert.main(conn=conn) File "virt-convert", line 111, in main destdir=options.destination, dry=options.dry) File "/home/zippy/work/virt-manager.git/virtconv/formats.py", line 314, in convert_disks newpath) RuntimeError: New path name '/var/lib/libvirt/images/fedora.qcow2' already exists Problem is, even in test suite we really touch the host paths. This in general will spit unpredictable results. Resolution consists of making this specific part of the code fault tolerant if ran under test suite. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> |
||
---|---|---|
.. | ||
__init__.py | ||
formats.py | ||
ovf.py | ||
vmx.py |