Awesome! Thanks for all of your help. I was able to install this package and upgraded vdsm which appears to have resolved the disk errors I was seeing.
On Mon, 2017-01-09 at 18:11 +0000, Pavel Gashev wrote: > Now QEMU Enterprise Virtualization packages are built separately: > > # yum --enablerepo=extras install centos-release-qemu-ev > > -----Original Message----- > From: Michael Watters <michael.watt...@dart.biz> > Date: Monday 9 January 2017 at 19:19 > To: "Users@ovirt.org" <Users@ovirt.org>, Pavel Gashev <p...@acronis.co > m> > Subject: Re: [ovirt-users] Disk move failures > > I built the rpms but there are some dependency errors when I attempt > to > upgrade. > > qemu-img-rhev >= 10:2.3.0-31.el7_2.16 is needed by vdsm-4.17.35- > 1.el7.centos.noarch > > qemu-kvm-rhev >= 10:2.3.0-31.el7_2.16 is needed by vdsm-4.17.35- > 1.el7.centos.noarch > > These packages appear to be part of ovirt 4.0 so it looks like an > upgrade will be needed unless there is a way to obtain updated > packages > for ovirt 3.6. > > > On Mon, 2017-01-09 at 14:44 +0000, Pavel Gashev wrote: > > Michael, > > > > I'd recommend to build an rpm: > > > > # yum --enablerepo=extras install -y epel-release git > > # git clone https://github.com/oVirt/vdsm.git > > # cd vdsm > > # git checkout v4.17.35 > > # yum install -y `cat ./automation/build-artifacts.packages` > > # ./automation/build-artifacts.sh > > > > -----Original Message----- > > From: Michael Watters <michael.watt...@dart.biz> > > Date: Monday 9 January 2017 at 17:26 > > To: "Users@ovirt.org" <Users@ovirt.org>, Pavel Gashev <Pax@acronis. > > co > > m> > > Subject: Re: [ovirt-users] Disk move failures > > > > Is there a way to upgrade vdsm without upgrading everything else? > > > > > > On Sat, 2017-01-07 at 09:36 +0000, Pavel Gashev wrote: > > > The same is here. Upgrade vdsm to 4.17.35. > > > > > > -----Original Message----- > > > From: <users-boun...@ovirt.org> on behalf of Michael Watters > > > <Michael > > > .watt...@dart.biz> > > > Date: Saturday 7 January 2017 at 00:04 > > > To: "Users@ovirt.org" <Users@ovirt.org> > > > Subject: [ovirt-users] Disk move failures > > > > > > I am receiving several LVM errors when attempting to move a disk > > > from > > > one storage domain to another. > > > > > > > VDSM ovirt-node-production2 command failed: Logical Volume > > > > extend > > > > > > failed > > > > > > vdsm.log shows a failure message as follows. > > > > > > > d6d4529e-db0d-49ac-a0c3-ee9d2e8cc9bb::ERROR::2017-01-06 > > > > > > 15:05:54,926::image::405::Storage.Image::(_createTargetImage) > > > Unexpected error > > > Traceback (most recent call last): > > > File "/usr/share/vdsm/storage/image.py", line 394, in > > > _createTargetImage > > > dstVol.extend((volParams['apparentsize'] + 511) / 512) > > > File "/usr/share/vdsm/storage/blockVolume.py", line 310, in > > > extend > > > lvm.extendLV(self.sdUUID, self.volUUID, sizemb) > > > File "/usr/share/vdsm/storage/lvm.py", line 1179, in extendLV > > > _resizeLV("lvextend", vgName, lvName, size) > > > File "/usr/share/vdsm/storage/lvm.py", line 1175, in _resizeLV > > > raise se.LogicalVolumeExtendError(vgName, lvName, "%sM" % > > > (size, > > > )) > > > LogicalVolumeExtendError: Logical Volume extend failed: > > > 'vgname=32f7c737-c1ee-4d2e-82a7-1b5e6efe0cf8 lvname=7ec88b4b- > > > e893- > > > 47dc- > > > 895f-5f8e584ed2cf newsize=1024M' > > > > > > Does anybody know what would cause this? I am able to create > > > volumes > > > and extend them from the command line without any issues. > > > _______________________________________________ > > > Users mailing list > > > Users@ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users