- Users - oVirt List Archives

Ovirt-4.4.7 Adding host to existing cluster will attempt to run ovirt-hosted-engine-setup
by Paul-Erik Törrönen 15 Aug '21

15 Aug '21

I have an existing oVirt-installation to which I want to add a new host (from the UI). However the adding fails because oVirt tries to then install the ovirt-hosted-engine-setup despite the fact that in the New host-dialog I left the Choose hosted engine deployment action as None. As a result the installation then aborts: 2021-08-15 13:17:37 EEST - TASK [ovirt-host-deploy-vdsm : Install ovirt-hosted-engine-setup package] ****** 2021-08-15 13:17:37 EEST - 2021-08-15 13:17:37 EEST - fatal: [new.host]: FAILED! => {"changed": false, "failures": ["No package ovirt-hosted-engine-setup available."], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []} 2021-08-15 13:17:37 EEST - { "status" : "OK", "msg" : "", "data" : { "uuid" : "98a244fb-15da-4192-a8fc-b23a5e5b7594", "counter" : 55, "stdout" : "fatal: [new.host]: FAILED! => {\"changed\": false, \"failures\": [\"No package ovirt-hosted-engine-setup available.\"], \"msg\": \"Failed to install some of the specified packages\", \"rc\": 1, \"results\": []}", "start_line" : 47, "end_line" : 48, "runner_ident" : "fe710372-fdb1-11eb-81f0-ecf4bb63099f", "event" : "runner_on_failed", "pid" : 24931, "created" : "2021-08-15T10:17:35.963320", "parent_uuid" : "ecf4bb63-099f-2448-1b83-0000000001a7", "event_data" : { "playbook" : "ovirt-host-deploy.yml", "playbook_uuid" : "8f70f945-4008-4159-b469-7ff04c9c242b", "play" : "all", "play_uuid" : "ecf4bb63-099f-2448-1b83-000000000006", "play_pattern" : "all", "task" : "Install ovirt-hosted-engine-setup package", "task_uuid" : "ecf4bb63-099f-2448-1b83-0000000001a7", "task_action" : "yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:6", "role" : "ovirt-host-deploy-vdsm", "host" : "new.host", "remote_addr" : "new.host", "res" : { "msg" : "Failed to install some of the specified packages", "failures" : [ "No package ovirt-hosted-engine-setup available." ], "results" : [ ], "rc" : 1, "invocation" : { "module_args" : { "name" : [ "ovirt-hosted-engine-setup" ], "state" : "present", "allow_downgrade" : false, "autoremove" : false, "bugfix" : false, "disable_gpg_check" : false, "disable_plugin" : [ ], "disablerepo" : [ ], "download_only" : false, "enable_plugin" : [ ], "enablerepo" : [ ], ... Poltsi

1 0

about the clonetype of the vm disk when vm is cloned from template
by Tommy Sway 14 Aug '21

14 Aug '21

There are some options for clone disk for other platform like oVirt. --clonetype [thin|full] A thin clone uses copy-on-write (COW) reflinked clone meaning it is dependent on the base template, but enables rapid cloning. Full clone will make a full physical copy hence not be dependent on the base template. Thin clone uses less space and will not be as performant as full clone, especially under heavy write workloads. By default a thin clone is created, great for testing; should be avoided in production environments. I want to know which type is oVirt using when we clone vm from template ?

2 2

Hosted engine on HCI cluster is not running
by David White 14 Aug '21

14 Aug '21

Hello, It appears that my Manager / hosted-engine isn't working, and I'm unable to get it to start. I have a 3-node HCI cluster, but right now, Gluster is only running on 1 host (so no replication). I was hoping to upgrade / replace the storage on my 2nd host today, but aborted that maintenance when I found that I couldn't even get into the Manager. The storage is mounted, but here's what I see: > [root@cha2-storage dwhite]# hosted-engine --vm-statusThe hosted engine configuration has not been retrieved from shared storage. Please ensure that ovirt-ha-agent is running and the storage server is reachable. > > [root@cha2-storage dwhite]# 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: active (running) since Fri 2021-08-13 11:10:51 EDT; 2h 44min ago > Main PID: 3591872 (ovirt-ha-agent) > Tasks: 1 (limit: 409676) > Memory: 21.5M > CGroup: /system.slice/ovirt-ha-agent.service > └─3591872 /usr/libexec/platform-python /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent > > Aug 13 11:10:51 cha2-storage.mgt.barredowlweb.com systemd[1]: Started oVirt Hosted Engine High Availability Monitoring Agent. Any time I try to do anything like connect the engine storage, disconnect the engine storage, or connect to the console, it just sits there, and doesn't do anything, and I eventually have to ctl-c out of it. Maybe I have to be patient? When I ctl-c, I get a trackback error: > [root@cha2-storage dwhite]# hosted-engine --console^CTraceback (most recent call last): > File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main > > "__main__", mod_spec) > File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code > exec(code, run_globals) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/vdsm_helper.py", line 214, in <module> > [root@cha2-storage dwhite]# args.command(args) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/vdsm_helper.py", line 42, in func > f(*args, **kwargs) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/vdsm_helper.py", line 91, in checkVmStatus > cli = ohautil.connect_vdsm_json_rpc() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/util.py", line 472, in connect_vdsm_json_rpc > __vdsm_json_rpc_connect(logger, timeout) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/util.py", line 395, in __vdsm_json_rpc_connect > timeout=timeout) > File "/usr/lib/python3.6/site-packages/vdsm/client.py", line 154, in connect > outgoing_heartbeat=outgoing_heartbeat, nr_retries=nr_retries) > File "/usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py", line 426, in SimpleClient > nr_retries, reconnect_interval) > File "/usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py", line 448, in StandAloneRpcClient > client = StompClient(utils.create_connected_socket(host, port, sslctx), > File "/usr/lib/python3.6/site-packages/vdsm/utils.py", line 379, in create_connected_socket > sock.connect((host, port)) > File "/usr/lib64/python3.6/ssl.py", line 1068, in connect > self._real_connect(addr, False) > File "/usr/lib64/python3.6/ssl.py", line 1059, in _real_connect > self.do_handshake() > File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake > self._sslobj.do_handshake() > File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake > self._sslobj.do_handshake() This is what I see in /var/log/ovirt-hosted-engine-ha/broker.log: > MainThread::WARNING::2021-08-11 10:24:41,596::storage_broker::100::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: Connection to storage server failed > MainThread::ERROR::2021-08-11 10:24:41,596::broker::69::ovirt_hosted_engine_ha.broker.broker.Broker::(run) Failed initializing the broker: Connection to storage server failed > MainThread::ERROR::2021-08-11 10:24:41,598::broker::71::ovirt_hosted_engine_ha.broker.broker.Broker::(run) Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 64, in run > self._storage_broker_instance = self._get_storage_broker() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 143, in _get_storage_broker > return storage_broker.StorageBroker() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 97, in __init__ > self._backend.connect() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 375, in connect > sserver.connect_storage_server() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py", line 451, in connect_storage_server > 'Connection to storage server failed' > RuntimeError: Connection to storage server failed > > MainThread::ERROR::2021-08-11 10:24:41,599::broker::72::ovirt_hosted_engine_ha.broker.broker.Broker::(run) Trying to restart the broker > MainThread::INFO::2021-08-11 10:24:42,439::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.4.7 started > MainThread::INFO::2021-08-11 10:24:44,442::monitor::45::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/submonitors > MainThread::INFO::2021-08-11 10:24:44,443::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > MainThread::INFO::2021-08-11 10:24:44,449::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > MainThread::INFO::2021-08-11 10:24:44,450::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > MainThread::INFO::2021-08-11 10:24:44,451::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > MainThread::INFO::2021-08-11 10:24:44,451::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > MainThread::INFO::2021-08-11 10:24:44,452::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > MainThread::INFO::2021-08-11 10:24:44,452::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > MainThread::INFO::2021-08-11 10:24:44,452::monitor::63::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Finished loading submonitors And I see this in /var/log/vdsm/vdsm.log: > 2021-08-13 14:08:10,844-0400 ERROR (Reactor thread) [ProtocolDetector.AcceptorImpl] Unhandled exception in acceptor (protocoldetector:76) > Traceback (most recent call last): > File "/usr/lib64/python3.6/asyncore.py", line 108, in readwrite > File "/usr/lib64/python3.6/asyncore.py", line 417, in handle_read_event > File "/usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py", line 57, in handle_accept > File "/usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py", line 173, in _delegate_call > File "/usr/lib/python3.6/site-packages/vdsm/protocoldetector.py", line 53, in handle_accept > File "/usr/lib64/python3.6/asyncore.py", line 348, in accept > File "/usr/lib64/python3.6/socket.py", line 205, in accept > OSError: [Errno 24] Too many open files Can anyone help? Sent with ProtonMail Secure Email.

2 3

[ANN] oVirt 4.4.8 Fifth Release Candidate is now available for testing
by Lev Veyde 13 Aug '21

13 Aug '21

oVirt 4.4.8 Fifth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.8 Fifth Release Candidate for testing, as of August 13th, 2021. This update is the eighth in a series of stabilization updates to the 4.4 series. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.8 release highlights: http://www.ovirt.org/release/4.4.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.4.8/ [2] http://resources.ovirt.org/pub/ovirt-4.4-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

Unable to connect to the Graphic server
by Gangi Reddy 13 Aug '21

13 Aug '21

We are receiving below error while attempt to connect SPICE console. No block in network firewall. Version: Software Version:4.4.6.7-1.el8 Error: Unable to connect to the Graphic server .vv

1 1

Automigration of VMs from other hypervisors
by KK CHN 11 Aug '21

11 Aug '21

Hi list, I am in the process of migrating 150+ VMs running on Rhevm4.1 to KVM based OpenStack installation ( Ussuri with KVm and glance as image storage.) What I am doing now, manually shutdown each VM through RHVM GUI and export to export domain and scp those image files of each VM to our OpenStack controller node and uploading to glance and creating each VM manually. query 1. Is there a better way to automate this migration by any utility or scripts ? Any one done this kind of automatic migration before what was your approach? Or whats the better approach instead of doing manual migration ? Or only manually I have to repeat the process for all 150+ Virtual machines? ( guest VMs are CentOS7 and Redhat Linux 7 with LVM data partitions attached) Kindly share your thoughts.. Query 2. other than this 150+ VMs Redhat Linux 7 and Centos VMs on Rhevm 4.1, I have to migrate 50+ VMs which hosted on hyperV. What the method / approach for exporting from HyperV and importing to OpenStack Ussuri version with glance with KVM hpervisor ? ( This is the ffirst time I am going to use hyperV, no much idea about export from hyperv and Import to KVM) Will the images exported form HyperV(vhdx image disks with single disk and multiple disk(max 3 disk) VMs) can be directly imported to KVM ? does KVM support this or need to modify vhdx disk images to any other format ? What is the best approach should be in case of HyperV hosted VMs( Windows 2012 guest machines and Linux guest machines ) to be imported to KVM based OpenStack(Ussuri version with glance as image storage ). Thanks in advance Kris

1 0

Ubuntu 20.04 cloud-init
by Pavel Šipoš 11 Aug '21

11 Aug '21

Hi. We are using oVirt version 4.3.10.4-1.el7 I am trying to use clod-init function in ovirt to set password and add ssh keys for VM on first boot. It is working perfectly on Centos7, Centos8, but not with Ubuntu 20.04.02 . On VM Cloud-init package and quemu-guest-agent are installed, services are running - I checked that and then used Run once to test further but no luck. It looks like its not even trying to set anything. I am open to suggestions how to debug this. I see no errors if I look into /var/log/cloud-init logs on VM. Did anyone else had similar problem? Can anyone confirm that cloud-init function in ovirt should work with ubuntu 20.04? Packages used: cloud-init 21.2-3-g899bfaa9-0ubuntu2~20.04.1 qemu-guest-agent 1:4.2-3ubuntu6.17 I made ovirt template myself using packer (qemu) that also uses cloud-init for bootstrapping. Thank you in advance! Pavel -- -- Pavel Sipos, Arnes <pavel.sipos(a)arnes.si> ARNES, p.p. 7, SI-1001 Ljubljana, Slovenia T: +386 1 479 88 00 W: www.arnes.si, aai.arnes.si

2 2

low iscsi storage space
by Leonardo Costa 10 Aug '21

10 Aug '21

Hello. I'm having a problem that I can't solve, I have 20Tb of space on Ovirt but on my DELL SCV 3000 storage, only 5Tb free on the volume. It seems to me that the deleted machines are not removing the disks in the storage iscsi. Could anyone help?

2 1

Major network issue with 4.4.7
by Andrea Chierici 10 Aug '21

10 Aug '21

Dear all, I've been using ovirt for at least 6 years and only lately I've stepped into a weird problem that I hope someone will be able to give help. My hardware is: - blade lenovo for hosts, with dual switch - dell equallogic for iscsi storage, directly connected to the blade switches - The two host network cards are configured with bonding and all the vlans are accessed from it (mtu 9000) - all the hosts and ovirt engine have firewalld service disabled) My engine is hosted on a separate vmware vm (I will evaluate the self hosted engine later...). I want to stress the fact that for years this setup worked smoothly without any significant issue (and all the minor updates were completed flawlessly). A few weeks ago I started the update from the rock solid 4.3 to the latest 4.4.7. I began with the manager, following the docs, installing a new centos8 vm and importing the backup: everything went smootly and I was able to get access to the manager without any problem, all the machines still there :) I then began updating the hosts, from centos7 to centos8 stream, one by one. Immediately I noticed network issues, with the VMs hosted on the first updated host. Migrating VMs from centos8 host to other centos8 quite often fails, but the main issue is this: *if I start one of the VMs on the centos8 host, they have no network connectivity. If I migrate them to a centos7 hosts the network starts to work, and if I migrate the VMs back to the centos8 host, the network keeps working.* I am puzzled and can't understand what's going on. Generally speaking all the centos8 hosts (I have 6 in my cluster, and now 3 are centos8 while the rest is still centos7) seem to be very unstable, meaning that the VMs they host are quite often showing network issues and temporary glitches. Can someone give a hint on how to solve this weird issue? Thanks, Andrea -- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --

3 4

live merge of snapshots failed
by g.vasilopoulos＠uoc.gr 10 Aug '21

10 Aug '21

Hello I have a situation with a vm in which I cannot delete the snapshot. The whole thing is quite strange because I can delete the snapshot when I create and delete it from the web interface but when I do it with a python script through the API it failes. The script does create snapshot-> download snapshot-> delete snapshot and I used the examples from ovirt python sdk on githab to create it ,in general it works prety well. But on a specific machine (so far) it cannot delete the live snapshot Ovirt is 4.3.10 and the guest is a windows 10 pc. Windows 10 guest has 2 disks attached both on different fc domains one on an ssd emc and the other on an hdd emc. Both disks are prealocated. I cannot figure out what the problem is so far the related engine log: 2021-08-03 15:51:00,385+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-61) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Comma nd 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: '74c83880-581b-4774-ae51-8c4af0c92c53' type:'Merge' to complete 2021-08-03 15:51:00,385+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-61) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete ( jobId = 62bf8c83-cd78-42a5-b57d-d67ddfdee8ee) 2021-08-03 15:51:00,387+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-61) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:01,388+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-30) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) 2021-08-03 15:51:07,491+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-38) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'MoveImageGroup' (id: '1de1b800-873f-405f-805b-f44397740909') waiting on child command id: 'd1136344-2888-4d63-8fe1-b506426bc8aa' type:'CopyImageGroupWithData' to complete 2021-08-03 15:51:11,513+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:12,522+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: '74c83880-581b-4774-ae51-8c4af0c92c53' type:'Merge' to complete 2021-08-03 15:51:12,523+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = 62bf8c83-cd78-42a5-b57d-d67ddfdee8ee) 2021-08-03 15:51:12,527+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:13,528+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-37) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) 2021-08-03 15:51:21,635+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-58) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:22,655+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: '74c83880-581b-4774-ae51-8c4af0c92c53' type:'Merge' to complete 2021-08-03 15:51:22,661+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Merge command (jobId = 62bf8c83-cd78-42a5-b57d-d67ddfdee8ee) has completed for images '7611ebcf-5323-45ca-b16c-9302d0bdedc6'..'17618ba1-4ab8-49eb-a991-fc3d602ced14' 2021-08-03 15:51:22,664+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:23,664+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) 2021-08-03 15:51:24,672+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Live Merge command step 'MERGE_STATUS' 2021-08-03 15:51:24,699+03 INFO [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Running command: MergeStatusCommand internal: true. Entities affected : ID: 96000ec9-e181-44eb-893f-e0a36e3a6775 Type: Storage 8-03 15:51:24,749+03 INFO [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Successfully removed volume 17618ba1-4 ab8-49eb-a991-fc3d602ced14 from the chain 2021-08-03 15:51:24,749+03 INFO [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Volume merge type 'COMMIT' 2021-08-03 15:51:25,691+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGroup WithData' (id: 'd1136344-2888-4d63-8fe1-b506426bc8aa') waiting on child command id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5' type:'CopyImageGroupVolumesData' to complete 2021-08-03 15:51:26,692+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGrou pVolumesData' (id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5') waiting on child command id: 'f46d65cb-32d9-4269-982e-6e19331b8a27' type:'CopyData' to complete 2021-08-03 15:51:26,711+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Liv e Merge command step 'DESTROY_IMAGE' 2021-08-03 15:51:26,726+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Running command: DestroyImageCommand internal: true. Entities affected : ID: 96000ec9-e181-44eb-893f-e0a36e3a6775 Type: Storage 2021-08-03 15:51:26,747+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DestroyImageVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, DestroyIma geVDSCommand( DestroyImageVDSCommandParameters:{storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', ignoreFailoverLimit='false', storageDomainId='96000ec9-e181-44eb-893f-e0a36e3a6775', imageGroupId='205a30a3-f c06-4ceb-8ef2-018f16d4ccbb', imageId='00000000-0000-0000-0000-000000000000', imageList='[17618ba1-4ab8-49eb-a991-fc3d602ced14]', postZero='false', force='false'}), log id: 307a3fb1 2021-08-03 15:51:26,834+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DestroyImageVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, DestroyIm ageVDSCommand, return: , log id: 307a3fb1 2021-08-03 15:51:26,846+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::Adding CommandM ultiAsyncTasks object for command 'baaa5254-261c-452a-84b4-0a8b397cdb62' 2021-08-03 15:51:26,847+03 INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandMultiAsyncTasks::attachTas k: Attaching task 'ae2e80a4-d224-4fc3-a84b-859042811525' to command 'baaa5254-261c-452a-84b4-0a8b397cdb62'. 2021-08-03 15:51:26,857+03 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Adding task 'ae2e80a4-d224-4fc3-a 84b-859042811525' (Parent Command 'DestroyImage', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2021-08-03 15:51:26,858+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Successfully star ted task to remove orphaned volumes 2021-08-03 15:51:26,863+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] BaseAsyncTask::startPollingTask: Star ting to poll task 'ae2e80a4-d224-4fc3-a84b-859042811525'. 2021-08-03 15:51:26,863+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] BaseAsyncTask::startPollingTask: Star ting to poll task 'ae2e80a4-d224-4fc3-a84b-859042811525'. 2021-08-03 15:51:28,799+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-88) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on destroy image command to complete the task (taskId = ae2e80a4-d224-4fc3-a84b-859042811525) 2021-08-03 15:51:30,805+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-48) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: 'baaa5254-261c-452a-84b4-0a8b397cdb62' type:'DestroyImage' to complete 2021-08-03 15:51:31,824+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:32,825+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on destroy image command to complete the task (taskId = ae2e80a4-d224-4fc3-a84b-859042811525) 2021-08-03 15:51:32,831+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:33,594+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'DestroyImage' completed, handling the result. 2021-08-03 15:51:33,594+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'DestroyImage' succeeded, clearing tasks. 2021-08-03 15:51:33,594+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'ae2e80a4-d224-4fc3-a84b-859042811525' 2021-08-03 15:51:33,595+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', ignoreFailoverLimit='false', taskId='ae2e80a4-d224-4fc3-a84b-859042811525'}), log id: 6225ae22 2021-08-03 15:51:33,596+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, HSMClearTaskVDSCommand(HostName = ovirt2-7.vmmgmt-int.uoc.gr, HSMTaskGuidBaseVDSCommandParameters:{hostId='10599b78-5f45-48d2-bfe0-028f3dae69eb', taskId='ae2e80a4-d224-4fc3-a84b-859042811525'}), log id: 45b18a8a 2021-08-03 15:51:33,611+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, HSMClearTaskVDSCommand, return: , log id: 45b18a8a 2021-08-03 15:51:33,611+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, SPMClearTaskVDSCommand, return: , log id: 6225ae22 2021-08-03 15:51:33,614+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] BaseAsyncTask::removeTaskFromDB: Removed task 'ae2e80a4-d224-4fc3-a84b-859042811525' from DataBase 2021-08-03 15:51:33,614+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity 'baaa5254-261c-452a-84b4-0a8b397cdb62' 2021-08-03 15:51:33,839+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-95) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Merge command (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) has completed for images '84c005da-cbec-4ace-8619-5a8e2ae5ea75'..'b43b7c33-5b53-4332-a2e0-f950debb919b' 2021-08-03 15:51:34,847+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Live Merge command step 'MERGE_STATUS' 2021-08-03 15:51:34,917+03 ERROR [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Failed to live merge. Top volume b43b7c33-5b53-4332-a2e0-f950debb919b is still in qemu chain [b43b7c33-5b53-4332-a2e0-f950debb919b, 84c005da-cbec-4ace-8619-5a8e2ae5ea75] 2021-08-03 15:51:35,866+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGroupWithData' (id: 'd1136344-2888-4d63-8fe1-b506426bc8aa') waiting on child command id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5' type:'CopyImageGroupVolumesData' to complete 2021-08-03 15:51:36,867+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGroupVolumesData' (id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5') waiting on child command id: 'f46d65cb-32d9-4269-982e-6e19331b8a27' type:'CopyData' to complete 2021-08-03 15:51:36,873+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a failed child command status for step 'MERGE_STATUS' 2021-08-03 15:51:36,873+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' child commands '[a7de75fe-e94c-4795-9310-2c8fc3d6d3fc, ec806ac6-929f-42d9-a86e-98d6a39a4718, 6443529c-d753-48f6-8a9e-af1f9f09dfb5]' executions were completed, status 'FAILED' 2021-08-03 15:51:37,982+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Merging of snapshot '1cd4985b-b0c0-40d6-bbde-54451e43bef6' images '84c005da-cbec-4ace-8619-5a8e2ae5ea75'..'b43b7c33-5b53-4332-a2e0-f950debb919b' failed. Images have been marked illegal and can no longer be previewed or reverted to. Please retry Live Merge on the snapshot to complete the operation. 2021-08-03 15:51:37,985+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' with failure. 2021-08-03 15:51:39,014+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Live Merge command step 'REDUCE_IMAGE' 2021-08-03 15:51:39,029+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] No need to execute reduce image command, skipping its execution. Storage Type: 'FCP', Disk: 'anova.admin.uoc.gr_Disk2' Snapshot: 'anova.admin.uoc.gr-2021-08-03' 2021-08-03 15:51:39,034+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' id: '80dc4609-b91f-4e93-bc12-7b2083933e5a' child commands '[18653ea6-166c-41a3-b335-84525871b9e6, 74c83880-581b-4774-ae51-8c4af0c92c53, 92e92d8e-b099-47dd-ba8c-e3db907f9a62, baaa5254-261c-452a-84b4-0a8b397cdb62]' executions were completed, status 'SUCCEEDED' 2021-08-03 15:51:39,040+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '80dc4609-b91f-4e93-bc12-7b2083933e5a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:40,046+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, GetImageInfoVDSCommand( GetImageInfoVDSCommandParameters:{storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', ignoreFailoverLimit='false', storageDomainId='96000ec9-e181-44eb-893f-e0a36e3a6775', imageGroupId='205a30a3-fc06-4ceb-8ef2-018f16d4ccbb', imageId='7611ebcf-5323-45ca-b16c-9302d0bdedc6'}), log id: 4c98e4db 2021-08-03 15:51:40,047+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, GetVolumeInfoVDSCommand(HostName = ovirt2-7.vmmgmt-int.uoc.gr, GetVolumeInfoVDSCommandParameters:{hostId='10599b78-5f45-48d2-bfe0-028f3dae69eb', storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', storageDomainId='96000ec9-e181-44eb-893f-e0a36e3a6775', imageGroupId='205a30a3-fc06-4ceb-8ef2-018f16d4ccbb', imageId='7611ebcf-5323-45ca-b16c-9302d0bdedc6'}), log id: 4aca5f83 2021-08-03 15:51:40,084+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, GetVolumeInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@70097e6, log id: 4aca5f83 2021-08-03 15:51:40,084+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, GetImageInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@70097e6, log id: 4c98e4db 2021-08-03 15:51:40,283+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Successfully merged snapshot '1cd4985b-b0c0-40d6-bbde-54451e43bef6' images '17618ba1-4ab8-49eb-a991-fc3d602ced14'..'7611ebcf-5323-45ca-b16c-9302d0bdedc6' 2021-08-03 15:51:40,287+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' successfully. 2021-08-03 15:51:40,296+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9' child commands '[87bc90c7-2aa5-4a1b-b58c-54296518658a, 80dc4609-b91f-4e93-bc12-7b2083933e5a]' executions were completed, status 'FAILED' 2021-08-03 15:51:41,322+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 2021-08-03 15:51:41,353+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [3bf9345d-fab2-490f-ba44-6aa014bbb743] EVENT_ID: USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot 'anova.admin.uoc.gr-2021-08-03' for VM 'anova.admin.uoc.gr'. Any help would be highly appreciated

3 8

Q: Get Host Capabilities Failed after restart
by Andrei Verovski 10 Aug '21

10 Aug '21

Hi, I have oVirt 4.4.7.6-1.el8 and one problematic node (HP ProLiant with CentOS 8 stream). After replacing server rack router switch and restart got this error I can’t recover from: VDSM node14 command Get Host Capabilities failed: Message timeout which can be caused by communication issues vdsm-network running fine, but vdsmd can’t start on node14 for whatever reason. All other nodes running fine. Aug 09 10:24:12 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running dummybr Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running tune_system Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running test_space Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running test_lo Aug 09 10:24:13 node14.mydomain.lv systemd[1]: Started Virtual Desktop Server Manager. Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_systemd(sudo:session): Failed to create session: Start job for unit user-0.slice failed with 'canceled' Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_unix(sudo:session): session closed for user root Aug 09 10:24:17 node14.mydomain.lv vdsm[6754]: WARN MOM not available. Error: [Errno 2] No such file or directory Aug 09 10:24:17 node14.mydomain.lv vdsm[6754]: WARN MOM not available, KSM stats will be missing. Error: In web gui -> Management I can’t do anything with the host except restart. Stop aborts with error, all other commands are gray-ed out. Status is “Unassigned”. Host is answering to pings as usual. vdsm.log (from node14) attached. Thanks in advance for any help.

2 11

Storage Domains for a VM from Template
by Shantur Rathore 09 Aug '21

09 Aug '21

Hi all, I have multiple storage domains in my DC. One is backed up that has templates and another one which isn't backed up and I want to use it for VM instances of the template. I cannot find an option to create the VM from a template and use a storage domain other than where the template is stored. Is it even possible? Thanks, Shantur

2 3

any configuration when clients can't directly access oVirt cluster?
by yam yam 09 Aug '21

09 Aug '21

Hello, Under my environment, clients must go through a proxy to reach the oVirt cluster(physical nodes), so that I applied DNAT rules for engine and VM IPs to clients. but there were still some issues like VNC console(+browser) don't work, and I'm not sure other features work well. so, I'm wondering whether there is any oVirt configuration or some guides for such case using the proxy. Thanks,

2 1

ISO Upload in in Paused by System Status
by louisb＠ameritech.net 09 Aug '21

09 Aug '21

I'm attempting to upload an ISO that is approximately 9GB in size. I've succssfullly started th upload process via the oVirt Management Console/Disk. The upload started however, it now has a status of "Paused by System". My storage type is set to NFS Data. Is something happing the back ground that contributing to the "Paused by System"? I have mor the 84TB of space available so I don't think it is a space issue. Is there something that I need to do? At this time I'm going to wait and see if it moves forward on its own. Please provide me with any help or direction. Thanks

5 10

adding new host failed with error "CPU does not match the Cluster CPU Type"
by jimod4＠yahoo.com 09 Aug '21

09 Aug '21

i get the below error when i try to add a new kvm host to the cluster. I know that the cpu is a haswell, Intel E5-2640 v3. if i run "virsh capabilities" it returns <model>Haswell-noTSX-IBRS</model>. My KVM server is redhat 8.4 fully patched today on an DL-360 Gen9. oVirt is at 4.4.7.7-1.el8. i have tried many diffent CPU settings for the cluster and none of them work. this is new oVirt install. ERROR: "The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: vmx, model_Haswell-noTSX, nx. Please update the host CPU microcode or change the Cluster CPU Type." MIRCOCODE: root@kvm09 ~]# dmesg | grep 'microcode' [ 0.000000] microcode: microcode updated early to revision 0x46, date = 2021-01-27 [ 1.625108] microcode: sig=0x306f2, pf=0x1, revision=0x46 [ 1.625753] microcode: Microcode Update Driver: v2.2.

3 3

Adding new host to a cluster and stuck at "Detect if host is a prebuilt image".
by fauzuwan.nazri93＠gmail.com 08 Aug '21

08 Aug '21

Hello everyone, I try to add a host to a new cluster and during provisioning the event showed "Detect if host is a prebuilt image." and it just stuck there forever. Version: ovirt-node-ng-image-update-placeholder-4.4.7.1-1.el8.noarch Actual results: Host provisioning stuck at "Detect if host is a prebuilt image." Expected results: Provisioning successful. By checking the ovirt host deployment playbook logs, I can't found any useful output. Below is the last output form the logs. 2021-08-06 19:25:12 MYT - TASK [ovirt-host-deploy-facts : Detect if host is a prebuilt image] ************ 2021-08-06 19:25:12 MYT - ok: [ovirth02.zyzyx.virtnet] 2021-08-06 19:25:12 MYT - { "status" : "OK", "msg" : "", "data" : { "uuid" : "a7b74be9-30ab-4ca4-b2b6-e7af6b86bb6c", "counter" : 24, "stdout" : "ok: [ovirth02.zyzyx.virtnet]", "start_line" : 22, "end_line" : 23, "runner_ident" : "f155ccc8-f6a8-11eb-94c2-00e04cf8ff45", "event" : "runner_on_ok", "pid" : 1549383, "created" : "2021-08-06T11:25:10.333884", "parent_uuid" : "00e04cf8-ff45-b99d-863c-000000000182", "event_data" : { "playbook" : "ovirt-host-deploy.yml", "playbook_uuid" : "c1e368bf-e183-47c0-b6f5-377114c20eab", "play" : "all", "play_uuid" : "00e04cf8-ff45-b99d-863c-000000000007", "play_pattern" : "all", "task" : "Detect if host is a prebuilt image", "task_uuid" : "00e04cf8-ff45-b99d-863c-000000000182", "task_action" : "set_fact", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-facts/tasks/host-os.yml:26", "role" : "ovirt-host-deploy-facts", "host" : "ovirth02.zyzyx.virtnet", "remote_addr" : "ovirth02.zyzyx.virtnet", "res" : { "changed" : false, "ansible_facts" : { "node_host" : true }, "_ansible_no_log" : false }, "start" : "2021-08-06T11:25:10.254355", "end" : "2021-08-06T11:25:10.333550", "duration" : 0.079195, "event_loop" : null, "uuid" : "a7b74be9-30ab-4ca4-b2b6-e7af6b86bb6c" } } } 2021-08-06 19:25:12 MYT - TASK [ovirt-host-deploy-facts : Reset configuration of advanced virtualization module] *** 2021-08-06 19:25:12 MYT - TASK [ovirt-host-deploy-facts : Find relevant advanced virtualization module version] *** 2021-08-06 19:25:12 MYT - TASK [ovirt-host-deploy-facts : Enable advanced virtualization module] ********* 2021-08-06 19:25:12 MYT - TASK [ovirt-host-deploy-facts : Ensure Python3 is installed for CentOS/RHEL8 hosts] *** Thank You.

2 1

fencing and (virtual) power button pression reaction
by Gianluca Cecchi 07 Aug '21

07 Aug '21

Hello, in RHCS we have the fencing concept for targets very similar to the oVirt ones: avoid data corruption and also fast react to problematic hosts situations. The implementation is quite similar to the oVirt one, with several fencing agents sometimes common, like fence_ipmilan. In RHCS documentation there is a chapter describing how to configure hosts so that they don't react to power button pressure. This guarantees that failover is as fast as possible, and also that the same host to be fenced, could create more damages if it reacts and begins the shutdown procedure instead of simply powering off. See: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht… It seems to me that oVirt / RHV lack this feature. Inside oVirt NGN and also RHVH-H, the /etc/systemd/logind.conf file is not configured with an entry of type HandlePowerKey=ignore So in some cases of tests I'm doing, I see in its virtual console that the to-be-fenced host begins its OS shutdown flow when it detects the power button pressure. Typically after 2-3 seconds the system powers off and then on again, but I also saw about 10 seconds delays in one case. I have opened a case (number 03002278) for my RHV products, but I would also like to get your comments here if I'm wrong with my considerations. Gianluca

2 1

Architecture design docs
by Jesse Hu 07 Aug '21

07 Aug '21

Hi there, is there any any architecture design docs for oVirt (Engine & Node & VDSM) for neebee to learn? https://www.ovirt.org/Architecture gives 404. Thanks.

4 5

Re: Install of RHV 4.4 failing - "Host is not up, please check logs, perhaps also on the engine machine"
by Brock Collins 07 Aug '21

07 Aug '21

Needed to add appropriate DNS entry / MAC for the VM It is a 192.168.2.122 typically* Sent from my iPhone

1 0

Data recovery from (now unused, but still mounted) Gluster Volume for a single VM
by David White 06 Aug '21

06 Aug '21

My hyperconverged cluster was running out of space. The reason for that is a good problem to have - I've grown more in the last 4 months than in the past 4-5 years combined. But the downside was, I had to go ahead and upgrade my storage, and it became urgent to do so. I began that process last week. I have 3 volumes: [root@cha2-storage dwhite]# gluster volume list data engine vmstore I did the following on all 3 of my volumes: 1) Converted cluster from Replica 3 to Replica 2, arbiter 1 - I did run into an issue where some VMs were paused, but I was able to poweroff and power on those VMs again with no issue 2) Ran the following on Host 2: # gluster volume remove-brick data replica 1 cha1-storage.mgt.my-domain.com:/gluster_bricks/data/data force # gluster volume remove-brick vmstore replica 1 cha1-storage.mgt.my-domain.com:/gluster_bricks/vmstore/vmstore force # gluster volume remove-brick engine replica 1 cha1-storage.mgt.my-domain.com:/gluster_bricks/engine/engine force (rebuilt the array & reboot the server -- when I rebooted, I commented out the original UUIDs from /etc/fstab for the gluster storage) # lvcreate -L 2157G --zero n -T gluster_vg_sdb/gluster_thinpool_gluster_vg_sdb # lvcreate -L 75G -n gluster_lv_engine gluster_vg_sdb # lvcreate -V 600G --thin -n gluster_lv_data gluster_vg_sdb/gluster_thinpool_gluster_vg_sdb # lvcreate -V 1536G --thin -n gluster_lv_vmstore gluster_vg_sdb/gluster_thinpool_gluster_vg_sdb # mkfs.xfs /dev/gluster_vg_sdb/gluster_lv_engine # mkfs.xfs /dev/gluster_vg_sdb/gluster_lv_data # mkfs.xfs /dev/gluster_vg_sdb/gluster_lv_vmstore At this point, I ran lsblk --fs to get the new UUIDs, and put them into /etc/fstab # mount -a # gluster volume add-brick engine replica 2 cha2-storage.mgt.my-domain.com:/gluster_bricks/engine/engine force # gluster volume add-brick vmstore replica 2 cha2-storage.mgt.my-domain.com:/gluster_bricks/vmstore/vmstore force # gluster volume add-brick data replica 2 cha2-storage.mgt.my-domain.com:/gluster_bricks/data/data force So far so good. 3) I was running critically low on disk space on the replica, so I:- Let the gluster volume heal - Then I removed the Host 1 bricks from the volumes When I removed the Host 1 bricks, I made sure that there were no additional healing tasks, then proceeded to do so:# gluster volume remove-brick data replica 1 cha1-storage.mgt.my-domain.com:/gluster_bricks/data/data force # gluster volume remove-brick vmstore replica 1 cha1-storage.mgt.my-domain.com:/gluster_bricks/vmstore/vmstore force At this point, I ran into problems. All of my VMs went into a Paused state, and I had to reboot all of them. All VMs came back online, but two VMs were corrupted. I wound up re-building them from scratch. Unfortunately, we lost a lot of data on 1 of the VMs, as I didn't realize backups were broken on that particular VM. Is there a way for me to go into those disks (that are still mounted to Host 1), examine the Gluster content, and somehow mount / recover the data from the VM that we lost? Sent with ProtonMail Secure Email.

4 9

non-critical request - Disk volume label - Web-ui
by Jorge Visentini 06 Aug '21

06 Aug '21

Hi everyone! Firstly, congratulations for the evolution of the oVirt 4.4.7. A *non-critical* request for a future version... if possible, add a label in disk volumes, in Web-ui. Thank you all! [image: image.png] -- Att, Jorge Visentini +55 55 98432-9868

1 0

Wondering a way to create a universal USB Live OS to connect to VM Portal
by eta.entropy＠gmail.com 06 Aug '21

06 Aug '21

Hi All, once oVirt Infrastracture has been setup, VMs created, assigned to users and they manage them through VM Portal, I'm wondering if there is an easy way to provide to end users a USB key that will just > plug into any computer or boot from it > connect to given VM Portal to manage assigned VMs > connect to given SPICE console to enter assigned VMs Just like a Linux Live USB with preconfigured service to be started and to connect to VM Portal or SPICE console Is there something already available to start from ? Is this something doable or am I dreaming ? Thanks for any input

1 0

Question about PCI storage passthrough for a single guest VM
by Tony Pearce 06 Aug '21

06 Aug '21

I have configured a host with pci passthrough for GPU pass through. Using this knowledge I went ahead and configured nvme SSD pci pass through. On the guest, I partitioned and mounted the SSD without any issues. Searching google for this exact setup I only see results about "local storage" where local storage = using a disk image on the hosts storage. So I have come here to try and find out if there are any concerns or gripes or issues with using nvme pci pass through compared to local storage. Some more detail about the setup: I have 2 identical hosts (nvidia gpu and also nvme pci SSD). A few weeks ago when I started researching converting one of these systems over (from native ubuntu) to ovirt using gpu pci pass through I found the information about local storage. I have 1 host (host #1) set up with local storage mode and the guest VM is using a disk image on this local storage. Host 2 has an identical hardware setup but I did not configure local storage for this host. Instead, I have the ovirt host OS installed on a SATA HDD and the nvme SSD is in pci pass through to a different guest instance. What I notice is Host 2 disk performance is approx. +30% increase over host #1 when running simple dd tests to write data to the disk. So at first glance it appears the nvme pci pass through gives better performance and this is desired, but I have not seen any ovirt documentation that explains that this is supported or any guidelines on configuring such a setup. Aside from the usual caveats when running pci pass through, are there any other gotchya's when running this type of setup (pci nvme ssd pass through)? I am trying to discover any unknowns about this before I use this for real data. I have no previous experience with this and this is my main reason for emailing the group. Any insight appreciated. Kind regards, Tony Pearce

2 3

glance.ovirt.org planned outage: 10.08.2021 at 01:00 UTC
by Evgheni Dereveanchin 06 Aug '21

06 Aug '21

Hi everyone, There's an outage scheduled in order to move glance.ovirt.org to new hardware. This will happen after midnight the upcoming Tuesday between 1AM and 3AM UTC. It will not be possible to pull images from our Glance image registry during this period. Other services will not be affected. If you see any CI jobs failing on Glance tests - please re-run them in the morning after the planned outage window is over. If issues persist please report it via JIRA or reach out to me personally. -- Regards, Evgheni Dereveanchin

1 0

[ANN] oVirt 4.4.8 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 06 Aug '21

06 Aug '21

oVirt 4.4.8 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.8 Fourth Release Candidate for testing, as of August 6th, 2021. This update is the eighth in a series of stabilization updates to the 4.4 series. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.8 release highlights: http://www.ovirt.org/release/4.4.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.4.8/ [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.*

1 0