On Fri, Mar 22, 2013 at 08:24:35PM +0200, Limor Gavish wrote:
Hello,
I am using Ovirt 3.2 on Fedora 18:
[wil@bufferoverflow ~]$ rpm -q vdsm
vdsm-4.10.3-7.fc18.x86_64
(the engine is built from sources).
I seem to have hit this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=922515
This bug is only one part of the problem, but it's nasty enough that I
have just suggested it as a fix to the ovirt-3.2 branch of vdsm:
http://gerrit.ovirt.org/13303
Could you test if with it, vdsm relinquishes its spm role, and recovers
as operational?
in the following configuration:
Single host (no migrations)
Created a VM, installed an OS inside (Fedora18)
stopped the VM.
created template from it.
Created an additional VM from the template using thin provision.
Started the second VM.
in addition to the errors in the logs the storage domains (both data and
ISO) crashed, i.e went to "unknown" and "inactive" states
respectively.
(see the attached engine.log)
I attached the VDSM and engine logs.
is there a way to work around this problem?
It happens repeatedly.
Yuval Meir