January 2022 - Users - oVirt List Archives

Cinderlib RBD ceph template issues
by Sketch 01 Feb '22

01 Feb '22

This is on oVirt 4.4.8, engine on CS8, hosts on C8, cluster and DC are both set to 4.6. With a newly configured cinderlib/ceph RBD setup. I can create new VM images, and copy existing VM images, but I can't copy existing template images to RBD. When I do, I try, I get this error in cinderlib.log (see below), which sounds like the disk already exists there, but it definitely does not. This leaves me unable to create new VMs on RBD, only migrate existing VM disks. 2021-09-01 04:31:05,881 - cinder.volume.driver - INFO - Driver hasn't implemented _init_vendor_properties() 2021-09-01 04:31:05,882 - cinderlib-client - INFO - Creating volume '0e8b9aca-1eb1-4837-ac9e-cb3d8f4c1676', with size '500' GB [5c5d0a6b] 2021-09-01 04:31:05,943 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Entity '<class 'cinder.db.sqlalchemy.models.Volume'>' has no property 'glance_metadata' [5c5d0a6b] 2021-09-01 04:31:05,944 - cinder - CRITICAL - Unhandled error Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 455, in create self._raise_with_resource() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 222, in _raise_with_resource six.reraise(*exc_info) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 448, in create model_update = self.backend.driver.create_volume(self._ovo) File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 986, in create_volume features=client.features) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 190, in doit result = proxy_call(self._autowrap, f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 148, in proxy_call rv = execute(f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 129, in execute six.reraise(c, e, tb) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 83, in tworker rv = meth(*args, **kwargs) File "rbd.pyx", line 629, in rbd.RBD.create rbd.ImageExists: [errno 17] RBD image already exists (error creating image) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/base.py", line 399, in _entity_descriptor return getattr(entity, key) AttributeError: type object 'Volume' has no attribute 'glance_metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 170, in main args.command(args) File "./cinderlib-client.py", line 208, in create_volume backend.create_volume(int(args.size), id=args.volume_id) File "/usr/lib/python3.6/site-packages/cinderlib/cinderlib.py", line 175, in create_volume vol.create() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 457, in create self.save() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 628, in save self.persistence.set_volume(self) File "/usr/lib/python3.6/site-packages/cinderlib/persistence/dbms.py", line 254, in set_volume self.db.volume_update(objects.CONTEXT, volume.id, changed) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 236, in wrapper return f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 184, in wrapper return f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 2570, in volume_update result = query.filter_by(id=volume_id).update(values) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/query.py", line 3818, in update update_op.exec_() File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1670, in exec_ self._do_pre_synchronize() File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1743, in _do_pre_synchronize self._additional_evaluators(evaluator_compiler) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1912, in _additional_evaluators values = self._resolved_values_keys_as_propnames File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1831, in _resolved_values_keys_as_propnames for k, v in self._resolved_values: File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1818, in _resolved_values desc = _entity_descriptor(self.mapper, k) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/base.py", line 402, in _entity_descriptor "Entity '%s' has no property '%s'" % (description, key) sqlalchemy.exc.InvalidRequestError: Entity '<class 'cinder.db.sqlalchemy.models.Volume'>' has no property 'glance_metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 390, in <module> sys.exit(main(sys.argv[1:])) File "./cinderlib-client.py", line 176, in main sys.stderr.write(traceback.format_exc(e)) File "/usr/lib64/python3.6/traceback.py", line 167, in format_exc return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 121, in format_exception type(value), value, tb, limit=limit).format(chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 509, in __init__ capture_locals=capture_locals) File "/usr/lib64/python3.6/traceback.py", line 338, in extract if limit >= 0: TypeError: '>=' not supported between instances of 'InvalidRequestError' and 'int'

3 4

gerrit.ovirt.org upgrade
by Denis Volkov 01 Feb '22

01 Feb '22

Hello Gerrit.ovirt.org will be upgraded later today. Approximate start time is 4PM UTC. During the upgrade service will be shut down and so will not be available. -- Denis Volkov

3 10

no snaphot but engines complains there is one when trying to remove disk
by Nathanaël Blanchet 01 Feb '22

01 Feb '22

Hi all, A colleague launched this morning a snapshot creation, there was no error message but he wasn't able to start the vm anymore, with this issue : VM PSI-SYB-DEV is down with error. Exit message: Unable to get volume size for domain a5be6cae-f0c8-452f-b7cd-70d0e5eed710 volume 109fac1e-c2e3-4ba6-9867-5d1c94d3a447.. I tried many things but nothing works: it is impossible to remove this disk, or copy it, or clone the vm : Cannot detach Virtual Disk. The disk is already configured in a snapshot. In order to detach it, remove the disk's snapshots. There is no snaphost listed into webui or api (so not snapshot id), while disk_snapshots exists into the associated storage domain. So I tried to remove disks snapshot direvctly with API followind the DELETE method |DELETE /api/storagedomains/{storage_id}/disksnapshots/{image_id}| [Cannot remove Disk Snapshot. VM\'s Snapshot does not exist.] In conclusion: vm_disks can't be removed because of the non existent associated vm's snapshot id. I tried to remove vm_snapshots disks references directly into the postgres DB but I didn't find the correct table. What can I do now? Your precious help is welcome. -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

3 9

oVirt 4.4.10 Async update #2
by Sandro Bonazzola 30 Jan '22

30 Jan '22

On January 26th 2022 the oVirt project released an async update to the following packages: - ovirt-engine 4.4.10.6 Fixing the following bugs: - [BZ 2044277 <https://bugzilla.redhat.com/show_bug.cgi?id=2044277>] - Replace ovirt-engine-extension-logger-log4j with internal ovirt-engine implementation Package ovirt-engine-extension-logger-log4j has been obsoleted and replaced by internal ovirt-engine implementation in oVirt Engine 4.4.10.6. During upgrade from previous oVirt versions to oVirt 4.4.10 ovirt-engine-extension-logger-log4j package is uninstalled if it was previously installed. If you used ovirt-engine-extension-logger-log4j in previous oVirt versions, you will need to manually remove existing ovirt-engine-extension-logger-log4j configuration files and configure the new feature of sending log records to remote syslog service according to the Administration Guide. Also after successful upgrade to oVirt 4.4.10 you can manually uninstall log4j12 package without breaking oVirt setup: $ dnf remove log4j12 - [BZ 2044257 <https://bugzilla.redhat.com/show_bug.cgi?id=2044257>] - Bump snmp4j library version to remove dependency on log4j oVirt Engine 4.4.10.6 is requiring snmp4j >= 3.6.4, which no longer depends on log4j library -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

5 7

Problems with OVirt 4.3 on old IBM HS22 blades
by manieq.net＠gmail.com 28 Jan '22

28 Jan '22

Hi all, I'm pretty new to OVirt so forgive me if this problems is trivial... I received an old IBM BladeCenter H chassis with a few HS22 blades. Some of them are successfully working in my Ovirt farm, but some not. The NonOperational nodes are not used because of missing Westmere model. I use 4.3.10 wersion because 4.4 did not supported some old HW (net adapters, IIRC). The problem is that many blades are almost identical. For example ("Hosts" page --> "General" tab --> "Hardware" section): * BLADE 1 (not working): Manufacturer:IBM Family:System x Product Name:BladeCenter HS22 -[7870H4G]- Version:07 UUID:e36b6686-d111-11df-9dce-e41f13cb90d0 Serial Number:06FP476 CPU Model Name:Intel(R) Xeon(R) CPU X5670 @ 2.93GHz CPU Type:Intel Nehalem IBRS SSBD Family CPU Sockets:2 CPU Cores per Socket:6 CPU Threads per Core:2 (SMT Enabled) * BLADE 2 (working fine): Manufacturer: IBM Family: System x Product Name: BladeCenter HS22 -[7870H4G]- Version: 07 UUID: 30f2fcc8-d0ce-11df-bc12-e41f13cb90cc Serial Number: 06FP469 CPU Model Name: Intel(R) Xeon(R) CPU X5670 @ 2.93GHz CPU Type: Intel Westmere IBRS SSBD Family CPU Sockets: 2 CPU Cores per Socket: 6 CPU Threads per Core: 2 (SMT Enabled) They have same CPU, same HW model, even S/N shows they were produced in the same time. How is it possible to identify X5670 so differently? Any hints/suggestions what to check/change? "Software" section of BLADE 2 (the good one): OS Version: RHEL - 7 - 8.2003.0.el7.centos OS Description: oVirt Node 4.3.10 Kernel Version: 3.10.0 - 1127.8.2.el7.x86_64 KVM Version: 2.12.0 - 44.1.el7_8.1 LIBVIRT Version: libvirt-4.5.0-33.el7_8.1 VDSM Version: vdsm-4.30.46-1.el7 SPICE Version: 0.14.0 - 9.el7 GlusterFS Version: glusterfs-6.9-1.el7 CEPH Version: librbd1-10.2.5-4.el7 Open vSwitch Version: openvswitch-2.11.0-4.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1, SSBD: 3 VNC Encryption: Disabled Best regards, Mariusz

3 2

Re: [ovirt-devel] Re: how to UI/API certificates with a valid one (ex: let's encrypt) ? ( as open shift required one )
by Guillaume Pavese 26 Jan '22

26 Jan '22

Hello, I too have a problem using custom cert with OCP provisioning on oVirt I followed the following documentation to update the default cert with my letsencrypt one : https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/ht… This documentation is similar to the one linked by Yedidyah Bar David : https://www.ovirt.org/documentation/administration_guide/index.html#appe-Re… After following these steps, I can verify in my browser that the engine is now behind the new custom certificate from letsencrypt. However, the old certificate is still served by the url : https://engine.fqdn/ovirt-engine/services/pki-resource?resource=ca-certific… When running openshift-install create install-config, the certificate that is automaticlly retrived from engine.fqdn:443 is the old one, not the new custom one. Are there missing steps in the above procedures? Best, Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group On Tue, Jan 25, 2022 at 1:57 AM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > Il giorno dom 23 gen 2022 alle ore 08:15 Eric Tiquet < > eric.tiquet(a)gmail.com> ha scritto: > >> Hello community, >> Would like to use ovirt & openshift, a this might be trivial but I am >> juste blocked at 'step two'. >> (As openshift refuse to use the ovirt without valid certificates and the >> insecure workaround does'not work) >> >> I can't find any usefull information to setup the UI/API certificates. ( >> ex: there is no apache...) >> Could someone please point me to the correct tuto's or instruction ? >> > > This is the development mailing list. For looking for help on oVirt, I > recommend asking on user mailing list instead: > https://lists.ovirt.org/archives/list/users@ovirt.org/ . > I assume you are following > https://docs.okd.io/4.9/installing/installing_rhv/installing-rhv-default.ht… > > If the documentation there is not clear enough, I would recommend opening > an issue on https://github.com/openshift/openshift-docs/issues or > discussing it on https://github.com/openshift/okd/discussions > > > >> >> With kind regards, >> Eric >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/A6S264FUJVUNO… >> > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://www.redhat.com/> > > *Red Hat respects your work life balance. Therefore there is no need to > answer this email out of your office hours.* > > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/Y4XAESPURFI2T… > -- Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. <https://interactiv-group.com/disclaimer.html>

2 1

New oVirt setup with OVN : Hypervisor with LACP bond : queries
by ravi k 26 Jan '22

26 Jan '22

Hello team, Thank you for all the wonderful work you've been doing. I'm starting out new with oVirt and OVN. So please excuse me if the questions are too naive. We intend to do a POC to check if we can migrate VMs off our current VMware to oVirt. The intention is to migrate the VMs with the same IP into oVirt. We've setup oVirt with three hypervisors. All of them have four ethernet adapters. We have SDN implemented in our network and LACP bonds are created at the switch level. So we've created two bonds, bond0 and bond1 in each hypervisor. bond0 has the logical networks with vlan tagging created like bond0.101, bond0.102 etc. As a part of the POC we also want to explore OVN as well to check if we can implement a zero trust security policy. Here are the questions now :) 1. We would like to migrate VMs with the current IP into oVirt. Is it possible to achieve this? I've been reading notes and pages that mention about extending the physical network into OVN. But it's a bit confusing on how to implement it. How do we connect OVN to the physical network? Does the fact that we have a SDN make it easier to get this done? I am still reading the ovn-architecture page. It is mentioned that the gateway is the component that extends a tunnel-based logical network into a physical network. 2. We have the IP for the hypervisor assigned on a logical network(ovirtmgmt) in bond0. I read in https://lists.ovirt.org/archives/list/users@ovirt.org/thread/CIE6MZ47GRCEX4… that oVirt does not care about how the IP is configured when creating the tunnels. 3. Once we have OVN setup, ovn logical networks created and VMs created/migrated, how do we establish the zero trust policy? From what I've read there are ACLs and security groups. Any pointers on where to explore more about implementing it. If you've read till here, thank you for your patience. Regards, ravi

3 7

VM Migrations failing to newly upgraded host
by k.gunasekhar＠non.keysight.com 25 Jan '22

25 Jan '22

I am able to power on vms on newly upgraded host, But not able to migrate VMs from other hosts to new host or newly upgraded hosts to other hosts. This was worked fine before upgraded. i see below logs Unable to read from monitor: Connection reset by peer internal error: qemu unexpectedly closed the monitor: 2022-01-24T17:51:46.598571Z qemu-kvm: get_pci_config_device: Bad config > 2022-01-24T17:51:46.598627Z qemu-kvm: Failed to load PCIDevice:config 2022-01-24T17:51:46.598635Z qemu-kvm: Failed to load pcie-root-port:parent_obj.parent_obj.parent_obj 2022-01-24T17:51:46.598642Z qemu-kvm: error while loading state for instance 0x0 of device '0000:00:02.0/pcie-root-port' 2022-01-24T17:51:46.598830Z qemu-kvm: load of migration failed: Invalid argument Guest agent is not responding: QEMU guest agent is not connected Guest agent is not responding: QEMU guest agent is not connected Guest agent is not responding: QEMU guest agent is not connected OS Version: RHEL - 8.6 - 1.el8 OS Description: CentOS Stream 8 Kernel Version: 4.18.0 - 358.el8.x86_64 KVM Version: 6.1.0 - 5.module_el8.6.0+1040+0ae94936 LIBVIRT Version: libvirt-7.10.0-1.module_el8.6.0+1046+bd8eec5e VDSM Version: vdsm-4.40.100.2-1.el8 SPICE Version: 0.14.3 - 4.el8 GlusterFS Version: [N/A] CEPH Version: librbd1-16.2.7-1.el8s Open vSwitch Version: openvswitch-2.11-1.el8 Nmstate Version: nmstate-1.2.1-0.1.alpha1.el8

3 2

Migration failed due to an Error: Fatal error during migration
by Gunasekhar Kothapalli 25 Jan '22

25 Jan '22

I am able to power on vms on newly upgraded host, But not able to migrate VMs from other hosts to new host or newly upgraded hosts to other hosts. This was worked fine before upgraded. Host logs ============================================================================== Unable to read from monitor: Connection reset by peer internal error: qemu unexpectedly closed the monitor: 2022-01-24T17:51:46.598571Z qemu-kvm: get_pci_config_device: Bad config > 2022-01-24T17:51:46.598627Z qemu-kvm: Failed to load PCIDevice:config 2022-01-24T17:51:46.598635Z qemu-kvm: Failed to load pcie-root-port:parent_obj.parent_obj.parent_obj 2022-01-24T17:51:46.598642Z qemu-kvm: error while loading state for instance 0x0 of device '0000:00:02.0/pcie-root-port' 2022-01-24T17:51:46.598830Z qemu-kvm: load of migration failed: Invalid argument Guest agent is not responding: QEMU guest agent is not connected Guest agent is not responding: QEMU guest agent is not connected Guest agent is not responding: QEMU guest agent is not connected Engine Logs =========================================================== 2022-01-24 11:31:25,080-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-21) [] Adding VM '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) to re-run list 2022-01-24 11:31:25,099-07 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2331914) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal error during migration (VM: zzz2019, Source: lcoskvmp07.cos.is.keysight.com, Destination: lcoskvmp03.cos.is.keysight.com) 2022-01-24 18:39:47,897-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-771) [a78e85d4-068a-41c1-a8fa-b3acd8c69317] EVENT_ID: VM_MIGRATION_START(62), Migration started (VM: zzz2019, Source: lcoskvmp07.cos.is.keysight.com, Destination: lcoskvmp03.cos.is.keysight.com, User: k.gunasekhar@non.keysight.com@KEYSIGHT). 2022-01-24 18:40:01,417-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-27) [] VM '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) was unexpectedly detected as 'Down' on VDS 'ee23b44d-976d-4889-8769-59b56e4b23c0'(lcoskvmp03.cos.is.keysight.com) (expected on '0d58953f-b3cc-4bac-b3b2-08baeeee1bca') 2022-01-24 18:40:01,589-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-27) [] VM '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) was unexpectedly detected as 'Down' on VDS 'ee23b44d-976d-4889-8769-59b56e4b23c0'(lcoskvmp03.cos.is.keysight.com) (expected on '0d58953f-b3cc-4bac-b3b2-08baeeee1bca') 2022-01-24 18:40:01,589-07 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-27) [] Migration of VM 'zzz2019' to host 'lcoskvmp03.cos.is.keysight.com' failed: VM destroyed during the startup. 2022-01-24 18:40:01,591-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-17) [] VM '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) moved from 'MigratingFrom' --> 'Up' 2022-01-24 18:40:01,591-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-17) [] Adding VM '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) to re-run list 2022-01-24 18:40:01,611-07 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2348837) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal error during migration (VM: zzz2019, Source: lcoskvmp07.cos.is.keysight.com, Destination: lcoskvmp03.cos.is.keysight.com) [root@lcosovirt02 ovirt-engine]#

3 3

Import an exported VM using Ansible
by paolo＠airaldi.it 25 Jan '22

25 Jan '22

Hello everybody! I'm trying to automate a copy of a VM from one Datacenter to another using an Ansible.playbook. I'm able to: - Create a snapshot of the source VM - create a clone from the snapshot - remove the snapshot - attach an Export Domain - export the clone to the Export Domain - remove the clone - detach the Export domain from the source Datacenter and attach to the destination. Unfortunately I cannot find a module to: - import the VM from the Export Domain - delete the VM image from the Export Domain. Any hint on how to do that? Thanks in advance. Cheers. Paolo PS: if someone is interested I can share the playbook.

4 3