- Users - oVirt List Archives

How to run oVirt on CentOS 8 (or 8.1 or Stream)
by Nate Revo 13 Dec '19

13 Dec '19

I have a system that requires the 4x kernel to run and wanted to run oVirt on top of CentOS. Seems as I'm looking around, rhel/centos 8 support for ovirt is slated for v 4.4. What's the progress with running on Centos 8+ and how do I run ovirt on Centos 8, now. Thanks in advance, -Nate Revo P.S. Will code for pizza -- Nathan Revo, RHCE OpenShift Specialist Solutions Architect Red Hat NorthWest Strategic <https://www.redhat.com/> nrevo(a)redhat.com M: 801-885-8182 <https://www.redhat.com/>

2 1

ovirt vdsm and networking
by kim.kargaard＠noroff.no 13 Dec '19

13 Dec '19

Hi, We are running CentOS and ovirt 4.3.4. We currently have four nodes and have set up the networks as follows: ovirtmanagmeent network - set up as a tagged vlan with a static IP SAN network - set up as a tagged vlan with a static IP student network - set up as a tagged vlan fw network - set up as a tagged vlan The ovirtmanagement and SAN networks were configured on the CentOS boxes during after installing CentOS and before adding the nodes as hosts. The student network and the fw network were configured through the ovirt admin panel. However, because of this, the student network is not assigned a static IP on the nodes and serves the VM's using the DHCP on the firewall. The ovirt management network is set as the display network and every time I try to change that to the student network, ovirt admin panel tells me that I can't because there is no IP address assigned to the student network vlan. I tried using ip addr add to add a static IP on the one CentOS node, but this does not get picked up by ovirt and of course ovirt controls the actual vlan files on the CentOS box through VDSM, so any changes I make there will likely just be overwritten. So, my question is, should I stop VDSM, add the IP to the vlan files on the CentOS nodes and then restart VDSM or is there a proper way of solving this? I need the Display Network to be set to the student network. Thank you for any help. Kim

3 3

oVirt 4.4.0 Alpha release is now available for testing
by Sandro Bonazzola 13 Dec '19

13 Dec '19

oVirt 4.4.0 Alpha release is now available for testing The oVirt Project is excited to announce the availability of the alpha release of oVirt 4.4.0 for testing, as of December 13th, 2019 This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics on top of oVirt 4.3. Important notes before you try it Please note this is an Alpha release. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production, and it is not feature complete. In particular, please note that upgrades from 4.3 and future upgrades from this alpha to the final 4.4 release from this version are not supported. Some of the features included in oVirt 4.4.0 Alpha require content that will be available in CentOS Linux 8.1 which is currently being built from Red Hat Enterprise Linux 8.1. If you want to have a better experience you can test oVirt 4.4.0 Alpha on Red Hat Enterprise Linux 8.1. Known Issues - After installation open the Default cluster and hit “Save”, for any other new Cluster using CPU autodetection the dialog needs to be explicitly saved after the detection happens, after first host is added. (bug https://bugzilla.redhat.com/1770697) - Migrate, Cluster Upgrade, Export VM buttons cannot be clicked. Fixed in ovirt-engine-ui-extensions-1.0.11 Installation instructions For the engine: either use appliance or: - Install CentOS Linux 7.7 minimal from http://centos.mirror.garr.it/centos/7.7.1908/isos/x86_64/CentOS-7-x86_64-Mi… - yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - yum update (reboot if needed) - yum install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8.0 from http://centos.mirror.garr.it/centos/8.0.1905/isos/x86_64/CentOS-8-x86_64-19… ; select minimal installation - yum config-manager --set-enabled PowerTools - yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - yum update (reboot if needed) - Attach the host to engine and let it be deployed. What’s new in oVirt 4.4.0 Alpha? - Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8), for both oVirt Node and standalone CentOS Linux hosts - Easier network management and configuration flexibility with NetworkManager - VMs based on a more modern Q35 chipset with legacy seabios and UEFI firmware - Support for direct passthrough of local host disks to VMs - Live migration improvements for High Performance guests. - New Windows Guest tools installer based on WiX framework now moved to VirtioWin project - Dropped support for cluster level prior to 4.2 - Dropped SDK3 support - 4K disks support - Exporting a VM to a data domain - Editing of floating disks - Integrating ansible-runner into engine, which allows a more detailed monitoring of playbooks executed from engine - Adding/reinstalling hosts are now completely based on Ansible - The OpenStack Neutron Agent cannot be configured by oVirt anymore, it should be configured by TripleO instead This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but < 8.0) * CentOS Linux (or similar) 7.7 or later (but < 8.0) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.0 or later * CentOS Linux (or similar) 8.0 or later * oVirt Node 4.4 based on CentOS Linux 8.0 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. If you manage more than one oVirt instance, OKD or RDO we also recommend to try ManageIQ <http://manageiq.org/>. In such a case, please be sure to take the qc2 image and not the ova image. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.0 release highlights: http://www.ovirt.org/release/4.4.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.0/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- 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.*

2 2

Re: Ovirt OVN help needed
by Strahil 13 Dec '19

13 Dec '19

Hi Dominik, Thanks for the reply. Sadly the openstack module is missing on the engine and I have to figure it out. Can't I just undeploy the ovn and then redeploy it back ? Best Regards, Strahil NikolovOn Dec 12, 2019 09:32, Dominik Holler <dholler(a)redhat.com> wrote: > > The cleanest way to clean up is to remove all entities on the OpenStack Network API on ovirt-provider-ovn, e.g. by something like > https://gist.github.com/dominikholler/19bcdc5f14f42ab5f069086fd2ff5e37#file… > This should work, if not, please report a bug. > > To bypass the ovirt-provider-ovn, which is not recommended and might end in an inconsistent state, you could use ovn-nbctl . > > > > On Thu, Dec 12, 2019 at 3:33 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Hi Community, >> >> can someone hint me how to get rid of some ports? I just want to 'reset' my ovn setup. >> >> Here is what I have so far: >> >> [root@ovirt1 openvswitch]# ovs-vsctl list interface >> _uuid : be89c214-10e4-4a97-a9eb-1b82bc433a24 >> admin_state : up >> bfd : {} >> bfd_status : {} >> cfm_fault : [] >> cfm_fault_status : [] >> cfm_flap_count : [] >> cfm_health : [] >> cfm_mpid : [] >> cfm_remote_mpids : [] >> cfm_remote_opstate : [] >> duplex : [] >> error : [] >> external_ids : {} >> ifindex : 35 >> ingress_policing_burst: 0 >> ingress_policing_rate: 0 >> lacp_current : [] >> link_resets : 0 >> link_speed : [] >> link_state : up >> lldp : {} >> mac : [] >> mac_in_use : "7a:7d:1d:a7:43:1d" >> mtu : [] >> mtu_request : [] >> name : "ovn-25cc77-0" >> ofport : 6 >> ofport_request : [] >> options : {csum="true", key=flow, remote_ip="192.168.1.64"} >> other_config : {} >> statistics : {rx_bytes=0, rx_packets=0, tx_bytes=0, tx_packets=0} >> status : {tunnel_egress_iface=ovirtmgmt, tunnel_egress_iface_carrier=up} >> type : geneve >> >> _uuid : ec6a6688-e5d6-4346-ac47-ece1b8379440 >> admin_state : down >> bfd : {} >> bfd_status : {} >> cfm_fault : [] >> cfm_fault_status : [] >> cfm_flap_count : [] >> cfm_health : [] >> cfm_mpid : [] >> cfm_remote_mpids : [] >> cfm_remote_opstate : [] >> duplex : [] >> error : [] >> external_ids : {} >> ifindex : 13 >> ingress_policing_burst: 0 >> ingress_policing_rate: 0 >> lacp_current : [] >> link_resets : 0 >> link_speed : [] >> link_state : down >> lldp : {} >> mac : [] >> mac_in_use : "66:36:dd:63:dc:48" >> mtu : 1500 >> mtu_request : [] >> name : br-int >> ofport : 65534 >> ofport_request : [] >> options : {} >> other_config : {} >> statistics : {collisions=0, rx_bytes=0, rx_crc_err=0, rx_dropped=0, rx_errors=0, rx_frame_err=0, rx_over_err=0, rx_packets=0, tx_bytes=0, tx_dropped=0, tx_errors=0, tx_packets=0} >> status : {driver_name=openvswitch} >> type : internal >> >> _uuid : 1e511b4d-f7c2-499f-bd8c-07236e7bb7af >> admin_state : up >> bfd : {} >> bfd_status : {} >> cfm_fault : [] >> cfm_fault_status : [] >> cfm_flap_count : [] >> cfm_health : [] >> cfm_mpid : [] >> cfm_remote_mpids : [] >> cfm_remote_opstate : [] >> duplex : [] >> error : [] >> external_ids : {} >> ifindex : 35 >> ingress_policing_burst: 0 >> ingress_policing_rate: 0 >> lacp_current : [] >> link_resets : 0 >> link_speed : [] >> link_state : up >> lldp : {} >> mac : [] >> mac_in_use : "1a:85:d1:d9:e2:a5" >> mtu : [] >> mtu_request : [] >> name : "ovn-566849-0" >> ofport : 5 >> ofport_request : [] >> options : {csum="true", key=flow, remote_ip="192.168.1.41"} >> other_config : {} >> statistics : {rx_bytes=0, rx_packets=0, tx_bytes=0, tx_packets=0} >> status : {tunnel_egress_iface=ovirtmgmt, tunnel_egress_iface_carrier=up} >> type : geneve >> >> >> When I try to remove a port - it never ends (just hanging): >> >> [root@ovirt1 openvswitch]# ovs-vsctl --dry-run del-port br-int ovn-25cc77-0 >> In journal I see only this: >> дек 12 04:13:57 ovirt1.localdomain ovs-vsctl[22030]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --dry-run del-port br-int ovn-25cc77-0 >> >> The stranger part to me is the log output: >> >> [root@ovirt1 openvswitch]# grep ovn-25cc77-0 /var/log/openvswitch/*.log >> /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:26:28.642Z|00032|bridge|INFO|bridge br-int: added interface ovn-25cc77-0 on port 14 >> /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:45:15.646Z|00113|bridge|INFO|bridge br-int: deleted interface ovn-25cc77-0 on port 14 >> /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:45:15.861Z|00116|bridge|INFO|bridge br-int: added interface ovn-25cc77-0 on port 2 >> /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:50:36.678Z|00118|bridge|INFO|bridge br-int: deleted interface ovn-25cc77-0 on port 2 >> /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:52:31.180Z|00121|bridge|INFO|bridge br-int: added interface ovn-25cc77-0 on port 3 >> /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:55:09.734Z|00125|bridge|INFO|bridge br-int: deleted interface ovn-25cc77-0 on port 3 >> /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:58:15.138Z|00127|bridge|INFO|bridge br-int: added interface ovn-25cc77-0 on port 6 >> >> I'm also attaching the verbose output of the dryrun. >> >> Thanks in advance. >> >> Best Regards, >> Strahil Nikolov >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IG7YJPINVAF2B…

2 1

Re: Still having NFS issues. (Permissions)
by Strahil 13 Dec '19

13 Dec '19

Why do you use 'all_squash' ? all_squashMap all uids and gids to the anonymous user. Useful for NFS-exported public FTP directories, news spool directories, etc. The opposite option is no_all_squash, which is the default setting. Best Regards, Strahil NikolovOn Dec 10, 2019 07:46, Tony Brian Albers <tba(a)kb.dk> wrote: > > On Mon, 2019-12-09 at 18:43 +0000, Robert Webb wrote: > > To add, the 757 permission does not need to be on the .lease or the > > .meta files. > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/KZF6RCSRW2QV3… > > Good morning, > > Check SELinux just in case. > > Here's my config: > > NFS server: > /etc/exports: > /data/ovirt > *(rw,sync,no_subtree_check,all_squash,anonuid=36,anongid=36) > > Folder: > [root@kst001 ~]# ls -ld /data/ovirt > drwxr-xr-x 3 vdsm kvm 76 Jun 1 2017 /data/ovirt > > Subfolders: > [root@kst001 ~]# ls -l /data/ovirt/* > -rwxr-xr-x 1 vdsm kvm 0 Dec 10 06:38 /data/ovirt/__DIRECT_IO_TEST__ > > /data/ovirt/a597d0aa-bf22-47a3-a8a3-e5cecf3e20e0: > total 4 > drwxr-xr-x 2 vdsm kvm 117 Jun 1 2017 dom_md > drwxr-xr-x 56 vdsm kvm 4096 Dec 2 14:51 images > drwxr-xr-x 4 vdsm kvm 42 Jun 1 2017 master > [root@kst001 ~]# > > > The user: > [root@kst001 ~]# id vdsm > uid=36(vdsm) gid=36(kvm) groups=36(kvm) > [root@kst001 ~]# > > And output from 'mount' on a host: > kst001:/data/ovirt on /rhev/data-center/mnt/kst001:_data_ovirt type nfs > (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,nolock, > nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,mountaddr=<nfs- > server- > ip>,mountvers=3,mountport=20048,mountproto=udp,local_lock=all,addr=<nfs > -server-ip>) > > > HTH > > /tony > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/T6S32XNRB6S67…

3 2

Re: Still having NFS issues. (Permissions)
by Nir Soffer 13 Dec '19

13 Dec '19

On Tue, Dec 10, 2019 at 4:35 PM Robert Webb <rwebb(a)ropeguru.com> wrote: ... > >https://ovirt.org/develop/troubleshooting-nfs-storage-issues.html > > > >Generally speaking: > > > >Files there are created by vdsm (vdsmd), but are used (when running VMs) > >by qemu. So both of them need access. > > So the link to the NFS storage troubleshooting page is where I found that the perms needed to be 755. I think this is an error in the troubleshooting page. There is no reason to allow access to other users except vdsm:kvm. ... > Like this: > > drwxr-xr-x+ 2 vdsm kvm 4096 Dec 10 09:03 . > drwxr-xr-x+ 3 vdsm kvm 4096 Dec 10 09:02 .. > -rw-rw---- 1 vdsm kvm 53687091200 Dec 10 09:02 5a514067-82fb-42f9-b436-f8f93883fe27 > -rw-rw---- 1 vdsm kvm 1048576 Dec 10 09:03 5a514067-82fb-42f9-b436-f8f93883fe27.lease > -rw-r--r-- 1 vdsm kvm 298 Dec 10 09:03 5a514067-82fb-42f9-b436-f8f93883fe27.meta > > > So, with all that said, I cleaned everything up and my directory permissions look like what Tony posted for his. I have added in his export options to my setup and rebooted my host. > > I created a new VM from scratch and the files under images now look like this: > > drwxr-xr-x+ 2 vdsm kvm 4096 Dec 10 09:03 . > drwxr-xr-x+ 3 vdsm kvm 4096 Dec 10 09:02 .. > -rw-rw---- 1 vdsm kvm 53687091200 Dec 10 09:02 5a514067-82fb-42f9-b436-f8f93883fe27 > -rw-rw---- 1 vdsm kvm 1048576 Dec 10 09:03 5a514067-82fb-42f9-b436-f8f93883fe27.lease > -rw-r--r-- 1 vdsm kvm 298 Dec 10 09:03 5a514067-82fb-42f9-b436-f8f93883fe27.meta > > > Still not the 755 as expected, It is not expected, the permissions look normal. These are the permissions used for volumes on file based storage: lib/vdsm/storage/constants.py:FILE_VOLUME_PERMISSIONS = 0o660 but I am guessing with the addition of the "anonuid=36,anongid=36" to the exports, everything is now working as expected. The VM will boot and run as expected. There was nothing in the any of the documentation which alluded to possibly needed the additional options in the NFS export options. I this is a libvirt issue, it tries to access volumes as root, and without anonuid=36,anongid=36 it will be squashed to nobody and fail. Nir

1 1

Hosted Engine Failover Timing
by Robert Webb 12 Dec '19

12 Dec '19

So in doing some testing, I pulled the plug on my node where the hosted engine was running. Rough timing was about 3.5 minutes before the portal was available again. I searched around first, but could not find if there was any way to speed of the detection time in order to reboot the hosted engine quicker. Right now I am only testing this and will add in VM's later, which I understand should reboot a lot quicker.

1 0

Did a change in Ansible 2.9 in the ovirt_vm_facts module break the hosted-engine-setup?
by thomas＠hoberg.net 12 Dec '19

12 Dec '19

I am having problems installing a 3-node HCI cluster on machines that used to work fine.... and on a fresh set of servers, too. After a series of setbacks on a set of machines with failed installations and potentially failed clean-ups, I am ssing a fresh set of servers that had never run oVirt before. Patched to just before today's bigger changes (new kernel..) installation failed during the setup of the local hosted engine first and when I switched from GUi to script setup 'hosted-engine --deploy' *without* doing a cleanup this time, it progressed further to the point where the local VM had actually been teleported onto the (gluster based) cluster and is running there. In what seems the absolutely final action before adding the other two hosts, ansible is doing a finaly inventory of the virtual machine and collects facts or rather information (that's perhaps the breaking point) about that first VM before I would continue, only the data structure got renamed between ansible 2.8 and 2.9 according to this: https://fossies.org/diffs/ansible/2.8.5_vs_2.9.0rc1/lib/ansible/modules/clo… And the resulting error message from the /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-*.log file is: 2019-12-04 13:15:19,232+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_vms": [{"affinity_labels": [], "applications": [], "bios": {"boot_menu": {"enabled": false}, "type": "i440fx_sea_bios"}, "cdroms": [], "cluster": {"href": "/ovirt-engine/api/clusters/6616551e-1695-11ea-a86b-00163e34e004", "id": "6616551e-1695-11ea-a86b-00163e34e004"}, "comment": "", "cpu": {"architecture": "x86_64", "topology": {"cores": 1, "sockets": 4, "threads": 1}}, "cpu_profile": {"href": "/ovirt-engine/api/cpuprofiles/58ca604e-01a7-003f-01de-000000000250", "id": "58ca604e-01a7-003f-01de-000000000250"}, "cpu_shares": 0, "creation_time": "2019-12-04 13:01:12.780000+00:00", "delete_protected": false, "description": "", "disk_attachments": [], "display": {"address": "127.0.0.1", "allow_override": false, "certificate": {"content": "-----BEGIN CERTIFICATE-----(redacted)-----END CERTIFICATE-----\n", "organization": "***", "subject": "**"}, "copy_paste_enabled": true, "disconnect_action": "LOCK_SCREEN", "file_transfer_enabled": true, "monitors": 1, "port": 5900, "single_qxl_pci": false, "smartcard_enabled": false, "type": "vnc"}, "fqdn": "xdrd1001s.priv.atos.fr", "graphics_consoles": [], "guest_operating_system": {"architecture": "x86_64", "codename": "", "distribution": "CentOS Linux", "family": "Linux", "kernel": {"version": {"build": 0, "full_version": "3.10.0-1062.4.3.el7.x86_64", "major": 3, "minor": 10, "revision": 1062}}, "version": {"full_version": "7", "major": 7}}, "guest_time_zone": {"name": "GMT", "utc_offset": "+00:00"}, "high_availability": {"enabled": false, "priority": 0}, "host": {"href": "/ovirt-engine/api/hosts/75d096fd-4a2f-4ba4-b9fb-941f86daf624", "id": "75d096fd-4a2f-4ba4-b9fb-941f86daf624"}, "host_devices": [], "href": "/ovirt-engine/api/vms/dee6ec3b-5b4a-4063-ade9-12dece0f5fab", "id": "dee6ec3b-5b4a-4063-ade9-12dece0f5fab", "io": {"threads": 1}, "katello_errata": [], "la rge_icon": {"href": "/ovirt-engine/api/icons/9588ebfc-865a-4969-9829-d170d3654900", "id": "9588ebfc-865a-4969-9829-d170d3654900"}, "memory": 17179869184, "memory_policy": {"guaranteed": 17179869184, "max": 17179869184}, "migration": {"auto_converge": "inherit", "compressed": "inherit"}, "migration_downtime": -1, "multi_queues_enabled": true, "name": "external-HostedEngineLocal", "next_run_configuration_exists": false, "nics": [], "numa_nodes": [], "numa_tune_mode": "interleave", "origin": "external", "original_template": {"href": "/ovirt-engine/api/templates/00000000-0000-0000-0000-000000000000", "id": "00000000-0000-0000-0000-000000000000"}, "os": {"boot": {"devices": ["hd"]}, "type": "other"}, "permissions": [], "placement_policy": {"affinity": "migratable"}, "quota": {"id": "7af18f3a-1695-11ea-ab7e-00163e34e004"}, "reported_devices": [], "run_once": false, "sessions": [], "small_icon": {"href": "/ovirt-engine/api/icons/dec3572e-7465-4527-884b-f7c2eb2ed811", "id": "dec3572e-7465-4 527-884b-f7c2eb2ed811"}, "snapshots": [], "sso": {"methods": [{"id": "guest_agent"}]}, "start_paused": false, "stateless": false, "statistics": [], "status": "unknown", "storage_error_resume_behaviour": "auto_resume", "tags": [], "template": {"href": "/ovirt-engine/api/templates/00000000-0000-0000-0000-000000000000", "id": "00000000-0000-0000-0000-000000000000"}, "time_zone": {"name": "Etc/GMT"}, "type": "desktop", "usb": {"enabled": false}, "watchdogs": []}]}, "attempts": 24, "changed": false, "deprecations": [{"msg": "The 'ovirt_vm_facts' module has been renamed to 'ovirt_vm_info', and the renamed one no longer returns ansible_facts", "version": "2.13"}]} If that is the case, wouldn't that imply that there is no test case that covers the most typical HCI deployment when Ansible is updated? That would be truly frightening...

2 4

Re: ovirt 4.3.7 geo-replication not working
by Strahil 12 Dec '19

12 Dec '19

Hi Adrian, Have you checked the following link: https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infras… Best Regards, Strahil NikolovOn Dec 12, 2019 12:35, adrianquintero(a)gmail.com wrote: > > Hi Sahina/Strahil, > We followed the recommended setup from gluster documentation however one of my colleagues noticed a python entry in the logs, turns out it is a missing sym link to a library > > We created the following symlink to all the master servers (cluster 1 oVirt 1) and slave servers (Cluster 2, oVirt2) and geo-sync started working: > /lib64/libgfchangelog.so -> /lib64/libgfchangelog.so.0 > -------------------------------------------------------------------------------------------------------------------------------------------------------- > MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > host1.mydomain1.com geo-master /gluster_bricks/geo-master/geo-master root slave1.mydomain2.com::geo-slave slave1.mydomain2.com Active Changelog Crawl 2019-12-12 05:22:56 > host2.mydomain1.com geo-master /gluster_bricks/geo-master/geo-master root slave1.mydomain2.com::geo-slave slave2.mydomain2.com Passive N/A N/A > host3.mydomain1.com geo-master /gluster_bricks/geo-master/geo-master root slave1.mydomain2.com::geo-slave slave3.mydomain2.com Passive N/A N/A > -------------------------------------------------------------------------------------------------------------------------------------------------------- > we still require a bit more testing but at least it is syncing now. > > I am trying to find good documentation on how to achieve geo-replication for oVirt, is that something you can point me to? basically looking for a way to do Geo-replication from site A to Site B, but the Geo-Replication pop up window from ovirt does not seem to have the functionality to connect to a slave server from another oVirt setup.... > > > > As a side note, from the oVirt WEB UI the "cancel button" for the "New Geo-Replication" does not seem to work: storage > volumes > "select your volume" > "click 'Geo-Replication' > > Any good documentation you can point me to is welcome. > > thank you for the swift assistance. > > Regards, > > Adrian > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/EQHPJ3AUTWMSC…

1 0

Re: HCL: 4.3.7: Hosted engine fails
by Ralf Schenk 12 Dec '19

12 Dec '19

Hello, hosted engine deployment simply fails on EPYC with 4.3.7. See my earlier posts "HostedEngine Deployment fails on AMD EPYC 7402P 4.3.7". I was able to get this up and running by modifying HostedEngine VM XML while Installation tries to start the engine. Great fun ! virsh -r dumpxml HostedEngine shows: <cpu mode='custom' match='exact' check='partial'> <model fallback='allow'>EPYC</model> <topology sockets='16' cores='4' threads='1'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='virt-ssbd'/> which is not working. I removed the line with virt-ssbd via virsh edit and then it was able to start Engine. To modify the defined HostedEngine you need to create an account for libvirt via saslpasswd2 to be able to "virsh edit HostedEngine" saslpasswd2 -c -f /etc/libvirt/passwd.db admin@ovirt so your Passdb shows: sasldblistusers2 /etc/libvirt/passwd.db vdsm@ovirt: userPassword admin@ovirt: userPassword If the HostedEngine runs afterwards let it run so it updates the persitent configuration in hosted-storage. I also modified these by untarring and maniplulating the correspondent XML-Strings !. Really ugly and disfunctional. Bye Am 11.12.2019 um 14:33 schrieb Robert Webb: > I could not find if that CPU supported SSBD or not. > > Log into one your nodes via console and run, "cat /proc/cpuinfo" and check the "flags" section and see if SSBD is listed. If not, then look at your cluster config under the "General" section and see what it has for "Cluster CPU Type". Make sure it hasn't chosen a CPU type which it thinks has SSBD available. > > I have a Xeon X5670 and it does support SSBD and there is a specific CPU type selected named, "Intel Westmere IBRS SSBD Family". > > Hope this helps. > > ________________________________________ > From: Christian Reiss <email(a)christian-reiss.de> > Sent: Wednesday, December 11, 2019 7:55 AM > To: users(a)ovirt.org > Subject: [ovirt-users] HCL: 4.3.7: Hosted engine fails > > Hey all, > > Using a homogeneous ovirt-node-ng-4.3.7-0.20191121.0 freshly created > cluster using node installer I am unable to deploy the hosted engine. > Everything else worked. > > In vdsm.log is a line, just after attempting to start the engine: > > libvirtError: the CPU is incompatible with host CPU: Host CPU does not > provide required features: virt-ssbd > > I am using AMD EPYC 7282 16-Core Processors. > > I have attached > > - vdsm.log (during and failing the start) > - messages (for bootup / libvirt messages) > - dmesg (grub / boot config) > - deploy.log (browser output during deployment) > - virt-capabilites (virsh -r capabilities) > > I can't think -or don't know- off any other log files of interest here, > but I am more than happy to oblige. > > notectl check tells me > > Status: OK > Bootloader ... OK > Layer boot entries ... OK > Valid boot entries ... OK > Mount points ... OK > Separate /var ... OK > Discard is used ... OK > Basic storage ... OK > Initialized VG ... OK > Initialized Thin Pool ... OK > Initialized LVs ... OK > Thin storage ... OK > Checking available space in thinpool ... OK > Checking thinpool auto-extend ... OK > vdsmd ... OK > > layers: > ovirt-node-ng-4.3.7-0.20191121.0: > ovirt-node-ng-4.3.7-0.20191121.0+1 > bootloader: > default: ovirt-node-ng-4.3.7-0.20191121.0 (3.10.0-1062.4.3.el7.x86_64) > entries: > ovirt-node-ng-4.3.7-0.20191121.0 (3.10.0-1062.4.3.el7.x86_64): > index: 0 > title: ovirt-node-ng-4.3.7-0.20191121.0 (3.10.0-1062.4.3.el7.x86_64) > kernel: > /boot/ovirt-node-ng-4.3.7-0.20191121.0+1/vmlinuz-3.10.0-1062.4.3.el7.x86_64 > args: "ro crashkernel=auto rd.lvm.lv=onn_node01/swap > rd.lvm.lv=onn_node01/ovirt-node-ng-4.3.7-0.20191121.0+1 rhgb quiet > LANG=en_GB.UTF-8 img.bootid=ovirt-node-ng-4.3.7-0.20191121.0+1" > initrd: > /boot/ovirt-node-ng-4.3.7-0.20191121.0+1/initramfs-3.10.0-1062.4.3.el7.x86_64.img > root: /dev/onn_node01/ovirt-node-ng-4.3.7-0.20191121.0+1 > current_layer: ovirt-node-ng-4.3.7-0.20191121.0+1 > > > The odd thing is the hosted engine vm does get started during initial > configuration and works. Just when the ansible stuff is done an its > moved over to ha storage the CPU quirks start. > > So far I learned that ssbd is a mitigation protection but the flag is > not in my cpu. Well, ssbd is virt-ssbd is not. > > I am *starting* with ovirt. I would really, really welcome it if > recommendations would include clues on how to make it happen. > I do rtfm, but I was unable to find anything (or any solution) anywhere. > Not after 80 hours of working on this. > > Thank you all. > -Chris. > > -- > Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon > support(a)alpha-labs.net \ / Campaign > X against HTML > WEB alpha-labs.net / \ in eMails > > GPG Retrieval https://gpg.christian-reiss.de > GPG ID ABCD43C5, 0x44E29126ABCD43C5 > GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 > > "It's better to reign in hell than to serve in heaven.", > John Milton, Paradise lost. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/MXW3L2HAXJCYY… -- *Ralf Schenk* fon +49 (0) 24 05 / 40 83 70 fax +49 (0) 24 05 / 40 83 759 mail *rs(a)databay.de* <mailto:rs@databay.de> *Databay AG* Jens-Otto-Krag-Straße 11 D-52146 Würselen *www.databay.de* <http://www.databay.de> Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202 Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. Philipp Hermanns Aufsichtsratsvorsitzender: Wilhelm Dohmen ------------------------------------------------------------------------

2 1

Re: ovirt 4.3.7 geo-replication not working
by Strahil 12 Dec '19

12 Dec '19

Hi Adrian, Have you checked the passwordless rsync between master and slave volume nodes ? Best Regards, Strahil NikolovOn Dec 11, 2019 22:36, adrianquintero(a)gmail.com wrote: > > Hi, > I am trying to setup geo-replication between 2 sites, but I keep getting: > [root@host1 ~]# gluster vol geo-rep geo-master slave1.mydomain2.com::geo-slave status > > MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > host1.mydomain1.com geo-master /gluster_bricks/geo-master/geo-master root slave1.mydomain2.com::geo-slave N/A Faulty N/A N/A > host2.mydomain2.com geo-master /gluster_bricks/geo-master/geo-master root slave1.mydomain2.com::geo-slave N/A Faulty N/A N/A > vmm11.virt.iad3p geo-master /gluster_bricks/geo-master/geo-master root slave1.mydomain2.com::geo-slave N/A Faulty N/A N/A > > > oVirt GUI has an icon in the volume that says "volume data is being geo-replicated" but we know that is not the case > From the logs i can see: > [2019-12-11 19:57:48.441557] I [fuse-bridge.c:6810:fini] 0-fuse: Unmounting '/tmp/gsyncd-aux-mount-5WaCmt'. > [2019-12-11 19:57:48.441578] I [fuse-bridge.c:6815:fini] 0-fuse: Closing fuse connection to '/tmp/gsyncd-aux-mount-5WaCmt' > > and > [2019-12-11 19:45:14.785758] I [monitor(monitor):278:monitor] Monitor: worker died in startup phase brick=/gluster_bricks/geo-master/geo-master > > thoughts? > > thanks, > > Adrian > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TPTAODQ3Q4ZDK…

5 5

Mixing compute and storage without (initial) HCI
by thomas＠hoberg.net 12 Dec '19

12 Dec '19

Some documentation, especially on older RHEV versions seems to indicate that Gluster storage roles and compute server roles in an oVirt cluster or actually exclusive. Yet HCI is all about doing both, which is slightly confusing when you try to overcome HCI issues simply by running the management engine in a "side car", in my case simply a KVM VM running on a host that's not part of the HCI (attempted) cluster. So the HCI wizard failed to deploy the management VM, but left me with a working Gluster. I then went ahead and used a fresh CentOS 7.7 VM to install the hosted engine the the script variant without an appliance. That went ... not too bad initially, it even found the Gluster bricks eventually, installed the three hosts, looked almost ready to go, but something must be wrong with the "ovirtmgmt" network. It looks alright in the network configuration, where it has all roles, but when I try to create a VM, I cannot select it as the standard network for the VM. Any new network I might try to define, won't work either. So apart from these detail problems: Is the prohibition against mising both roles, gluster and (compute) cluster still in place? Because there are also documentation remnants which seem to indicate that a management engine for an existing cluster can actually be converted into a VM managed by the hosted engine e.g. as part of a recovery, repeating later what the HCI setup attempts to automate.

2 1

Gluster mount still fails on Engine deployment - any suggestions...
by rob.downer＠orbitalsystems.co.uk 12 Dec '19

12 Dec '19

Hi Engine deployment fails here... [ INFO ] TASK [ovirt.hosted_engine_setup : Add glusterfs storage domain] [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Unexpected exception]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Unexpected exception]\". HTTP response code is 400."} However Gluster looks good... I have reinstalled all nodes from scratch. root@ovirt3 ~]# gluster volume status Status of volume: data Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gfs3.gluster.private:/gluster_bricks/ data/data 49152 0 Y 3756 Brick gfs2.gluster.private:/gluster_bricks/ data/data 49153 0 Y 3181 Brick gfs1.gluster.private:/gluster_bricks/ data/data 49152 0 Y 15548 Self-heal Daemon on localhost N/A N/A Y 17602 Self-heal Daemon on gfs1.gluster.private N/A N/A Y 15706 Self-heal Daemon on gfs2.gluster.private N/A N/A Y 3348 Task Status of Volume data ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: engine Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gfs3.gluster.private:/gluster_bricks/ engine/engine 49153 0 Y 3769 Brick gfs2.gluster.private:/gluster_bricks/ engine/engine 49154 0 Y 3194 Brick gfs1.gluster.private:/gluster_bricks/ engine/engine 49153 0 Y 15559 Self-heal Daemon on localhost N/A N/A Y 17602 Self-heal Daemon on gfs1.gluster.private N/A N/A Y 15706 Self-heal Daemon on gfs2.gluster.private N/A N/A Y 3348 Task Status of Volume engine ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: vmstore Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gfs3.gluster.private:/gluster_bricks/ vmstore/vmstore 49154 0 Y 3786 Brick gfs2.gluster.private:/gluster_bricks/ vmstore/vmstore 49152 0 Y 2901 Brick gfs1.gluster.private:/gluster_bricks/ vmstore/vmstore 49154 0 Y 15568 Self-heal Daemon on localhost N/A N/A Y 17602 Self-heal Daemon on gfs1.gluster.private N/A N/A Y 15706 Self-heal Daemon on gfs2.gluster.private N/A N/A Y 3348 Task Status of Volume vmstore ------------------------------------------------------------------------------ There are no active volume tasks

2 1

Re: OVN communications between hosts
by Strahil 12 Dec '19

12 Dec '19

Hi Pavel, Would you mind to share the list of ovn devices you have. Currently in UI, I don't have any network (except ovirtmgmt) and I see multiplee devices. My guess is that I should remove all but the br-int , but I would like not to kill my cluster communication :) Best Regards, Strahil NikolovOn Dec 11, 2019 10:25, Pavel Nakonechnyi <pavel(a)gremwell.com> wrote: > > Hi Strahil, > > On Tuesday, 10 December 2019 20:50:27 CET Strahil wrote: > > Hi Pavel, > > > > Can you explain how did you find the issue. > > > > I'm new in OVN and I experience the same symptoms . > > > > I'm not sure what will be the best approach to start cleanly with OVN. > > > > I am new to OVN / OpenVSwitch too. :) > > What helped me to begin with is capturing traffic on "ovirtmgmnt" interface using tcpdump and looking into it for packets related to data exchange between VMs over virtual network. I found communications over UDP:6081, which were fine by themselves. However, this helped to craft more targeted search requests which lead me to this discussion: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/PVJJPK7MQOFLXJ… > > Some suggestions there were helpful to at least become slightly more familiar with how the things work. > > Anyway, lack of documentation on this matter (I know that there are high-level old docs) does not help to resolve such cases. > > >

2 1

Ovirt OVN help needed
by Strahil Nikolov 12 Dec '19

12 Dec '19

Hi Community, can someone hint me how to get rid of some ports? I just want to 'reset' my ovn setup. Here is what I have so far: [root@ovirt1 openvswitch]# ovs-vsctl list interface _uuid : be89c214-10e4-4a97-a9eb-1b82bc433a24 admin_state : up bfd : {} bfd_status : {} cfm_fault : [] cfm_fault_status : [] cfm_flap_count : [] cfm_health : [] cfm_mpid : [] cfm_remote_mpids : [] cfm_remote_opstate : [] duplex : [] error : [] external_ids : {} ifindex : 35 ingress_policing_burst: 0 ingress_policing_rate: 0 lacp_current : [] link_resets : 0 link_speed : [] link_state : up lldp : {} mac : [] mac_in_use : "7a:7d:1d:a7:43:1d" mtu : [] mtu_request : [] name : "ovn-25cc77-0" ofport : 6 ofport_request : [] options : {csum="true", key=flow, remote_ip="192.168.1.64"} other_config : {} statistics : {rx_bytes=0, rx_packets=0, tx_bytes=0, tx_packets=0} status : {tunnel_egress_iface=ovirtmgmt, tunnel_egress_iface_carrier=up} type : geneve _uuid : ec6a6688-e5d6-4346-ac47-ece1b8379440 admin_state : down bfd : {} bfd_status : {} cfm_fault : [] cfm_fault_status : [] cfm_flap_count : [] cfm_health : [] cfm_mpid : [] cfm_remote_mpids : [] cfm_remote_opstate : [] duplex : [] error : [] external_ids : {} ifindex : 13 ingress_policing_burst: 0 ingress_policing_rate: 0 lacp_current : [] link_resets : 0 link_speed : [] link_state : down lldp : {} mac : [] mac_in_use : "66:36:dd:63:dc:48" mtu : 1500 mtu_request : [] name : br-int ofport : 65534 ofport_request : [] options : {} other_config : {} statistics : {collisions=0, rx_bytes=0, rx_crc_err=0, rx_dropped=0, rx_errors=0, rx_frame_err=0, rx_over_err=0, rx_packets=0, tx_bytes=0, tx_dropped=0, tx_errors=0, tx_packets=0} status : {driver_name=openvswitch} type : internal _uuid : 1e511b4d-f7c2-499f-bd8c-07236e7bb7af admin_state : up bfd : {} bfd_status : {} cfm_fault : [] cfm_fault_status : [] cfm_flap_count : [] cfm_health : [] cfm_mpid : [] cfm_remote_mpids : [] cfm_remote_opstate : [] duplex : [] error : [] external_ids : {} ifindex : 35 ingress_policing_burst: 0 ingress_policing_rate: 0 lacp_current : [] link_resets : 0 link_speed : [] link_state : up lldp : {} mac : [] mac_in_use : "1a:85:d1:d9:e2:a5" mtu : [] mtu_request : [] name : "ovn-566849-0" ofport : 5 ofport_request : [] options : {csum="true", key=flow, remote_ip="192.168.1.41"} other_config : {} statistics : {rx_bytes=0, rx_packets=0, tx_bytes=0, tx_packets=0} status : {tunnel_egress_iface=ovirtmgmt, tunnel_egress_iface_carrier=up} type : geneve When I try to remove a port - it never ends (just hanging): [root@ovirt1 openvswitch]# ovs-vsctl --dry-run del-port br-int ovn-25cc77-0 In journal I see only this:дек 12 04:13:57 ovirt1.localdomain ovs-vsctl[22030]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --dry-run del-port br-int ovn-25cc77-0 The stranger part to me is the log output: [root@ovirt1 openvswitch]# grep ovn-25cc77-0 /var/log/openvswitch/*.log /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:26:28.642Z|00032|bridge|INFO|bridge br-int: added interface ovn-25cc77-0 on port 14 /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:45:15.646Z|00113|bridge|INFO|bridge br-int: deleted interface ovn-25cc77-0 on port 14 /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:45:15.861Z|00116|bridge|INFO|bridge br-int: added interface ovn-25cc77-0 on port 2 /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:50:36.678Z|00118|bridge|INFO|bridge br-int: deleted interface ovn-25cc77-0 on port 2 /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:52:31.180Z|00121|bridge|INFO|bridge br-int: added interface ovn-25cc77-0 on port 3 /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:55:09.734Z|00125|bridge|INFO|bridge br-int: deleted interface ovn-25cc77-0 on port 3 /var/log/openvswitch/ovs-vswitchd.log:2019-12-12T01:58:15.138Z|00127|bridge|INFO|bridge br-int: added interface ovn-25cc77-0 on port 6 I'm also attaching the verbose output of the dryrun. Thanks in advance. Best Regards,Strahil Nikolov

2 1

ovirt 4.3.7 geo-replication not working
by adrianquintero＠gmail.com 11 Dec '19

11 Dec '19

Hi, I am trying to setup geo-replication between 2 sites, but I keep getting: [root@host1 ~]# gluster vol geo-rep geo-master slave1.mydomain2.com::geo-slave status MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- host1.mydomain1.com geo-master /gluster_bricks/geo-master/geo-master root slave1.mydomain2.com::geo-slave N/A Faulty N/A N/A host2.mydomain2.com geo-master /gluster_bricks/geo-master/geo-master root slave1.mydomain2.com::geo-slave N/A Faulty N/A N/A vmm11.virt.iad3p geo-master /gluster_bricks/geo-master/geo-master root slave1.mydomain2.com::geo-slave N/A Faulty N/A N/A oVirt GUI has an icon in the volume that says "volume data is being geo-replicated" but we know that is not the case From the logs i can see: [2019-12-11 19:57:48.441557] I [fuse-bridge.c:6810:fini] 0-fuse: Unmounting '/tmp/gsyncd-aux-mount-5WaCmt'. [2019-12-11 19:57:48.441578] I [fuse-bridge.c:6815:fini] 0-fuse: Closing fuse connection to '/tmp/gsyncd-aux-mount-5WaCmt' and [2019-12-11 19:45:14.785758] I [monitor(monitor):278:monitor] Monitor: worker died in startup phase brick=/gluster_bricks/geo-master/geo-master thoughts? thanks, Adrian

1 0

Re: 3node HCI fails when HostedEngineLocal is trying to add additional Gluster members
by Strahil 11 Dec '19

11 Dec '19

Most probably the vdsm or supervdsm's PreExec task is doing it (they got multiple, so you can run manually till you find it out). Just try the following: systemctl stop vdsmd supervdsmd systemctl start supervdsmd Check for certs systemctl start vdsmd Keep in mind that that the chain of events (at least for me is): 1. VG activation 2. VDO activation 3. Gluster brick is mounted (I use systemd service due to deps between vdo, gluster brick and glusterd) 4. Glusterd and libvirt are started 5. Sanlock is started 6. Supervdsm 7. Vdsm If this is a host that will host HostedEngine VM: 8. Ovirt-ha-broker 9. Ovirt-ha-agent After cleanup, did you reboot? Best Regards, Strahil NikolovOn Dec 4, 2019 17:14, thomas(a)hoberg.net wrote: > > After spending another couple of hours trying to track down the problem, I have found that the "lost connection" seems due to KVM shutting down, because it cannot find the certificates for the Spice and VNC connections in /etc/pki/vdsm/*, where 'ovirt-hosted-engine-cleanup' deleted them. > > So now I wonder: Who is supposed to (re-)generated them afterwards? > > Assuming that it was a much earlier step I proceeded to completely undo the deployment, get rid of the Gluster setup etc. and start from the very beginning, only to find that that didn't change a thing: It still missed those certificates.... > > ...while something or someone *did* generated them when I tried a distinct and new set of nodes for counter-testing.. > > That setup failed with an Ansible error (reported separately), but I have now grown afraid of using 'ovirt-hosted-engine-cleanup' when I don't know how to get the ciphers/keys for /etc/pki/vsdm/{spice|vnc} regenerated... > > Can anyone shed some light into this darkness? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z7AFFFU6KMDPS…

2 1

CPU Type compatibility matrix
by Gianluca Cecchi 11 Dec '19

11 Dec '19

Hello, In my case I currently have a cluster with hosts with cpu Intel E5-2680 v4 (each socket with 14 cores) and their Cluster is set as "Intel Broadwell Family" and I would like to add in the same oVirt Cluster two more hosts with Intel E5-2640 v4 cpus (each socket 10 cores) that should be the same CPU Family Type. Is it true? Is there a sort of matrix where one could compare and match? Thanks in advance, Gianluca

4 3

Gluster set up fails - Nearly there I think...
by rob.downer＠orbitalsystems.co.uk 11 Dec '19

11 Dec '19

Gluster fails with vdo: ERROR - Device /dev/sdb excluded by a filter.\n", however I have run [root@ovirt1 ~]# vdo create --name=vdo1 --device=/dev/sdb --force Creating VDO vdo1 Starting VDO vdo1 Starting compression on VDO vdo1 VDO instance 1 volume is ready at /dev/mapper/vdo1 [root@ovirt1 ~]# there are no filters in lvm.conf I have run wipefs -a /dev/sdb —force on all hosts before start

5 9

[ovirt-announce] [ANN] oVirt 4.3.8 Second Release Candidate is now available for testing
by Lev Veyde 11 Dec '19

11 Dec '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.8 Second Release Candidate for testing, as of December 11th, 2019. This update is a release candidate of the eighth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available Additional Resources: * Read more about the oVirt 4.3.8 release highlights: http://www.ovirt.org/release/4.3.8/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.8/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

update from 4.2 to 4.3
by Enrico Becchetti 11 Dec '19

11 Dec '19

Dear All. my engine running in a virtual machine Centos 7.6.1810 and ovirt release is 4.2.8.2-1.el7 my hypervisors are Centos 7.6.1810 with vdsm 4.20.46-1.el7, allof them are ovirt-4.2 repository. Now I need to update to the last 4.3 any suggestions ? Thanks a lot Best Regards Enrico -- _______________________________________________________________________ Enrico Becchetti Servizio di Calcolo e Reti Istituto Nazionale di Fisica Nucleare - Sezione di Perugia Via Pascoli,c/o Dipartimento di Fisica 06123 Perugia (ITALY) Phone:+39 075 5852777 Mail: Enrico.Becchetti<at>pg.infn.it ______________________________________________________________________

2 1

Re: Clusters: Clarification needed on the ballooning memory feature and its affects on the physical hosts memory
by donagh.moran＠oracle.com 11 Dec '19

11 Dec '19

Hi Paul Thanks for the info, you makes it clear what each memory attribute represents in Ovirt but I'm still a little unclear how I would generate over 80% memory usage on the host. Shared Memory: 0% The Max free Memory for scheduling new VMs is 7978 MB which makes sense as its roughly the reminder of 200% of the total host memory minus the memory size allocated for the 4 VM's

1 0

katello-host-tools-3.5.1 and Red Hat Satellite 6.4
by Matthias Leopold 11 Dec '19

11 Dec '19

Hi, I'm trying to register hosts running CentOS 7.6 and oVirt 4.3.5 to a Red Hat Satellite 6.4 server. The oVirt hosts have katello-host-tools-3.5.1 packages from oVirt repos, which seem to be too new for the Red Hat Satellite 6.4 server, Satellite says: Errata: Could not calculate errata status, ensure host is registered and the katello-host-tools package is installed Is there a way to get around this? Downgrade katello-host-tools? -> is this OK for oVirt? Upgrade Red Hat Satellite? -> server not under my control... Is there a compatibility matrix for katello-host-tools and Red Hat Satellite versions? I'm new to this topic.... thx Matthias

3 3

Can't access Storage > Volumes through the UI.
by Valentin Bajrami 11 Dec '19

11 Dec '19

Hello everyone, Recently, I upgraded ovirt-engine from 4.2.5.3-1.el7 to 4.3.6.7-1.el7 but going to Storage > Volumes nothing seems to happen. Volumes does not open up. The error I see in the debugger mode (firefox) is as follows: org.ovirt.engine.ui.uicompat.EnumTranslator WARNING: Missing Enum resource 'V5'. Cannot find constant 'StorageFormatType___V5'; expecting a method name. There is also a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1759102 Anyone any diea? -- Met vriendelijke groeten / Kind regards, Valentin Bajrami Target Holding

4 9

unable to connect to the graphic server console.vv
by Pradeep Danthi 11 Dec '19

11 Dec '19

Dear Ovirt Team, Kindly help with this issues that I am facing in my Redhat Virtualization servers. I am unable to access my VM through console, I am getting this error when I right click and try connecting console. My observation is, this is happening after renewing the self-signed ssl certificate in all the nodes as nodes were non responsive before renewing the ssl lcertificate. Kindly help as we are unable to access the VMs through console (console.vv) Regards, Pradip 9900056579 ________________________________ This email was scanned by Bitdefender

1 0

Re: OVN communications between hosts
by Strahil 11 Dec '19

11 Dec '19

Hi Pavel, Can you explain how did you find the issue. I'm new in OVN and I experience the same symptoms . I'm not sure what will be the best approach to start cleanly with OVN. Best Regards, Strahil NikolovOn Dec 10, 2019 19:06, Pavel Nakonechnyi <pavel(a)gremwell.com> wrote: > > Hi Pavel Nakonechnyi, > > > > > However, if such VMs are on different hosts, then no packets are received on both VMs. > > > > Could you please suggest me a way to properly debug and fix this problem? I would like to be able to distribute several VMs connected to the single virtual network across hosts. > > > > It appears that the problem was (as usual) with my setup which is a bit messy as it was based on experimental environment. The issues was triggered by changing the IP address of one of the hosts. I actually just added an alias to ovrtmgmnt interface and then changed the IP via oVirt engine... > > Anyway, command `ovs-vsctl list Interface` showed that one of the switch peers was still referenced by the old, unused IP address. The easiest way to fix it for me was to re-add the host to cluster. After that cross-host communication between VMs started to work properly. > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XC6UEXHBEEX2I…

2 1

Re: OVN communications between hosts
by Strahil 10 Dec '19

10 Dec '19

Hi All, It seems that I have several devices listed in 'ovs-vsctl list interface' despite removing all networks except ovirtmgmt. Can someone tell me which devices I should leave (so I can remove the rest) ? Thanks in advance. Best Regards, Strahil Nikolov On Dec 10, 2019 21:50, Strahil <hunter86_bg(a)yahoo.com> wrote: > > Hi Pavel, > > Can you explain how did you find the issue. > > I'm new in OVN and I experience the same symptoms . > > I'm not sure what will be the best approach to start cleanly with OVN. > > Best Regards, > Strahil NikolovOn Dec 10, 2019 19:06, Pavel Nakonechnyi <pavel(a)gremwell.com> wrote: > > > > Hi Pavel Nakonechnyi, > > > > > > > > However, if such VMs are on different hosts, then no packets are received on both VMs. > > > > > > Could you please suggest me a way to properly debug and fix this problem? I would like to be able to distribute several VMs connected to the single virtual network across hosts. > > > > > > > It appears that the problem was (as usual) with my setup which is a bit messy as it was based on experimental environment. The issues was triggered by changing the IP address of one of the hosts. I actually just added an alias to ovrtmgmnt interface and then changed the IP via oVirt engine... > > > > Anyway, command `ovs-vsctl list Interface` showed that one of the switch peers was still referenced by the old, unused IP address. The easiest way to fix it for me was to re-add the host to cluster. After that cross-host communication between VMs started to work properly. > > > > > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XC6UEXHBEEX2I…

1 0

ovirtsdk4 error
by jeremy_tourville＠hotmail.com 10 Dec '19

10 Dec '19

I have a server which runs a project from Github called SecGen. SecGen uses Vagrant to provision VMs from templates. When I go to my project folder and run vagrant up I get an error. user@localhost:~/bin/SecGen/projects/SecGen20191207_183811$ vagrant up Bringing machine 'escalation' up with 'ovirt4' provider... ==> escalation: Creating VM with the following settings... ==> escalation: -- Name: SecGen-default-scenario-escalation ==> escalation: -- Cluster: Default ==> escalation: -- Template: Vcentos77 ==> escalation: -- Console Type: spice ==> escalation: -- Memory: ==> escalation: ---- Memory: 512 MB ==> escalation: ---- Maximum: 512 MB ==> escalation: ---- Guaranteed: 512 MB ==> escalation: -- Cpu: ==> escalation: ---- Cores: 1 ==> escalation: ---- Sockets: 1 ==> escalation: ---- Threads: 1 ==> escalation: -- Cloud-Init: false ==> escalation: An error occured. Recovering.. ==> escalation: VM is not created. Please run `vagrant up` first. /home/user/.vagrant.d/gems/2.4.9/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/reader.rb:272:in `read': Can't find a reader for tag 'html' (OvirtSDK4::Error) from /home/user/.vagrant.d/gems/2.4.9/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/service.rb:66:in `check_fault' from /home/user/.vagrant.d/gems/2.4.9/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/services.rb:35570:in `add' from /home/user/.vagrant.d/gems/2.4.9/gems/vagrant-ovirt4-1.2.2/lib/vagrant-ovirt4/action/create_vm.rb:67:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /home/user/.vagrant.d/gems/2.4.9/gems/vagrant-ovirt4-1.2.2/lib/vagrant-ovirt4/action/set_name_of_domain.rb:17:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:121:in `block in finalize_action' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builder.rb:116:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/runner.rb:102:in `block in run' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/util/busy.rb:19:in `busy' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/runner.rb:102:in `run' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/call.rb:53:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /home/user/.vagrant.d/gems/2.4.9/gems/vagrant-ovirt4-1.2.2/lib/vagrant-ovirt4/action/connect_ovirt.rb:31:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/config_validate.rb:25:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builder.rb:116:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/runner.rb:102:in `block in run' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/util/busy.rb:19:in `busy' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/runner.rb:102:in `run' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:238:in `action_raw' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:209:in `block in action' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/environment.rb:613:in `lock' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:195:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:195:in `action' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run' Here is the top part of my Vagrantfile. # -*- mode: ruby -*- # vi: set ft=ruby : # This file was generated by SecGen # 2019-12-07 18:38:19 +0000 # Based on scenarios/default_scenario.xml VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.define "escalation" do |escalation| #oVirt provider begin escalation.vm.provider :ovirt4 do |ovirt| ovirt.username = 'admin@internal' ovirt.password = 'admin' ovirt.url = 'https://engine.cyber-range.lan/ovirt-engine/' ovirt.cluster = 'Default' ovirt.template = 'Vcentos77' ovirt.memory_size = '512 MB' ovirt.console = 'spice' # ovirt.filtered_api = true ovirt.insecure = true ovirt.debug = true end # oVirt provider end Can anyone tell me what is wrong?

2 2

OVN communications between hosts
by Pavel Nakonechnyi 10 Dec '19

10 Dec '19

Hi all, I have a working setup of oVirt (currently 4.3.7) as self-hosted engine consisting of three virtualization hosts. Each of them has several VMs with public IP addresses which work fine. The problem is with virtual networks created on "ovirt-provider-ovn". I can create a new network with the corresponding vNIC and attach two VMs to this vNIC. If both VMs are on the same host, virtual network works, VMs can exchange packets. However, if such VMs are on different hosts, then no packets are received on both VMs. With tcpdump I see traffic going from sender VM over "ovirtmgmnt" interface. The traffic successfully leaves one host and arrives to another, so I conclude that firewall is configured properly to allow UDP 6081 traffic. What I noted are the following messages in /var/log/openvswitch/ovs-vswitchd.log (on one of the hosts): 2019-12-10T12:10:11.177Z|00009|tunnel(handler4)|WARN|receive tunnel port not found (arp,tun_id=0x2,tun_src=172.18.53.254,tun_dst=172.18.53.202,tun_ipv6_src=::,tun_ipv6_dst=::,tun_gbp_id=0,tun_gbp_flags=0,tun_tos=0,tun_ttl=64,tun_erspan_ver=0,tun_flags=csum|key,in_port=2,vlan_tci=0x0000,dl_src=56:6f:03:4b:00:1f,dl_dst=ff:ff:ff:ff:ff:ff,arp_spa=10.1.1.102,arp_tpa=10.1.1.1,arp_op=1,arp_sha=56:6f:03:4b:00:1f,arp_tha=00:00:00:00:00:00) Here 172.18.53.254 is IP of host1, 172.18.53.202 -- host2 (having this log), 10.1.1.102 -- VM IP on host1 and 10.1.1.1 -- VM IP on host2. Could you please suggest me a way to properly debug and fix this problem? I would like to be able to distribute several VMs connected to the single virtual network across hosts. Thanks in advance! -- WBR, Pavel +32478910884

1 1

Re: katello-host-tools-3.5.1 and Red Hat Satellite 6.4
by Matthias Leopold 10 Dec '19

10 Dec '19

thanks, but all this is given other CentOS 7 hosts (with katello* packages provided by the Satellite server) are OK at the moment I'm looking into https://access.redhat.com/solutions/3517471 I'll ask our Satellite admin tomorrow Regards Matthias Am 10.12.19 um 17:28 schrieb Staniforth, Paul: > Hello Matthias, > > The oVirt hosts need to be registered in redhat satellite as a content > host and the satellite host will need to have the centos and oVirt yum > repositories added so they can create a content view. The first step I > would do is ask whoever manages your satellite server if they are > managing any Centos hosts. > > > > > Regards, > Paul S. > ------------------------------------------------------------------------ > *From:* Matthias Leopold <matthias.leopold(a)meduniwien.ac.at> > *Sent:* 10 December 2019 14:33 > *To:* users <users(a)ovirt.org> > *Subject:* [ovirt-users] katello-host-tools-3.5.1 and Red Hat Satellite 6.4 > Hi, > > I'm trying to register hosts running CentOS 7.6 and oVirt 4.3.5 to a Red > Hat Satellite 6.4 server. The oVirt hosts have katello-host-tools-3.5.1 > packages from oVirt repos, which seem to be too new for the Red Hat > Satellite 6.4 server, Satellite says: > > Errata: > Could not calculate errata status, ensure host is registered and the > katello-host-tools package is installed > > Is there a way to get around this? > Downgrade katello-host-tools? -> is this OK for oVirt? > Upgrade Red Hat Satellite? -> server not under my control... > Is there a compatibility matrix for katello-host-tools and Red Hat > Satellite versions? > > I'm new to this topic.... > > thx > Matthias > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > oVirt Code of Conduct: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > List Archives: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ > -- Matthias Leopold IT Systems & Communications Medizinische Universität Wien Spitalgasse 23 / BT 88 /Ebene 00 A-1090 Wien Tel: +43 1 40160-21241 Fax: +43 1 40160-921200

1 0

Re: Issue deploying self hosted engine on new install
by Robert Webb 10 Dec '19

10 Dec '19

Just wanted to close this out. Now that I have solved my NFS issues, I completed a clean install of oVirt node on two Dell R410's and ran the self hosted engine wizard on one of them. The install went flawless and I now have a working setup. Thanks for the time and patience from everyone who helped. ________________________________________ From: Robert Webb <rwebb(a)ropeguru.com> Sent: Tuesday, December 10, 2019 8:10 AM To: Yedidyah Bar David Cc: Nate Revo; users(a)ovirt.org Subject: [ovirt-users] Re: Issue deploying self hosted engine on new install I have a thread going reference the NFS permission issue. Going to move all my replies into that since it is not a direct issue with the hosted engine. Thanks for your replies. ________________________________ From: Yedidyah Bar David <didi(a)redhat.com> Sent: Tuesday, December 10, 2019 1:46 AM To: Robert Webb <rwebb(a)ropeguru.com> Cc: Nate Revo <nrevo(a)redhat.com>; users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Issue deploying self hosted engine on new install On Mon, Dec 9, 2019 at 3:06 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > > Nate, > > > > Thanks for the tip, but the NAS is Debian based. > > > > > > Is it potentially an SELinux denial? I seem to recall an SELinux Boolean that needs to be set on the nfs server. You might want to check audit log on both nfs server and your host. What error do you get in vdsm.log? > > > > On Sun, Dec 8, 2019, 4:00 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > > Didi, > > Apologies for the delayed reply. > > I tracked the issue down after giving up on the self hosted install. I installed it to a VM running CentOS 7 running on another platform and then added my hosts. > > After adding the hosts and dploying a VM on oVirt, everything deployed perfectly, I could never get the VM to start. Digging further, I found that it is apparently a NFS permission on my NAS. What is odd is that I can add the Storage domain with no issues, I can create a VM, but the VM will never start due to a permission issue on the disk image. > > On my NAS if I just go into the shared folder permissions and not change anything but just tell it to apply configured permissions to all files and folders, the newly created VM runs just fine. For some reason when oVirt creates new files in storage, it is leaving off the execute for the vdsm user. I also notice that for the image and lease files, it also leaves off any permisson for "other" . NOt sure why the permissions are not being applied correctly. But that is an issue for me to figure out on my NAS, OpenMediaVault. > > drwxrwsrwx+ 2 vdsm kvm 4096 Dec 7 23:53 . > drwxrwsrwx+ 8 vdsm kvm 4096 Dec 7 23:13 .. > -rw-rw----+ 1 vdsm kvm 53687091200 Dec 7 23:13 0605d785-f4df-49b1-af27-1f035148921c > -rw-rw----+ 1 vdsm kvm 1048576 Dec 7 23:13 0605d785-f4df-49b1-af27-1f035148921c.lease > -rw-rw-rw-+ 1 vdsm kvm 251 Dec 7 23:53 0605d785-f4df-49b1-af27-1f035148921c.meta > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FQGIOYW36MWWW… > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TBHWVVP67DDLF… -- Didi

1 0

Clusters: Clarification needed on the ballooning memory feature and its affects on the physical hosts memory
by donagh.moran＠oracle.com 10 Dec '19

10 Dec '19

Hi For test purposes I'm configuring cluster with ballooning enabled and memory over-commit set to 200% with one host (total memory 128600 MB) connected. I then create 4 linux based VM's and I set the following on each: memory size: 62000MB, max memory: 248000MB (default value set when memory size is set) and a guaranteed memory value of 31000MB (default value set when memory size is set). This all works as expected, I can start 4 VM's with a total memory size that double the physical memory available on the host. What I don't understand is when I view the general info on my host I see that the available memory is much higher than expected. Physical Memory:128600 MB total, 11574 MB used, 117026 MB free. When researching the set up required to test this feature I came across this post https://lists.ovirt.org/pipermail/users/2017-October/084675.html. It states the hosts memory load needs to exceed 80%. I was hoping that the allocation of physical memory to each VM would satisfy this condition but I am not sure it does. I have a few questions on this Should setting the physical memory to each VM would satisfy the greater than 80% conditions? Given we have guaranteed memory for each VM of 31000MB should the total of 124000Mb exceed the free memory on the host? Does the hosts used physical memory only represent each VM's disk 4Gb virtual size? Will the hosts free memory only decrease as the VM's consume storage? Any clarification on the above questions would be most appreciated. Regards Donagh

2 1

Re: Cannot obtain information from export domain
by Strahil 10 Dec '19

10 Dec '19

Hi can you describe your actions? Usually the export is like this: 1. You make a backup of the VM 2. You migrate the disks to the export storage domain 3. You shut down the VM 4. Set the storage domain in maintenance and then detach it from the oVirt 5. You atttach it to the new oVirt 6. Once the domain is active - click on import VM tab and import all VMs (defining the cluster you want them to be running on) 7. Power up VM and then migrate the disks to the permanent storage. Best Regards, Strahil NikolovOn Nov 26, 2019 19:41, Arthur Rodrigues Stilben <arthur.stilben(a)gmail.com> wrote: > > Hello everyone, > > I'm trying to export a virtual machine, but I'm getting the following error: > > 2019-11-26 16:30:06,250-02 ERROR > [org.ovirt.engine.core.bll.exportimport.GetVmsFromExportDomainQuery] > (default task-22) [b9a0b9d5-2127-4002-9cee-2e3525bccc89] Exception: > org.ovirt.engine.core.common.errors.EngineException: EngineException: > org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException: > IRSGenericException: IRSErrorException: Failed to GetVmsInfoVDS, error = > Storage domain does not exist: > (u'5ac6c35d-0406-4a06-a682-ed8fb2d1933f',), code = 358 (Failed with > error StorageDomainDoesNotExist and code 358) > > 2019-11-26 16:30:06,249-02 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (default task-22) [b9a0b9d5-2127-4002-9cee-2e3525bccc89] EVENT_ID: > IMPORTEXPORT_GET_VMS_INFO_FAILED(200), Correlation ID: null, Call Stack: > null, Custom ID: null, Custom Event ID: -1, Message: Failed to retrieve > VM/Templates information from export domain BackupMV > > The version of the oVirt that I am using is 4.1. > > Att, > > -- > Arthur Rodrigues Stilben > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z6FQ45UVQODSR…

2 1

Still having NFS issues. (Permissions)
by Robert Webb 10 Dec '19

10 Dec '19

So I have doubled checked everything I can think of and am still having issues. I have an NFS Storage Domain attached and I can now create, modify, and remove VM's with no issues. The issue I am having is when it is time to power on the VM. The issue is that when oVirt tries to access the image, access is being denied. I have double checked the documentation against my setup and it all looks right. I have the VDSM user and KVM group created with id's of 36. New files are being created with permissions of 755, just as the documentation describes. What I have found out though, is that in order for oVirt to have access to the files, the "other" permission has to be a 7. So effectiviely I need to have 757, rwx, on the files. Is there a user that I am missing from the documentation, or a user on oVirt that should be in a group, that isn't? Someone previously mentioned the sanlock user, but I do not see anything special that is required for it. This is my last hurdle before really being able to dig into oVirt.

3 4

Re: Issue deploying self hosted engine on new install
by Yedidyah Bar David 10 Dec '19

10 Dec '19

On Mon, Dec 9, 2019 at 3:06 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > > Nate, > > > > Thanks for the tip, but the NAS is Debian based. > > > > > > Is it potentially an SELinux denial? I seem to recall an SELinux Boolean that needs to be set on the nfs server. You might want to check audit log on both nfs server and your host. What error do you get in vdsm.log? > > > > On Sun, Dec 8, 2019, 4:00 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > > Didi, > > Apologies for the delayed reply. > > I tracked the issue down after giving up on the self hosted install. I installed it to a VM running CentOS 7 running on another platform and then added my hosts. > > After adding the hosts and dploying a VM on oVirt, everything deployed perfectly, I could never get the VM to start. Digging further, I found that it is apparently a NFS permission on my NAS. What is odd is that I can add the Storage domain with no issues, I can create a VM, but the VM will never start due to a permission issue on the disk image. > > On my NAS if I just go into the shared folder permissions and not change anything but just tell it to apply configured permissions to all files and folders, the newly created VM runs just fine. For some reason when oVirt creates new files in storage, it is leaving off the execute for the vdsm user. I also notice that for the image and lease files, it also leaves off any permisson for "other" . NOt sure why the permissions are not being applied correctly. But that is an issue for me to figure out on my NAS, OpenMediaVault. > > drwxrwsrwx+ 2 vdsm kvm 4096 Dec 7 23:53 . > drwxrwsrwx+ 8 vdsm kvm 4096 Dec 7 23:13 .. > -rw-rw----+ 1 vdsm kvm 53687091200 Dec 7 23:13 0605d785-f4df-49b1-af27-1f035148921c > -rw-rw----+ 1 vdsm kvm 1048576 Dec 7 23:13 0605d785-f4df-49b1-af27-1f035148921c.lease > -rw-rw-rw-+ 1 vdsm kvm 251 Dec 7 23:53 0605d785-f4df-49b1-af27-1f035148921c.meta > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FQGIOYW36MWWW… > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TBHWVVP67DDLF… -- Didi

2 1

ovirt rest api: how to get wwnn and wwnp of fiber channel of the KVM host managed by Ovirt manager using rest api
by Vivek Basappa 09 Dec '19

09 Dec '19

Hello, I am new to Ovirt , trying to dig through documentation, I am working on integrating Hitachi SAN storage with Ovirt manager. working on Hitachi SAN storage integration, I am trying to get WWNN and WWNP port details of the KVM Host using REST API. but I am unable to find any documentations in REST API about that. I could see that information in Ovirt Admin UI. how can I get this information trough REST API any help is appreciated regards Vivek

1 0

Issue in setting up
by Johns 09 Dec '19

09 Dec '19

Hi all, I just tried to use oVirt in multi-server, Manager in one VM and Host in a dedicated machine, every time I try to attach host I get this error. networks, the following networks are missing on host: 'ovirtmgmt' I have created a bridge but no luck , please help

2 1

Re: Issue deploying self hosted engine on new install
by Yedidyah Bar David 09 Dec '19

09 Dec '19

On Fri, Dec 6, 2019 at 3:35 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > > Hi all, > > I am trying to deploy the self hosted engine via cockpit and it is failing at the very end of deployment when it is checking the VM Health. I have done multiple clean installs and run this and it fails every time. > > I have also tried from the cli via ssh with the same outcome. > > After the failure, if I look at the oVirt Machines section of the node, the VM is there but will not start. > > Anyone else having this issue? Can you please check/share relevant parts of relevant logs? Including /var/log/ovirt* /var/log/vdsm* from the host, and /var/log/ovirt* from the engine machine, if you can access it. Thanks and best regards, -- Didi

3 3

Importing a Virtual Machine from a KVM Host
by Dirk Streubel 09 Dec '19

09 Dec '19

Hello everbody, i am just a little bit confused about importing Qemu Images from my KVM Host. At home, and at work i am using a ovirt engine in a VM. The Version is 4.3.7 and on bare metal my host. Everything works fine but i have the same problem at home and on work. I want to import my qcow2 Images from a KVM Host but i will not work. The command virsh -r -c 'qemu+tcp://root@host1.example.org/system' list --all shows me akk my VMs. But when i want to load the images in the GUI, nothing happens. I follow this instruction: https://www.ovirt.org/develop/release-management/features/virt/KvmToOvirt.h… After that, i take a look on the official 4.3 Rhev Documentation from Red Hat. There stand this: Log in to the proxy host and generate SSH keys for the vdsm user. sudo -u vdsm ssh-keygen So, i have no proxy host. So i want to do this on my ovirt-engine. Is this right? Next thing: the user vdsm is locked on the ovirt-engine machine and the host. So, do i have to unlocked the account of the user vdsm or what is the best way. My Problem is i found nothing that would help me to solve this problem. Maybe somebody here do me a favour and help me to solve this "challenge" Regards Dirk

3 3

Re: Windows Sluggish Performance
by Strahil 09 Dec '19

09 Dec '19

What is your virtual GPU ? I'm using QLX, and despite being sluggish, when you tune windows for best performance -it is workable. Of course, if you passthrough a GPU, performance will be completely different. Best Regards, Strahil NikolovOn Dec 3, 2019 21:19, Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: > > Anyone? > > On Tue, 3 Dec 2019 at 11:21 PM, Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: >> >> Hello Everyone, >> >> I managed to install Windows Server 2016 server on Ovirt node using ovirt engine.All virtio-Win drivers also installed, but the performance of Windows using console is very sluggish and mouse pointer is not at all responsive. >> >> Can anyone let me know, what could be the reason. Not able to to even add IP to VM as mouse doesn’t work at all. >> >> Thanks

4 4

Re: Increase memory of hosted engine
by Strahil 08 Dec '19

08 Dec '19

When you edit the memory, wait till tomorrow before powering off and powering on. The file in 3.1 is just a backup :D Best Regards, Strahil NikolovOn Dec 8, 2019 18:06, Stefan Wolf <shb256(a)gmail.com> wrote: > > thank you for your replay, > > I am happy if it works > 1. check > 2. check > 3.1 check -> I cant see where is use this config file later, or it is just a backup? > 4.1 check i changed to > <ovirt-vm:memGuaranteedSize type="int">16384</ovirt-vm:memGuaranteedSize> > <ovirt-vm:minGuaranteedMemoryMb type="int">16384</ovirt-vm:minGuaranteedMemoryMb> > and > > <maxMemory slots='16' unit='KiB'>15625000</maxMemory> > <memory unit='KiB'>15625000</memory> > <currentMemory unit='KiB'>15625000</currentMemory> > > after write, quite und open these values have changed back to > <memory unit='KiB'>4194304</memory> > <currentMemory unit='KiB'>4194304</currentMemory> > > BREAK ;) > > after stopping the hosted engine with hosted-engine --vm-shutdown and powering it up with hosted-engine vm-start > everything is reverted ;( > > BREAK > > hosted engine is now up and running, maintenance ist still global, > changed again with virtsh edit HostedEngine. as written above it changes back > > I will wait for tomorrow. > > Or did I missunderstand something > > In which file the maxmem is hidden? > > thx shb > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/DWVBZO2OE6U62…

1 0

Re: Hyper-V to KVM | v2v
by Vijay Sachdeva 08 Dec '19

08 Dec '19

Anyone ? On Sun, 8 Dec 2019 at 2:00 AM, Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: > What step I did was: > > > > 1. Used qemu-img to convert the vhdx to raw img > 2. Created a blank disk and copied my converted disk to same location. > 3. Renamed the converted drive with the name of blank disk. > 4. Created a VM and attached my converted disk to VM. > > > > Error: No bootable disk found > > > > > > But when I attack this disk to another running VM, there I can see the > data. But noting booting as bootable. > > > > Vijay Sachdeva > > > > > > > > *From: *Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> > > > *Date: *Sunday, 8 December 2019 at 1:48 AM > *To: *Strahil <hunter86_bg(a)yahoo.com>, users <users(a)ovirt.org> > *Subject: *Re: [ovirt-users] Hyper-V to KVM | v2v > > > > One question, once disk is converted to KVM format. > > > > What is the way to use that drive and run a VM from it within Ovirt > environment. > > > > Vijay Sachdeva > > > > > > *From: *Strahil <hunter86_bg(a)yahoo.com> > *Date: *Friday, 6 December 2019 at 8:57 PM > *To: *users <users(a)ovirt.org>, Vijay <vijay.sachdeva(a)indiqus.com> > *Subject: *Re: [ovirt-users] Hyper-V to KVM | v2v > > > > Have you tried to power up and fully shutdown the VM ? > > Best Regards, > Strahil Nikolov > > On Dec 6, 2019 15:52, Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: > > Hello, > > > > I am trying to convert a Hyper-V guest VM to run on KVM using virt-v2v > utility. > > > > Getting below error: > > > > [image: cid:image001.png@01D5AC6A.8B510030] > > > > Any suggestions how to solve this. > > > > Thanks > > > > Vijay Sachdeva > > > >

2 3

Increase memory of hosted engine
by Stefan Wolf 08 Dec '19

08 Dec '19

hello, I ve decrease the memory of the hosted engine. now I am not able to increase the memory permantly right now the memory has 4096 MB Max Memory is 7936 MB and guaranted memory is 7936MB I can increase the memory up to 7936 MB in the manager, it changes immediately. I can not increase to more then 7936 MB because this is max Memory If I change Max memory to 16384 the gueanted memery gets a red border an the error is max memory ist 4096 MB I ve found this one https://access.redhat.com/solutions/964693 and tried to change the memSize in /etc/ovirt-hosted-engine/vm.conf to 16384 I ve also stoppt every ovirt-ha-agent and changed every vm.conf. After starting ovirt-ha-agent every vm.conf changed to 4096 again has somebody a solution to increase the memory again? thx shb

2 2

Failed export to OVA
by Geoff Sweet 08 Dec '19

08 Dec '19

I'm currently running a stand alone server on 4.2.0.2-1.el7.centos. I know this is an older version and I am trying to do some exports for migrations off of it. The Export to OVA seems simple enough but it fails consistently and I really can't figure out why. The logfiles don't provide a lot of information that speaks to me. I double checked the known bug (of older versions) to make sure there is a description set for the disks associated with the VM. I also tried to look in the Ansible logs referenced below but no such log exists. I've also tried multiple different paths for the output. All with the same failure. Below you can see I am attempting to export to /tmp/. Here is the output of the engine logs: ###### engine.log ###### 2019-12-03 11:15:43,320-08 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-3785977) [d25a398d-f650-4911-ae2a-2ca2b54e8396] EVENT_ID: IMPORTEXPORT_STARTING_EXPORT_VM_TO_OVA(1,223), Starting to export Vm GRAYLOG as a Virtual Appliance 2019-12-03 11:15:43,916-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-12) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:15:43,923-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-12) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'default' is using 0 threads out of 1 and 5 tasks are waiting in the queue. 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'engine' is using 0 threads out of 500, 9 threads waiting for tasks and 0 tasks in queue. 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'engineScheduled' is using 0 threads out of 100 and 100 tasks are waiting in the queue. 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'engineThreadMonitoring' is using 1 threads out of 1 and 0 tasks are waiting in the queue. 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'hostUpdatesChecker' is using 0 threads out of 5 and 5 tasks are waiting in the queue. 2019-12-03 11:15:45,979-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:15:45,988-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:15:46,882-08 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] Polling and updating Async Tasks: 1 tasks, 1 tasks to poll now 2019-12-03 11:15:46,893-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] SPMAsyncTask::PollTask: Polling task 'fe1a173f-869c-4522-9984-9c57bace7c87' (Parent Command 'CopyImageGroup', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'running'. 2019-12-03 11:15:46,893-08 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] Finished polling Tasks, will poll again in 10 seconds. 2019-12-03 11:15:50,059-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:15:50,064-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:15:58,074-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:15:58,080-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:16:08,138-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:16:08,144-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:16:18,219-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-19) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:16:18,227-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-19) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:16:28,297-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:16:28,304-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:16:38,371-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-42) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:16:38,377-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-42) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:16:48,389-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:16:48,394-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:16:58,406-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:16:58,412-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:17:08,423-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:17:08,429-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:17:18,442-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:17:18,449-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:17:28,461-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-99) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:17:28,466-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-99) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:17:38,476-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:17:38,481-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:17:48,492-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-69) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:17:48,499-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-69) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:17:58,509-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-85) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:17:58,515-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-85) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:18:08,577-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-68) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:18:08,582-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-68) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:18:18,651-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:18:18,657-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:18:28,723-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:18:28,728-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:18:38,739-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:18:38,744-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:18:48,754-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-27) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:18:48,759-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-27) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:18:58,821-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-51) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:18:58,826-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-51) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:19:08,889-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-79) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:19:08,894-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-79) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:19:18,906-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:19:18,911-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:19:28,925-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:19:28,932-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:19:38,945-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:19:38,952-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:19:48,962-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:19:48,967-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:19:58,978-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-52) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:19:58,983-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-52) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:20:09,063-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-8) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:20:09,068-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-8) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:20:19,154-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-32) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:20:19,159-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-32) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:20:29,169-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-9) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:20:29,174-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-9) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:20:39,184-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-48) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:20:39,189-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-48) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:20:49,199-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:20:49,205-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:20:59,217-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-30) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:20:59,222-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-30) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:21:09,233-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:21:09,239-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:21:19,254-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:21:19,260-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:21:29,324-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:21:29,332-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:21:39,341-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:21:39,347-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:21:49,413-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-27) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:21:49,418-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-27) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:21:59,429-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:21:59,434-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:22:09,497-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-17) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:22:09,502-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-17) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:22:19,568-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-82) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:22:19,573-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-82) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:22:29,583-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:22:29,589-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:22:39,600-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-11) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:22:39,606-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-11) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:22:49,616-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:22:49,621-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:22:59,632-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-53) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:22:59,638-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-53) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:23:09,648-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-71) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:23:09,653-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-71) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:23:19,663-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-28) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:23:19,669-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-28) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:23:29,679-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:23:29,684-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:23:39,694-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-70) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:23:39,699-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-70) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:23:49,712-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-34) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:23:49,719-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-34) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:23:59,781-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-4) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:23:59,786-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-4) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:24:07,476-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] SPMAsyncTask::PollTask: Polling task 'fe1a173f-869c-4522-9984-9c57bace7c87' (Parent Command 'CopyImageGroup', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'finished', result 'success'. 2019-12-03 11:24:07,479-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] BaseAsyncTask::onTaskEndSuccess: Task 'fe1a173f-869c-4522-9984-9c57bace7c87' (Parent Command 'CopyImageGroup', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended successfully. 2019-12-03 11:24:07,479-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] CommandAsyncTask::endActionIfNecessary: All tasks of command '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' has ended -> executing 'endAction' 2019-12-03 11:24:07,479-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247'): calling endAction '. 2019-12-03 11:24:07,480-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [] CommandAsyncTask::endCommandAction [within thread] context: Attempting to endAction 'CopyImageGroup', 2019-12-03 11:24:07,492-08 INFO [org.ovirt.engine.core.bll.storage.disk.image.CopyImageGroupCommand] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command [id=0e3e3df9-73f5-4ca2-b592-0b9ce7371247]: Updating status to 'SUCCEEDED', The command end method logic will be executed by one of its parent commands. 2019-12-03 11:24:07,492-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'CopyImageGroup' completed, handling the result. 2019-12-03 11:24:07,493-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'CopyImageGroup' succeeded, clearing tasks. 2019-12-03 11:24:07,493-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fe1a173f-869c-4522-9984-9c57bace7c87' 2019-12-03 11:24:07,496-08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='7bb7ac30-0406-4fbf-802f-57b1a575383f', ignoreFailoverLimit='false', taskId='fe1a173f-869c-4522-9984-9c57bace7c87'}), log id: 693daae4 2019-12-03 11:24:07,498-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, HSMClearTaskVDSCommand(HostName = KVMCLST1A, HSMTaskGuidBaseVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b', taskId='fe1a173f-869c-4522-9984-9c57bace7c87'}), log id: 3d8ab113 2019-12-03 11:24:07,514-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, HSMClearTaskVDSCommand, log id: 3d8ab113 2019-12-03 11:24:07,514-08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, SPMClearTaskVDSCommand, log id: 693daae4 2019-12-03 11:24:07,517-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] BaseAsyncTask::removeTaskFromDB: Removed task 'fe1a173f-869c-4522-9984-9c57bace7c87' from DataBase 2019-12-03 11:24:07,517-08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-3786044) [d25a398d-f650-4911-ae2a-2ca2b54e8396] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' 2019-12-03 11:24:09,852-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:24:09,858-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' child commands '[0e3e3df9-73f5-4ca2-b592-0b9ce7371247]' executions were completed, status 'SUCCEEDED' 2019-12-03 11:24:10,867-08 INFO [org.ovirt.engine.core.bll.storage.disk.CreateAllOvaDisksCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Ending command 'org.ovirt.engine.core.bll.storage.disk.CreateAllOvaDisksCommand' successfully. 2019-12-03 11:24:10,877-08 INFO [org.ovirt.engine.core.bll.storage.disk.image.CopyImageGroupCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Ending command 'org.ovirt.engine.core.bll.storage.disk.image.CopyImageGroupCommand' successfully. 2019-12-03 11:24:10,887-08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, GetImageInfoVDSCommand( GetImageInfoVDSCommandParameters:{storagePoolId='7bb7ac30-0406-4fbf-802f-57b1a575383f', ignoreFailoverLimit='false', storageDomainId='c79208ed-8753-4ded-a137-8f08dfff5a40', imageGroupId='a1b75b90-04c8-4f8d-899e-7d0354e36b09', imageId='2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9'}), log id: 4ba602b2 2019-12-03 11:24:10,890-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, GetVolumeInfoVDSCommand(HostName = KVMCLST1A, GetVolumeInfoVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b', storagePoolId='7bb7ac30-0406-4fbf-802f-57b1a575383f', storageDomainId='c79208ed-8753-4ded-a137-8f08dfff5a40', imageGroupId='a1b75b90-04c8-4f8d-899e-7d0354e36b09', imageId='2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9'}), log id: 2524e570 2019-12-03 11:24:10,914-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, GetVolumeInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@4c8c88fe, log id: 2524e570 2019-12-03 11:24:10,914-08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, GetImageInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@4c8c88fe, log id: 4ba602b2 2019-12-03 11:24:10,988-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, PrepareImageVDSCommand(HostName = KVMCLST1A, PrepareImageVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b'}), log id: 11dbdafe 2019-12-03 11:24:11,010-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, PrepareImageVDSCommand, return: PrepareImageReturn:{status='Status [code=0, message=Done]'}, log id: 11dbdafe 2019-12-03 11:24:11,014-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetQemuImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, GetQemuImageInfoVDSCommand(HostName = KVMCLST1A, GetVolumeInfoVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b', storagePoolId='7bb7ac30-0406-4fbf-802f-57b1a575383f', storageDomainId='c79208ed-8753-4ded-a137-8f08dfff5a40', imageGroupId='a1b75b90-04c8-4f8d-899e-7d0354e36b09', imageId='2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9'}), log id: 79697ffd 2019-12-03 11:24:11,221-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetQemuImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, GetQemuImageInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.QemuImageInfo@5f543b3b, log id: 79697ffd 2019-12-03 11:24:11,226-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.TeardownImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] START, TeardownImageVDSCommand(HostName = KVMCLST1A, ImageActionsVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b'}), log id: 1f4cb783 2019-12-03 11:24:11,230-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.TeardownImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-21) [d25a398d-f650-4911-ae2a-2ca2b54e8396] FINISH, TeardownImageVDSCommand, return: StatusReturn:{status='Status [code=0, message=Done]'}, log id: 1f4cb783 2019-12-03 11:24:12,266-08 INFO [org.ovirt.engine.core.bll.CreateOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Running command: CreateOvaCommand internal: true. 2019-12-03 11:24:12,271-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] START, PrepareImageVDSCommand(HostName = KVMCLST1A, PrepareImageVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b'}), log id: 6e612ef8 2019-12-03 11:24:12,294-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] FINISH, PrepareImageVDSCommand, return: PrepareImageReturn:{status='Status [code=0, message=Done]'}, log id: 6e612ef8 2019-12-03 11:24:12,301-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] START, GetVolumeInfoVDSCommand(HostName = KVMCLST1A, GetVolumeInfoVDSCommandParameters:{hostId='960bcd30-c9b4-4aca-bc3e-4e710651d80b', storagePoolId='7bb7ac30-0406-4fbf-802f-57b1a575383f', storageDomainId='c79208ed-8753-4ded-a137-8f08dfff5a40', imageGroupId='a1b75b90-04c8-4f8d-899e-7d0354e36b09', imageId='2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9'}), log id: 648e4c38 2019-12-03 11:24:12,321-08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] FINISH, GetVolumeInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@4c8c88fe, log id: 648e4c38 2019-12-03 11:24:12,332-08 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Executing Ansible command: [/usr/bin/ansible-playbook, --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa, --inventory=/tmp/ansible-inventory830646465207814253, --extra-vars=target_directory=/tmp, --extra-vars=ova_name=GRAYLOG.ova, --extra-vars=ovirt_ova_pack_ovf='<?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\"?><ovf:Envelope xmlns:ovf=\\\" http://schemas.dmtf.org/ovf/envelope/1\\\" xmlns:rasd=\\\" http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSet…" xmlns:vssd=\\\" http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingD…" xmlns:xsi=\\\"http://www.w3.org/2001/XMLSchema-instance\\\" xmlns=\\\" http://schemas.dmtf.org/ovf/envelope/1\\\" xmlns:ovirt=\\\" http://www.ovirt.org/ovf\\\"><References><File ovf:href=\\\"2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9\\\" ovf:id=\\\"2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9\\\" ovf:size=\\\"3448045568\\\"></File></References><NetworkSection><Info>List of networks</Info><Network ovf:name=\\\"net_HOME\\\"></Network></NetworkSection><DiskSection><Info>List of Virtual Disks</Info><Disk ovf:diskId=\\\"a1b75b90-04c8-4f8d-899e-7d0354e36b09\\\" ovf:capacity=\\\"100\\\" ovf:capacityAllocationUnits=\\\"byte * 2^30\\\" ovf:populatedSize=\\\"3448045568\\\" ovf:parentRef=\\\"\\\" ovf:fileRef=\\\"2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9\\\" ovf:format=\\\" http://www.gnome.org/~markmc/qcow-image-format.html\\\" ovf:volume-format=\\\"COW\\\" ovf:volume-type=\\\"Sparse\\\" ovf:disk-interface=\\\"VirtIO_SCSI\\\" ovf:boot=\\\"true\\\" ovf:pass-discard=\\\"false\\\" ovf:disk-alias=\\\"GRAYLOG_Disk1\\\" ovf:disk-description=\\\"GRAYLOG_Disk1\\\" ovf:wipe-after-delete=\\\"false\\\" ovf:description=\\\"Active VM\\\" ovf:disk_storage_type=\\\"IMAGE\\\" ovf:cinder_volume_type=\\\"\\\"></Disk></DiskSection><VirtualSystem ovf:id=\\\"aecb985a-450a-43f1-957a-09776aa48899\\\"><Name>GRAYLOG</Name><Description>GrayLog looging system</Description><CreationDate>2018/01/27 23:20:25</CreationDate><ExportDate>2019/12/03 19:24:12</ExportDate><DeleteProtected>false</DeleteProtected><SsoMethod>guest_agent</SsoMethod><IsSmartcardEnabled>false</IsSmartcardEnabled><TimeZone>Etc/GMT</TimeZone><default_boot_sequence>9</default_boot_sequence><Generation>66</Generation><ClusterCompatibilityVersion>4.2</ClusterCompatibilityVersion><VmType>1</VmType><ResumeBehavior>AUTO_RESUME</ResumeBehavior><MinAllocatedMem>4096</MinAllocatedMem><IsStateless>false</IsStateless><IsRunAndPause>false</IsRunAndPause><AutoStartup>true</AutoStartup><Priority>1</Priority><CreatedByUserId>5a655cbf-012a-0161-03dc-000000000307</CreatedByUserId><VmInit ovf:regenerateKeys=\\\"false\\\" ovf:networks=\\\"[ ]\\\"></VmInit><MigrationSupport>0</MigrationSupport><IsBootMenuEnabled>true</IsBootMenuEnabled><IsSpiceFileTransferEnabled>true</IsSpiceFileTransferEnabled><IsSpiceCopyPasteEnabled>true</IsSpiceCopyPasteEnabled><AllowConsoleReconnect>true</AllowConsoleReconnect><ConsoleDisconnectAction>LOCK_SCREEN</ConsoleDisconnectAction><CustomEmulatedMachine></CustomEmulatedMachine><CustomCpuName></CustomCpuName><PredefinedProperties></PredefinedProperties><UserDefinedProperties></UserDefinedProperties><MaxMemorySizeMb>16384</MaxMemorySizeMb><TemplateId>00000000-0000-0000-0000-000000000000</TemplateId><TemplateName>Blank</TemplateName><IsInitilized>true</IsInitilized><Origin>3</Origin><app_list>kernel-3.10.0-693.17.1.el7,ovirt-guest-agent-common-1.0.13-2.el7,kernel-3.10.0-693.el7</app_list><quota_id>5b0590e8-9611-4240-abdc-07cd4bbaed1f</quota_id><DefaultDisplayType>1</DefaultDisplayType><TrustedService>false</TrustedService><OriginalTemplateId>00000000-0000-0000-0000-000000000000</OriginalTemplateId><OriginalTemplateName>Blank</OriginalTemplateName><UseHostCpu>false</UseHostCpu><UseLatestVersion>false</UseLatestVersion><StopTime>2019/12/03 18:44:44</StopTime><OperatingSystemSection ovf:id=\\\"80\\\" ovirt:id=\\\"24\\\" ovf:required=\\\"false\\\"><Info>Guest Operating System</Info><Description>Red Hat Enterprise Linux 7.x x64</Description></OperatingSystemSection><VirtualHardwareSection><Info>2 CPU, 4096 Memory</Info><System><vssd:VirtualSystemType>ENGINE 4.1.0.0</vssd:VirtualSystemType></System><Item><rasd:Caption>2 virtual cpu</rasd:Caption><rasd:Description>Number of virtual CPU</rasd:Description><rasd:InstanceId>1</rasd:InstanceId><rasd:ResourceType>3</rasd:ResourceType><rasd:num_of_sockets>2</rasd:num_of_sockets><rasd:cpu_per_socket>1</rasd:cpu_per_socket><rasd:threads_per_cpu>1</rasd:threads_per_cpu><rasd:max_num_of_vcpus>16</rasd:max_num_of_vcpus><rasd:VirtualQuantity>2</rasd:VirtualQuantity></Item><Item><rasd:Caption>4096 MB of memory</rasd:Caption><rasd:Description>Memory Size</rasd:Description><rasd:InstanceId>2</rasd:InstanceId><rasd:ResourceType>4</rasd:ResourceType><rasd:AllocationUnits>MegaBytes</rasd:AllocationUnits><rasd:VirtualQuantity>4096</rasd:VirtualQuantity></Item><Item><rasd:Caption>GRAYLOG_Disk1</rasd:Caption><rasd:InstanceId>2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9</rasd:InstanceId><rasd:ResourceType>17</rasd:ResourceType><rasd:HostResource>ovf:disk/a1b75b90-04c8-4f8d-899e-7d0354e36b09</rasd:HostResource><rasd:Parent>00000000-0000-0000-0000-000000000000</rasd:Parent><rasd:Template>00000000-0000-0000-0000-000000000000</rasd:Template><rasd:ApplicationList></rasd:ApplicationList><rasd:StorageId>c79208ed-8753-4ded-a137-8f08dfff5a40</rasd:StorageId><rasd:StoragePoolId>7bb7ac30-0406-4fbf-802f-57b1a575383f</rasd:StoragePoolId><rasd:CreationDate>2019/12/03 19:15:38</rasd:CreationDate><rasd:LastModified>2019/12/03 19:15:38</rasd:LastModified><rasd:last_modified_date>2019/12/03 19:15:38</rasd:last_modified_date><Type>disk</Type><Device>disk</Device><rasd:Address>{type=drive, bus=0, controller=0, target=0, unit=0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>scsi0-0-0-0</Alias></Item><Item><rasd:Caption>Ethernet adapter on net_HOME</rasd:Caption><rasd:InstanceId>4adaa616-f98b-4e1f-b60f-14156665e344</rasd:InstanceId><rasd:ResourceType>10</rasd:ResourceType><rasd:OtherResourceType>net_HOME</rasd:OtherResourceType><rasd:ResourceSubType>3</rasd:ResourceSubType><rasd:Connection>net_HOME</rasd:Connection><rasd:Linked>true</rasd:Linked><rasd:Name>nic1</rasd:Name><rasd:ElementName>nic1</rasd:ElementName><rasd:MACAddress>00:1a:4a:16:01:04</rasd:MACAddress><rasd:speed>1000</rasd:speed><Type>interface</Type><Device>bridge</Device><rasd:Address>{type=pci, slot=0x03, bus=0x00, domain=0x0000, function=0x0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>net0</Alias></Item><Item><rasd:Caption>USB Controller</rasd:Caption><rasd:InstanceId>3</rasd:InstanceId><rasd:ResourceType>23</rasd:ResourceType><rasd:UsbPolicy>DISABLED</rasd:UsbPolicy></Item><Item><rasd:Caption>Graphical Controller</rasd:Caption><rasd:InstanceId>585fc912-16d6-421d-acda-eeaa17b955c1</rasd:InstanceId><rasd:ResourceType>20</rasd:ResourceType><rasd:VirtualQuantity>1</rasd:VirtualQuantity><rasd:SinglePciQxl>false</rasd:SinglePciQxl><Type>video</Type><Device>qxl</Device><rasd:Address>{type=pci, slot=0x02, bus=0x00, domain=0x0000, function=0x0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>video0</Alias><SpecParams><vgamem>16384</vgamem><heads>1</heads><vram>32768</vram><ram>65536</ram></SpecParams></Item><Item><rasd:Caption>Graphical Framebuffer</rasd:Caption><rasd:InstanceId>8c56ce64-dc7b-4a05-995a-eba2f31997fe</rasd:InstanceId><rasd:ResourceType>26</rasd:ResourceType><Type>graphics</Type><Device>spice</Device><rasd:Address></rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias></Alias></Item><Item><rasd:Caption>Graphical Framebuffer</rasd:Caption><rasd:InstanceId>ecfe54b9-26f1-4f44-9745-50cc45c9d50e</rasd:InstanceId><rasd:ResourceType>26</rasd:ResourceType><Type>graphics</Type><Device>vnc</Device><rasd:Address></rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias></Alias></Item><Item><rasd:Caption>CDROM</rasd:Caption><rasd:InstanceId>922be48e-a7ef-4490-8a46-df6d09d30aab</rasd:InstanceId><rasd:ResourceType>15</rasd:ResourceType><Type>disk</Type><Device>cdrom</Device><rasd:Address>{type=drive, bus=1, controller=0, target=0, unit=0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>true</IsReadOnly><Alias>ide0-1-0</Alias><SpecParams><path>CentOS-7-x86_64-NetInstall-1708.iso</path></SpecParams></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>e4f99c78-0a99-4b36-a3da-34e9267c9d59</rasd:InstanceId><Type>channel</Type><Device>spicevmc</Device><rasd:Address>{type=virtio-serial, bus=0, controller=0, port=3}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>channel2</Alias></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>0307995b-613a-4819-b667-4c077880eca9</rasd:InstanceId><Type>controller</Type><Device>ide</Device><rasd:Address>{type=pci, slot=0x01, bus=0x00, domain=0x0000, function=0x1}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>ide</Alias><SpecParams><index>0</index></SpecParams></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>0cc781c0-18c8-4096-8ab5-062eb51b1ef9</rasd:InstanceId><Type>channel</Type><Device>unix</Device><rasd:Address>{type=virtio-serial, bus=0, controller=0, port=1}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>channel0</Alias></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>55a35000-8756-45e5-89e6-32c914b1ef75</rasd:InstanceId><Type>channel</Type><Device>unix</Device><rasd:Address>{type=virtio-serial, bus=0, controller=0, port=2}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>channel1</Alias></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>c4cc5f36-26c3-4f1e-9a40-7cb1a4c28025</rasd:InstanceId><Type>controller</Type><Device>virtio-serial</Device><rasd:Address>{type=pci, slot=0x05, bus=0x00, domain=0x0000, function=0x0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>virtio-serial0</Alias></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>d64ea1bd-cf70-4786-9bfd-80121e30cbdf</rasd:InstanceId><Type>controller</Type><Device>usb</Device><rasd:Address>{type=pci, slot=0x01, bus=0x00, domain=0x0000, function=0x2}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>usb</Alias><SpecParams><index>0</index><model>piix3-uhci</model></SpecParams></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>2b5977d2-133d-4180-98b8-e96ab5401a0f</rasd:InstanceId><Type>rng</Type><Device>virtio</Device><rasd:Address>{type=pci, slot=0x06, bus=0x00, domain=0x0000, function=0x0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>rng0</Alias><SpecParams><source>urandom</source></SpecParams></Item><Item><rasd:ResourceType>0</rasd:ResourceType><rasd:InstanceId>f0c7a69b-6cd6-4428-84bf-5e862cb20202</rasd:InstanceId><Type>controller</Type><Device>virtio-scsi</Device><rasd:Address>{type=pci, slot=0x04, bus=0x00, domain=0x0000, function=0x0}</rasd:Address><BootOrder>0</BootOrder><IsPlugged>true</IsPlugged><IsReadOnly>false</IsReadOnly><Alias>scsi0</Alias></Item></VirtualHardwareSection></VirtualSystem></ovf:Envelope>', --extra-vars=ovirt_ova_pack_disks=/rhev/data-center/mnt/10.25.0.11:_mnt_vol01_kvmclst1_vmstore/c79208ed-8753-4ded-a137-8f08dfff5a40/images/a1b75b90-04c8-4f8d-899e-7d0354e36b09/2508c6d1-4ac2-4580-bb51-47fb3f4ca4f9::3448045568, /usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml] [Logfile: /var/log/ovirt-engine/ova/ovirt-export-ova-ansible-20191203112412-kvmclst1a.home.whootis.com-67d3d8f2.log] 2019-12-03 11:24:22,637-08 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Ansible playbook command has exited with value: 2 2019-12-03 11:24:22,638-08 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Failed to create OVA. Please check logs for more details: /var/log/ovirt-engine/ova/ovirt-export-ova-ansible-20191203112412-kvmclst1a.home.whootis.com-67d3d8f2.log 2019-12-03 11:24:22,640-08 ERROR [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Failed to create OVA file 2019-12-03 11:24:22,640-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Command 'ExportOva' id: 'd684210f-56b3-41ba-a699-e93341afdba2' failed when attempting to perform the next operation, marking as FAILED '[ef1b7dde-5908-4f1f-9d0a-228bf234d9fa]' 2019-12-03 11:24:22,640-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-40) [67d3d8f2] Command 'ExportOva' id: 'd684210f-56b3-41ba-a699-e93341afdba2' child commands '[ef1b7dde-5908-4f1f-9d0a-228bf234d9fa]' executions were completed, status 'FAILED' 2019-12-03 11:24:23,655-08 ERROR [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Ending command 'org.ovirt.engine.core.bll.exportimport.ExportOvaCommand' with failure. 2019-12-03 11:24:23,657-08 INFO [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Lock freed to object 'EngineLock:{exclusiveLocks='[aecb985a-450a-43f1-957a-09776aa48899=VM]', sharedLocks=''}' 2019-12-03 11:24:23,667-08 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [d25a398d-f650-4911-ae2a-2ca2b54e8396] EVENT_ID: IMPORTEXPORT_EXPORT_VM_TO_OVA_FAILED(1,225), Failed to export Vm GRAYLOG as a Virtual Appliance to path /tmp/GRAYLOG.ova on Host KVMCLST1A Thanks for any help you can be! -Geoff

3 2

Re: ovirt-ha-agent not running
by Strahil 08 Dec '19

08 Dec '19

What is the content of '/rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/' ? Usually when you restart the broker & agent, they will check if the links exist and are recreated again. You can try to set the host into maintenance (local), then stop ovirt-ha-agent & ovirt-ha-broker . Then start the broker and after it -> the agent. You can increase the log level via : /etc/ovirt-hosted-engine-ha/agent-log.conf /etc/ovirt-hosted-engine-ha/broker-log.conf (Don't forget to restart the service). Best Regards, Strahil NikolovOn Dec 7, 2019 17:22, Stefan Wolf <shb256(a)gmail.com> wrote: > > and here is the broker.log > > MainThread::INFO::2019-12-07 15:20:03,563::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started > MainThread::INFO::2019-12-07 15:20:03,564::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors > MainThread::INFO::2019-12-07 15:20:03,564::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > MainThread::INFO::2019-12-07 15:20:03,565::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > MainThread::INFO::2019-12-07 15:20:03,566::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > MainThread::INFO::2019-12-07 15:20:03,566::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > MainThread::INFO::2019-12-07 15:20:03,567::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > MainThread::INFO::2019-12-07 15:20:03,567::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > MainThread::INFO::2019-12-07 15:20:03,568::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > MainThread::INFO::2019-12-07 15:20:03,569::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > MainThread::INFO::2019-12-07 15:20:03,569::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > MainThread::INFO::2019-12-07 15:20:03,574::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > MainThread::INFO::2019-12-07 15:20:03,575::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > MainThread::INFO::2019-12-07 15:20:03,576::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > MainThread::INFO::2019-12-07 15:20:03,577::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > MainThread::INFO::2019-12-07 15:20:03,577::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > MainThread::INFO::2019-12-07 15:20:03,577::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Finished loading submonitors > MainThread::INFO::2019-12-07 15:20:03,651::storage_backends::373::ovirt_hosted_engine_ha.lib.storage_backends::(connect) Connecting the storage > MainThread::INFO::2019-12-07 15:20:03,652::storage_server::349::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server) Connecting storage server > MainThread::INFO::2019-12-07 15:20:03,716::storage_server::356::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server) Connecting storage server > MainThread::INFO::2019-12-07 15:20:03,748::storage_server::413::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server) Refreshing the storage domain > MainThread::WARNING::2019-12-07 15:20:06,985::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/hosted-engine.lockspace' > > > maybe it helps > > bye shb > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KECDUEVCHP3OS…

3 3

Re: Hyper-V to KVM | v2v
by Strahil 07 Dec '19

07 Dec '19

Have you tried to power up and fully shutdown the VM ? Best Regards, Strahil NikolovOn Dec 6, 2019 15:52, Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote: > > Hello, > > > > I am trying to convert a Hyper-V guest VM to run on KVM using virt-v2v utility. > > > > Getting below error: > > > > > > Any suggestions how to solve this. > > > > Thanks > > > > Vijay Sachdeva > >

2 2

ovirt-ha-agent not running
by Stefan Wolf 07 Dec '19

07 Dec '19

hello, since some days ovirt-ha-agent is not running anymore i ve 4 ovirt hosts and only on one host the agent is running. maybe it was from an update, because i lost one agent after an other. i ve done a complete fresh install for the host with the latest ovirt node. I ve got on tree hosts this error [root@kvm380 ~]# systemctl status ovirt-ha-agent ● ovirt-ha-agent.service - oVirt Hosted Engine High Availability Monitoring Agent Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-agent.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Sa 2019-12-07 14:56:21 UTC; 5s ago Process: 28002 ExecStart=/usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent (code=exited, status=157) Main PID: 28002 (code=exited, status=157) Tasks: 0 CGroup: /system.slice/ovirt-ha-agent.service Dez 07 14:56:21 kvm380.durchhalten.intern systemd[1]: ovirt-ha-agent.service: main process exited, code=exited, status=157/n/a Dez 07 14:56:21 kvm380.durchhalten.intern systemd[1]: Unit ovirt-ha-agent.service entered failed state. Dez 07 14:56:21 kvm380.durchhalten.intern systemd[1]: ovirt-ha-agent.service failed. and this is in /var/log/ovirt-hosted-engine-ha/agent.log MainThread::INFO::2019-12-07 15:01:51,048::agent::67::ovirt_hosted_engine_ha.agent.agent.Agent::(run) ovirt-hosted-engine-ha agent 2.3.6 started MainThread::INFO::2019-12-07 15:01:51,161::hosted_engine::234::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_hostname) Found certificate common name: kvm380.durchhalten.intern MainThread::INFO::2019-12-07 15:01:51,374::hosted_engine::543::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker) Initializing ha-broker connection MainThread::INFO::2019-12-07 15:01:51,378::brokerlink::80::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Starting monitor network, options {'tcp_t_address': None, 'network_test': None, 'tcp_t_port': None, 'addr': '192.168.200.1'} MainThread::ERROR::2019-12-07 15:01:51,379::hosted_engine::559::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker) Failed to start necessary monitors MainThread::ERROR::2019-12-07 15:01:51,381::agent::144::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 131, in _run_agent return action(he) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_proper return he.start_monitoring() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 432, in start_monitoring self._initialize_broker() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 556, in _initialize_broker m.get('options', {})) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 89, in start_monitor ).format(t=type, o=options, e=e) RequestError: brokerlink - failed to start monitor via ovirt-ha-broker: [Errno 2] No such file or directory, [monitor: 'network', options: {'tcp_t_address': None, 'network_test': None, 'tcp_t_port': None, 'addr': '192.168.200.1'}] MainThread::ERROR::2019-12-07 15:01:51,381::agent::145::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Trying to restart agent MainThread::INFO::2019-12-07 15:01:51,382::agent::89::ovirt_hosted_engine_ha.agent.agent.Agent::(run) Agent shutting down maybe someone can give me an advice thx shb

1 1

VLANs with one NIC in ovirt
by siovelrm＠gmail.com 06 Dec '19

06 Dec '19

Hi, is it possible to use different VLANs with one NIC in ovirt? Regards

4 4

Hyper-V to KVM | v2v
by Vijay Sachdeva 06 Dec '19

06 Dec '19

Hello, I am trying to convert a Hyper-V guest VM to run on KVM using virt-v2v utility. Getting below error: Any suggestions how to solve this. Thanks Vijay Sachdeva

3 2

Issue deploying self hosted engine on new install
by Robert Webb 06 Dec '19

06 Dec '19

Hi all, I am trying to deploy the self hosted engine via cockpit and it is failing at the very end of deployment when it is checking the VM Health. I have done multiple clean installs and run this and it fails every time. I have also tried from the cli via ssh with the same outcome. After the failure, if I look at the oVirt Machines section of the node, the VM is there but will not start. Anyone else having this issue?

1 0