April 2017 - Users - oVirt List Archives

Python-SDK4: How to list user permissions?
by nicolas＠devels.es 11 Apr '17

11 Apr '17

Hi, I'm trying to get a user's list of permissions, i.e., list all permissions a user have on VMs and VmPools. In SDK3 that was easy as I could run (being 'u' a User object): for perm in u.permissions.list(): vm = perm.get_vm() vmpool = perm.get_vmpool() if vm or vmpool: print "User has some permissions!" In SDK4 I cannot reproduce the same logic. u.permissions returns an empty list ([]). What I have so far is something like this: for u in users_serv.list(): if u.user_name == 'admin@internal': continue vms_service = sys_serv.vms_service() for vm in vms_service.list(): vms = vms_service.vm_service(id=vm.id) ps = vms.permissions_service() for perm in ps.list(): perm_service = ps.permission_service(id=perm.id) getperm = perm_service.get() if getperm.user.user_name == u.user_name: print "Permission for %s" % (u.user_name) if getperm.vm: print "VM: %s" % (getperm.vm.id) if getperm.vm_pool: print "VmPool: %s" % (getperm.vm_pool.id) However, this seems a bit overkill. We have nearly 850 VMs and for a single user this takes about 25 minutes to run. Additionally, it doesn't seem to return any permission, although I know this user has some permissions over 2 VMs (not sure where is it messed up). I also tried using the system_service.permissions_service() but it seems to return only the global permissions. Is there an easier way to do this? Thanks!

5 14

More 4.1 Networking Questions
by Charles Tassell 10 Apr '17

10 Apr '17

Hi Everyone, Okay, I'm again having problems with getting basic networking setup with oVirt 4.1 Here is my situation. I have two servers I want to use to create an oVirt cluster, with two different networks. My "public" network is a 1G link on device em1 connected to my Internet feed, and my "storage" network is a 10G link connected on device p5p1 to my file server. Since I need to connect to my storage network in order to do the install, I selected p5p1 has the ovirtmgmt interface when installing the hosted engine. That worked fine, I got everything installed, so I used some ssh-proxy magic to connect to the web console and completed the install (setup a Storage domain and create a new network vmNet for VM networking and added em1 to it.) The problem was that when I added a second network device to the HostedEngine VM (so that I can connect to it from my public network) it would intermittently go down. I did some digging and found some IPV6 errors in the dmesg (IPv6: eth1: IPv6 duplicate address 2001:410:e000:902:21a:4aff:fe16:151 detected!) so I disabled IPv6 on both eth0 and eth1 in the HostedEngine and rebooted it. The problem is that when I restarted the VM, the eth1 device was missing. So, my question is: Can I add a second NIC to the HostedEngine VM and make it stick, or will it be deleted whenever the engine VM is restarted? Is there a better way to do what I'm trying to do, ie, should I setup ovirtmgmt on the public em1 interface, and then create the "storage" network after the fact for connecting to the datastores and such. Is that even possible, or required? I was thinking that it would be better for migrations and other management functions to happen on the faster 10G network, but if the HostedEngine doesn't need to be able to connect to the storage network maybe it's not worth the effort? Eventually I want to setup LACP on the storage network, but I had to wipe the servers and reinstall from scratch the last time I tried to set that up. I was thinking that it was because I setup the bonding before installing oVirt, so I didn't do that this time. Here are my /etc/sysconfig/network-scripts/ifcfg-* files in case I did something wrong there (I'm more familiar with Debian/Ubuntu network setup than CentOS) ifcfg-eth0: (ovirtmgmt aka storage) ---------------- BROADCAST=192.168.130.255 NETMASK=255.255.255.0 BOOTPROTO=static DEVICE=eth0 IPADDR=192.168.130.179 ONBOOT=yes DOMAIN=public.net ZONE=public IPV6INIT=no ifcfg-eth1: (vmNet aka Internet) ---------------- BROADCAST=192.168.1.255 NETMASK=255.255.255.0 BOOTPROTO=static DEVICE=eth1 IPADDR=192.168.1.179 GATEWAY=192.168.1.254 ONBOOT=yes DNS1=192.168.1.1 DNS2=192.168.1.2 DOMAIN=public.net ZONE=public IPV6INIT=no

5 6

Upgrade hypervisor to 4.1.1.1
by eric stam 10 Apr '17

10 Apr '17

Yesterday I executed an upgrade on my hypervisor to version 4.1.1.1 After the upgrade, it is impossible to start a virtual machine on it. The messages I found: Failed to connect socket to '/var/run/libvirt/virtlogd-sock': Connection refused [root@vm-1 log]# hosted-engine --vm-status | grep -i engine Engine status : {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "down"} state=EngineUnexpectedlyDown The redhead version: CentOS Linux release 7.3.1611 (Core) Is this a known problem? Regards, Eric

5 8

Installation of ovirtNode3.6 on VMware workstation is failing
by martin chamambo 10 Apr '17

10 Apr '17

Good day I am using ovirtEngine 4.0 and ovirtnode 4.0 .... on the same engine i also need to test ovirtNode 3.6 since its supported. Initially i struggled with installing ovirt engine 4.0 until i selected LVM thin provisioning the same trick is not working with ovirtNode3.6 ....any type of partition ,standard partition ,LVM ,LVM thin provisioning is not working is there anyone who experienced the same issue

3 6

Error in starting vdsm in host
by shubham dubey 10 Apr '17

10 Apr '17

Hello, I am trying to install and configure vdsm in a newly created centos 7.3.The packages that I have installed is vdsm, vdsm-cli and libvirtd. Now when I am trying to start the vdsm service I am getting this error. [root@localhost ~]# systemctl start vdsmd Job for vdsmd.service failed because the control process exited with error code. See "systemctl status vdsmd.service" and "journalctl -xe" for details. [root@localhost ~]# journalctl -xe -- The result is failed. Apr 07 23:06:47 localhost.localdomain systemd[1]: Dependency failed for MOM instance configured for VDSM purposes. -- Subject: Unit mom-vdsm.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mom-vdsm.service has failed. -- -- The result is dependency. Apr 07 23:06:47 localhost.localdomain systemd[1]: Job mom-vdsm.service/start failed with result 'dependency'. Apr 07 23:06:47 localhost.localdomain systemd[1]: Unit vdsmd.service entered failed state. Apr 07 23:06:47 localhost.localdomain systemd[1]: vdsmd.service failed. Apr 07 23:06:47 localhost.localdomain systemd[1]: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Invalid re Apr 07 23:06:47 localhost.localdomain systemd[1]: vdsmd.service holdoff time over, scheduling restart. Apr 07 23:06:47 localhost.localdomain systemd[1]: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is ma Apr 07 23:06:47 localhost.localdomain systemd[1]: start request repeated too quickly for vdsmd.service Apr 07 23:06:47 localhost.localdomain systemd[1]: Failed to start Virtual Desktop Server Manager. -- Subject: Unit vdsmd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit vdsmd.service has failed. -- -- The result is failed. Apr 07 23:06:47 localhost.localdomain systemd[1]: Dependency failed for MOM instance configured for VDSM purposes. -- Subject: Unit mom-vdsm.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mom-vdsm.service has failed. -- -- The result is dependency. Apr 07 23:06:47 localhost.localdomain systemd[1]: Job mom-vdsm.service/start failed with result 'dependency'. Apr 07 23:06:47 localhost.localdomain systemd[1]: Unit vdsmd.service entered failed state. Apr 07 23:06:47 localhost.localdomain systemd[1]: vdsmd.service failed. the momd service output is [root@localhost ~]# systemctl status momd ● momd.service - Memory Overcommitment Manager Daemon Loaded: loaded (/usr/lib/systemd/system/momd.service; static; vendor preset: disabled) Active: inactive (dead) since Fri 2017-04-07 23:15:32 IST; 3s ago Process: 13031 ExecStart=/usr/sbin/momd -c /etc/momd.conf -d --pid-file /var/run/momd.pid (code=exited, status=0/SUCCESS) Main PID: 13034 (code=exited, status=0/SUCCESS) Apr 07 23:15:32 localhost.localdomain systemd[1]: Starting Memory Overcommitment Manager Daemon... Apr 07 23:15:32 localhost.localdomain systemd[1]: PID file /var/run/momd.pid not readable (yet?) after start. Apr 07 23:15:32 localhost.localdomain systemd[1]: Started Memory Overcommitment Manager Daemon. Apr 07 23:15:32 localhost.localdomain python[13034]: No worthy mechs found the output for starting mom-vdsm service is [root@localhost ~]# systemctl restart mom-vdsm.service A dependency job for mom-vdsm.service failed. See 'journalctl -xe' for details. [root@localhost ~]# journalctl -xe -- The result is failed. Apr 07 23:18:40 localhost.localdomain systemd[1]: Dependency failed for MOM instance configured for VDSM purposes. -- Subject: Unit mom-vdsm.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mom-vdsm.service has failed. -- -- The result is dependency. Apr 07 23:18:40 localhost.localdomain systemd[1]: Job mom-vdsm.service/start failed with result 'dependency'. Apr 07 23:18:40 localhost.localdomain systemd[1]: Unit vdsmd.service entered failed state. Apr 07 23:18:40 localhost.localdomain systemd[1]: vdsmd.service failed. Apr 07 23:18:40 localhost.localdomain systemd[1]: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Invalid re Apr 07 23:18:40 localhost.localdomain systemd[1]: vdsmd.service holdoff time over, scheduling restart. Apr 07 23:18:40 localhost.localdomain systemd[1]: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is ma Apr 07 23:18:40 localhost.localdomain systemd[1]: start request repeated too quickly for vdsmd.service Apr 07 23:18:40 localhost.localdomain systemd[1]: Failed to start Virtual Desktop Server Manager. -- Subject: Unit vdsmd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit vdsmd.service has failed. -- -- The result is failed. Apr 07 23:18:40 localhost.localdomain systemd[1]: Dependency failed for MOM instance configured for VDSM purposes. -- Subject: Unit mom-vdsm.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mom-vdsm.service has failed. -- -- The result is dependency. Apr 07 23:18:40 localhost.localdomain systemd[1]: Job mom-vdsm.service/start failed with result 'dependency'. Apr 07 23:18:40 localhost.localdomain systemd[1]: Unit vdsmd.service entered failed state. Apr 07 23:18:40 localhost.localdomain systemd[1]: vdsmd.service failed. Thanks, Shubham

2 3

[Ovirt 4.0 Python SDK] Host fail to move in Maintenance State
by TranceWorldLogic . 10 Apr '17

10 Apr '17

Hi, I was trying to deactivate host via python SDK but found that host is not moving in Maintenance State. In this scenario, I found that I have one additional network added in cluster but not setup on Host. Hence it retrying in background for network sync. Because of this I suspect host is fail to move in maintenance state. Can someone help me how to force via python API to deactivate host ? Or Can I stop background sync of host ? Thanks, ~Rohit

2 1

SKD4
by Fabrice Bacchella 09 Apr '17

09 Apr '17

I trying to migrate my python code from sdk3 to sdk4, is there any migration doc, documentation help about that ? Even google is unable to find anything relevant about that.

5 23

Initial network setup question ...
by Alan Bunch 09 Apr '17

09 Apr '17

--_000_BN6PR02MB27088B8677653C5B013E5F7CFA0C0BN6PR02MB2708namp_ Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Hello all, I have a question about the initial setup for ovirt. I have 3 nodes that I = am about ready to install a hyper converged setup using Gluster for storage= and hosted-engine. Gluster is setup and the volumes are mounted. My question is this: What does the networking setup need to look like at install time ? Do I nee= d to setup all of the bonds, vlans and bridges before I start the install o= r should I just set an ovirtmgmt bond/vlan/bridge and setup the rest of the= networking inside of ovirt. I expect to need 3 or 4 networks/vlan to match= my existing networks to attach vm's to. Any help or pointers would be appreciated. Thank You --_000_BN6PR02MB27088B8677653C5B013E5F7CFA0C0BN6PR02MB2708namp_ Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> Hello all,<o:p></o:p> <o:p> </o:p> I have a question about the initial setup for ovirt.= I have 3 nodes that I am about ready to install a hyper converged setup us= ing Gluster for storage and hosted-engine. Gluster is setup and the volumes= are mounted. <o:p></o:p> <o:p> </o:p> My question is this:<o:p></o:p> What does the networking setup need to look like at = install time ? Do I need to setup all of the bonds, vlans and bridges befor= e I start the install or should I just set an ovirtmgmt bond/vlan/bridge an= d setup the rest of the networking inside of ovirt. I expect to need 3 or 4 networks/vlan to match my existin= g networks to attach vm's to.<o:p></o:p> <o:p> </o:p> Any help or pointers would be appreciated.<o:p></o:p= > <o:p> </o:p> Thank You<o:p></o:p> </div> </body> </html> --_000_BN6PR02MB27088B8677653C5B013E5F7CFA0C0BN6PR02MB2708namp_--

2 1

oVirt repositories 101; or everything you wanted to know about oVirt repositories and didn't ask
by Eyal Edri 09 Apr '17

09 Apr '17

Hi oVirt developers and users, Some of you might be familiar with the oVirt repositories and all their flavors, while some of you are just familiar with the official releases. The fact is, we have plenty of them and each has its own role and a right usage. Moreover, we did a significant overhaul on all the repositories in the past months, So hopefully now it will be easier to explain which repo to use when. I'll start with reviewing each oVirt repository and give a bit of background and the logic behind it, how to consume it and the relevant usage for it. For simplicity, I'll review the repositories on the 4.1 release, but it valid for all other oVirt releases ( except 'master' which doesn't have an official or pre-release repositories ). I will also upload this information to the oVirt.org site, but since this is important, I didn't want to wait with the sending this email. *oVirt repositories* *Official repositories* *Desc:* here you can find the official signed oVirt RPMs, immediately after an official release has been done. *Path:* http://resources.ovirt.org/pub/ovirt-4.1/rpm/$distro *Update frequency:* on every oVirt release, usually happens on a monthly cadence. *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm *Who should use it? * oVirt users, developers or anyone who wants a final and official release *Pre-release repositories* *Desc:* here you can find the pre-release bits of oVirt RC builds, just before they are released. *Path:* http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/$distro *Update frequency:* usually on a weekly or bi-weekly basis *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt- release41-pre.rpm *Who should use it? * oVirt users, developers or anyone who wants to try out oVirt new version before its out, Keeping in mind this isn't a fully verified release and might still have critical bugs which are not fixed yet. Packages in this repo are verified by automation and checked by humans for basic sanity before publishing. *Nightly snapshot (verified) repositories* *Desc:* here you can find the nightly snapshot of RPMs, which passed basic sanity by our 'oVirt System Tests' framework in the oVirt CI system. *Path:* http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm/$distro *Update frequency:* Every night *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt- release41-snapshot.rpm *Who should use it? * oVirt users, developers or anyone who wants to try out oVirt latest bits right of the build oven! We trust our system tests, which already run more than 40 various tests such as 'add host', 'create VM', 'live migration' and more! *** Important note: the snapshot repositories are verified only in master currently, we might do the same for 4.1 soon, as we see no issues with master so far ** * *The above repos should suffice to most usres and developers, but if you feel its not enough and you still need a faster verified repo, look below! * *Advanced oVirt repositories* *Builds artifacts repo* *Desc:* This is a new feature from oVirt 'standard CI' project, where each 'build-artifacts' job is actually a yum repo as well. *Path:* http://jenkins.ovirt.org/job/ovirt-engine_4.1_ build-artifacts-on-demand-el7-x86_64/lastSuccessfulBuild/ artifact/exported-artifacts ( example ) *Update frequency:* after each commit or 'ci please build' comment *Release rpm: *N/A *Who should use it? * oVirt developers who need latest RPMs from another oVirt project and cannot or need not wait for that project`s packages to pass OST". oVirt developers running manual OST job and need to test an open Gerrit patch, using the 'ci please build' command. *Tested repositories* *Desc:* The tested repositories hold all the oVIrt packages which passed CI ( similar to snapshot repos ) and retain also version history for X versions back. *Path:* http://resources.ovirt.org/repos/ovirt/tested/4.1/rpm/$distro *Update frequency:* after each 'build artifacts' job is triggered by any oVirt project and if the packages passed sanity checks *Release rpm: *N/A *Who should use it? * If you want to have latest and greatest oVirt packages and can't wait for the nightly repo. If you are testing upgrades or need more than one version of a pacakge in your repo. *Experimental repositories * *Desc:* Internal CI repos which are a part of the 'experimental' flow which runs OST on each built package. *Path:* http://resources.ovirt.org/repos/ovirt/experimental/ 4.1/latest.tested/rpm/el7/$distro *Update frequency:* after each 'build artifacts' job is triggered by any oVirt project and if the packages passed sanity checks *Release rpm: *N/A *Who should use it? * *No one other than internal CI jobs.* These repos are constantly refreshed and RPMs are being removed from them, so they are very prone to errors, please don't use them. I hope this makes a bit of order in all the repos and how to use them. If you still have questions, please don't hesitate to contact the infra team at infra(a)ovirt.org or just reply to this thread. -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

moving disk from one storage domain to another
by Bill James 09 Apr '17

09 Apr '17

We are trying to convert our qa environment from local nfs to gluster. When I move a disk with a VM that is running on same server as the storage it fails. When I move a disk with VM running on a different system it works. VM running on same system as disk: 2017-04-06 13:31:00,588 ERROR (jsonrpc/6) [virt.vm] (vmId='e598485a-dc74-43f7-8447-e00ac44dae21') Unable to start replication for vda to {u'domainID': u'6affd8c3-2c51-4cd1-8300-bfbbb14edbe9', 'volumeInfo': {'domainID': u'6affd8c3-2c 51-4cd1-8300-bfbbb14edbe9', 'volType': 'path', 'leaseOffset': 0, 'path': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5', 'volumeID': u'30fd46c9-c738-4b13-aeca-3dc9ffc677f5', 'leasePath': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5.lease', 'imageID': u'7ae9b3f7-3507-4469-a080-d0944d0ab753'}, 'diskType': 'file', 'format': 'cow', 'cache': 'none', u'volumeID': u'30fd46c9-c738-4b13-aeca-3dc9ffc677f5', u'imageID': u'7ae9b3f7-3507-4469-a080-d0944d0ab753', u'poolID': u'8b6303b3-79c6-4633-ae21-71b15ed00675', u'device': 'disk', 'path': u'/rhev/data-center/8b6303b3-79c6-4633-ae21-71b15ed00675/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5', 'propagateErrors': u'off', 'volumeChain': [{'domainID': u'6affd8c3-2c51-4cd1-8300-bfbbb14edbe9', 'volType': 'path', 'leaseOffset': 0, 'path': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/6756eb05-6803-42a7-a3a2-10233bf2ca8d', 'volumeID': u'6756eb05-6803-42a7-a3a2-10233bf2ca8d', 'leasePath': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/6756eb05-6803-42a7-a3a2-10233bf2ca8d.lease', 'imageID': u'7ae9b3f7-3507-4469-a080-d0944d0ab753'}, {'domainID': u'6affd8c3-2c51-4cd1-8300-bfbbb14edbe9', 'volType': 'path', 'leaseOffset': 0, 'path': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5', 'volumeID': u'30fd46c9-c738-4b13-aeca-3dc9ffc677f5', 'leasePath': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5.lease', 'imageID': u'7ae9b3f7-3507-4469-a080-d0944d0ab753'}]} (vm:3594) Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 3588, in diskReplicateStart self._startDriveReplication(drive) File "/usr/share/vdsm/virt/vm.py", line 3713, in _startDriveReplication self._dom.blockCopy(drive.name, destxml, flags=flags) File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 69, in f ret = attr(*args, **kwargs) 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 684, in blockCopy if ret == -1: raise libvirtError ('virDomainBlockCopy() failed', dom=self) libvirtError: internal error: unable to execute QEMU command 'drive-mirror': Could not open '/rhev/data-center/8b6303b3-79c6-4633-ae21-71b15ed00675/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5': Permission denied [root@ovirt1 test vdsm]# ls -l /rhev/data-center/8b6303b3-79c6-4633-ae21-71b15ed00675/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5 -rw-rw---- 2 vdsm kvm 197120 Apr 6 13:29 /rhev/data-center/8b6303b3-79c6-4633-ae21-71b15ed00675/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5 Then if I try and rerun it it says, even though move failed: 2017-04-06 13:49:27,197 INFO (jsonrpc/1) [dispatcher] Run and protect: getAllTasksStatuses, Return response: {'allT asksStatus': {'078d962c-e682-40f9-a177-2a8b479a7d8b': {'code': 212, 'message': 'Volume already exists', 'taskState': 'finished', 'taskResult': 'cleanSuccess', 'taskID': '078d962c-e682-40f9-a177-2a8b479a7d8b'}}} (logUtils:52) So now I have to clean up the disks that it failed to move so I can migrate the VM and then move the disk again. Or so it seems. Failed move disks do exist in new location, even though it "failed". vdsm.log attached. ovirt-engine-tools-4.1.0.4-1.el7.centos.noarch vdsm-4.19.4-1.el7.centos.x86_64

4 4