- Users - oVirt List Archives

Unassigned hosts
by Nardus Geldenhuys 07 Aug '20

07 Aug '20

Hi oVirt land Hope you are well. Got a bit of an issue, actually a big issue. We had some sort of dip of some sort. All the VM's is still running, but some of the hosts is show "Unassigned" or "NonResponsive". So all the hosts was showing UP and was fine before our dip. So I did increase vdsHeartbeatInSecond to 240, no luck. I still get a timeout on the engine lock even thou I can connect to that host from the engine using nc to test to port 54321. I also did restart vdsmd and also rebooted the host with no luck. nc -v someserver 54321 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.40.2.172:54321. 2020-08-05 20:20:34,256+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-70) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM someserver command Get Host Capabilities failed: Message timeout which can be caused by communication issues Any troubleshoot ideas will be gladly appreciated. Regards Nar

4 14

Re: [ovirt-devel] Error during deployment of self hosted engine oVirt 4.4
by Michal Skrivanek 07 Aug '20

07 Aug '20

> On 6 Aug 2020, at 00:41, i iordanov <iiordanov(a)gmail.com> wrote: > > Hi Michal, > > I dug down enough to see that I could alter the option that specifies the supported CPUs in the database. What would have helped me is a diff of what was removed. Ultimately, I didn't have enough time to dig for the diff, but if you know where it can be found it may be of use for other people that need to use a Penryn based server. Hi, the diff is right there, the option value for 4.2 cluster still has it. so you just need that piece (penryn definition) to copy&paste into the 4.4 entry(i think the numbers are then duplicated, but it shouldn’t really matter, cpu name is the "key”) Thanks, michal > > I was able to swap two systems at my place and get a Nehalem one to use with oVirt, but if I get a chance I may try to revert to the older one since it's a bit more convenient for me to use. I would certainly try updating the DB if I could get the diff where you guys removed the line from the DB seed files. > > Cheers and thanks! > iordan > > On Tue, Aug 4, 2020 at 4:46 AM Michal Skrivanek <michal.skrivanek(a)redhat.com <mailto:michal.skrivanek@redhat.com>> wrote: > > >> On 4 Aug 2020, at 06:10, i iordanov <iiordanov(a)gmail.com <mailto:iiordanov@gmail.com>> wrote: >> >> It seems the issue stems from cpu type being empty. >> >> 'cpu': {'architecture': 'undefined', 'type': ''} >> >> 2020-08-03 23:31:39,888-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 cluster_facts: {'changed': False, 'ansible_facts': {'ovirt_clusters': [{'href': '/ovirt-engine/api/clusters/0eb77d38-d5fe-11ea-8808-00163e42a94a', 'comment': '', 'description': 'The default server cluster', 'id': '0eb77d38-d5fe-11ea-8808-00163e42a94a', 'name': 'Default', 'affinity_groups': [], 'ballooning_enabled': True, 'bios_type': 'cluster_default', 'cpu': {'architecture': 'undefined', 'type': ''}, 'cpu_profiles': [], 'data_center': {'href': '/ovirt-engine/api/datacenters/0ea3b60e-d5fe-11ea-a87c-00163e42a94a', 'id': '0ea3b60e-d5fe-11ea-a87c-00163e42a94a'}, 'enabled_features': [], 'error_handling': {'on_error': 'migrate'}, 'external_network_providers': [], 'fencing_policy': {'enabled': True, 'skip_if_connectivity_broken': {'enabled': False, 'threshold': 50}, 'skip_if_gluster_bricks_up': False, 'skip_if_gluster_quorum_not_met': False, 'skip_if_sd_active': {'enabled': False}}, 'firewall_type': 'firewalld', 'gluster_hooks': [], 'gluster_service': False, 'gluster_volumes': [], 'ha_reservation': False, 'ksm': {'enabled': True, 'merge_across_nodes': True}, 'log_max_memory_used_threshold': 95, 'log_max_memory_used_threshold_type': 'percentage', 'mac_pool': {'href': '/ovirt-engine/api/macpools/58ca604b-017d-0374-0220-00000000014e', 'id': '58ca604b-017d-0374-0220-00000000014e'}, 'memory_policy': {'over_commit': {'percent': 100}, 'transparent_huge_pages': {'enabled': True}}, 'migration': {'auto_converge': 'inherit', 'bandwidth': {'assignment_method': 'auto'}, 'compressed': 'inherit', 'encrypted': 'inherit', 'policy': {'id': '80554327-0569-496b-bdeb-fcbbf52b827b'}}, 'network_filters': [], 'networks': [], 'permissions': [], 'required_rng_sources': ['urandom'], 'scheduling_policy': {'href': '/ovirt-engine/api/schedulingpolicies/b4ed2332-a7ac-4d5f-9596-99a439cb2812', 'id': 'b4ed2332-a7ac-4d5f-9596-99a439cb2812'}, 'switch_type': 'legacy', 'threads_as_cores': False, 'trusted_service': False, 'tunnel_migration': False, 'version': {'major': 4, 'minor': 4}, 'virt_service': True, 'vnc_encryption': False}]}, 'deprecations': [{'msg': "The 'ovirt_cluster_facts' module has been renamed to 'ovirt_cluster_info', and the renamed one no longer returns ansible_facts", 'version': '2.13'}], 'failed': False} >> >> Perhaps this Penryn series CPU is too old for this oVirt installation... > > Yes, we dropped Penryn from supported CPU list i 4.3. You could probably stil make it run but it would need messing with engine’s db, adding back Nehalem entry to ServerCPUList(e.g. from 4.2 cluster version line) and resume the deployment somehow. > >> >> iordan >> >> On Mon, Aug 3, 2020 at 11:54 PM i iordanov <iiordanov(a)gmail.com <mailto:iiordanov@gmail.com>> wrote: >> Hi guys, >> >> I am trying to install oVirt 4.4 for testing of the aSPICE and Opaque Android clients and tried to follow this slightly outdated doc: >> >> https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engin… <https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engin…> >> >> to deploy an all-in-one self-hosted engine using the command-line. >> >> I started with a clean CentOS 8 installation, set up an NFS server and tested that mounts work from the local host and other hosts, opened all ports with firewalld to my LAN and localhost (but left firewalld enabled). >> >> During the run of >> hosted-engine --deploy >> I got the following error: >> >> 2020-08-03 23:31:51,426-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 TASK [ovirt.hosted_engine_setup : debug] >> 2020-08-03 23:31:51,827-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 server_cpu_dict: {'Intel Nehalem Family': 'Nehalem', 'Secure Intel Nehalem Family': 'Nehalem,+sp >> ec-ctrl,+ssbd,+md-clear', 'Intel Westmere Family': 'Westmere', 'Secure Intel Westmere Family': 'Westmere,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel SandyBridge Family': 'SandyBridge', 'Secure Intel SandyBridge Fa >> mily': 'SandyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel IvyBridge Family': 'IvyBridge', 'Secure Intel IvyBridge Family': 'IvyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel Haswell Family': 'Haswell-noTSX >> ', 'Secure Intel Haswell Family': 'Haswell-noTSX,+spec-ctrl,+ssbd,+md-clear', 'Intel Broadwell Family': 'Broadwell-noTSX', 'Secure Intel Broadwell Family': 'Broadwell-noTSX,+spec-ctrl,+ssbd,+md-clear', 'Intel Sk >> ylake Client Family': 'Skylake-Client,-hle,-rtm', 'Secure Intel Skylake Client Family': 'Skylake-Client,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm', 'Intel Skylake Server Family': 'Skylake-Server,-hle,-rtm', 'Secure I >> ntel Skylake Server Family': 'Skylake-Server,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm', 'Intel Cascadelake Server Family': 'Cascadelake-Server,-hle,-rtm,+arch-capabilities', 'Secure Intel Cascadelake Server Family': >> 'Cascadelake-Server,+md-clear,+mds-no,-hle,-rtm,+tsx-ctrl,+arch-capabilities', 'AMD Opteron G4': 'Opteron_G4', 'AMD Opteron G5': 'Opteron_G5', 'AMD EPYC': 'EPYC', 'Secure AMD EPYC': 'EPYC,+ibpb,+virt-ssbd', 'IB >> M POWER8': 'POWER8', 'IBM POWER9': 'POWER9', 'IBM z114, z196': 'z196-base', 'IBM zBC12, zEC12': 'zEC12-base', 'IBM z13s, z13': 'z13-base', 'IBM z14': 'z14-base'} >> 2020-08-03 23:31:52,128-0400 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 TASK [ovirt.hosted_engine_setup : Convert CPU model name] >> 2020-08-03 23:31:52,530-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {'msg': "The task includes an option with an undefined variable. The error was: 'dict object' ha >> s no attribute ''\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': line 105, column 15, but may\nbe elsewhere in th >> e file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n - debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task >> . Only one syntax may be used.\n", '_ansible_no_log': False} >> 2020-08-03 23:31:52,630-0400 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. >> The error was: 'dict object' has no attribute ''\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': line 105, column >> 15, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n - debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' shortha >> nd syntax and YAML in this task. Only one syntax may be used.\n"} >> 2020-08-03 23:31:52,931-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 PLAY RECAP [localhost] : ok: 35 changed: 5 unreachable: 0 skipped: 5 failed: 1 >> 2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:215 ansible-playbook rc: 2 >> 2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:222 ansible-playbook stdout: >> 2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:225 ansible-playbook stderr: >> 2020-08-03 23:31:53,033-0400 DEBUG otopi.context context._executeMethod:145 method exception >> Traceback (most recent call last): >> File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod >> method['method']() >> File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/target_vm.py", line 238, in _closeup >> r = ah.run() >> File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 229, in run >> raise RuntimeError(_('Failed executing ansible-playbook')) >> RuntimeError: Failed executing ansible-playbook >> 2020-08-03 23:31:53,034-0400 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Failed executing ansible-playbook >> >> On line 105 of the Ansible config file indicated, there is the following task: >> - debug: var=server_cpu_dict >> >> However, here is a bit more of the file: >> - name: Parse server CPU list >> set_fact: >> server_cpu_dict: "{{ server_cpu_dict | combine({item.split(':')[1]: item.split(':')[3]}) }}" >> with_items: >- >> {{ server_cpu_list.json['values']['system_option_value'][0]['value'].split('; ')|list|difference(['']) }} >> - debug: var=server_cpu_dict >> - name: Convert CPU model name >> set_fact: >> cluster_cpu_model: "{{ server_cpu_dict[cluster_cpu.type] }}" >> - debug: var=cluster_cpu_model >> - name: Parse emulated_machine >> set_fact: >> emulated_machine: >> emulated_machine_list.json['values']['system_option_value'][0]['value'].replace( >> '[','').replace(']','').split(', ')|first >> >> Exact version of the package that contains the file in question: >> >> ovirt-ansible-hosted-engine-setup-1.1.7-1.el8.noarch >> >> Many thanks for your attention! Please cc me when you reply, as I may not be monitoring the mailing list actively. Happy to provide any other information. >> >> In case it's relevant, the CPU of the machine: >> >> # cat /proc/cpuinfo >> processor : 0 >> vendor_id : GenuineIntel >> cpu family : 6 >> model : 23 >> model name : Intel(R) Xeon(R) CPU X5460 @ 3.16GHz >> stepping : 6 >> microcode : 0x60f >> cpu MHz : 2703.129 >> cache size : 6144 KB >> physical id : 0 >> siblings : 4 >> core id : 0 >> cpu cores : 4 >> apicid : 0 >> initial apicid : 0 >> fpu : yes >> fpu_exception : yes >> cpuid level : 10 >> wp : yes >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm pti tpr_shadow vnmi flexpriority dtherm >> bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit >> bogomips : 6318.15 >> clflush size : 64 >> cache_alignment : 64 >> address sizes : 38 bits physical, 48 bits virtual >> power management: >> >> Sincerely, >> iordan >> >> -- >> The conscious mind has only one thread of execution. >> >> >> -- >> The conscious mind has only one thread of execution. >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org <mailto:devel@ovirt.org> >> To unsubscribe send an email to devel-leave(a)ovirt.org <mailto:devel-leave@ovirt.org> >> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> >> List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/4CUXHTZTTAW6Y… <https://lists.ovirt.org/archives/list/devel@ovirt.org/message/4CUXHTZTTAW6Y…> > > > -- > The conscious mind has only one thread of execution.

1 0

oVirt 4.4.1 HCI single server deployment failed nested-kvm
by wodel youchi 07 Aug '20

07 Aug '20

Hi, I am using these versions for my test : - ovirt-engine-appliance-4.4-20200723102445.1.el8.x86_64.rpm - ovirt-node-ng-installer-4.4.1-2020072310.el8.iso A single HCI server using nested KVM. The gluster part works now without error, but when I click the hosted-engine deployment button I get : *System data could not be retrieved!* *No valid network interface has been found * * If you are using Bonds or VLANs Use the following naming conventions: * - VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, eth1.128, enp3s0.50) - Bond interfaces: bond*number* (for example, bond0, bond1) - VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50, bond1.128) * Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad * Networking teaming is not supported and will cause errors From this log file I get : cat ovirt-hosted-engine-setup-ansible-get_network_interfaces-xxxxxxxx.log 2020-07-29 15:27:09,246+0100 DEBUG var changed: host "localhost" var "otopi_host_net" type "<class 'list'>" value: "[ "enp1s0", "enp2s0" ]" 2020-07-29 15:27:09,246+0100 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-eng ine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Filter unsupported interface types', 'task_duration ': 0} 2020-07-29 15:27:09,246+0100 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe804bc5940> kwargs 2020-07-29 15:27:09,514+0100 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-ho sted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : debug'} 2020-07-29 15:27:09,515+0100 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : debug kwargs is_conditional:False 2020-07-29 15:27:09,515+0100 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : debug kwargs 2020-07-29 15:27:09,792+0100 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-eng ine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': '', 'task_duration': 0} 2020-07-29 15:27:09,793+0100 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe804cb45f8> kwargs 2020-07-29 15:27:10,059+0100 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-ho sted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Failed if only teaming devices are availible '} 2020-07-29 15:27:10,059+0100 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Failed if only teaming devices are availible kwargs is_conditional:False 2020-07-29 15:27:10,060+0100 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Failed if only teaming devices are a vailible kwargs 2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var "ansible_play_hosts" type "<class 'list'>" value: "[]" 2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var "ansible_play_batch" type "<class 'list'>" value: "[]" 2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var "play_hosts" type "<class 'list'>" value: "[]" 2020-07-29 15:27:10,376+0100 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "msg": "The conditional check *'(otopi_host_net.ansible_facts.otopi_host_net | length == 0)' failed. The error was: error while evaluating conditional ((otopi_host_net.ansible_facts.otopi_host_net | length == 0)): 'list object' has no attribute 'ansible_facts'\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/filter_team_devices.yml': line 29, column 13, * but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n- debug: var=otopi_ho st_net\n ^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task. Only one syntax may be used.\n" }, "ansible_task": "Failed if only teaming devices are availible", "ansible_type": "task", "status": "FAILED", "task_duration": 0 } 2020-07-29 15:27:10,377+0100 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe804c175c0> kwargs ignor e_errors:None 2020-07-29 15:27:10,378+0100 INFO ansible stats { "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_playbook_duration": "00:15 Minutes", "ansible_result": "type: <class 'dict'>\nstr: {'localhost': {'ok': 16, 'failures': 1, 'unreachable': 0, 'changed': 1, 'skipped': 2 , 'rescued': 0, 'ignored': 0}}", "ansible_type": "finish", "status": "FAILED" } 2020-07-29 15:27:10,378+0100 INFO SUMMARY: Duration Task Name -------- -------- [ < 1 sec ] Execute just a specific set of steps [ 00:02 ] Force facts gathering [ 00:01 ] Get all active network interfaces [ < 1 sec ] Filter bonds with bad naming [ < 1 sec ] Generate output list [ 00:01 ] Collect interface types [ < 1 sec ] Get list of Team devices [ < 1 sec ] Filter unsupported interface types [ FAILED ] Failed if only teaming devices are availible 2020-07-29 15:27:10,378+0100 DEBUG ansible on_any args <ansible.executor.stats.AggregateStats object at 0x7fe8074bce80> kwargs Regards.

6 8

Setting Up oVirt + NFS Storage Issues
by Arden Shackelford 07 Aug '20

07 Aug '20

Hello! Been looking to get setup with oVirt for a few weeks and had a chance the past week or so to attempt getting it all setup. Ended up doing a bit of troubleshooting but finally got to the point where the Cockpit setup prompts for me setting up the storage piece, for which I've opted for NFS (path of least resistance for now). However, I constantly run into this issue (pulled from the administration portal events page): VDSM asgard.shackfam.net command CreateStorageDomainVDS failed: Could not initialize cluster lock: () This specifically shows up in the following task for the Ansible piece: [ovirt.hosted_engine_setup : Add NFS storage domain] When I browse the NFS share, I do see a file structure being created, which kind of confuses me based on the error provide in the Administration portal. Any suggestions on what would be best steps forward at this point? For reference, here's my setup: 1x oVirt Node 1x NFS server (storage01: NFS shares mainly managed by ZFS)

3 5

4.2.8 and yum update
by carl langlois 06 Aug '20

06 Aug '20

Hi all, I am in the process of upgrading our cluster to 4.3. But first i need to update everything to 4.2.8 and update the os to the latest 7.x. I was able to update the self-hosted engine to the latest 4.2.8 and centos 7.8. But when i tried to update the host yum update got broken gluster packages. The current host that i'm trying to update is on 7.5. If i look at the release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve this. Any suggestions?. Carl

2 6

[ANN] oVirt 4.4.2 Second Release Candidate is now available for testing
by Lev Veyde 06 Aug '20

06 Aug '20

oVirt 4.4.2 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.2 Second Release Candidate for testing, as of August 6th, 2020. This update is the second in a series of stabilization updates to the 4.4 series. 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 the engine: either use appliance or: - Install CentOS Linux 8.2 minimal from: https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8.2 from https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to the engine and let it be deployed. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (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 for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.2 release highlights: http://www.ovirt.org/release/4.4.2/ * 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.2/ [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

Re: VDSM can't see StoragePool
by Nardus Geldenhuys 06 Aug '20

06 Aug '20

Hi Hope you are well. Did you find a solution for this? Think we have the same type of issue. Regards Nar

1 0

useful workaround for catch-22 situation with nic drivers and Windows
by i iordanov 06 Aug '20

06 Aug '20

Hello, I just wanted to post a nice workaround I came up with in case it helps anybody. The reason I needed it is that in oVirt 4.4, it appears I am unable to change the nic1 type when creating VMs (maybe that's a bug?) and I necessarily end up with the default nic1 type which needs a virtio driver in Windows which is obviously not present on a clean install. Also, since there is no networking, it can't be downloaded. I did think of mounting a USB stick via remote-viewer, but something is wonky there too - the USB device selection menu item is grayed out, and no, it's not permissions. So what i did was to create an .iso file with spice-guest-tools-latest.exe in it and copy the resulting iso file to the ISO domain. Then, I was easily able to attach the ISO to the Windows machine in question and install spice-guest-tools, which made the network adapter work. Quick snippet of how I created the .iso: $ find test test test/spice-guest-tools-latest.exe $ mkisofs -o spice-tools.iso test I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 0 Total directory bytes: 116 Path table size(bytes): 10 Max brk space used 0 5124 extents written (10 MB) Hope it helps somebody :). Cheers! iordan -- The conscious mind has only one thread of execution.

2 1

Resize partition cause oVirt installation failed
by hkexdong＠yahoo.com.hk 06 Aug '20

06 Aug '20

I've 2 x 512GB SSD. Purely for oVirt 4.4.1 (CentOS 8.2) installation. Using auto partitioning will assign 800+ GB to root partition. I think that's too much so manually reduce it to 80 GB. As there are 2 disks. I want to form RAID too. So, I manually change all the partitions from "LVM thin provisioning" to "RAID" (with RAID 1). Eventually, cause the installation failed with a message "There was an error running the kickstart script at line ....." If I don't make any change to the partitions. The installation success. Is this a known issue? oVirt not allow resize partition and using Linux software RAID?

4 5

General Design question for oVirt set up between locations
by Holger Petrick 05 Aug '20

05 Aug '20

Hello, I'm looking to deploy oVirt for a company which has locations in different countries. As I know and also set up in my test environment, the oVirt Engine is the central place to manage different Data Center in a central place. But how to manage a location when the network connection between a Data Center and oVirt Engine is down? Is it possible to set up on each location a hosted engine and connect also the "local" engine / hosts to a "Central" Engine? What is the recommendation to deploy oVirt on multiple location? Thank you. Holger

2 2

Semi off-topic: invalid SPF record for ovirt.org
by Chris Adams 05 Aug '20

05 Aug '20

Not sure where to send this (so sending to the list); the ovirt.org SPF record is invalid: $ dig ovirt.org txt +short "v=spf1 a:mail.ovirt.org a:gerrit.ovirt.org 66.187.233.88 ~all" The bare IP address needs to be "ip4:66.187.233.88" instead. -- Chris Adams <cma(a)cmadams.net>

2 1

Subject: [ANN] Updated oVirt release 4.4.1.5
by Lev Veyde 05 Aug '20

05 Aug '20

The oVirt Team has just released a new version of oVirt Node package that fixes oVirt Hyperconverged deployment related issue: Bug 1862588 <https://bugzilla.redhat.com/show_bug.cgi?id=1862588> - Update to gluster-7.7 with ovirt-ng node 4.4.1 Updated ovirt-node-ng-installer had been built and a new torrent for this ISO is now available at https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4.1… Relevant changes compared to previous version: - Gluster 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/ - Ansible 2.9.11: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Boot Hole vulnerability in grub2 (CVE-2020-1073) fix: https://blog.centos.org/2020/08/centos-community-newsletter-august-2020-200… -- 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 start vms in a specific host
by miguel.garcia＠toshibagcs.com 04 Aug '20

04 Aug '20

I had added a couple new hosts in my cluster (hyp16,hyp17) both followed the same procedure but at the moment to start vms all of them goes to hyp16, if I tried to migrate a vm to hyp 17 the migration task fails. Here is the log trying to do migration: 2020-07-22 17:19:12,352-04 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] Running command: MigrateVmToServerCommand internal: false. Entities affected : ID: 24939bc1-5359-4f9d-b742-b32143c02eb1 Type: VMAction group MIGRATE_VM with role type USER 2020-07-22 17:19:12,421-04 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId='15466e1a-1f44-472c-94fc-84b132ff1c7d', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1', srcHost='172.16.99.12', dstVdsId='3663f46b-61db-4b4c-a6c0-03fedc90edf0', dstHost='172.16.99.19:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth='625', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=ab ort, params=[]}}]]', dstQemu='172.16.99.19'}), log id: 4f624ae2 2020-07-22 17:19:12,423-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] START, MigrateBrokerVDSCommand(HostName = hyp10.infra, MigrateVDSCommandParameters:{hostId='15466e1a-1f44-472c-94fc-84b132ff1c7d', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1', srcHost='172.16.99.12', dstVdsId='3663f46b-61db-4b4c-a6c0-03fedc90edf0', dstHost='172.16.99.19:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth='625', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntim e, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='172.16.99.19'}), log id: 7ead484c 2020-07-22 17:19:12,587-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] FINISH, MigrateBrokerVDSCommand, return: , log id: 7ead484c 2020-07-22 17:19:12,589-04 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 4f624ae2 2020-07-22 17:19:12,597-04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] EVENT_ID: VM_MIGRATION_START(62), Migration started (VM: Test, Source: hyp10.infra, Destination: hyp17.infra, User: Miguel.Garcia@). 2020-07-22 17:19:14,050-04 INFO [org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet] (default task-2378) [] User antonio.acosta@ successfully logged out 2020-07-22 17:19:14,069-04 INFO [org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand] (default task-2380) [27d07a90] Running command: TerminateSessionsForTokenCommand internal: true. 2020-07-22 17:19:14,405-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-12) [] VM '24939bc1-5359-4f9d-b742-b32143c02eb1' was reported as Down on VDS '3663f46b-61db-4b4c-a6c0-03fedc90edf0'(hyp17.infra) 2020-07-22 17:19:14,406-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-12) [] START, DestroyVDSCommand(HostName = hyp17.infra, DestroyVmVDSCommandParameters:{hostId='3663f46b-61db-4b4c-a6c0-03fedc90edf0', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 7d54e8da 2020-07-22 17:19:14,823-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-12) [] Failed to destroy VM '24939bc1-5359-4f9d-b742-b32143c02eb1' because VM does not exist, ignoring 2020-07-22 17:19:14,823-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-12) [] FINISH, DestroyVDSCommand, return: , log id: 7d54e8da 2020-07-22 17:19:14,824-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-12) [] VM '24939bc1-5359-4f9d-b742-b32143c02eb1'(Test) was unexpectedly detected as 'Down' on VDS '3663f46b-61db-4b4c-a6c0-03fedc90edf0'(hyp17.infra) (expected on '15466e1a-1f44-472c-94fc-84b132ff1c7d') 2020-07-22 17:19:14,824-04 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-12) [] Migration of VM 'Test' to host 'hyp17.infra' failed: VM destroyed during the startup. 2020-07-22 17:19:14,824-04 WARN [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-3) [] skipping VM '24939bc1-5359-4f9d-b742-b32143c02eb1' from this monitoring cycle - the VM data has changed since fetching the data 2020-07-22 17:19:17,224-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [] VM '24939bc1-5359-4f9d-b742-b32143c02eb1'(Test) moved from 'MigratingFrom' --> 'Up' 2020-07-22 17:19:17,224-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [] Adding VM '24939bc1-5359-4f9d-b742-b32143c02eb1'(Test) to re-run list 2020-07-22 17:19:17,229-04 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [] Rerun VM '24939bc1-5359-4f9d-b742-b32143c02eb1'. Called from VDS 'hyp10.infra' 2020-07-22 17:19:17,310-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-12994) [] START, MigrateStatusVDSCommand(HostName = hyp10.infra, MigrateStatusVDSCommandParameters:{hostId='15466e1a-1f44-472c-94fc-84b132ff1c7d', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1'}), log id: 74cf526d 2020-07-22 17:19:17,533-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-12994) [] FINISH, MigrateStatusVDSCommand, return: , log id: 74cf526d 2020-07-22 17:19:17,587-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-12994) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed (VM: Test, Source: hyp10.infra, Destination: hyp17.infra). 2020-07-22 17:19:17,591-04 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (EE-ManagedThreadFactory-engine-Thread-12994) [] Lock freed to object 'EngineLock:{exclusiveLocks='[24939bc1-5359-4f9d-b742-b32143c02eb1=VM]', sharedLocks=''}'

2 2

4.4rc issue with attaching logical network to ib0
by Edward Berger 04 Aug '20

04 Aug '20

I'm trying to add a logical network to an omnipath (which appears as an infinband ib0 under centos kernel driver) and the attempt errors out, under 4.4RC. This used to work under 4.3 on the same hardware. 'Unexpected failure of libnm when running the mainloop: run execution'}, code = -32603 I want to use ib0 for network file systems and VM migrations.

2 3

Windows TimeZone UTC
by Erez Zarum 04 Aug '20

04 Aug '20

The Engine has the TimeZone types compiled, this may be an issue when one wants to configure a Windows Machine to use UTC as a Timezone instead of GMT. Using GMT sets the Windows VM to "London, Dublin" time which may cause issues with daylight saving for some users. There should be an option to supply our own Timezone or the least, make sure it is indeed coordinated with what Windows supports.

4 8

error importing from VMware, and workaround
by Philip Brown 04 Aug '20

04 Aug '20

more details in my saga of problem imports from VMware/vsphere to ovirt (4.4.1 node) I had done a couple successfully, but my next one kept failing. Couldnt figure out why. The only things resembling an error in the import logs, were this: (trimmed a bit) "rpm -e vmware-tools-nox vmware-tools-common" { "message": "libguestfs error: command: error: Failed dependencies:\n\tvmware-tools-nox = 8.3.19 is needed by (installed) vmware-tools-8.3.19-1310361.el6.x86_64", "timestamp": "2020-08-02T21:28:08.797433658+00:00", "type": "error" } I thought to myself.. nah, that couldnt be it. import failed.. because you couldnt REMOVE a package??? that would be dumb. but that was the problem. I started up the old vm, did a yum remove 'vmware-*' reexported from VMware, and then imported... and this time, the import worked. Please fix that behaviour. -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

3 2

oVirt 4.4 Self-Hosted Installation failed
by enmanuelmoreira＠gmail.com 04 Aug '20

04 Aug '20

Hi There! I'm trying to install oVirt self-hosted on Fedora 32 with kvm and the install failed. I got the following message on ovirt console: Host localhost installation failed. Failed to execute Ansible host-deploy role: failed. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20200727183159-localhost-5de7c489.log. and the log content: [root@localhost ~]# tail -100 /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20200727183159-localhost-5de7c489.log "end" : "2020-07-27 18:35:18.688022", "delta" : "0:00:00.190619", "changed" : true, "invocation" : { "module_args" : { "_raw_params" : "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.oqj_hat2qemu'\n", "warn" : true, "_uses_shell" : false, "stdin_add_newline" : true, "strip_empty_ends" : true, "argv" : null, "chdir" : null, "executable" : null, "creates" : null, "removes" : null, "stdin" : null } }, "stdout_lines" : [ "-----BEGIN CERTIFICATE REQUEST-----", "MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++", "QCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb", "b1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ", "QVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X", "XeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7", "h2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6", "WDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h", "n27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq", "FsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730", "iXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7", "0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx", "btRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j", "rXgOHdj+ve1g", "-----END CERTIFICATE REQUEST-----" ], "stderr_lines" : [ "Generating a RSA private key", "....................................................................................................................................................+++++", ".....................................+++++", "writing new private key to '/tmp/ansible.oqj_hat2qemu'", "-----" ], "_ansible_no_log" : false, "failed" : false, "item" : { "changed" : true, "path" : "/tmp/ansible.oqj_hat2qemu", "uid" : 0, "gid" : 0, "owner" : "root", "group" : "root", "mode" : "0600", "state" : "file", "secontext" : "unconfined_u:object_r:user_tmp_t:s0", "size" : 0, "invocation" : { "module_args" : { "state" : "file", "suffix" : "qemu", "prefix" : "ansible.", "path" : null } }, "failed" : false, "item" : { "suffix" : "qemu", "pending_file" : "libvirt-migrate/server-key.pending.pem", "req_dir" : "requests-qemu" }, "ansible_loop_var" : "item" }, "ansible_loop_var" : "item", "_ansible_item_label" : { "changed" : true, "path" : "/tmp/ansible.oqj_hat2qemu", "uid" : 0, "gid" : 0, "owner" : "root", "group" : "root", "mode" : "0600", "state" : "file", "secontext" : "unconfined_u:object_r:user_tmp_t:s0", "size" : 0, "invocation" : { "module_args" : { "state" : "file", "suffix" : "qemu", "prefix" : "ansible.", "path" : null } }, "failed" : false, "item" : { "suffix" : "qemu", "pending_file" : "libvirt-migrate/server-key.pending.pem", "req_dir" : "requests-qemu" }, "ansible_loop_var" : "item" } } ], "changed" : true, "msg" : "All items completed" }, "start" : "2020-07-27T18:35:18.064749", "end" : "2020-07-27T18:35:18.714265", "duration" : 0.649516, "event_loop" : null, "uuid" : "ce9afcb5-6c75-44a8-a640-5152a8605b52" } } } 2020-07-27 18:35:20 UTC - TASK [ovirt-host-deploy-vdsm-certificates : Copy vdsm and QEMU CSRs] *********** 2020-07-27 18:35:20 UTC - 2020-07-27 18:35:20 UTC - [WARNING]: The loop variable 'item' is already in use. You should set the `loop_var` value in the `loop_control` option for the task to something else to avoid variable collisions and unexpected behavior. 2020-07-27 18:35:20 UTC - failed: [localhost] (item={'cmd': ['/usr/bin/openssl', 'req', '-new', '-newkey', 'rsa:2048', '-nodes', '-subj', '/', '-keyout', '/tmp/ansible.sksg5y_jvdsm'], 'stdout': '-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1\nIRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat\nJcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO\n/i0/xn0BO+kizB7SPMt3uyLJKAOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11\nH1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6\npBnl7rI0P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0\n0FBpOR5ANVOMselvFC0CAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq\nKH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs\n955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM\nVppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q\nKqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY\nHIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCV tLq1slpCHEH9T8++RdX/9Gn8\nyU7Y/+iqZ/Us\n-----END CERTIFICATE REQUEST-----', 'stderr': "Generating a RSA private key\n......+++++\n.............................+++++\nwriting new private key to '/tmp/ansible.sksg5y_jvdsm'\n-----", 'rc': 0, 'start': '2020-07-27 18:35:18.270606', 'end': '2020-07-27 18:35:18.314757', 'delta': '0:00:00.044151', 'changed': True, 'invocation': {'module_args': {'_raw_params': "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.sksg5y_jvdsm'\n", 'warn': True, '_uses_shell': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': ['-----BEGIN CERTIFICATE REQUEST-----', 'MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1', 'IRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat', 'JcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO', '/i0/xn0BO+kizB7S PMt3uyLJKAOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11', 'H1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6', 'pBnl7rI0P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0', '0FBpOR5ANVOMselvFC0CAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq', 'KH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs', '955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM', 'Vppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q', 'KqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY', 'HIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCVtLq1slpCHEH9T8++RdX/9Gn8', 'yU7Y/+iqZ/Us', '-----END CERTIFICATE REQUEST-----'], 'stderr_lines': ['Generating a RSA private key', '......+++++', '.............................+++++', "writing new private key to '/tmp/ansible.sksg5y_jvdsm'", '-----'], 'failed': False, 'item': {'changed': True, 'path': '/tmp/ansible.sksg5y_jvdsm', 'uid': 0, 'gid': 0, 'owner': 'root', 'group': 'root', 'mode': '0600', 'state': 'file', 'secontext' : 'unconfined_u:object_r:user_tmp_t:s0', 'size': 0, 'invocation': {'module_args': {'state': 'file', 'suffix': 'vdsm', 'prefix': 'ansible.', 'path': None}}, 'failed': False, 'item': {'suffix': 'vdsm', 'pending_file': 'keys/vdsmkey.pending.pem', 'req_dir': 'requests'}, 'ansible_loop_var': 'item'}, 'ansible_loop_var': 'item'}) => {"ansible_loop_var": "item", "item": {"ansible_loop_var": "item", "changed": true, "cmd": ["/usr/bin/openssl", "req", "-new", "-newkey", "rsa:2048", "-nodes", "-subj", "/", "-keyout", "/tmp/ansible.sksg5y_jvdsm"], "delta": "0:00:00.044151", "end": "2020-07-27 18:35:18.314757", "failed": false, "invocation": {"module_args": {"_raw_params": "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.sksg5y_jvdsm'\n", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": true}}, "item": {"an sible_loop_var": "item", "changed": true, "failed": false, "gid": 0, "group": "root", "invocation": {"module_args": {"path": null, "prefix": "ansible.", "state": "file", "suffix": "vdsm"}}, "item": {"pending_file": "keys/vdsmkey.pending.pem", "req_dir": "requests", "suffix": "vdsm"}, "mode": "0600", "owner": "root", "path": "/tmp/ansible.sksg5y_jvdsm", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 0, "state": "file", "uid": 0}, "rc": 0, "start": "2020-07-27 18:35:18.270606", "stderr": "Generating a RSA private key\n......+++++\n.............................+++++\nwriting new private key to '/tmp/ansible.sksg5y_jvdsm'\n-----", "stderr_lines": ["Generating a RSA private key", "......+++++", ".............................+++++", "writing new private key to '/tmp/ansible.sksg5y_jvdsm'", "-----"], "stdout": "-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1\nIRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat\ nJcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO\n/i0/xn0BO+kizB7SPMt3uyLJKAOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11\nH1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6\npBnl7rI0P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0\n0FBpOR5ANVOMselvFC0CAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq\nKH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs\n955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM\nVppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q\nKqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY\nHIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCVtLq1slpCHEH9T8++RdX/9Gn8\nyU7Y/+iqZ/Us\n-----END CERTIFICATE REQUEST-----", "stdout_lines": ["-----BEGIN CERTIFICATE REQUEST-----", "MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1", "IRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat", "JcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO", "/i0/xn0BO+kizB7SPMt3uyLJK AOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11", "H1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6", "pBnl7rI0P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0", "0FBpOR5ANVOMselvFC0CAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq", "KH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs", "955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM", "Vppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q", "KqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY", "HIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCVtLq1slpCHEH9T8++RdX/9Gn8", "yU7Y/+iqZ/Us", "-----END CERTIFICATE REQUEST-----"]}, "msg": "Failed to connect to the host via ssh: ovirt@localhost: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable": true} 2020-07-27 18:35:20 UTC - failed: [localhost] (item={'cmd': ['/usr/bin/openssl', 'req', '-new', '-newkey', 'rsa:2048', '-nodes', '-subj', '/', '-keyout', '/tmp/ansible.oqj_hat2qemu'], 'stdout': '-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++\nQCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb\nb1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ\nQVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X\nXeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7\nh2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6\nWDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h\nn27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq\nFsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730\niXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7\n0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx\nbtRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0 xdyfXU/9wFIhf3oFK3Slbo3j\nrXgOHdj+ve1g\n-----END CERTIFICATE REQUEST-----', 'stderr': "Generating a RSA private key\n....................................................................................................................................................+++++\n.....................................+++++\nwriting new private key to '/tmp/ansible.oqj_hat2qemu'\n-----", 'rc': 0, 'start': '2020-07-27 18:35:18.497403', 'end': '2020-07-27 18:35:18.688022', 'delta': '0:00:00.190619', 'changed': True, 'invocation': {'module_args': {'_raw_params': "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.oqj_hat2qemu'\n", 'warn': True, '_uses_shell': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': ['-----BEGIN CERTIFICATE REQUEST-----', 'MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++', 'QC G8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb', 'b1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ', 'QVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X', 'XeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7', 'h2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6', 'WDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h', 'n27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq', 'FsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730', 'iXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7', '0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx', 'btRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j', 'rXgOHdj+ve1g', '-----END CERTIFICATE REQUEST-----'], 'stderr_lines': ['Generating a RSA private key', '.................................................................................................................................................... +++++', '.....................................+++++', "writing new private key to '/tmp/ansible.oqj_hat2qemu'", '-----'], 'failed': False, 'item': {'changed': True, 'path': '/tmp/ansible.oqj_hat2qemu', 'uid': 0, 'gid': 0, 'owner': 'root', 'group': 'root', 'mode': '0600', 'state': 'file', 'secontext': 'unconfined_u:object_r:user_tmp_t:s0', 'size': 0, 'invocation': {'module_args': {'state': 'file', 'suffix': 'qemu', 'prefix': 'ansible.', 'path': None}}, 'failed': False, 'item': {'suffix': 'qemu', 'pending_file': 'libvirt-migrate/server-key.pending.pem', 'req_dir': 'requests-qemu'}, 'ansible_loop_var': 'item'}, 'ansible_loop_var': 'item'}) => {"ansible_loop_var": "item", "item": {"ansible_loop_var": "item", "changed": true, "cmd": ["/usr/bin/openssl", "req", "-new", "-newkey", "rsa:2048", "-nodes", "-subj", "/", "-keyout", "/tmp/ansible.oqj_hat2qemu"], "delta": "0:00:00.190619", "end": "2020-07-27 18:35:18.688022", "failed": false, "invocation": {"module_args": {"_raw_params": "'/usr/b in/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.oqj_hat2qemu'\n", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": true}}, "item": {"ansible_loop_var": "item", "changed": true, "failed": false, "gid": 0, "group": "root", "invocation": {"module_args": {"path": null, "prefix": "ansible.", "state": "file", "suffix": "qemu"}}, "item": {"pending_file": "libvirt-migrate/server-key.pending.pem", "req_dir": "requests-qemu", "suffix": "qemu"}, "mode": "0600", "owner": "root", "path": "/tmp/ansible.oqj_hat2qemu", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 0, "state": "file", "uid": 0}, "rc": 0, "start": "2020-07-27 18:35:18.497403", "stderr": "Generating a RSA private key\n............................................................................................................................ ........................+++++\n.....................................+++++\nwriting new private key to '/tmp/ansible.oqj_hat2qemu'\n-----", "stderr_lines": ["Generating a RSA private key", "....................................................................................................................................................+++++", ".....................................+++++", "writing new private key to '/tmp/ansible.oqj_hat2qemu'", "-----"], "stdout": "-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++\nQCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb\nb1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ\nQVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X\nXeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7\nh2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6\nWDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h\nn27hRFQ5n2hwRpLrbnD/KIkicNR9 sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq\nFsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730\niXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7\n0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx\nbtRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j\nrXgOHdj+ve1g\n-----END CERTIFICATE REQUEST-----", "stdout_lines": ["-----BEGIN CERTIFICATE REQUEST-----", "MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++", "QCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb", "b1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ", "QVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X", "XeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7", "h2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6", "WDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h", "n27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq", "FsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCb tpUIo/dERzHMsVS5O730", "iXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7", "0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx", "btRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j", "rXgOHdj+ve1g", "-----END CERTIFICATE REQUEST-----"]}, "msg": "Failed to connect to the host via ssh: ovirt@localhost: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable": true} 2020-07-27 18:35:20 UTC - fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "All items completed", "results": [{"ansible_loop_var": "item", "item": {"ansible_loop_var": "item", "changed": true, "cmd": ["/usr/bin/openssl", "req", "-new", "-newkey", "rsa:2048", "-nodes", "-subj", "/", "-keyout", "/tmp/ansible.sksg5y_jvdsm"], "delta": "0:00:00.044151", "end": "2020-07-27 18:35:18.314757", "failed": false, "invocation": {"module_args": {"_raw_params": "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.sksg5y_jvdsm'\n", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": true}}, "item": {"ansible_loop_var": "item", "changed": true, "failed": false, "gid": 0, "group": "root", "invocation": {"module_args": {"path": null, "prefix": "ansible.", "state": "file", "suffix": "vdsm"}}, "item": {"pending _file": "keys/vdsmkey.pending.pem", "req_dir": "requests", "suffix": "vdsm"}, "mode": "0600", "owner": "root", "path": "/tmp/ansible.sksg5y_jvdsm", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 0, "state": "file", "uid": 0}, "rc": 0, "start": "2020-07-27 18:35:18.270606", "stderr": "Generating a RSA private key\n......+++++\n.............................+++++\nwriting new private key to '/tmp/ansible.sksg5y_jvdsm'\n-----", "stderr_lines": ["Generating a RSA private key", "......+++++", ".............................+++++", "writing new private key to '/tmp/ansible.sksg5y_jvdsm'", "-----"], "stdout": "-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1\nIRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat\nJcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO\n/i0/xn0BO+kizB7SPMt3uyLJKAOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11\nH1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6\npBnl7rI0 P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0\n0FBpOR5ANVOMselvFC0CAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq\nKH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs\n955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM\nVppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q\nKqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY\nHIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCVtLq1slpCHEH9T8++RdX/9Gn8\nyU7Y/+iqZ/Us\n-----END CERTIFICATE REQUEST-----", "stdout_lines": ["-----BEGIN CERTIFICATE REQUEST-----", "MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1", "IRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat", "JcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO", "/i0/xn0BO+kizB7SPMt3uyLJKAOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11", "H1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6", "pBnl7rI0P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0", "0FBpOR5ANVOMselvFC0CAwEAAaAA MA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq", "KH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs", "955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM", "Vppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q", "KqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY", "HIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCVtLq1slpCHEH9T8++RdX/9Gn8", "yU7Y/+iqZ/Us", "-----END CERTIFICATE REQUEST-----"]}, "msg": "Failed to connect to the host via ssh: ovirt@localhost: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable": true}, {"ansible_loop_var": "item", "item": {"ansible_loop_var": "item", "changed": true, "cmd": ["/usr/bin/openssl", "req", "-new", "-newkey", "rsa:2048", "-nodes", "-subj", "/", "-keyout", "/tmp/ansible.oqj_hat2qemu"], "delta": "0:00:00.190619", "end": "2020-07-27 18:35:18.688022", "failed": false, "invocation": {"module_args": {"_raw_params": "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-node s'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.oqj_hat2qemu'\n", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": true}}, "item": {"ansible_loop_var": "item", "changed": true, "failed": false, "gid": 0, "group": "root", "invocation": {"module_args": {"path": null, "prefix": "ansible.", "state": "file", "suffix": "qemu"}}, "item": {"pending_file": "libvirt-migrate/server-key.pending.pem", "req_dir": "requests-qemu", "suffix": "qemu"}, "mode": "0600", "owner": "root", "path": "/tmp/ansible.oqj_hat2qemu", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 0, "state": "file", "uid": 0}, "rc": 0, "start": "2020-07-27 18:35:18.497403", "stderr": "Generating a RSA private key\n....................................................................................................................................................+++++\n.......................... ...........+++++\nwriting new private key to '/tmp/ansible.oqj_hat2qemu'\n-----", "stderr_lines": ["Generating a RSA private key", "....................................................................................................................................................+++++", ".....................................+++++", "writing new private key to '/tmp/ansible.oqj_hat2qemu'", "-----"], "stdout": "-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++\nQCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb\nb1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ\nQVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X\nXeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7\nh2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6\nWDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h\nn27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq\nFsN6gVI/RQY7BTmgP5c hThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730\niXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7\n0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx\nbtRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j\nrXgOHdj+ve1g\n-----END CERTIFICATE REQUEST-----", "stdout_lines": ["-----BEGIN CERTIFICATE REQUEST-----", "MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++", "QCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb", "b1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ", "QVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X", "XeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7", "h2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6", "WDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h", "n27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq", "FsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730", "iXjFERxAObnrzllohpahc42+dwxPrd4ZM FrRmA5m55/nN9VgCudHTo8Uzrv+iaN7", "0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx", "btRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j", "rXgOHdj+ve1g", "-----END CERTIFICATE REQUEST-----"]}, "msg": "Failed to connect to the host via ssh: ovirt@localhost: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable": true}]} 2020-07-27 18:35:20 UTC - PLAY RECAP ********************************************************************* localhost : ok=28 ch I want to install the host and the engine in the same VM (I did before with oVirt 4.3 but it doesn't work anymore) Could you help me please? Cheers.

3 5

where is error log for OVA import
by Philip Brown 01 Aug '20

01 Aug '20

I just tried to import an OVA file. The GUI status mentions that things seem to go along fairly happily.. it mentions that it creates a disk for it.... but then eventually just says "failed to import VM xxxxx into datacenter Default" with zero explanation. Isnt there a log file or something I can check, somewhere, to find out what the problem is? -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

4 6

testing ovirt 4.4 as single node VM inside 4.3
by Philip Brown 01 Aug '20

01 Aug '20

I'm having problems importing OVA exports from vmware 4, into ovirt 4.3 I've read that basically, this is a known issue and that ovirt 4.4 improves the import situation greatly. But I'd like to be able to prove it helps us, before comitting to large undertakings. Is it going to be doable to run a single node ovirt cluster as a VM inside another one? Or do I need to run it on bare metal? -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

4 4

Re: Changing FQDN
by Alex K 31 Jul '20

31 Jul '20

On Fri, Jul 31, 2020, 21:00 Alex K <rightkicktech(a)gmail.com> wrote: > > > On Fri, Jul 31, 2020, 18:26 Dominik Holler <dholler(a)redhat.com> wrote: > >> >> >> On Fri, Jul 31, 2020 at 4:00 PM Alex K <rightkicktech(a)gmail.com> wrote: >> >>> >>> >>> On Fri, Jul 31, 2020 at 4:50 PM Dominik Holler <dholler(a)redhat.com> >>> wrote: >>> >>>> >>>> >>>> On Fri, Jul 31, 2020 at 2:44 PM Alex K <rightkicktech(a)gmail.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I am running ovirt 4.2.8 >>>>> I did change ovirt engine FQDN using ovirt-engine-rename tool following >>>>> >>>>> >>>>> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… >>>>> >>>>> Hosts FQDN is also changed and all seem fine apart from OVN connection >>>>> and ImageIO proxy. >>>>> >>>>> About OVN, i just configured OVN and when I test connection I get: >>>>> >>>>> Failed with error Certificate for <new fqdn> doesn't match any of the >>>>> subject alternative names: [old fqdn] and code 5050) >>>>> >>>> >>>> >>>> Can you please replace all occurrences of the old fqdn by the new fqdn >>>> in >>>> /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf >>>> and >>>> systemctl restart ovirt-provider-ovn >>>> and let us know if this solves the problem? >>>> >>> DId it and the same error is reported. >>> Then tried to engine-setup and still same issue. >>> >> >> Can you please check if adjusting both URLs of the ovirt-provider-ovn >> external network provider in oVirt Engine in the >> oVirt Administration Portal -> Administration -> Providers -> >> ovirt-provider-ovn -> Edit >> solves the issue? >> > Forgot to mention that I had already changed that to reflect new fqdn. > Both url and hostname. > I think that the issue lies at the ca subject still referring to previous fqdn. > >> >> >>> >>>> This step is not yet automated by ovirt-engine-rename in oVirt-4.2. , >>>> please find more details in >>>> https://bugzilla.redhat.com/1501798 >>>> <https://bugzilla.redhat.com/show_bug.cgi?id=1501798> >>>> >>>> >>>> >>>> >>>>> >>>>> about Imageio proxy when I test the connection I do get nothing. No >>>>> error at engine.log or at GUI. >>>>> >>>>> Thus it seems that I have to generate/replace new certs. >>>>> Is there a way I can fix this until I switch to 4.3 and eventually to >>>>> 4.4 where it seems that this is handled from the rename tool? >>>>> >>>>> Thanks for any assistance. >>>>> Alex. >>>>> >>>>> _______________________________________________ >>>>> Users mailing list -- users(a)ovirt.org >>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>>> oVirt Code of Conduct: >>>>> https://www.ovirt.org/community/about/community-guidelines/ >>>>> List Archives: >>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/XKOUI5FPDDUY3… >>>>> >>>>

1 0

4.4.x - VLAN-based logical network can't attach to bonds?
by Mark R 31 Jul '20

31 Jul '20

Hello all, New 4.4.1 hosted-engine install. Pre-deploy, the host already had bond0 and its iSCSI interfaces configured. The deploy correctly sets up the ovirtmgmt interface using the bond, and when everything finishes up it's working as expected. However, I then need to create a VLAN-based network and attach to the same bond0 interface. Editing the host networks and dragging the VLAN 102 interface to the bond alongside ovirtmgmt, then clicking "OK" results in a failure every time. The error returned is: VDSM ovirt5.domain.com command HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': 'Unexpected failure of libnm when running the mainloop: run execution'} I can break the bond and apply this an any other VLAN-based network at will, but then it's not possible to add the interface I removed to create the bond again. That may be by design and it's not supposed to be possible to attach an interface and create a bond once you've already assigned logical networks to it. The error there is "Error while executing action HostSetupNetworks: Interface already in use". I'm just putting out feelers to see if this is a known issue that other people are hitting, or are other folks with hosted-engine 4.4.x deploys readily creating that initial bond0 interface and assigning any VLAN-based logical networks they want w/o issue? These same hosts (they still aren't in prod so I rebuild them at will) run 4.3 with no issues and setting up the exact same network configurations works flawlessly, it just becomes an issue on 4.4.1. This host was freshly installed today and has all updates. Thanks, Mark

3 7

Changing FQDN
by Alex K 31 Jul '20

31 Jul '20

Hi all, I am running ovirt 4.2.8 I did change ovirt engine FQDN using ovirt-engine-rename tool following https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… Hosts FQDN is also changed and all seem fine apart from OVN connection and ImageIO proxy. About OVN, i just configured OVN and when I test connection I get: Failed with error Certificate for <new fqdn> doesn't match any of the subject alternative names: [old fqdn] and code 5050) about Imageio proxy when I test the connection I do get nothing. No error at engine.log or at GUI. Thus it seems that I have to generate/replace new certs. Is there a way I can fix this until I switch to 4.3 and eventually to 4.4 where it seems that this is handled from the rename tool? Thanks for any assistance. Alex.

2 1

Guest VM snapshots are not retained when importing data storage domain
by Alex K 31 Jul '20

31 Jul '20

Hi all, I have a dual node self hosted cluster v4.3 using gluster as storage so as to test an actual scenario which will need to be followed at production. The purpose is to rename the cluster FQDN to a new one, wiping out any reference to the old previous FQDN. I was not successful in using the engine-rename tool or other means as there are leftovers from previous FQDN that cause issues. The cluster has a data storage domain with one guest VM running on it which has one snapshot. I am testing a destructive scenario as below and I find out that when importing the storage domain to the newly configured cluster, while the guest VM is imported fine, I do not see the guest VM disk snapshots. Steps that I follow for this scenario: *Initial status: * I have an ovirt cluster with two hosts named v0 and v1. The gluster storage domain is configured at a separate network where the hosts are named gluster0 and gluster1. The cluster has an engine and data storage domain named "engine" and "vms" respectively. The "vms" storage domain hosts one guest VM with one guest VM disk snapshot. All are configured with fqdn *localdomain.local* *# Steps to rename all cluster to new fqdn lab.local and import "vms" storage domain* 1. Set v1 ovirt host at maintenance then remove it from GUI. 2. At v1 install fresh CentOS7 using the new FQDN lab.local 3. at v0 set global maintenance and shutdown engine. Remove the engine storage data. (complete wipe of any engine related data. What is important is only VM guests and their snapshots). 4. at v0, remove bricks belonging to "engine" and "vms" gluster volumes of v1 and detach gluster peer v1. gluster volume remove-brick engine replica 1 gluster1:/gluster/engine/brick force gluster volume remove-brick vms replica 1 gluster1:/gluster/vms/brick force gluster peer detach gluster1 5. On v1, prepare gluster service, reattach peer and add bricks from v0. At this phase all data from vms gluster volume will be synced to the new host. Verify with `gluster heal info vms`. from v0 server run: gluster peer probe gluster1 gluster volume add-brick engine replica 2 gluster1:/gluster/engine/brick gluster volume add-brick vms replica 2 gluster1:/gluster/vms/brick At this state all gluster volume are up and in sync. We confirm "vms" sync with gluster volume heal info vms 6. At freshly installed v1 install engine using the same clean gluster engine volume: hosted-engine --deploy --config-append=/root/storage.conf --config-append=answers.conf (use new FQDN!) 7. Upon completion of engine deployment and after having ensured the vms gluster volume is synced (step 5) remove bricks of v0 host (v0 now should not be visible at ovirt GUI) and detach gluster peer v0. at v1 host run: gluster volume remove-brick engine replica 1 gluster0:/gluster/engine/brick force gluster volume remove-brick vms replica 1 gluster0:/gluster/vms/brick force gluster peer detach gluster0 8. Install fresh CentOS7 on v0 and prepare it with ovirt node packages, networking and gluster. 9. At v0, attach gluster bricks from v1. Confirm sync with gluster volume heal info. at v1 host: gluster peer probe gluster0 gluster volume add-brick engine replica 2 gluster0:/gluster/engine/brick gluster volume add-brick vms replica 2 gluster0:/gluster/vms/brick 10. at engine, add entry for v0 host at /etc/hosts. At ovirt GUI, add v0. /etc/hosts: 10.10.10.220 node0 v0.lab.local 10.10.10.221 node1 v1.lab.local 10.10.10.222 engine.lab.local engine 10.100.100.1 gluster0 10.100.100.2 gluster1 11. At ovirt GUI import vms gluster volume as vms storage domain. At this step I have to approve operation: [image: image.png] 12. At ovirt GUI, import VMs from vms storage domain. At this step the VM is found and imported from the imported storage domain "vms", but the VM does not show the previously available disk snapshot. The import of the storage domain should have retained the guest VM snapshot. How can this be troubleshooted? Do I have to keep some type of engine DB backup so as to make the snapshots visible? If yes, is it possible to restore this backup to a fresh engine that has a new FQDN? Thanx very much for any advise and hint. Alex

2 3

best way to have storage vlan available to host AND vms?
by Philip Brown 30 Jul '20

30 Jul '20

I'm trying to allow a particular iSCSI VLAN to be available to all hosts.. but also to a few select VMs. Im finding this challenging, since prior to now, I did host iSCSI config on the host-local level. i used the cockpit GUI to create a "VLAN" entity, assigned it to an interface, and then configured an IP address. But when I attempt to create a "network"(/aka VLAN) entity from the main hosted-engine level.. it seems to conflict with prior host-local created ones. and when I remove the host-local entries... I no longer seem to have a way in the GUI to create IP addresses for the host, from host cockpit? It recognises that the entity exists, but put it in the "unmanaged" section. So.. how can I handle this best? -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

2 4

10GB disk created on glusterfs storage has only 4096B in vm
by Jiří Sléžka 30 Jul '20

30 Jul '20

Hi, I have another spooky issue. CentOS 8.2, oVirt 4.4.1.10-1 I am trying to create vm on my HCI cluster (which in fact has only two nodes now, the third will be added later). I have created new 10GB disk on gluster storage (it behaves the same way when I chose prealocated or thin provision disk). Everything looks good (I was surprised how fast was this disk created) but when I run the vm then disk has only 4096 bytes. see http://mirror.slu.cz/tmp/ovirt_small_disk.png disk creation part of engine.log is here https://paste.slu.cz/?0e33e800609898d8#CEC2maoe7zk9b1zmnHaAENjaAnpiyzzGzPFS… the same part in vdsm.log on SPM host https://paste.slu.cz/?e89fdce800c39b28#3UWw7dXxQAmZysMSKp5NbeTWMNDghZVh2NLE… where could be problem? Did anybody experience this behavior? Cheers, Jiri

4 7

PKI Problem
by ramon＠clematide.ch 30 Jul '20

30 Jul '20

Hi I did a fresh installation of version 4.4.0.3. After the engine setup I replaced the apache certificate with a custom certificate. I used this article to do it: https://myhomelab.gr/linux/2020/01/20/replacing_ovirt_ssl.html To summarize, I replaced those files with my own authority and the signed custom certificate /etc/pki/ovirt-engine/keys/apache.key.nopass /etc/pki/ovirt-engine/certs/apache.cer /etc/pki/ovirt-engine/apache-ca.pem That worked so far, apache uses now my certificate, login is possible. To setup a new machine, I need to upload an iso image, which failed. I found this error in /var/log/ovirt-imageio/daemon.log 2020-07-08 20:43:23,750 INFO (Thread-10) [http] OPEN client=192.168.1.228 2020-07-08 20:43:23,767 INFO (Thread-10) [backends.http] Open backend netloc='the_secret_hostname:54322' path='/images/ef60404c-dc69-4a3d-bfaa-8571f675f3e1' cafile='/etc/pki/ovirt-engine/apache-ca.pem' secure=True 2020-07-08 20:43:23,770 ERROR (Thread-10) [http] Server error Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/http.py", line 699, in __call__ self.dispatch(req, resp) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/http.py", line 744, in dispatch return method(req, resp, *match.groups()) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/cors.py", line 84, in wrapper return func(self, req, resp, *args) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/images.py", line 66, in put backends.get(req, ticket, self.config), File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/__init__.py", line 53, in get cafile=config.tls.ca_file) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", line 48, in open secure=options.get("secure", True)) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", line 63, in __init__ options = self._options() File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", line 364, in _options self._con.request("OPTIONS", self.url.path) File "/usr/lib64/python3.6/http/client.py", line 1254, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib64/python3.6/http/client.py", line 1300, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib64/python3.6/http/client.py", line 1249, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib64/python3.6/http/client.py", line 1036, in _send_output self.send(msg) File "/usr/lib64/python3.6/http/client.py", line 974, in send self.connect() File "/usr/lib64/python3.6/http/client.py", line 1422, in connect server_hostname=server_hostname) File "/usr/lib64/python3.6/ssl.py", line 365, in wrap_socket _context=self, _session=session) File "/usr/lib64/python3.6/ssl.py", line 776, in __init__ 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() ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897) 2020-07-08 20:43:23,770 INFO (Thread-10) [http] CLOSE client=192.168.1.228 [connection 1 ops, 0.019775 s] [dispatch 1 ops, 0.003114 s] I'm a python developer so I had no problem reading the traceback. The SSL handshake fails when image-io tries to connect to what I think is called an ovn-provider. But it is using my new authority certificate cafile='/etc/pki/ovirt-engine/apache-ca.pem' which does not validate the certificate generated by the ovirt engine setup, which the ovn-provider probably uses. I didn't exactly know where the parameter for the validation ca file is. Probably it is the ca_file parameter in /etc/ovirt-imageio/conf.d/50-engine.conf. But that needs to be set to my own authority ca file. I modified the python file to set the ca_file parameter to the engine setups ca_file directly /usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/__init__.py So the function call around line 50 looks like this: backend = module.open( ticket.url, mode, sparse=ticket.sparse, dirty=ticket.dirty, cafile='/etc/pki/ovirt-engine/ca.pem' #config.tls.ca_file ) Now the image upload works, but obviously this is not the way to fix things. Is there an other way to make image-io accept the certificate from the engine setup, while using my custom certificate? I don't want to replace the certificates of all ovirt components with custom certificates. I only need the weblogin with my custom certificate. Regards

4 9

Problem with paused VMs in ovirt 4.3.10.
by Dmitry Sekretev 30 Jul '20

30 Jul '20

Hi! We have a problem with paused VMs in ovirt cluster. Please, help to solve this. In ovirt manager massege "VM rtb-stagedsw02-ovh has been paused." Resume fails with error "Failed to resume VM rtb-stagedsw02-ovh (Host: ovirt-node09-ovh.local, User: admin@internal-authz)." In oVirt Cluster 38 VM, paused VM only ubuntu 20.04 focal with docker swarm. Archived logs in attach. Packeges on ovirt nodes: python2-ovirt-setup-lib-1.2.0-1.el7.noarch ovirt-vmconsole-1.0.7-2.el7.noarch ovirt-provider-ovn-driver-1.2.29-1.el7.noarch ovirt-vmconsole-host-1.0.7-2.el7.noarch python2-ovirt-host-deploy-1.8.5-1.el7.noarch ovirt-imageio-common-1.5.3-0.el7.x86_64 cockpit-machines-ovirt-195.6-1.el7.centos.noarch ovirt-ansible-engine-setup-1.1.9-1.el7.noarch ovirt-host-dependencies-4.3.5-1.el7.x86_64 ovirt-host-4.3.5-1.el7.x86_64 python-ovirt-engine-sdk4-4.3.4-2.el7.x86_64 ovirt-host-deploy-common-1.8.5-1.el7.noarch ovirt-ansible-hosted-engine-setup-1.0.32-1.el7.noarch ovirt-hosted-engine-setup-2.3.13-1.el7.noarch ovirt-ansible-repositories-1.1.5-1.el7.noarch ovirt-imageio-daemon-1.5.3-0.el7.noarch cockpit-ovirt-dashboard-0.13.10-1.el7.noarch ovirt-release43-4.3.10-1.el7.noarch ovirt-hosted-engine-ha-2.3.6-1.el7.noarch Packeges on HostedEngine: ovirt-ansible-infra-1.1.13-1.el7.noarch ovirt-vmconsole-1.0.7-2.el7.noarch ovirt-engine-setup-plugin-websocket-proxy-4.3.10.4-1.el7.noarch ovirt-engine-websocket-proxy-4.3.10.4-1.el7.noarch ovirt-engine-restapi-4.3.10.4-1.el7.noarch ovirt-ansible-engine-setup-1.1.9-1.el7.noarch ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch ovirt-iso-uploader-4.3.2-1.el7.noarch ovirt-provider-ovn-1.2.29-1.el7.noarch ovirt-imageio-proxy-setup-1.5.3-0.el7.noarch ovirt-engine-extension-aaa-ldap-setup-1.3.10-1.el7.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.10.4-1.el7.noarch python-ovirt-engine-sdk4-4.3.4-2.el7.x86_64 python2-ovirt-host-deploy-1.8.5-1.el7.noarch ovirt-ansible-vm-infra-1.1.22-1.el7.noarch ovirt-engine-metrics-1.3.7-1.el7.noarch ovirt-ansible-disaster-recovery-1.2.0-1.el7.noarch ovirt-engine-wildfly-overlay-17.0.1-1.el7.noarch ovirt-ansible-roles-1.1.7-1.el7.noarch ovirt-engine-dwh-setup-4.3.8-1.el7.noarch python2-ovirt-engine-lib-4.3.10.4-1.el7.noarch ovirt-engine-extension-aaa-ldap-1.3.10-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.3.10.4-1.el7.noarch ovirt-engine-vmconsole-proxy-helper-4.3.10.4-1.el7.noarch ovirt-engine-tools-backup-4.3.10.4-1.el7.noarch ovirt-engine-webadmin-portal-4.3.10.4-1.el7.noarch ovirt-host-deploy-common-1.8.5-1.el7.noarch ovirt-ansible-image-template-1.1.12-1.el7.noarch ovirt-ansible-manageiq-1.1.14-1.el7.noarch ovirt-engine-wildfly-17.0.1-1.el7.x86_64 ovirt-ansible-hosted-engine-setup-1.0.32-1.el7.noarch ovirt-imageio-common-1.5.3-0.el7.x86_64 ovirt-imageio-proxy-1.5.3-0.el7.noarch python2-ovirt-setup-lib-1.2.0-1.el7.noarch ovirt-vmconsole-proxy-1.0.7-2.el7.noarch ovirt-engine-setup-base-4.3.10.4-1.el7.noarch ovirt-engine-setup-plugin-cinderlib-4.3.10.4-1.el7.noarch ovirt-engine-extensions-api-impl-4.3.10.4-1.el7.noarch ovirt-release43-4.3.10-1.el7.noarch ovirt-engine-backend-4.3.10.4-1.el7.noarch ovirt-engine-tools-4.3.10.4-1.el7.noarch ovirt-web-ui-1.6.0-1.el7.noarch ovirt-ansible-cluster-upgrade-1.1.14-1.el7.noarch ovirt-cockpit-sso-0.1.1-1.el7.noarch ovirt-engine-ui-extensions-1.0.10-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.3.10.4-1.el7.noarch ovirt-engine-4.3.10.4-1.el7.noarch ovirt-ansible-repositories-1.1.5-1.el7.noarch ovirt-engine-extension-aaa-jdbc-1.1.10-1.el7.noarch ovirt-host-deploy-java-1.8.5-1.el7.noarch ovirt-engine-dwh-4.3.8-1.el7.noarch ovirt-engine-api-explorer-0.0.5-1.el7.noarch ovirt-guest-agent-common-1.0.16-1.el7.noarch ovirt-engine-setup-4.3.10.4-1.el7.noarch ovirt-engine-dbscripts-4.3.10.4-1.el7.noarch In /var/log/ovirt-engine/engine.log: 2020-07-24 09:38:44,472+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] VM '18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99'(rtb-stagedsw02-ovh) move d from 'Up' --> 'Paused' 2020-07-24 09:38:44,493+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] EVENT_ID: VM_PAUSED(1,025), VM rtb-stagedsw02-ovh has been paused. In /var/log/vdsm/vdsm.log 2020-07-24 09:38:42,771+0300 INFO (libvirt/events) [virt.vm] (vmId='18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99') CPU stopped: onSuspend (vm:6100) 2020-07-24 09:38:44,328+0300 INFO (jsonrpc/1) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'message': 'Done', 'code': 0}, 'io_tune_policies_dict': {'4d9519f6-1ab9-4032-8fdf-4c6118531544': {'poli cy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glust erSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/images/e1cfb9ec-39d8-416d-9f5f-0b54765301d4/8f95d60d-931b-4764-993c-ba9373efe361', 'name': 'sda'}]}, 'b031a269-6bcd-40b7-9737-e47112a54b3a': {'po licy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glu sterSD/10.0.11.101:_vmstore01/5e05fed3-448b-4f86-b5ba-004982194c90/images/9c3cc7a0-254e-4756-91b6-fb54e21abf38/71dd8024-8aec-46da-a80f-34260655e929', 'name': 'sda'}, {'ioTune': {'write_bytes_sec': 0L, 'total_io ps_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glusterSD/10.0.11.101:_vmstore01/5e05fed3-448b-4f86-b5ba-004982194c90/images/ 3e3a5064-5fe1-40c0-81f5-44f1a3a4d503/13549972-82de-4746-aeea-3e1531f9c180', 'name': 'sdb'}]}, 'b5fad17c-fa9d-4a80-99e7-6f86e6e19c9b': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_ iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glusterSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/image s/15ce6cb0-6f06-4a31-92d8-b6e1bcabf3bc/613de344-d1ad-49aa-a2d0-d60ca9eb7cd3', 'name': 'sda'}]}, '18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'tota l_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': u'/rhev/data-center/mnt/glusterSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/im ages/7978e2db-c560-4315-a775-223f1b13ae31/d927eea8-e588-449e-b07b-c845d15b082e', 'name': 'sda'}, {'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_s ec': 0L, 'total_bytes_sec': 0L}, 'path': u'/rhev/data-center/mnt/glusterSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/images/b925dc2e-17ba-470d-a9be-cb96d4ef1f0d/951d9712-7160-4f88-a838-970aec8 2b3ea', 'name': 'sdb'}]}}} from=::1,34598 (api:54) 2020-07-24 09:38:49,747+0300 WARN (qgapoller/1) [virt.periodic.VmDispatcher] could not run <function <lambda> at 0x7fe5c84de6e0> on ['18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99'] (periodic:289) In /var/log/libvirt/qemu/rtb-stagedsw03-ovh.log KVM: entry failed, hardware error 0x80000021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=00001000 EBX=43117da8 ECX=0000000c EDX=00000121 ESI=00000003 EDI=17921000 EBP=43117cb0 ESP=43117c98 EIP=00008000 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES =0000 00000000 ffffffff 00809300 CS =9b00 7ff9b000 ffffffff 00809300 SS =0000 00000000 ffffffff 00809300 DS =0000 00000000 ffffffff 00809300 FS =0000 00000000 ffffffff 00809300 GS =0000 00000000 ffffffff 00809300 LDT=0000 00000000 000fffff 00000000 TR =0040 001ce000 0000206f 00008b00 GDT= 001cc000 0000007f IDT= 00000000 00000000 CR0=00050032 CR2=17921000 CR3=2b92a003 CR4=00000000 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000fffe0ff0 DR7=0000000000000400 EFER=0000000000000000 Code=ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff <ff> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

2 1

[ANN] oVirt 4.4.2 First Release Candidate is now available for testing
by Lev Veyde 30 Jul '20

30 Jul '20

oVirt 4.4.2 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.2 First Release Candidate for testing, as of July 30h, 2020. This update is the second in a series of stabilization updates to the 4.4 series. 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 the engine: either use appliance or: - Install CentOS Linux 8.2 minimal from: https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8.2 from https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to the engine and let it be deployed. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (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 for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.2 release highlights: http://www.ovirt.org/release/4.4.2/ * 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.2/ [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

Re: oVirt 4.3 ssh passwordless setup guide
by Sandro Bonazzola 30 Jul '20

30 Jul '20

Il giorno gio 23 lug 2020 alle ore 20:46 Morris, Roy <roy.morris(a)ventura.org> ha scritto: > Hello, > > > > Does anyone have a guide or how to on setting up oVirt with passwordless > ssh setup? I want to do this with a production environment to improve > security but I have never done this before and want to build a test > environment to try it out. > I think what you are looking for is: https://wiki.centos.org/HowTos/Network/SecuringSSH#Use_Public.2FPrivate_Key… for an explanation about passwordless ssh access. And then https://ovirt.org/documentation/administration_guide/#Adding_standard_hosts… on how to get the ssh public key to be added on /root/.ssh/authorized_keys on your hosts > > > Best regards, > > Roy Morris > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/OAEFVXWUIVQCP… > -- 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. <https://mojo.redhat.com/docs/DOC-1199578>*

1 0

Changing management network
by Alex K 30 Jul '20

30 Jul '20

Hi all, I see this has been asked in the past though I was not able to find a specific answer. I want to change the management network at a new subnet. In this case I am using /etc/hosts and not DNS, though the steps can be performed with DNS also. What i do is: 1. Enable global maintenance 2. SSH into engine and change its IP address to the new network and update /etc/hosts with new engine and hosts IP addresses. restart engine network. 3. Update /etc/hosts at each host to reflect new engine and host IPs. 4. Login at engine. the hosts will be by now shown as down. For each host, set host at maintenance and change its management net. Activate host, migrate engine and repeat. 5. Disable global maintenance. I did receive some errors at step 4, failing to update host network and such, though I did run at each host: ip addr add 10.10.50.X/24 dev ovirtmgmt so as to add on the fly the new host IP, in case engine wanted to have access a priory to this new IP (as already configured at /etc/hosts of engine), and unchecked the "verify engine connectivity" when saving network changes. When doing this, the host mgmt net was updated. Now, to make it slightly more difficult, I want to add also a VLAN tag at the same management net. When I attempt to enable VLAN tagging at the ovirt management net I get: [image: image.png] I proceed and since having configured already the VLANs, and after switching the host ports to the VLAN network, I do get access at the hosts and engine. Do you think this is fine or are there any other recommended steps? Thanx for any feedback. Alex

1 0

Re: Management Engine IP change
by Alex K 30 Jul '20

30 Jul '20

On Thu, Jul 30, 2020 at 2:45 PM Yedidyah Bar David <didi(a)redhat.com> wrote: > On Thu, Jul 30, 2020 at 1:47 PM Alex K <rightkicktech(a)gmail.com> wrote: > >> >> >> On Thu, Jul 30, 2020 at 1:30 PM Yedidyah Bar David <didi(a)redhat.com> >> wrote: >> >>> On Thu, Jul 30, 2020 at 1:20 PM Alex K <rightkicktech(a)gmail.com> wrote: >>> > >>> > >>> > >>> > On Thu, Jul 30, 2020 at 12:56 PM Yedidyah Bar David <didi(a)redhat.com> >>> wrote: >>> >> >>> >> On Thu, Jul 30, 2020 at 12:42 PM Alex K <rightkicktech(a)gmail.com> >>> wrote: >>> >> > >>> >> > >>> >> > >>> >> > On Thu, Jul 30, 2020 at 12:01 PM Yedidyah Bar David < >>> didi(a)redhat.com> wrote: >>> >> >> >>> >> >> On Thu, Jul 30, 2020 at 11:30 AM Alex K <rightkicktech(a)gmail.com> >>> wrote: >>> >> >>> >>> >> >>> >>> >> >>> >>> >> >>> On Tue, Jul 28, 2020 at 11:51 AM Anton Louw via Users < >>> users(a)ovirt.org> wrote: >>> >> >>>> >>> >> >>>> >>> >> >>>> >>> >> >>>> Hi All, >>> >> >>>> >>> >> >>>> >>> >> >>>> >>> >> >>>> Does somebody perhaps know the process of changing the Hosted >>> Engine IP address? I see that it is possible, I am just not sure if it is a >>> straight forward process using ‘nmtui’ or editing the network config file. >>> I have also ensured that everything was configured using the FQDN. >>> >> >>> >>> >> >>> Since the FQDN is not changing you should not have issues just >>> updating your DNS then changing manually the engine IP from the ifcfg-ethx >>> files then restart networking. >>> >> >>> What i find difficult and perhaps impossible is to change engine >>> FQDN, as one will need to regenerate all certs from scratch (otherwise you >>> will have issues with several services: imageio proxy, OVN, etc) and there >>> is no such procedure documented/or supported. >>> >> >> >>> >> >> >>> >> >> I wonder - how/what did you search for, that led you to this >>> conclusion? Or perhaps you even found it explicitly written somewhere? >>> >> > >>> >> > Searching around and testing in LAB. I am testing 4.3 though not >>> 4.4. I used engine-rename tool and although was able to change fqdn for >>> hosts and engine, I observed that some certificates were left out (for >>> example OVN was still complaining about certificate issue with subject name >>> not agreeing with the new FQDN - checking/downloading the relevant cert was >>> still showing the previous FQDN). I do not deem successful the renaming of >>> not all services are functional. >>> >> >>> >> Very well. >>> >> >>> >> I'd find your above statement less puzzling if you wrote instead "... >>> >> and the procedure for doing this is buggy/broken/incomplete"... >>> > >>> > I'm sorry for the confusion. >>> >>> No problem :-) >>> >>> >> >>> >> >>> >> >> >>> >> >> >>> >> >> There actually is: >>> >> >> >>> >> >> >>> >> >> >>> https://www.ovirt.org/documentation/administration_guide/#sect-The_oVirt_En… >>> >> > >>> >> > >>> >> > At this same link it reads: >>> >> > While the ovirt-engine-rename command creates a new certificate for >>> the web server on which the Engine runs, it does not affect the certificate >>> for the Engine or the certificate authority. Due to this, there is some >>> risk involved in using the ovirt-engine-rename command, particularly in >>> environments that have been upgraded from Red Hat Enterprise Virtualization >>> 3.2 and earlier. Therefore, changing the fully qualified domain name of the >>> Engine by running engine-cleanup and engine-setup is recommended where >>> possible. >>> >> > explaining my above findings from the tests. >>> >> >>> >> No. These are two different things: >>> >> >>> >> 1. Bugs. All software has bugs. Hopefully we fix them over time. If >>> >> you find one, please file it. >>> >> >>> >> 2. Inherent design (or other) problems - the software works as >>> >> intended, but that's not what you want... >>> > >>> > I do not intend to blame anyone. I really appreciate the work you all >>> are doing with this great project and understand that the community stream >>> may have bugs and rough edges or simply I might not be well informed. >>> >> >>> >> >>> >> See also: >>> >> >>> >> >>> https://www.ovirt.org/develop/networking/changing-engine-hostname.html >>> >> >>> >> >> >>> >> >> >>> >> >> That said, it indeed was somewhat broken for some time now - some >>> fixed were only added quite recently, and are available only in current 4.4: >>> >> > >>> >> > This is interesting and needed for migration scenarios. >>> >> >>> >> Can you please elaborate? >>> > >>> > I am thinking about a scenario where one will need to migrate a DC >>> from one FQDN to a completely new one (say I currently have >>> host1.domain1.com, host2.domain1.com, engine.domain1.com and want to >>> switch to host1.domain2.com, host2.domain2.com, engine.domain2.com) I >>> am currently facing one such need. I need to migrate existing DC from >>> domain1.com to domain2.com. Tried the engine-rename tool and changed >>> IPs of engine and hosts but observed the OVN certificate issue with 4.3. In >>> case this is sorted with 4.4 then I will see if this resolves my issue. >>> >>> These are _names_, for the same machines, right? I'd call it a rename, >>> then, not a migration. >>> >> Indeed. It is a rename. Same dc/cluster with different names. (my setup >> is one DC which has one cluster) >> >>> >>> If it's migration (you have two sets of physical machines, and want to >>> migrate the VMs from one set to the other), indeed using storage >>> import is simpler (perhaps using the DR tool/doc). >>> >> I tested a storage domain import at a 4.3 virtual test environment at >> same renamed DC/cluster and found out that the VM snapshots where not >> retained. >> As per >> https://www.ovirt.org/develop/release-management/features/storage/importsto… >> docs it should have kept the snapshots metadata. I am wondering why this is >> as losing the snapshots will be a major issue for me. >> > > I have no idea - please start a new thread, or file a bug and attach > relevant logs. Thanks. > > >> >> The steps I followed for the rename and data storage import are the >> following: >> >> *Assumptions: * >> We have an ovirt cluster (v4.3) with two hosts named v0 and v1. >> Also the "vms" storage domain does have the guest VMs. The guest VMs do >> have disk snapshots. >> >> *Steps: * >> 1. Set v1 ovirt host at maintenance then remove it. >> > 2. At v1 install fresh CentOS7 using the new FQDN >> > > You mean you have gluster on separate disks and do not wipe them during > reinstall, I guess. Reasonable, but a bit risky, depending on exactly how > you do this. > > If this is important, I'd consider doing a test (perhaps with a copy of > your real data, if possible), and see that I can restore everything from v1 > after this reinstallation (e.g. for the case where v0 dies right after or > during the reinstallation). > > Or perhaps you mean that you do wipe everything? This means you have no > storage replication for the duration of the process (which probably takes > several hours?). > I mean I do a complete wipe of the host having first removed its gluster bricks. The data are retained at the other host. Then later the same clean host is added as gluster peer and the relevant storage domain is synced back so as to repeat the wipe at the remaining host. Tested and all data are retained, except snapshots of VMs are lost or not visible when importing back the same storage domain, which does seem to not be related with gluster. At test environment it takes only a few minutes to sync as I have only one VM on this storage domain. > > >> 3. at v0, set global maintenance and shutdown engine. wipe the engine >> storage data from the relevant gluster mount. (the engine VM is completely >> deleted!) >> 4. at v0, remove bricks belonging to v1 and detach gluster peer v1. >> 5. On v1, prepare gluster service, reattach peer and add bricks from v0. >> At this phase all data from vms gluster volume will be synced to the new >> host. Verify with `gluster heal info vms`. >> 6. At freshly installed v1 install engine using the same clean gluster >> engine volume: >> `hosted-engine --deploy --config-append=/root/storage.conf >> --config-append=answers.conf` (use new FQDN!) >> 7. Upon completion of engine deployment and after having ensured the vms >> gluster volume is synced (step 5) remove bricks of v0 host (v0 now should >> not be visible at ovirt GUI) and detach gluster peer v0. >> 8. Install fresh CentOS7 on v0 and prepare it with ovirt node packages, >> networking and gluster. >> 9. At v0, attach gluster bricks from v1. Confirm sync with gluster volume >> heal info. >> 10. at engine, add entry for v0 host at /etc/hosts or update your DNS. At >> ovirt GUI, add v0 host >> 11. At ovirt GUI import vms gluster volume as vms storage domain. >> 12. At ovirt GUI, import VMs from vms storage domain. >> >> At step 11 I had to confirm the import as I received the following: >> >> [image: image.png] >> > > Perhaps this is why (or related to) you did not get the snapshots? But I > really don't know. Just note this on the other thread, when you post it. > This is the only blocking issue to complete my renaming of the cluster. Im happy with the long steps to wipe and setup from scratch, as long as snapshots are retained. I will try to open a new thread. > > >> At step 12, I successfully imported the VM though observed that the VM >> had no any snapshots. >> >> >> >>> >> >>> >> >>> >> If it's DR migration, perhaps you want storage export/import, as is >>> >> done using the DR tool: >>> >> >>> >> >>> https://www.ovirt.org/documentation/disaster-recovery-guide/disaster-recove… >>> >> >>> >> If you just want to use a new name, but do not need to completely >>> >> forget the old one, you can add it using SSO_ALTERNATE_ENGINE_FQDNS. >>> > >>> > I need to wipe out completely any reference to the old domain/FQDN. >>> >>> If it's indeed really completely, as in "if someone finds the old name >>> somewhere, it's going to be a problem/cost money/whatever", then the >>> rename tool is not for you. It's designed to impose minimal downtime >>> and use the new name wherever really important, but will keep the old >>> name e.g. in the CA (meaning, in the ca cert, and all the certs it >>> signed/signs). If that's a problem for you, the rename tool is not >>> solving it. If in current 4.4 you find an "important" place with the >>> old name, please file a bug. Thanks. >>> >> Yes, it must be wiped due to policy. I do not think there are other >> implications :) >> > > :-) > > >> Speaking about the production, which is still 4.2, I will then have to >> upgrade to 4.3 and then 4.4 if my LAB tests confirm the full rename is >> sorted at 4.4. >> > > Please note that 4.4 is EL8 only, both engine and hosts. > indeed. I would prefer at the moment to stick at 4.3. > > >> Thanx for pointing this out. >> I have to sort out also how to change the management network for which I >> will open a new thread. >> >> Thanx for your swift responses >> > > YW, good luck! > > >> >>> >> >>> >> >>> >> > Also I am wondering if I can change in some way the management >>> network and make from untagged to VLAN tagged. >>> >> >>> >> Sorry, no idea. Perhaps start a different thread about this. >>> > >>> > I will. thanx. >>> >> >>> >> >>> >> Best regards, >>> >> >>> >> >> >>> >> >> >>> >> >> >>> https://github.com/oVirt/ovirt-engine/commits/master/packaging/setup/plugin… >>> >> >> >>> >> >> I do not think I am aware of currently still-open bugs. If you >>> find one, please file it in bugzilla. Thanks! >>> >> >> >>> >> >>> >>> >> >>> I might be able to soon test this engine IP change in a virtual >>> environment and let you know. >>> >> >> >>> >> >> >>> >> >> Thanks and good luck! >>> >> >> -- >>> >> >> Didi >>> >> > >>> >> > _______________________________________________ >>> >> > Users mailing list -- users(a)ovirt.org >>> >> > To unsubscribe send an email to users-leave(a)ovirt.org >>> >> > Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> >> > oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> >> > List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/R5ZWCNEL3HPK5… >>> >> >>> >> >>> >> >>> >> -- >>> >> Didi >>> >> >>> > _______________________________________________ >>> > Users mailing list -- users(a)ovirt.org >>> > To unsubscribe send an email to users-leave(a)ovirt.org >>> > Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> > oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> > List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/4KX4WAZR3CH3I… >>> >>> >>> >>> -- >>> Didi >>> >>> > > -- > Didi >

1 0

Re: 10GB disk created on glusterfs storage has only 4096B in vm
by jury cat 30 Jul '20

30 Jul '20

Good that is ok for you now. As Gianluca told you the command to see all the gluster volume settings is : gluster volume get vol_name all The previous command you used : gluster volume info vol_name will list only modified settings from default and not all the settings. The output shows only volume "Options Reconfigured". Regarding if this is an important bug that affects gluster 7.6(or other versions) and should be disabled by default, i dont know for sure. I am just using ovirt as a hyperconvergence tool. Maybe someone from the ovirt developmemt team can answer that.

1 0

VM Snapshot inconsistent
by Arsène Gschwind 30 Jul '20

30 Jul '20

Hi, I running oVirt 4.3.9 with FC based storage. I'm running several VM with 3 disks on 3 different SD. Lately we did delete a VM Snapshot and that task failed after a while and since then the Snapshot is inconsistent. disk1 : Snapshot still visible in DB and on Storage using LVM commands disk2: Snapshot still visible in DB but not on storage anymore (It seems the merge did run correctly) disk3: Snapshot still visible in DB but not on storage ansmore (It seems the merge did run correctly) When I try to delete the snapshot again it runs forever and nothing happens. Is there a way to suppress that snapshot? Is it possible to merge disk1 with its snapshot using LVM commands and then cleanup the Engine DB? Thanks for any hint or help. rgds , arsene -- Arsène Gschwind <arsene.gschwind(a)unibas.ch<mailto:arsene.gschwind@unibas.ch>> Universitaet Basel

4 23

Re: Management Engine IP change
by Alex K 30 Jul '20

30 Jul '20

On Tue, Jul 28, 2020 at 11:51 AM Anton Louw via Users <users(a)ovirt.org> wrote: > > > Hi All, > > > > Does somebody perhaps know the process of changing the Hosted Engine IP > address? I see that it is possible, I am just not sure if it is a straight > forward process using ‘nmtui’ or editing the network config file. I have > also ensured that everything was configured using the FQDN. > Since the FQDN is not changing you should not have issues just updating your DNS then changing manually the engine IP from the ifcfg-ethx files then restart networking. What i find difficult and perhaps impossible is to change engine FQDN, as one will need to regenerate all certs from scratch (otherwise you will have issues with several services: imageio proxy, OVN, etc) and there is no such procedure documented/or supported. I might be able to soon test this engine IP change in a virtual environment and let you know. > > > Thanks > > *Anton Louw* > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > [image: F] <https://www.facebook.com/voxtelecomZA> > [image: T] <https://www.twitter.com/voxtelecom> > [image: I] <https://www.instagram.com/voxtelecomza/> > [image: L] <https://www.linkedin.com/company/voxtelecom> > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > [image: #VoxBrand] > <https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> > *Disclaimer* > > The contents of this email are confidential to the sender and the intended > recipient. Unless the contents are clearly and entirely of a personal > nature, they are subject to copyright in favour of the holding company of > the Vox group of companies. Any recipient who receives this email in error > should immediately report the error to the sender and permanently delete > this email from all storage devices. > > This email has been scanned for viruses and malware, and may have been > automatically archived by *Mimecast Ltd*, an innovator in Software as a > Service (SaaS) for business. Providing a *safer* and *more useful* place > for your human generated data. Specializing in; Security, archiving and > compliance. To find out more Click Here > <https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/EZPTYSINJMOIO… >

2 6

oVirt Node - Add Host Error
by Lovepreet Deol 30 Jul '20

30 Jul '20

Hi, Greetings for the day. I am trying to learn ovirt on vmware workstation and setting up a virtualization datacenter in it. My topology is as follows : [image: oVirt Topology NEW.PNG] Ovirt engine - release 44 ovirt node - 4.4.1.1 I am getting the following error when trying to add the ovirt node to ovirt engine. [image: error 2.PNG] Please help. Regards *Lovepreet Deol*

3 2

Upgrade procedure for oVirt
by Alex K 30 Jul '20

30 Jul '20

Hi all! I am going though an upgrade from ovirt 4.2 (4.2.8.2-1.el7) to 4.3 for a two node cluster with self hosted engine. I have done previously upgrades from 4.1 to 4.2 successfully with minor issues which where fixed. I wanted to confirm with you, in case I am missing anything that may have changed in the mean time, on the steps for minor and major upgrade: *# Ovirt procedure for minor upgrade: (4.x.y -> 4.x.z)* • enable global maintenance mode • at engine: engine-upgrade-check • at engine: yum update "ovirt-*-setup*" • at engine: engine-setup • at engine: yum update • at each host from GUI: host -> installation -> upgrade • at each host: yum update, reboot, activate *# Ovirt procedure for major upgrade (4.x -> 4.y)* • update DC to latest minor version (engine + nodes) • enable global maintenance • at engine: install major version repo: yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release4x.rpm • at engine: engine-upgrade-check • at engine: yum update "ovirt-*-setup*" • at engine: engine-setup • at engine: remove the old ovirt release from /etc/yum.repos.d • at engine: yum update • after completion of engine upgrade disable global maintenance • verify engine version • update each host/node: update to minor, then install new repo, remove old repo, yum update, reboot, activate • after completion of updates: set DC and cluster compatibility level to latest version 4.x. • shutdown guest VMs and confirm they start up again. (you may need to disable guest disk leases or re-activate guest disks) • check events for any issues and fix accordingly Am I missing anything? I am planning the upgrade hoping to have no issues since the cluster is hosting production VMs. Thanx for any feedback! Alex

2 4

Ovirt hypervisor as an DRBD node
by radchenko.anatoliy＠gmail.com 30 Jul '20

30 Jul '20

Hi community, I would like to use 3 nodes for hypervisor (hosted engine or install a separate VM with engine for its subsequent management) to use them as storage nodes - drbd 9 dual primary + quorum node (aka backup), ocfs 2 - so that the VMs used the hardware of both nodes (so to speak, hyperconverged with drbd). Can you tell me if there are any limits on the part of ovirt for this configuration and the best way to mount ocfs2 - iscsi via scst, posixFS or cinder? Thanks in advance Best regards

3 2

Re: Management Engine IP change
by thomas＠hoberg.net 30 Jul '20

30 Jul '20

I honestly don't know, because I have not tried myself, so you might just want to stop reading right here. But from what I understand about the design philosophy of oVirt, it should be ok to change it, while nobody probably ever tested it and everybody would tell you it's a bad idea to do so, unless you're willing to rebuild from scratch. The reason it *should* be ok is that the nodes don't care about the management engine. They care only about the information on the shared cluster storage. How that gets there, who changes it: They couldn't care less. Yet, I believe I have seen events being reported back to the management engine via REST API calls, referring to the management engine via URIs that should have been using FQDN only. So there is some biliateral communication going on, mostly asynchronous as far as I can see and not using IPs. What I can tell you, is that /etc/sysconfig/network-scripts/ifcfg-eth0 has NM_CONTROLLED=no inside, so nmtui won't go near it. You can change that, delete the line, edit the config... and hopefully it will live. And in case things go seriously wrong, you should be able to fix it with hosted-engine --console But, again, I never tried it myself. But I use DHCP on two out of four farms...

2 1

Migrate VMs from oVirt (3.5) to oVirt (4.4)
by Ian Easter 30 Jul '20

30 Jul '20

Hey folks, What is the proper course of action to migrate VMs managed by and older oVirt instance into a new oVirt instance? Assuming this was the best case to upgrade due to the age of the older instance. *Thank you,* *Ian*

2 1

oVirt thrashes Docker network during installation
by thomas＠hoberg.net 30 Jul '20

30 Jul '20

I want to run containers and VMs side by side and not necessarily nested. The main reason for that is GPUs, Voltas mostly, used for CUDA machine learning not for VDI, which is what most of the VM orchestrators like oVirt or vSphere seem to focus on. And CUDA drivers are notorious for refusing to work under KVM unless you pay $esla. oVirt is more of a side show in my environment, used to run some smaller functional VMs alongside bigger containers, but also in order to consolidate and re-distribute the local compute node storage as a Gluster storage pool: Kibbutz storage and compute, if you want, very much how I understand the HCI philosophy behind oVirt. The full integration of containers and VMs is still very much on the roadmap I believe, but I was surprised to see that even co-existence seems to be a problem currently. So I set-up a 3-node HCI on CentOS7 (GPU-less and older) hosts and then added additional (beefier GPGPU) CentOS7 hosts, that have been running CUDA workloads on the latest Docker-CE v19 something. The installation works fine, I can migrate VMs to these extra hosts etc., but to my dismay Docker containers on these hosts lose access to the local network, that is the entire subnet the host is in. For some strange reason I can still ping Internet hosts, perhaps even everything behind the host's gateway, but local connections are blocked. It would seem that the ovritmgmt network that the oVirt installation puts in breaks the docker0 bridge that Docker put there first. I'd consider that a bug, but I'd like to gather some feedback first, if anyone else has run into this problem. I've repeated this several times in completely distinct environments with the same results: Simply add a host with a working Docker-CE as an oVirt host to an existing DC/cluster and then try if you can still ping anyone on that net, including the Docker host from a busybox container afterwards (should try that ping just before you actually add it). No, I didn't try this with podman yet, because that's separate challenge with CUDA: Would love to know if that is part of QA for oVirt already.

5 9

Hosted Engine Deployement
by Vijay Sachdeva 30 Jul '20

30 Jul '20

Hi All, It tried deploying hosted engine using cli and got this error every time: Can anyone please let me know what here is missing..!! As it would be a great help.patri Thanks Vijay Sachdeva

3 3

Non storage nodes erronously included in quota calculations for HCI?
by thomas＠hoberg.net 30 Jul '20

30 Jul '20

For my home-lab I operate a 3 node HCI cluster on 100% passive Atoms, mostly to run light infrastructure services such as LDAP and NextCloud. I then add workstations or even laptops as pure compute hosts to the cluster for bigger but temporary things, that might actually run a different OS most of the time or just be shut off. From oVirt's point of view, these are just first put into maintenance and then shut down until needed again. No fencing or power management, all manual. All nodes, even the HCI ones, run CentOS7 with more of a workstation configuration, so updates pile up pretty quickly. After I recently upgraded one of these extra compute nodes, I found my three node HCI cluster not just faltering, but indeed very hard to reactivate at all. The faltering is a distinct issue: I have the impression that reboots of oVirt nodes cause broadcast storms on my rather simplistic 10Gibt L2 switch, which a normal CentOS instance (or any other OS) doesn't, but that's for another post. No what struck me, was that the gluster daemons on the three HCI nodes kept complaining about a lack of quorum long after the network was all back to normal, even if all three of them were there, saw each other perfectly on "gluster show status all", ready and without any healing issues pending at all. Glusterd would complain on all three nodes that there was no quota for the bricks and stop them. That went away as soon as I started one additional compute node, a node that was a gluster peer (because an oVirt host added to a HCI cluster always gets put into the Gluster, even if it's not contributing storage) but had no bricks. Immediately the gluster daemon on the three nodes with contributing bricks would report back good quota and launch the volumes (and thus all the rest of oVirt), even if in terms of *storage bricks* nothing had changed. I am afraid that downing the extra compute-only oVirtNode will bring down the HCI: Clearly not the type of redundancy it's designed to deliver. Evidently such compute-only hosts (and gluster members) get included into some quorum deliberations even if they hold not a single brick, neither storage nor arbitration. To me that seems like a bug, if that is indeed what happens: There I need your advice and suggestions. AFAIK HCI is a late addition to oVirt/RHEV as storage and compute were orginally designed to be completely distinct. In fact there are still remnants of documentation which seem to prohibit using a node for both compute and storage... what HCI is all about. And I have seen compute nodes with "matching" storage (parts of a distinct HCI setup, that was taken down but still had all the storage and Gluster elements operable), being happliy absorbed into a HCI cluster with all Gluster storage appearing in the GUI etc., without any manual creation or inclusion of bricks: Fully automatic (and undocumented)! In that case it makes sense to widen the scope of quota calculations when additional nodes are hyperconverged elements with contributing bricks. It also seems the only way to turn a 3 node HCI into 6 or 9 node one. But if you really just want to add compute nodes without bricks, those can't get "quota votes" without storage to play a role in the redundancy. I can easily imagine the missing "if then else" in the code here, but I was actually very surprised to see those failure and success messages coming from glusterd itself, which to my understanding is pretty unrelated to oVirt on top. Not from the management engine (wasn't running anyway), not from VDSM. Re-creating the scenario is very scary even if I have gone through this three times already, trying to just bring my HCI back up. And then there is so verbose logs all over the place that I'd like some advice which ones I should post. But simply speaking: Gluster peers should get no quota voting rights on volumes unless they contribute bricks. That rule seems broken. Those in the know, please let me know if am on a goose chase or if there is a real issue here that deserves a bug report.

2 5

OVA import does not upload disks
by Paolo Airaldi 29 Jul '20

29 Jul '20

Hello, I’m running 4.3.5.4-1.el7. I’ve exported a VM as OVA and now I’m trying to import it in another Data Center (it’s like a DR Data Center) Import runs successfully both from GUI and from Ansible, but imported VM disks are empty and the VM fails to boot. How can I import disks content too? Thanks in advance for any help. Paolo

2 2

Problem with paused VMs in ovirt 4.3.10.
by Damien 29 Jul '20

29 Jul '20

Hi! We have a problem with paused VMs in ovirt cluster. Please, help to solve this. In ovirt manager massege "VM rtb-stagedsw02-ovh has been paused." Resume fails with error "Failed to resume VM rtb-stagedsw02-ovh (Host: ovirt-node09-ovh.local, User: admin@internal-authz)." In oVirt Cluster 38 VM, paused VM only ubuntu 20.04 focal with docker swarm. Archived logs in attach. Packeges on ovirt nodes: python2-ovirt-setup-lib-1.2.0-1.el7.noarch ovirt-vmconsole-1.0.7-2.el7.noarch ovirt-provider-ovn-driver-1.2.29-1.el7.noarch ovirt-vmconsole-host-1.0.7-2.el7.noarch python2-ovirt-host-deploy-1.8.5-1.el7.noarch ovirt-imageio-common-1.5.3-0.el7.x86_64 cockpit-machines-ovirt-195.6-1.el7.centos.noarch ovirt-ansible-engine-setup-1.1.9-1.el7.noarch ovirt-host-dependencies-4.3.5-1.el7.x86_64 ovirt-host-4.3.5-1.el7.x86_64 python-ovirt-engine-sdk4-4.3.4-2.el7.x86_64 ovirt-host-deploy-common-1.8.5-1.el7.noarch ovirt-ansible-hosted-engine-setup-1.0.32-1.el7.noarch ovirt-hosted-engine-setup-2.3.13-1.el7.noarch ovirt-ansible-repositories-1.1.5-1.el7.noarch ovirt-imageio-daemon-1.5.3-0.el7.noarch cockpit-ovirt-dashboard-0.13.10-1.el7.noarch ovirt-release43-4.3.10-1.el7.noarch ovirt-hosted-engine-ha-2.3.6-1.el7.noarch Packeges on HostedEngine: ovirt-ansible-infra-1.1.13-1.el7.noarch ovirt-vmconsole-1.0.7-2.el7.noarch ovirt-engine-setup-plugin-websocket-proxy-4.3.10.4-1.el7.noarch ovirt-engine-websocket-proxy-4.3.10.4-1.el7.noarch ovirt-engine-restapi-4.3.10.4-1.el7.noarch ovirt-ansible-engine-setup-1.1.9-1.el7.noarch ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch ovirt-iso-uploader-4.3.2-1.el7.noarch ovirt-provider-ovn-1.2.29-1.el7.noarch ovirt-imageio-proxy-setup-1.5.3-0.el7.noarch ovirt-engine-extension-aaa-ldap-setup-1.3.10-1.el7.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.10.4-1.el7.noarch python-ovirt-engine-sdk4-4.3.4-2.el7.x86_64 python2-ovirt-host-deploy-1.8.5-1.el7.noarch ovirt-ansible-vm-infra-1.1.22-1.el7.noarch ovirt-engine-metrics-1.3.7-1.el7.noarch ovirt-ansible-disaster-recovery-1.2.0-1.el7.noarch ovirt-engine-wildfly-overlay-17.0.1-1.el7.noarch ovirt-ansible-roles-1.1.7-1.el7.noarch ovirt-engine-dwh-setup-4.3.8-1.el7.noarch python2-ovirt-engine-lib-4.3.10.4-1.el7.noarch ovirt-engine-extension-aaa-ldap-1.3.10-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.3.10.4-1.el7.noarch ovirt-engine-vmconsole-proxy-helper-4.3.10.4-1.el7.noarch ovirt-engine-tools-backup-4.3.10.4-1.el7.noarch ovirt-engine-webadmin-portal-4.3.10.4-1.el7.noarch ovirt-host-deploy-common-1.8.5-1.el7.noarch ovirt-ansible-image-template-1.1.12-1.el7.noarch ovirt-ansible-manageiq-1.1.14-1.el7.noarch ovirt-engine-wildfly-17.0.1-1.el7.x86_64 ovirt-ansible-hosted-engine-setup-1.0.32-1.el7.noarch ovirt-imageio-common-1.5.3-0.el7.x86_64 ovirt-imageio-proxy-1.5.3-0.el7.noarch python2-ovirt-setup-lib-1.2.0-1.el7.noarch ovirt-vmconsole-proxy-1.0.7-2.el7.noarch ovirt-engine-setup-base-4.3.10.4-1.el7.noarch ovirt-engine-setup-plugin-cinderlib-4.3.10.4-1.el7.noarch ovirt-engine-extensions-api-impl-4.3.10.4-1.el7.noarch ovirt-release43-4.3.10-1.el7.noarch ovirt-engine-backend-4.3.10.4-1.el7.noarch ovirt-engine-tools-4.3.10.4-1.el7.noarch ovirt-web-ui-1.6.0-1.el7.noarch ovirt-ansible-cluster-upgrade-1.1.14-1.el7.noarch ovirt-cockpit-sso-0.1.1-1.el7.noarch ovirt-engine-ui-extensions-1.0.10-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.3.10.4-1.el7.noarch ovirt-engine-4.3.10.4-1.el7.noarch ovirt-ansible-repositories-1.1.5-1.el7.noarch ovirt-engine-extension-aaa-jdbc-1.1.10-1.el7.noarch ovirt-host-deploy-java-1.8.5-1.el7.noarch ovirt-engine-dwh-4.3.8-1.el7.noarch ovirt-engine-api-explorer-0.0.5-1.el7.noarch ovirt-guest-agent-common-1.0.16-1.el7.noarch ovirt-engine-setup-4.3.10.4-1.el7.noarch ovirt-engine-dbscripts-4.3.10.4-1.el7.noarch In /var/log/ovirt-engine/engine.log: 2020-07-24 09:38:44,472+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] VM '18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99'(rtb-stagedsw02-ovh) move d from 'Up' --> 'Paused' 2020-07-24 09:38:44,493+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] EVENT_ID: VM_PAUSED(1,025), VM rtb-stagedsw02-ovh has been paused. In /var/log/vdsm/vdsm.log 2020-07-24 09:38:42,771+0300 INFO (libvirt/events) [virt.vm] (vmId='18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99') CPU stopped: onSuspend (vm:6100) 2020-07-24 09:38:44,328+0300 INFO (jsonrpc/1) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'message': 'Done', 'code': 0}, 'io_tune_policies_dict': {'4d9519f6-1ab9-4032-8fdf-4c6118531544': {'poli cy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glust erSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/images/e1cfb9ec-39d8-416d-9f5f-0b54765301d4/8f95d60d-931b-4764-993c-ba9373efe361', 'name': 'sda'}]}, 'b031a269-6bcd-40b7-9737-e47112a54b3a': {'po licy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glu sterSD/10.0.11.101:_vmstore01/5e05fed3-448b-4f86-b5ba-004982194c90/images/9c3cc7a0-254e-4756-91b6-fb54e21abf38/71dd8024-8aec-46da-a80f-34260655e929', 'name': 'sda'}, {'ioTune': {'write_bytes_sec': 0L, 'total_io ps_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glusterSD/10.0.11.101:_vmstore01/5e05fed3-448b-4f86-b5ba-004982194c90/images/ 3e3a5064-5fe1-40c0-81f5-44f1a3a4d503/13549972-82de-4746-aeea-3e1531f9c180', 'name': 'sdb'}]}, 'b5fad17c-fa9d-4a80-99e7-6f86e6e19c9b': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_ iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glusterSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/image s/15ce6cb0-6f06-4a31-92d8-b6e1bcabf3bc/613de344-d1ad-49aa-a2d0-d60ca9eb7cd3', 'name': 'sda'}]}, '18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'tota l_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': u'/rhev/data-center/mnt/glusterSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/im ages/7978e2db-c560-4315-a775-223f1b13ae31/d927eea8-e588-449e-b07b-c845d15b082e', 'name': 'sda'}, {'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_s ec': 0L, 'total_bytes_sec': 0L}, 'path': u'/rhev/data-center/mnt/glusterSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/images/b925dc2e-17ba-470d-a9be-cb96d4ef1f0d/951d9712-7160-4f88-a838-970aec8 2b3ea', 'name': 'sdb'}]}}} from=::1,34598 (api:54) 2020-07-24 09:38:49,747+0300 WARN (qgapoller/1) [virt.periodic.VmDispatcher] could not run <function <lambda> at 0x7fe5c84de6e0> on ['18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99'] (periodic:289) In /var/log/libvirt/qemu/rtb-stagedsw03-ovh.log KVM: entry failed, hardware error 0x80000021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=00001000 EBX=43117da8 ECX=0000000c EDX=00000121 ESI=00000003 EDI=17921000 EBP=43117cb0 ESP=43117c98 EIP=00008000 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES =0000 00000000 ffffffff 00809300 CS =9b00 7ff9b000 ffffffff 00809300 SS =0000 00000000 ffffffff 00809300 DS =0000 00000000 ffffffff 00809300 FS =0000 00000000 ffffffff 00809300 GS =0000 00000000 ffffffff 00809300 LDT=0000 00000000 000fffff 00000000 TR =0040 001ce000 0000206f 00008b00 GDT= 001cc000 0000007f IDT= 00000000 00000000 CR0=00050032 CR2=17921000 CR3=2b92a003 CR4=00000000 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000fffe0ff0 DR7=0000000000000400 EFER=0000000000000000 Code=ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff <ff> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

2 1

OVA exported from oVirt cannot be imported in oVirt
by thomas＠hoberg.net 29 Jul '20

29 Jul '20

I have successfully imported OVA files which came from VirtualBox before, something I'd consider the slightly greater hurdle. Exporting a VM to an OVA file and then importing it on another platform can obviously create compatibility issues, but oVirt <-> oVirt exports and imports with the same (or similar) release should obviously just work, right? Sadly, that doesn't seem to be the case. I've just exported a Linux VM, a Univention domain controller using Debian 9 to an OVA and tried importing it on another farm. The process finished without an error, but the machine wouldn't boot. Closer inspection reveals that the exported OVA file is about 100GB in size, which corresponds to the size of the thinly allocated primary disk, but actually contains only 28kb of data (the XML header), while the disk is all zeros ('strings <machine-name>.ova') Another VM I had exported a week ago contains about 2.3GB of data, but that machine also doesn't boot. When I attach its disk to another VM as a secondary, the file system seems to contain bogus data, most directories are unreadable and an fsck goes on for minutes. Export domains are deprecated but when I export the original and runnable VM there, I get 23GB, which corresponds to what the VM is actually using. Infortunately that doesn't give me the mobility for the VM that I desire, especially since I cannot have a shared export/import domain between farms. And then I really might want to use a different hypervisor for a VM that was developed on oVirt, e.g. to put on a laptop. I've been trying to find clues as to what's going on, but generally the OVA exports don't seem to be logged in any obvious place and even the imports on seem to get logged, when the OVAs need to be converted from a foreign format such as VirtualBox where the entire, seemingly rather complex process, is logged in /var/log/vdsm/import/<something> Am I the only one trying to use OVA export/import or is that part of standard Q&A testing?

1 0

Update OVF disks fails on each gluster 7.6 volumes using ovirt 4.4.1.1
by shadow emy 29 Jul '20

29 Jul '20

Failed to update OVF disks 1798e945-5be9-466e-b52d-f7f0a3bb2043, OVF data isn't updated on those OVF stores (Data Center Default, Storage Domain hosted_storage). I did not see anything with error in SPM host3 in /var/log/vdsm/vdsm.log In /var/log/vdsm/supervdsm.log i see MainProcess|jsonrpc/6::DEBUG::2020-07-29 19:05:05,845::supervdsm_server::93::SuperVdsm.ServerCallback::(wrapper) call webhookAdd with ('http://ovirt-engine.domain.local:80/ovirt-engine/services/glusterevents', None) {} MainProcess|jsonrpc/6::DEBUG::2020-07-29 19:05:05,845::commands::153::common.commands::(start) /usr/bin/taskset --cpu-list 0-39 /sbin/gluster-eventsapi webhook-add http://ovirt-engine.domain.local:80/ovirt-engine/services/glusterevents (cwd None) MainProcess|jsonrpc/6::DEBUG::2020-07-29 19:05:06,599::commands::98::common.commands::(run) FAILED: <err> = b'Webhook already exists\n'; <rc> = 5 MainProcess|jsonrpc/6::ERROR::2020-07-29 19:05:06,600::supervdsm_server::97::SuperVdsm.ServerCallback::(wrapper) Error in webhookAdd Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/gluster/events.py", line 42, in webhookAdd commands.run(command) File "/usr/lib/python3.6/site-packages/vdsm/common/commands.py", line 101, in run raise cmdutils.Error(args, p.returncode, out, err) vdsm.common.cmdutils.Error: Command ['/sbin/gluster-eventsapi', 'webhook-add', 'http://ovirt-engine.domain.local:80/ovirt-engine/services/glusterevents'] failed with rc=5 out=b'' err=b'Webhook already exists\n' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", line 95, in wrapper res = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/gluster/events.py", line 44, in webhookAdd raise ge.GlusterWebhookAddException(rc=e.rc, err=e.err) vdsm.gluster.exception.GlusterWebhookAddException: Failed to add webhook: rc=5 out=() err=b'Webhook already exists\n' MainProcess|jsonrpc/6::DEBUG::2020-07-29 19:05:10,818::supervdsm_server::93::SuperVdsm.ServerCallback::(wrapper) call tasksList with ([],) {} MainProcess|jsonrpc/6::DEBUG::2020-07-29 19:05:10,819::commands::153::common.commands::(start) /usr/bin/taskset --cpu-list 0-39 /usr/sbin/gluster --mode=script volume status all tasks --xml (cwd None) SPM message logs : Jul 29 18:58:22 host3 journal[460535]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf Jul 29 18:58:31 host3 journal[460535]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf Jul 29 18:58:42 host3 journal[460535]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf Jul 29 18:58:52 host3 journal[460535]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf Jul 29 18:59:03 host3 journal[460535]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm ERROR Failed extracting VM OVF from the OVF_STORE volume, falling back to initial vm.conf Hosted-Engine /var/log/ovirt-engine/engine.log 2020-07-29 18:52:40,901+03 WARN [org.ovirt.engine.core.dal.job.ExecutionMessageDirector] (default task-153) [1ec2d268-8d00-42ad-9660-0a05362a878b] The message key 'UpdateOvfStoreForStorageDomain' is missing from 'bundles/ExecutionMessages' 2020-07-29 18:52:40,933+03 INFO [org.ovirt.engine.core.bll.storage.domain.UpdateOvfStoreForStorageDomainCommand] (default task-153) [1ec2d268-8d00-42ad-9660-0a05362a878b] Lock Acquired to object 'EngineLock:{exclusiveLocks='[affd38b2-457d-4c9f-9802-1f5fadd7cd34=STORAGE]', sharedLocks=''}' 2020-07-29 18:52:40,989+03 INFO [org.ovirt.engine.core.bll.storage.domain.UpdateOvfStoreForStorageDomainCommand] (default task-153) [1ec2d268-8d00-42ad-9660-0a05362a878b] Running command: UpdateOvfStoreForStorageDomainCommand internal: false. Entities affected : ID: affd38b2-457d-4c9f-9802-1f5fadd7cd34 Type: StorageAction group MANIPULATE_STORAGE_DOMAIN with role type ADMIN 2020-07-29 18:52:41,002+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (default task-153) [71d7de10] Before acquiring and wait lock 'EngineLock:{exclusiveLocks='[15ea58fc-9435-11e9-b093-00163e11a571=OVF_UPDATE]', sharedLocks=''}' 2020-07-29 18:52:41,003+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (default task-153) [71d7de10] Lock-wait acquired to object 'EngineLock:{exclusiveLocks='[15ea58fc-9435-11e9-b093-00163e11a571=OVF_UPDATE]', sharedLocks=''}' 2020-07-29 18:52:41,023+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (default task-153) [71d7de10] Running command: ProcessOvfUpdateForStoragePoolCommand internal: true. Entities affected : ID: 15ea58fc-9435-11e9-b093-00163e11a571 Type: StoragePool 2020-07-29 18:52:41,039+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (default task-153) [71d7de10] Attempting to update VM OVFs in Data Center 'Default' 2020-07-29 18:52:41,060+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (default task-153) [71d7de10] Successfully updated VM OVFs in Data Center 'Default' 2020-07-29 18:52:41,060+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (default task-153) [71d7de10] Attempting to update template OVFs in Data Center 'Default' 2020-07-29 18:52:41,062+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (default task-153) [71d7de10] Successfully updated templates OVFs in Data Center 'Default' 2020-07-29 18:52:41,062+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (default task-153) [71d7de10] Attempting to remove unneeded template/vm OVFs in Data Center 'Default' 2020-07-29 18:52:41,073+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (default task-153) [71d7de10] Successfully removed unneeded template/vm OVFs in Data Center 'Default' 2020-07-29 18:52:41,091+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (default task-153) [71d7de10] Lock freed to object 'EngineLock:{exclusiveLocks='[15ea58fc-9435-11e9-b093-00163e11a571=OVF_UPDATE]', sharedLocks=''}' 2020-07-29 18:52:41,418+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] Lock Acquired to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[15ea58fc-9435-11e9-b093-00163e11a571=OVF_UPDATE]'}' 2020-07-29 18:52:41,440+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] Running command: ProcessOvfUpdateForStorageDomainCommand internal: true. Entities affected : ID: affd38b2-457d-4c9f-9802-1f5fadd7cd34 Type: StorageAction group MANIPULATE_STORAGE_DOMAIN with role type ADMIN 2020-07-29 18:52:41,465+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] START, SetVolumeDescriptionVDSCommand( SetVolumeDescriptionVDSCommandParameters:{storagePoolId='15ea58fc-9435-11e9-b093-00163e11a571', ignoreFailoverLimit='false', storageDomainId='affd38b2-457d-4c9f-9802-1f5fadd7cd34', imageGroupId='1798e945-5be9-466e-b52d-f7f0a3bb2043', imageId='8c0afaac-6c1a-40e5-ad21-54ce53ee6fdb'}), log id: 1f1cc366 2020-07-29 18:52:41,470+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] -- executeIrsBrokerCommand: calling 'setVolumeDescription', parameters: 2020-07-29 18:52:41,470+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] ++ spUUID=15ea58fc-9435-11e9-b093-00163e11a571 2020-07-29 18:52:41,470+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] ++ sdUUID=affd38b2-457d-4c9f-9802-1f5fadd7cd34 2020-07-29 18:52:41,471+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] ++ imageGroupGUID=1798e945-5be9-466e-b52d-f7f0a3bb2043 2020-07-29 18:52:41,471+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] ++ volUUID=8c0afaac-6c1a-40e5-ad21-54ce53ee6fdb 2020-07-29 18:52:41,471+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] ++ description={"Updated":false,"Last Updated":null,"Storage Domains":[{"uuid":"affd38b2-457d-4c9f-9802-1f5fadd7cd34"}],"Disk Description":"OVF_STORE"} 2020-07-29 18:52:41,545+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] FINISH, SetVolumeDescriptionVDSCommand, return: , log id: 1f1cc366 2020-07-29 18:52:41,570+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] Lock Acquired to object 'EngineLock:{exclusiveLocks='', sharedLocks='[33cde062-b8be-46af-b528-5963eb5d8e0d=VDS_EXECUTION]'}' 2020-07-29 18:52:41,615+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] Running command: UploadStreamCommand internal: true. Entities affected : ID: affd38b2-457d-4c9f-9802-1f5fadd7cd34 Type: Storage 2020-07-29 18:52:41,618+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] START, UploadStreamVDSCommand(HostName = host3.domain.local, UploadStreamVDSCommandParameters:{hostId='33cde062-b8be-46af-b528-5963eb5d8e0d'}), log id: 10e8c127 2020-07-29 18:52:41,618+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] -- executeVdsBrokerCommand, parameters: 2020-07-29 18:52:41,618+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] ++ spUUID=15ea58fc-9435-11e9-b093-00163e11a571 2020-07-29 18:52:41,619+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] ++ sdUUID=affd38b2-457d-4c9f-9802-1f5fadd7cd34 2020-07-29 18:52:41,619+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] ++ imageGUID=1798e945-5be9-466e-b52d-f7f0a3bb2043 2020-07-29 18:52:41,619+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] ++ volUUID=8c0afaac-6c1a-40e5-ad21-54ce53ee6fdb 2020-07-29 18:52:41,619+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] ++ size=26112 2020-07-29 18:52:41,664+03 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] Command 'UploadStreamVDSCommand(HostName = host3.domain.local, UploadStreamVDSCommandParameters:{hostId='33cde062-b8be-46af-b528-5963eb5d8e0d'})' execution failed: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <host3.domain.local> doesn't match any of the subject alternative names: [host3.domain.local] 2020-07-29 18:52:41,664+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] FINISH, UploadStreamVDSCommand, return: , log id: 10e8c127 2020-07-29 18:52:41,664+03 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engine-Thread-29741) [b4f2874] Clearing domains data for host host3.domain.local 2020-07-29 18:52:41,665+03 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engine-Thread-29741) [b4f2874] Host 'host3.domain.local' is not responding. 2020-07-29 18:52:41,664+03 ERROR [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] Command 'org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <host3.domain.local> doesn't match any of the subject alternative names: [host3.domain.local] (Failed with error VDS_NETWORK_ERROR and code 5022) 2020-07-29 18:52:41,686+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-29741) [b4f2874] EVENT_ID: VDS_HOST_NOT_RESPONDING(9,027), Host host3.domain.local is not responding. Host cannot be fenced automatically because power management for the host is disabled. 2020-07-29 18:52:41,711+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] Lock freed to object 'EngineLock:{exclusiveLocks='', sharedLocks='[33cde062-b8be-46af-b528-5963eb5d8e0d=VDS_EXECUTION]'}' 2020-07-29 18:52:41,740+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] EVENT_ID: UPDATE_FOR_OVF_STORES_FAILED(1,016), Failed to update OVF disks 1798e945-5be9-466e-b52d-f7f0a3bb2043, OVF data isn't updated on those OVF stores (Data Center Default, Storage Domain hosted_storage). 2020-07-29 18:52:41,777+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] EVENT_ID: UPDATE_OVF_FOR_STORAGE_DOMAIN_FAILED(190), Failed to update VMs/Templates OVF data for Storage Domain hosted_storage in Data Center Default. 2020-07-29 18:52:41,788+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[15ea58fc-9435-11e9-b093-00163e11a571=OVF_UPDATE]'}' 2020-07-29 18:52:41,797+03 ERROR [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] Command 'UpdateOvfStoreForStorageDomain' id: '9578b72d-bb33-4de6-b177-b851f7c367c8' with children [] failed when attempting to perform the next operation, marking as 'FAILED' 2020-07-29 18:52:41,797+03 ERROR [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] EngineException: ENGINE (Failed with error ENGINE and code 5001): org.ovirt.engine.core.common.errors.EngineException: EngineException: ENGINE (Failed with error ENGINE and code 5001) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.domain.UpdateOvfStoreForStorageDomainCommand.executeNextOperation(UpdateOvfStoreForStorageDomainCommand.java:124) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.domain.UpdateOvfStoreForStorageDomainCommand.performNextOperation(UpdateOvfStoreForStorageDomainCommand.java:112) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback.childCommandsExecutionEnded(SerialChildCommandsExecutionCallback.java:32) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.ChildCommandsCallbackBase.doPolling(ChildCommandsCallbackBase.java:80) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:175) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:360) at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:511) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:227) 2020-07-29 18:52:41,798+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-90) [b4f2874] Command 'UpdateOvfStoreForStorageDomain' id: '9578b72d-bb33-4de6-b177-b851f7c367c8' child commands '[]' executions were completed, status 'FAILED' 2020-07-29 18:52:42,725+03 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-17) [] START, GlusterServersListVDSCommand(HostName = host1.domain.local, VdsIdVDSCommandParametersBase:{hostId='157d2f37-6387-47a1-8bf9-bc20231726e7'}), log id: 42f3f507 2020-07-29 18:52:42,822+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-60) [b4f2874] Command 'ProcessOvfUpdateForStorageDomain' id: 'c83199b3-626d-494d-ab93-6ffadcc4e47a' child commands '[55b09b51-04d7-4257-ba05-8fbdd2f236fb]' executions were completed, status 'FAILED' 2020-07-29 18:52:42,851+03 ERROR [org.ovirt.engine.core.bll.storage.domain.UpdateOvfStoreForStorageDomainCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-60) [1ec2d268-8d00-42ad-9660-0a05362a878b] Ending command 'org.ovirt.engine.core.bll.storage.domain.UpdateOvfStoreForStorageDomainCommand' with failure. 2020-07-29 18:52:42,860+03 INFO [org.ovirt.engine.core.bll.storage.domain.UpdateOvfStoreForStorageDomainCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-60) [1ec2d268-8d00-42ad-9660-0a05362a878b] Lock freed to object 'EngineLock:{exclusiveLocks='[affd38b2-457d-4c9f-9802-1f5fadd7cd34=STORAGE]', sharedLocks=''}' 2020-07-29 18:52:43,254+03 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-17) [] FINISH, GlusterServersListVDSCommand, return: [192.168.10.20/24:CONNECTED, gluster3.domain.local:CONNECTED, gluster2.domain.local:CONNECTED], log id: 42f3f507 2020-07-29 18:52:43,266+03 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-17) [] START, GlusterVolumesListVDSCommand(HostName = host1.domain.local, GlusterVolumesListVDSParameters:{hostId='157d2f37-6387-47a1-8bf9-bc20231726e7'}), log id: 69d508fc 2020-07-29 18:52:43,605+03 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-17) [] FINISH, GlusterVolumesListVDSCommand, return: {46d80a34-6871-43a4-8b40-e5efe75bf578=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@4ff50ace, 4ef84624-8219-4850-96d5-ceeb7ed073ae=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@193d2158, 2169ec3c-b8fb-482e-9cd4-fdb751a037c5=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@e0fb06d6}, log id: 69d508fc 2020-07-29 18:52:43,898+03 ERROR [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-22) [b4f2874] Ending command 'org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand' with failure. 2020-07-29 18:52:47,327+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-37) [] START, GetHardwareInfoAsyncVDSCommand(HostName = host3.domain.local, VdsIdAndVdsVDSCommandParametersBase:{hostId='33cde062-b8be-46af-b528-5963eb5d8e0d', vds='Host[host3.domain.local,33cde062-b8be-46af-b528-5963eb5d8e0d]'}), log id: 9a0e1c5 2020-07-29 18:52:47,328+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-37) [] FINISH, GetHardwareInfoAsyncVDSCommand, return: , log id: 9a0e1c5

1 0

ovirt-engine DB datastore full
by Askhat ECC 29 Jul '20

29 Jul '20

Hello! I have ovirt cluster Version 4.2.4.5-1.el7 and hosted-engine with local database. HE-virtio-disk is full directory /var and can not be moved another domain storage. Can you say how migrate or another things to solve this problem? Thanks. Regards [image: Screenshot_1.jpg] [image: Screenshot_13.jpg] [image: image_2020_07_13T06_51_27_733Z.png]

2 1

VM locked and script unlock_entity.sh don't show any problem
by Thomas BURGUIERE 29 Jul '20

29 Jul '20

The WEB interface show that the VM is locked, but when we run unlock_entity.sh there is no problem reported. How we think the VM were locked : There were filesystem issues (shortage disk space on the ovirt engine HOST) during a backup sequence, those consequences were discovered a few days later. The VMs are backed-up with this way: https://github.com/wefixit-AT/oVirtBackup The ovirt-engine logs tell us that Postgres DB has encountered problem like this one during the backup process: Message: PL/pgSQL function updatevdsdynamic(integer,integer,character varying,numeric,character varying,boolean,integer,integer,integer,uuid,integer,integer,integer,integer,integer,integer,integer,integer,character varying,character varying,character varying,character varying,integer,character varying,integer,integer,integer,boolean,character varying,character varying,character varying,character varying,character varying,character varying,character varying,character varying,character varying,character varying,character varying,integer,text,integer,character varying,character varying,character varying,character varying,character varying,character varying,text,text,smallint,integer,smallint,boolean,character varying,text,text,boolean,boolean,text,character varying,boolean,uuid,boolean,jsonb) line 4 at SQL statement; nested exception is org.postgresql.util.PSQLException: ERROR: could not extend file "base/16385/190997": No space left on device Later, we saw that those VMs they got a lock icon in the status column since this episode. This did not appear immediatly, but maybe a few hours after. It happens that those locked VMs are sort-of limited in the way that there are numerous things we cannot do with them, such as: - edit parameters (i.e. memory). - start them again after they get halted by unix command (halt -p) - copy the related disk. The version of ovirt used 4.2.1 Is there an other way to unlock the VMs ? Or to get unlock_entity.sh to work ?

1 1

New ovirt 4.4.0.3-1.el8 leaves disks in illegal state on all snapshot actions
by Henri Aanstoot 28 Jul '20

28 Jul '20

Hi all, I've got 2 two node setup, image based installs. When doing ova exports or generic snapshots, things seem in order. Removing snapshots shows warning 'disk in illegal state' Mouse hover shows .. please do not shutdown before succesfully remove snapshot ovirt-engine log 2020-07-22 16:40:37,549+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedExecutorService-commandCoordinator-Thread-2) [264b0047-5aa6-4380-9d32-eb328fd6bed0] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM node2.lab command MergeVDS failed: Merge failed 2020-07-22 16:40:37,549+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand] (EE-ManagedExecutorService-commandCoordinator-Thread-2) [264b0047-5aa6-4380-9d32-eb328fd6bed0] Command 'MergeVDSCommand(HostName = node2.lab, MergeVDSCommandParameters:{hostId='02df5213-1243-4671-a1c6-6489d7146319', vmId='64c25543-bef7-4fdd-8204-6507046f5a34', storagePoolId='5a4ea80c-b3b2-11ea-a890-00163e3cb866', storageDomainId='9a12f1b2-5378-46cc-964d-3575695e823f', imageGroupId='3f7ac8d8-f1ab-4c7a-91cc-f34d0b8a1cb8', imageId='c757e740-9013-4ae0-901d-316932f4af0e', baseImageId='ebe50730-dec3-4f29-8a38-9ae7c59f2aef', topImageId='c757e740-9013-4ae0-901d-316932f4af0e', bandwidth='0'})' execution failed: VDSGenericException: VDSErrorException: Failed to MergeVDS, error = Merge failed, code = 52 2020-07-22 16:40:37,549+02 ERROR [org.ovirt.engine.core.bll.MergeCommand] (EE-ManagedExecutorService-commandCoordinator-Thread-2) [264b0047-5aa6-4380-9d32-eb328fd6bed0] Engine exception thrown while sending merge command: org.ovirt.engine.core.common.errors.EngineException: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to MergeVDS, error = Merge failed, code = 52 (Failed with error mergeErr and code 52) Caused by: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to MergeVDS, error = Merge failed, code = 52 <driver name='qemu' error_policy='report'/> <driver name='qemu' type='qcow2' cache='none' error_policy='stop' io='threads'/> 2020-07-22 16:40:39,659+02 ERROR [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedExecutorService-commandCoordinator-Thread-3) [264b0047-5aa6-4380-9d32-eb328fd6bed0] Failed to live merge. Top volume c757e740-9013-4ae0-901d-316932f4af0e is still in qemu chain [ebe50730-dec3-4f29-8a38-9ae7c59f2aef, c757e740-9013-4ae0-901d-316932f4af0e] 2020-07-22 16:40:41,524+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-58) [264b0047-5aa6-4380-9d32-eb328fd6bed0] Command id: 'e0b2bce7-afe0-4955-ae46-38bcb8719852 failed child command status for step 'MERGE_STATUS' 2020-07-22 16:40:42,597+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-53) [264b0047-5aa6-4380-9d32-eb328fd6bed0] Merging of snapshot 'ef8f7e06-e48c-4a8c-983c-64e3d4ebfcf9' images 'ebe50730-dec3-4f29-8a38-9ae7c59f2aef'..'c757e740-9013-4ae0-901d-316932f4af0e' 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. 2020-07-22 16:40:42,603+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-53) [264b0047-5aa6-4380-9d32-eb328fd6bed0] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' with failure. 2020-07-22 16:40:43,679+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-15) [264b0047-5aa6-4380-9d32-eb328fd6bed0] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 2020-07-22 16:40:43,774+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-15) [264b0047-5aa6-4380-9d32-eb328fd6bed0] EVENT_ID: USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot 'Auto-generated for Export To OVA' for VM 'Adhoc'. VDSM on hypervisor 2020-07-22 14:14:30,220+0200 ERROR (jsonrpc/5) [virt.vm] (vmId='14283e6d-c3f0-4011-b90f-a1272f0fbc10') Live merge failed (job: e59c54d9-b8d3-44d0-9147-9dd40dff57b9) (vm:5381) if ret == -1: raise libvirtError ('virDomainBlockCommit() failed', dom=self) libvirt.libvirtError: internal error: qemu block name 'json:{"backing": {"driver": "qcow2", "file": {"driver": "file", "filename": "/rhev/data-center/mnt/10.12.0.9:_exports_data/9a12f1b2-5378-46cc-964d-3575695e823f/images/3206de41-ccdc-4f2d-a968-5e4da6c2ca3e/bb3aed4b-fc41-456a-9c18-1409a9aa6d14"}}, "driver": "qcow2", "file": {"driver": "file", "filename": "/rhev/data-center/mnt/10.12.0.9:_exports_data/9a12f1b2-5378-46cc-964d-3575695e823f/images/3206de41-ccdc-4f2d-a968-5e4da6c2ca3e/3995b256-2afb-4853-9360-33d0c12e5fd1"}}' doesn't match expected '/rhev/data-center/mnt/10.12.0.9: _exports_data/9a12f1b2-5378-46cc-964d-3575695e823f/images/3206de41-ccdc-4f2d-a968-5e4da6c2ca3e/3995b256-2afb-4853-9360-33d0c12e5fd1' 2020-07-22 14:14:30,234+0200 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call VM.merge failed (error 52) in 0.17 seconds (__init__:312) 2020-07-22 14:17:28,798+0200 INFO (jsonrpc/2) [api] FINISH getStats error=Virtual machine does not exist: {'vmId': '698d486c-edbf-4e28-a199-31a2e27bd808'} (api:129) 2020-07-22 14:17:28,798+0200 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call VM.getStats failed (error 1) in 0.00 seconds (__init__:312) Also in log, INFO (jsonrpc/1) [api.virt] FINISH getStats return={'status': {'code': 1, 'message': "Virtual machine does not exist: But is is there and accessible Any advice here? Henri ovirt 4.4.0.3-1.el8 OS Version: RHEL - 8 - 1.1911.0.9.el8 OS Description: oVirt Node 4.4.0 Kernel Version: 4.18.0 - 147.8.1.el8_1.x86_64 KVM Version: 4.1.0 - 23.el8.1 LIBVIRT Version: libvirt-5.6.0-10.el8 VDSM Version: vdsm-4.40.16-1.el8 SPICE Version: 0.14.2 - 1.el8 GlusterFS Version: glusterfs-7.5-1.el8 CEPH Version: librbd1-12.2.7-9.el8 Open vSwitch Version: openvswitch-2.11.1-5.el8 Nmstate Version: nmstate-0.2.10-1.el8

3 4

Re: Issue with ovirt 4.4 after doing some incremental backups.
by Eyal Shenitzky 28 Jul '20

28 Jul '20

Hi Łukasz, Can you please provide vdsm.log and libvirt.log? On Tue, 28 Jul 2020 at 16:05, Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > Hello, > > After doing a few vm backups, something breaks and I am unable to perform > any operations. I cannot do incremental backups and even full backups > doesn't work. I have this issue third time. I don't know how to fix this so > I am currently making new vms for testing purposes > > VDSM ovirt44-h2.storware.local command StartVmBackupVDS failed: Backup > Error: {'vm_id': '116aa6eb-31a1-43db-9b1e-ad6e32fb9260', 'backup': > <vdsm.virt.backup.BackupConfig object at 0x7f42602bba20>, 'reason': "Error > starting backup: internal error: unable to execute QEMU command > 'transaction': Dirty bitmap 'ef0dfe55-c08c-4d9e-ad32-d6b6d5cbdac6' not > found"} > > > Best Regards, > > Łukasz Kołaciński > > Junior Java Developer > > e-mail: l.kolacinski(a)storware.eu > <m.helbert(a)storware.eu> > > > > > *[image: STORWARE]* <http://www.storware.eu/> > > > > *ul. Leszno 8/44 01-192 Warszawa www.storware.eu > <https://www.storware.eu/>* > > *[image: facebook]* <https://www.facebook.com/storware> > > *[image: twitter]* <https://twitter.com/storware> > > *[image: linkedin]* <https://www.linkedin.com/company/storware> > > *[image: Storware_Stopka_09]* > <https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> > > > > *Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa > 000510131* *, NIP 5213672602.** Wiadomość ta jest przeznaczona jedynie > dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne > i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, > przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub > podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub > podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez > pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie > tej wiadomości z wszelkich komputerów. **This message is intended only > for the person or entity to which it is addressed and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended recipient > is prohibited. If you have received this message in error, please contact > the sender and remove the material from all of your computer systems.* > > -- Regards, Eyal Shenitzky

1 0