Created attachment 1235330 [details] vdsm log Description of problem: When trying to run VM with payload, it fails due to permission denied: 2016-12-26 05:16:56,805 ERROR (vm/a54b4957) [virt.vm] (vmId='a54b4957-308e-409e-90c1-470a68cd754a') The vm start process failed (vm:616) Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 552, in _startUnderlyingVm self._run() File "/usr/share/vdsm/virt/vm.py", line 1993, in _run self._connection.createXML(domxml, flags), File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 123, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 941, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3782, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: 2016-12-26T10:16:56.605466Z qemu-kvm: -drive file=/var/run/vdsm/payload/a54b4957-308e-409e-90c1-470a68cd754a.57ae79e33f43177978fa6f9cfef8 b5de.img,format=raw,if=none,id=drive-ide0-1-1,readonly=on: Could not open '/var/run/vdsm/payload/a54b4957-308e-409e-90c1-470a68cd754a.57ae79e33f43177978fa6f9cfef8b5de.img': Permission denied 2016-12-26 05:16:56,809 INFO (vm/a54b4957) [virt.vm] (vmId='a54b4957-308e-409e-90c1-470a68cd754a') Changed state to Down: internal error: process exited while connecting to monitor: 2016-12-26T10:16:56.605466Z qemu-kvm: -drive file=/var/run/vdsm/payload/a54b4957-308e-409e-90c1-470a68cd754a.57ae79e33f43177978fa6f9cfef8b5de.img,format=raw,if=none,id=drive-ide0-1-1,readonly=on: Could not open '/var/run/vdsm/payload/a54b4 957-308e-409e-90c1-470a68cd754a.57ae79e33f43177978fa6f9cfef8b5de.img': Permission denied (code=1) (vm:1198) Version-Release number of selected component (if applicable): vdsm-4.19.1-32.git08f506f.el7.centos.x86_64.rpm How reproducible: Always - and seems to be a regression from 4.0. Steps to Reproduce: 1. Run ovirt-system-tests on Master (or 4.1)
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Created attachment 1235331 [details] engine log
@Dan: can this really happen also on the 4.1? I see the patch causing the issue was merged only to master.
Correct. This is master only, and needs no further follow up.