action #54173
Updated by riafarov almost 5 years ago
## Observation ``` Formatting '/var/lib/libvirt/images/openQA-SUT-2b.img', fmt=qcow2 size=21474836480 cluster_size=65536 lazy_refcounts=off refcount_bits=16 [2019-07-12T10:10:45.345 CEST] [debug] Command's stderr: qemu-img: /var/lib/libvirt/images/openQA-SUT-2b.img: Failed to get "write" lock Is another process using the image? ``` Under certain conditions, we have lock on the image file remaining. There are multiple ways to address such issue, like using random postfix in the image name + cleanup. As seems that destroy command from previous run fails, so we need to check why. This will solve root cause of the issue. Alternative will be to investigate the problem and call lsof to see which process uses the image and put more things to investigate the issue in case it occurs. We also could re-try in case command fails, or test if we can get write lock before with qemu-img info command. openQA test in scenario sle-12-SP5-Server-DVD-x86_64-minimal+base@yast-xen-pv@svirt-xen-pv fails in [bootloader_start](https://openqa.suse.de/tests/3055073/modules/bootloader_start/steps/17) ## Test suite description Mantainer: jrivera Select a minimal textmode installation by starting with the default and unselecting all patterns except for "base" and "minimal". Not to be confused with the new system role "minimal" introduced with SLE15. Test modules 'grub_disable_timeout' and 'grub_test' in xen-pv are not scheduled due to grub2 doesn't support xfb console. ## Reproducible Fails since (at least) Build [0222](https://openqa.suse.de/tests/3055073) (current job) ## Expected result Last good: [0219](https://openqa.suse.de/tests/3045172) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?test=minimal%2Bbase%40yast-xen-pv&distri=sle&arch=x86_64&version=12-SP5&flavor=Server-DVD&machine=svirt-xen-pv)