----- Original Message ----- > From: "Eduardo Ramos" <eduardo(a)freedominterface.org&gt; > To: "users" <users(a)ovirt.org&gt; > Sent: Friday, February 7, 2014 2:35:03 PM > Subject: [Users] 'Drive' object has no attribute 'format' > > Hi all! > > I'm getting this strange message on my vdsm.log > > Thread-187887::ERROR::2014-02-07 > 10:31:13,246::sampling::355::vm.Vm::(collect) > vmId=`226fb21b-ce7e-45ec-8e6e-75b987374ead`::Stats function failed: > <AdvancedStatsFunction _highWrite at 0x2d328f0> > Traceback (most recent call last): > File "/usr/share/vdsm/sampling.py", line 351, in collect > statsFunction() > File "/usr/share/vdsm/sampling.py", line 226, in __call__ > retValue = self._function(*args, **kwargs) > File "/usr/share/vdsm/vm.py", line 528, in _highWrite > self._vm.extendDrivesIfNeeded() > File "/usr/share/vdsm/vm.py", line 2285, in extendDrivesIfNeeded > if not drive.blockDev or drive.format != 'cow': > AttributeError: 'Drive' object has no attribute 'format' > > Anyone know what could be happening? Hi Eduardo, I'm afraid you have a vm with an invalid drive, created without the required "format" attribute. We have seen this issue when upgrading from old versions, or when migrating vms. See https://bugzilla.redhat.com/show_bug.cgi?id=1055437 Can you add more information that will help debug this issue? - ovirt-engine/vdsm versions - logs: engine.log, vdsm.log - what was the trigger of this error (e.g. started when migrating vm?) If you think your case is not relevant to bug 1055437, please open a new bug. Thanks, Nir

----- Original Message ----- > From: "Eduardo Ramos" <eduardo(a)freedominterface.org&gt; > To: "Nir Soffer" <nsoffer(a)redhat.com&gt; > Cc: "users" <users(a)ovirt.org&gt; > Sent: Monday, February 10, 2014 9:13:50 PM > Subject: Re: [Users] 'Drive' object has no attribute 'format' > > Hi Nir, thanks for responding. > > That's what you asked me. > > vdms: > [root@gauss vdsm]# rpm -qa | grep vdsm > vdsm-4.10.3-0.36.23.el6.x86_64 > > engine: > [eduardo@ovirt-dir ~]$ rpm -qa|grep ovirt > ovirt-engine-3.2.2-1.1.43.el6.noarch A patch that may fix the root cause of this issue was just merged upstream: http://gerrit.ovirt.org/24202 This patch should be available soon in rhev-3.3.x release and ovirt-3.4. The best way to handle this issue and get support would be to upgrade the vdsm on the host to a recent version.

> Follows the logs on my dropbox: > > https://www.dropbox.com/sh/cp93cqzs7ow4zp2/XRDsr_D1L3/ovirt I'll inspect these logs later. You did not describe what you were doing with the system when the problem started. Can you add more information about it? What was the change or operation that triggered this issue? Thanks, Nir _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

----- Original Message ----- > From: "Ayal Baron" <abaron(a)redhat.com&gt; > To: "Nir Soffer" <nsoffer(a)redhat.com&gt; > Cc: "Eduardo Ramos" <eduardo(a)freedominterface.org&gt;, "users" > <users(a)ovirt.org&gt; > Sent: Tuesday, February 11, 2014 8:17:53 PM > Subject: Re: [Users] 'Drive' object has no attribute 'format' > ----- Original Message ----- > > > > ----- Original Message ----- > > > From: "Eduardo Ramos" <eduardo(a)freedominterface.org&gt; > > > To: "Nir Soffer" <nsoffer(a)redhat.com&gt; > > > Cc: "users" <users(a)ovirt.org&gt; > > > Sent: Monday, February 10, 2014 9:13:50 PM > > > Subject: Re: [Users] 'Drive' object has no attribute 'format' > > > > > Hi Nir, thanks for responding. > > > > > That's what you asked me. > > > > > vdms: > > > [root@gauss vdsm]# rpm -qa | grep vdsm > > > vdsm-4.10.3-0.36.23.el6.x86_64 > > > > > engine: > > > [eduardo@ovirt-dir ~]$ rpm -qa|grep ovirt > > > ovirt-engine-3.2.2-1.1.43.el6.noarch > > > A patch that may fix the root cause of this issue was just merged > > upstream: > > http://gerrit.ovirt.org/24202 > > > This patch should be available soon in rhev-3.3.x release and ovirt-3.4. > > > The best way to handle this issue and get support would be to upgrade > > the vdsm on the host to a recent version. > the vdsm on *all* the hosts. > also note that this affects only setups that have been upgraded from > previous > versions. Do you think this is an issue with old recovery files? https://bugzilla.redhat.com/show_bug.cgi?id=994534