----- Original Message -----
----- Original Message -----
From: "Ayal Baron" <abaron@redhat.com> To: "Nir Soffer" <nsoffer@redhat.com> Cc: "Eduardo Ramos" <eduardo@freedominterface.org>, "users" <users@ovirt.org> 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@freedominterface.org> To: "Nir Soffer" <nsoffer@redhat.com> Cc: "users" <users@ovirt.org> 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
No, the patch you referenced fixes a case where you start a VM in oVirt 3.2 and upgrade vdsm to 3.3 (or migrate the vm to a host running vdsm 3.3). The problem is that the path vdsm has on the newer host is out of sync with the libvirt xml and libvirt does not correlate the two paths despite them leading to the same disk. (i.e. libvirt assumes that after migration paths to disks remain the same).