- Users - oVirt List Archives

Re: why cannot set the power management proxy server ?
by Tommy Sway 27 Sep '21

27 Sep '21

I set lanplus=1, and then it ok. What’s meaning of it ? From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Friday, September 24, 2021 3:13 AM To: Tommy Sway <sz_cuitao(a)163.com> Subject: Re: [ovirt-users] why cannot set the power management proxy server ? Try adding 'lanplus=0' into the options. Best Regards, Strahil Nikolov On Thu, Sep 23, 2021 at 5:59, Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > wrote: I can use ipmitool to send commands from any KVM host to other hosts in the same cluster. However, an internal error is reported when CONFIGURING power proxy on engine. How can I locate the fault? _______________________________________________ Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@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/62XDSQNJTOPRK…

2 3

Hypervisor broken
by Hans Scheffers 27 Sep '21

27 Sep '21

Hi all, I am new here, been searching the mailing list on a regular base when I encountered problems and till now I always was able to keep the system up & running. As said... till now... I have oVirt at home, and I have about 7 vm's running on it. Lately I have had some troubles with my electricity, which results in a complete power outage on a irregular base. Yesterday I had a power outage which left the system unbootable with the following errors: error: ../../grub-core/loader/i386/pc/linux.c:170:invalid magic number. error: ../../grub-core/loader/i386/pc/linux.c:1418:you need to load the kernel first. Press any key to continue Normally this can be solved following https://access.redhat.com/solutions/5829141, but his time also the files in /boot had a size of 0 bytes. So basically i did not have a working kernel on the system anymore. https://www.thegeekdiary.com/centos-rhel-7-how-to-install-kernel-from-res... does work for CentOS 8 also, but the ovirt 4.8 iso does not have the same directory structure. Using CentOS 8 installs a kernel, but not a bootable system. When booting the ovirt kernel, I get a rescue prompt with the following error: "Warning: /dev/onn/ovirt-node-ng-4.4.6.3-0.20210518.0+1 does not exist" Is there a way i can start the installer in troubleshooting mode so I can do a reinstall and keep the current configuration or can I just reinstall and import the current datacenter in it?

1 0

Hosted Engine cluster version compatib.
by Andrea Chierici 24 Sep '21

24 Sep '21

Dear all, I have just updated my ovirt installation, with self hosted engine, from 4.4.5 to 4.4.8.5-1. Everything went smoothly and in a few minutes the system was back up and running. A little issue is still puzzling me. I am asked to update from 4.5 to 4.6 the cluster and data center compatibility level. When I try to issue the command from the cluster config I get this error: > Error while executing action: Cannot update cluster because the update > triggered update of the VMs/Templates and it failed for the following: > HostedEngine. To fix the issue, please go to each of them, edit, > change the Custom Compatibility Version (or other fields changed > previously in the cluster dialog) and press OK. If the save does not > pass, fix the dialog validation. After successful cluster update, you > can revert your Custom Compatibility Version change (or other > changes). If the problem still persists, you may refer to the > engine.log file for further details. It's very strange because the config of the hostedengine is "plain" and there are no constrains on compatibility version, as you can see in this picture: In any case, if I try to force compatibility with 4.6 I get this error: > Error while executing action: > > HostedEngine: > > There was an attempt to change Hosted Engine VM values that are > locked. So I am stuck. Not a big deal at the moment, but sooner or later I will have to do this upgrade and I don't know where I am wrong. Can anybody give a clue? Thanks in advance, Andrea -- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --

5 15

Ooops! in last step of Hyperconverged deployment
by Harry O 24 Sep '21

24 Sep '21

Hi, In the second engine dep run in Hyperconverged deployment I get red "Ooops!" in cockpit. I think it fails on some networking setup. The first oVirt Node says "Hosted Engine is up!" but the other nodes is not added to HostedEngine yet. There is no network connectivity to the Engine outside node1, I can ssh to engine from node1 on the right IP-address. Please tell what logs I should pull.

2 21

how to automatically join AD for windows guest
by wharton wang 24 Sep '21

24 Sep '21

Hi there, anyone could help to tell how to configure sysprep or something on oVirt engine, so it makes vm automatically join active directory . TIA.

1 0

About the vm memory limit
by Tommy Sway 24 Sep '21

24 Sep '21

I would like to ask if there is any limit on the memory size of virtual machines, or performance curve or something like that? As long as there is memory on the physical machine, the more virtual machines the better? In our usage scenario, there are many virtual machines with databases, and their memory varies greatly. For some virtual machines, 4G memory is enough, while for some virtual machines, 64GB memory is needed. I want to know what is the best use of memory for a virtual machine, since the virtual machine is just a QEMU emulation process on a physical machine, and I worry that it is not using as much memory as a physical machine. Understand this so that we can develop guidelines for optimal memory usage scenarios for virtual machines. Thank you!

1 0

about the power management of the hosts
by Tommy Sway 23 Sep '21

23 Sep '21

Everybody, hi: I would like to ask, after the configuration of power management on the host, under what circumstances will work? That is, when does the engine send a request to the IPMI module to restart the power supply? Is it necessary to configure power management modules in the production environment? Are there any risks? Thanks!

4 12

oVirt 4.4.8 Async update #4
by Sandro Bonazzola 23 Sep '21

23 Sep '21

oVirt 4.4.8 Async update #4 On September 23rd 2021 the oVirt project released an async update to the following packages: - ovirt-engine 4.4.8.6 Fixing the following bugs: Bug 2005221 <https://bugzilla.redhat.com/show_bug.cgi?id=2005221> - Cluster compatibility version upgrade from 4.5 to 4.6 -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Sparse VMs from Templates - Storage issues
by Shantur Rathore 23 Sep '21

23 Sep '21

Hi all, I have a setup as detailed below - iSCSI Storage Domain - Template with Thin QCOW2 disk - Multiple VMs from Template with Thin disk oVirt Node 4.4.4 When the VMs boots up it downloads some data to it and that leads to increase in volume size. I see that every few seconds the VM gets paused with "VM X has been paused due to no Storage space error." and then after few seconds "VM X has recovered from paused back to up" Sometimes after a many pause and recovery the VM dies with "VM X is down with error. Exit message: Lost connection with qemu process." and I have to restart the VMs. My questions. 1. How to work around this dying VM? 2. Is there a way to use sparse disks without VM being paused again and again? Thanks in advance. Shantur

6 13

about the vm disk type
by Tommy Sway 23 Sep '21

23 Sep '21

When I create the VM's image disk, I am not asked to select the following type of disk. What is the default value ? Thanks. QCOW2 Formatted Virtual Machine Storage QCOW2 is a storage format for virtual disks. QCOW stands for QEMU copy-on-write. The QCOW2 format decouples the physical storage layer from the virtual layer by adding a mapping between logical and physical blocks. Each logical block is mapped to its physical offset, which enables storage over-commitment and virtual machine snapshots, where each QCOW volume only represents changes made to an underlying virtual disk. The initial mapping points all logical blocks to the offsets in the backing file or volume. When a virtual machine writes data to a QCOW2 volume after a snapshot, the relevant block is read from the backing volume, modified with the new information and written into a new snapshot QCOW2 volume. Then the map is updated to point to the new place. Raw The raw storage format has a performance advantage over QCOW2 in that no formatting is applied to virtual disks stored in the raw format. Virtual machine data operations on virtual disks stored in raw format require no additional work from hosts. When a virtual machine writes data to a given offset in its virtual disk, the I/O is written to the same offset on the backing file or logical volume. Raw format requires that the entire space of the defined image be preallocated unless using externally managed thin provisioned LUNs from a storage array.

3 9

why cannot set the power management proxy server ?
by Tommy Sway 23 Sep '21

23 Sep '21

I can use ipmitool to send commands from any KVM host to other hosts in the same cluster. However, an internal error is reported when CONFIGURING power proxy on engine. How can I locate the fault?

1 0

about the OVF_STORE and the xleases volume
by Tommy Sway 23 Sep '21

23 Sep '21

I wonder if the xleases volume mentioned here refers to ovf_store ? * A new xleases volume to support VM leases - this feature adds the ability to acquire a lease per virtual machine on shared storage without attaching the lease to a virtual machine disk. A VM lease offers two important capabilities: * Avoiding split-brain. * Starting a VM on another host if the original host becomes non-responsive, which improves the availability of HA VMs.

2 5

[ANN] oVirt 4.4.8 Async update #1
by Sandro Bonazzola 22 Sep '21

22 Sep '21

oVirt 4.4.8 Async update #1 On August 26th 2021 the oVirt project released an async update to the following packages: - ovirt-ansible-collection 1.6.2 - ovirt-engine 4.4.8.5 - ovirt-release44 4.4.8.1 - oVirt Node 4.4.8.1 - oVirt Appliance 4.4-20210826 Fixing the following bugs: - Bug 1947709 <https://bugzilla.redhat.com/show_bug.cgi?id=1947709> - [IPv6] HostedEngineLocal is an isolated libvirt network, breaking upgrades from 4.3 - Bug 1966873 <https://bugzilla.redhat.com/show_bug.cgi?id=1966873> - [RFE] Create Ansible role for remove stale LUNs example remove_mpath_device.yml - Bug 1997663 <https://bugzilla.redhat.com/show_bug.cgi?id=1997663> - Keep cinbderlib dependencies optional for 4.4.8 - Bug 1996816 <https://bugzilla.redhat.com/show_bug.cgi?id=1996816> - Cluster upgrade fails with: 'OAuthException invalid_grant: The provided authorization grant for the auth code has expired. oVirt Node Changes: - Consume above oVirt updates - GlusterFS 8.6: https://docs.gluster.org/en/latest/release-notes/8.6/ - Fixes for: - CVE-2021-22923 <https://access.redhat.com/security/cve/CVE-2021-22923> curl: Metalink download sends credentials - CVE-2021-22922 <https://access.redhat.com/security/cve/CVE-2021-22922> curl: Content not matching hash in Metalink is not being discarded Full diff list: --- ovirt-node-ng-image-4.4.8.manifest-rpm 2021-08-19 07:57:44.081590739 +0200 +++ ovirt-node-ng-image-4.4.8.1.manifest-rpm 2021-08-27 08:11:54.863736688 +0200 @@ -2,7 +2,7 @@ -ModemManager-glib-1.10.8-3.el8.x86_64 -NetworkManager-1.32.6-1.el8.x86_64 -NetworkManager-config-server-1.32.6-1.el8.noarch -NetworkManager-libnm-1.32.6-1.el8.x86_64 -NetworkManager-ovs-1.32.6-1.el8.x86_64 -NetworkManager-team-1.32.6-1.el8.x86_64 -NetworkManager-tui-1.32.6-1.el8.x86_64 +ModemManager-glib-1.10.8-4.el8.x86_64 +NetworkManager-1.32.8-1.el8.x86_64 +NetworkManager-config-server-1.32.8-1.el8.noarch +NetworkManager-libnm-1.32.8-1.el8.x86_64 +NetworkManager-ovs-1.32.8-1.el8.x86_64 +NetworkManager-team-1.32.8-1.el8.x86_64 +NetworkManager-tui-1.32.8-1.el8.x86_64 @@ -94 +94 @@ -curl-7.61.1-18.el8.x86_64 +curl-7.61.1-18.el8_4.1.x86_64 @@ -106,4 +106,4 @@ -device-mapper-1.02.177-5.el8.x86_64 -device-mapper-event-1.02.177-5.el8.x86_64 -device-mapper-event-libs-1.02.177-5.el8.x86_64 -device-mapper-libs-1.02.177-5.el8.x86_64 +device-mapper-1.02.177-6.el8.x86_64 +device-mapper-event-1.02.177-6.el8.x86_64 +device-mapper-event-libs-1.02.177-6.el8.x86_64 +device-mapper-libs-1.02.177-6.el8.x86_64 @@ -140,36 +140,36 @@ -fence-agents-all-4.2.1-74.el8.x86_64 -fence-agents-amt-ws-4.2.1-74.el8.noarch -fence-agents-apc-4.2.1-74.el8.noarch -fence-agents-apc-snmp-4.2.1-74.el8.noarch -fence-agents-bladecenter-4.2.1-74.el8.noarch -fence-agents-brocade-4.2.1-74.el8.noarch -fence-agents-cisco-mds-4.2.1-74.el8.noarch -fence-agents-cisco-ucs-4.2.1-74.el8.noarch -fence-agents-common-4.2.1-74.el8.noarch -fence-agents-compute-4.2.1-74.el8.noarch -fence-agents-drac5-4.2.1-74.el8.noarch -fence-agents-eaton-snmp-4.2.1-74.el8.noarch -fence-agents-emerson-4.2.1-74.el8.noarch -fence-agents-eps-4.2.1-74.el8.noarch -fence-agents-heuristics-ping-4.2.1-74.el8.noarch -fence-agents-hpblade-4.2.1-74.el8.noarch -fence-agents-ibmblade-4.2.1-74.el8.noarch -fence-agents-ifmib-4.2.1-74.el8.noarch -fence-agents-ilo-moonshot-4.2.1-74.el8.noarch -fence-agents-ilo-mp-4.2.1-74.el8.noarch -fence-agents-ilo-ssh-4.2.1-74.el8.noarch -fence-agents-ilo2-4.2.1-74.el8.noarch -fence-agents-intelmodular-4.2.1-74.el8.noarch -fence-agents-ipdu-4.2.1-74.el8.noarch -fence-agents-ipmilan-4.2.1-74.el8.noarch -fence-agents-kdump-4.2.1-74.el8.x86_64 -fence-agents-mpath-4.2.1-74.el8.noarch -fence-agents-redfish-4.2.1-74.el8.x86_64 -fence-agents-rhevm-4.2.1-74.el8.noarch -fence-agents-rsa-4.2.1-74.el8.noarch -fence-agents-rsb-4.2.1-74.el8.noarch -fence-agents-sbd-4.2.1-74.el8.noarch -fence-agents-scsi-4.2.1-74.el8.noarch -fence-agents-vmware-rest-4.2.1-74.el8.noarch -fence-agents-vmware-soap-4.2.1-74.el8.noarch -fence-agents-wti-4.2.1-74.el8.noarch +fence-agents-all-4.2.1-75.el8.x86_64 +fence-agents-amt-ws-4.2.1-75.el8.noarch +fence-agents-apc-4.2.1-75.el8.noarch +fence-agents-apc-snmp-4.2.1-75.el8.noarch +fence-agents-bladecenter-4.2.1-75.el8.noarch +fence-agents-brocade-4.2.1-75.el8.noarch +fence-agents-cisco-mds-4.2.1-75.el8.noarch +fence-agents-cisco-ucs-4.2.1-75.el8.noarch +fence-agents-common-4.2.1-75.el8.noarch +fence-agents-compute-4.2.1-75.el8.noarch +fence-agents-drac5-4.2.1-75.el8.noarch +fence-agents-eaton-snmp-4.2.1-75.el8.noarch +fence-agents-emerson-4.2.1-75.el8.noarch +fence-agents-eps-4.2.1-75.el8.noarch +fence-agents-heuristics-ping-4.2.1-75.el8.noarch +fence-agents-hpblade-4.2.1-75.el8.noarch +fence-agents-ibmblade-4.2.1-75.el8.noarch +fence-agents-ifmib-4.2.1-75.el8.noarch +fence-agents-ilo-moonshot-4.2.1-75.el8.noarch +fence-agents-ilo-mp-4.2.1-75.el8.noarch +fence-agents-ilo-ssh-4.2.1-75.el8.noarch +fence-agents-ilo2-4.2.1-75.el8.noarch +fence-agents-intelmodular-4.2.1-75.el8.noarch +fence-agents-ipdu-4.2.1-75.el8.noarch +fence-agents-ipmilan-4.2.1-75.el8.noarch +fence-agents-kdump-4.2.1-75.el8.x86_64 +fence-agents-mpath-4.2.1-75.el8.noarch +fence-agents-redfish-4.2.1-75.el8.x86_64 +fence-agents-rhevm-4.2.1-75.el8.noarch +fence-agents-rsa-4.2.1-75.el8.noarch +fence-agents-rsb-4.2.1-75.el8.noarch +fence-agents-sbd-4.2.1-75.el8.noarch +fence-agents-scsi-4.2.1-75.el8.noarch +fence-agents-vmware-rest-4.2.1-75.el8.noarch +fence-agents-vmware-soap-4.2.1-75.el8.noarch +fence-agents-wti-4.2.1-75.el8.noarch @@ -215,7 +215,7 @@ -glusterfs-8.5-2.el8.x86_64 -glusterfs-cli-8.5-2.el8.x86_64 -glusterfs-client-xlators-8.5-2.el8.x86_64 -glusterfs-events-8.5-2.el8.x86_64 -glusterfs-fuse-8.5-2.el8.x86_64 -glusterfs-geo-replication-8.5-2.el8.x86_64 -glusterfs-server-8.5-2.el8.x86_64 +glusterfs-8.6-1.el8.x86_64 +glusterfs-cli-8.6-1.el8.x86_64 +glusterfs-client-xlators-8.6-1.el8.x86_64 +glusterfs-events-8.6-1.el8.x86_64 +glusterfs-fuse-8.6-1.el8.x86_64 +glusterfs-geo-replication-8.6-1.el8.x86_64 +glusterfs-server-8.6-1.el8.x86_64 @@ -301,5 +301,5 @@ -kernel-4.18.0-326.el8.x86_64 -kernel-core-4.18.0-326.el8.x86_64 -kernel-modules-4.18.0-326.el8.x86_64 -kernel-tools-4.18.0-326.el8.x86_64 -kernel-tools-libs-4.18.0-326.el8.x86_64 +kernel-4.18.0-331.el8.x86_64 +kernel-core-4.18.0-331.el8.x86_64 +kernel-modules-4.18.0-331.el8.x86_64 +kernel-tools-4.18.0-331.el8.x86_64 +kernel-tools-libs-4.18.0-331.el8.x86_64 @@ -310 +310 @@ -kmod-kvdo-6.2.5.65-79.el8.x86_64 +kmod-kvdo-6.2.5.72-79.el8.x86_64 @@ -363 +363 @@ -libcurl-7.61.1-18.el8.x86_64 +libcurl-7.61.1-18.el8_4.1.x86_64 @@ -381,6 +381,6 @@ -libgfapi0-8.5-2.el8.x86_64 -libgfchangelog0-8.5-2.el8.x86_64 -libgfrpc0-8.5-2.el8.x86_64 -libgfxdr0-8.5-2.el8.x86_64 -libglusterd0-8.5-2.el8.x86_64 -libglusterfs0-8.5-2.el8.x86_64 +libgfapi0-8.6-1.el8.x86_64 +libgfchangelog0-8.6-1.el8.x86_64 +libgfrpc0-8.6-1.el8.x86_64 +libgfxdr0-8.6-1.el8.x86_64 +libglusterd0-8.6-1.el8.x86_64 +libglusterfs0-8.6-1.el8.x86_64 @@ -416 +415,0 @@ -libmetalink-0.1.3-7.el8.x86_64 @@ -558,2 +557,2 @@ -lvm2-2.03.12-5.el8.x86_64 -lvm2-libs-2.03.12-5.el8.x86_64 +lvm2-2.03.12-6.el8.x86_64 +lvm2-libs-2.03.12-6.el8.x86_64 @@ -641 +640 @@ -ovirt-ansible-collection-1.6.0-1.el8.noarch +ovirt-ansible-collection-1.6.2-1.el8.noarch @@ -649 +648 @@ -ovirt-node-ng-image-update-placeholder-4.4.8-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.8.1-1.el8.noarch @@ -657,2 +656,2 @@ -ovirt-release-host-node-4.4.8-1.el8.noarch -ovirt-release44-4.4.8-1.el8.noarch +ovirt-release-host-node-4.4.8.1-1.el8.noarch +ovirt-release44-4.4.8.1-1.el8.noarch @@ -665,3 +664,3 @@ -pacemaker-cluster-libs-2.1.0-5.el8.x86_64 -pacemaker-libs-2.1.0-5.el8.x86_64 -pacemaker-schemas-2.1.0-5.el8.noarch +pacemaker-cluster-libs-2.1.0-6.el8.x86_64 +pacemaker-libs-2.1.0-6.el8.x86_64 +pacemaker-schemas-2.1.0-6.el8.noarch @@ -773 +772 @@ -python3-gluster-8.5-2.el8.x86_64 +python3-gluster-8.6-1.el8.x86_64 @@ -835 +834 @@ -python3-perf-4.18.0-326.el8.x86_64 +python3-perf-4.18.0-331.el8.x86_64 @@ -935,2 +934,2 @@ -selinux-policy-3.14.3-75.el8.noarch -selinux-policy-targeted-3.14.3-75.el8.noarch +selinux-policy-3.14.3-76.el8.noarch +selinux-policy-targeted-3.14.3-76.el8.noarch @@ -941 +940 @@ -shadow-utils-4.6-13.el8.x86_64 +shadow-utils-4.6-14.el8.x86_64 @@ -948 +947 @@ -sos-4.1-4.el8.noarch +sos-4.1-5.el8.noarch -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 1

Frequent events seen like VM "vmname" is not responding
by manoj.sharma99765＠gmail.com 22 Sep '21

22 Sep '21

I am using oVirt Open Virtualization Manager Software Version:4.4.6.8-1.el8 and we have single node running on oVirt Node 4.4.6. We are facing slowness while using VM and also we face connection reset issue between VM and Target servers ( Nexus ) We are getting below logs in ovirt manager events VM "vmname" is not responding Getting this for all the running VMs . We checked resources and utilization of the node everything seems very normal. Could you please guide on how can we solve/debug further on this ?

2 4

Cannot activate a Storage Domain after an oVirt crash
by nicolas＠devels.es 21 Sep '21

21 Sep '21

Hi, We're running oVirt 4.3.8 and we recently had a oVirt crash after moving too much disks between storage domains. Concretely, one of the Storage Domains reports status "Unknown", "Total/Free/Guaranteed free spaces" are "[N/A]". After trying to activate it in the Domain Center we see messages like these from all of the hosts: VDSM hostX command GetVGInfoVDS failed: Volume Group does not exist: (u'vg_uuid: Usi3y8-S4eq-EXtl-FA58-MA3K-b4vE-4d9SCp',) I tried putting the Storage Domain in maintenance and it fails with messages like: Storage Domain iaasb13 (Data Center KVMRojo) was deactivated by system because it's not visible by any of the hosts. Failed to update OVF disks 8661acd1-d1c4-44a0-a4d4-ddee834844e9, OVF data isn't updated on those OVF stores (Data Center KVMRojo, Storage Domain iaasb13). Failed to update VMs/Templates OVF data for Storage Domain iaasb13 in Data Center KVMRojo. I'm sure the storage domain backend is up and running, and the LUN being exported. Any hints how can I debug this problem and restore the Storage Domain? Thanks.

4 11

Re: Failed to activate Storage Domain --- ovirt 4.2
by fabian.rapetti＠gmail.com 20 Sep '21

20 Sep '21

Hi all. I'm using Ovrit 4.3.10 two nodes cluster and facing the same error (second metadata area corruption). Does anybody know if there is a solution for that? Our software include: lvm2-2.02.186-7.el7_8.2.x86_64 Virt Node 4.3.10 kernel 3.10.0-1127.8.2.el7.x86_64 device-mapper-multipath-libs-0.4.9-131.el7.x86_64 libvirt-4.5.0-33.el7_8.1.x86_64 Thanks in advance

2 2

How to renew an Ovirt host certificate (vdsmcert.pem) ?
by noua.toukourou＠uni.lu 19 Sep '21

19 Sep '21

Hi, I have an Ovirt host that the vdsmcert.pem expired. The problem is that host contains the self-hosted engine. How to renew the certificate without breaking the self-hosted engine ? Thanks,

3 3

Getting issue in finalize section after disk successfully uploaded
by avishek.sarkar＠broadcom.com 19 Sep '21

19 Sep '21

I have used upload-disk.py to upload qcow2 image to data center...however getting below errror ./upload-disk.py --engine-url 'https://xyz.net' --username='xyz(a)abc.net' --password-file=password --sd-name='SEC-ABC' --cafile='/home/jenkins/crt/ca.crt' --disk-format="qcow2" --disk-sparse image-XYZ Checking image... Image format: qcow2 Disk format: cow Disk content type: data Disk provisioned size: 10737418240 Disk initial size: 5526847488 Disk name: image-avishek.qcow2 Connecting... Creating disk... Creating transfer session... Uploading image... [ 100.00% ] 10.00 GiB, 11.34 seconds, 903.09 MiB/s Finalizing transfer session... Traceback (most recent call last): File "./upload-disk.py", line 300, in <module> transfer_service.finalize() File "/usr/lib64/python3.6/site-packages/ovirtsdk4/services.py", line 13971, in finalize return self._internal_action(action, 'finalize', None, headers, query, wait) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error ovirtsdk4.AuthError: Fault reason is "Operation Failed". Fault detail is "[User is not authorized to perform this action.]". HTTP response code is 403.

2 1

I'm in trouble....
by Wesley Stewart 18 Sep '21

18 Sep '21

Luckily this is for a home lab and nothing critical is lost. However I was trying to change the subnet my host was on. And I found out that you cant do that. So I reverted back but my hosted engine wasnt happy about my NFS mounts. so I did a engine-cleanup and an engine-setup. Went through the prompts and thought nothing of it. I logged back into ovirt, and everything looks like it was a brand new install. No VMs or anything. I believe I have a fairly recent backup somewhere... trying to track that down, but it's not looking good. Currently running 4.3.10. I have been planning out my 4.4 upgrade anyways. I would prefer to not start from scratch... but if I do it is not the end of the world, will just take a lot more time. Looking for some guidance! Thank you.

2 5

Re: [External] : about the password of the engine host and worker KVM hosts
by Tommy Sway 18 Sep '21

18 Sep '21

Thank you! From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of Marcos Sungaila Sent: Friday, September 17, 2021 11:51 PM To: Tommy Sway <sz_cuitao(a)163.com>; users(a)ovirt.org Subject: [ovirt-users] Re: [External] : about the password of the engine host and worker KVM hosts Hi Tommy, Yes, you can change root password on all hosts with no problem. Your cluster will keep working fine. Regards Marcos From: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Sent: sexta-feira, 17 de setembro de 2021 06:12 To: users(a)ovirt.org <mailto:users@ovirt.org> Subject: [External] : [ovirt-users] about the password of the engine host and worker KVM hosts I have successfully installed and deployed OLVM, where the Engine uses a separate physical server and the virtual machines work on other worker servers. Due to the company's internal security policy, I now need to change the root user password for all servers. Is that ok? Will cluster running be affected? Thanks!

1 0

Re: about the password of the engine host and worker KVM hosts
by Tommy Sway 18 Sep '21

18 Sep '21

Thank you! From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of Matthew.Stier(a)fujitsu.com Sent: Friday, September 17, 2021 11:45 PM To: Tommy Sway <sz_cuitao(a)163.com>; users(a)ovirt.org Subject: [ovirt-users] Re: about the password of the engine host and worker KVM hosts My understanding, is that OLVM/oVirt use the root password to push it's SSH credentials at first login. Once that is done, all other SSH access is though those credentials. You should be able to change the root password without issue. From: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Sent: Friday, September 17, 2021 4:12 AM To: users(a)ovirt.org <mailto:users@ovirt.org> Subject: [ovirt-users] about the password of the engine host and worker KVM hosts I have successfully installed and deployed OLVM, where the Engine uses a separate physical server and the virtual machines work on other worker servers. Due to the company's internal security policy, I now need to change the root user password for all servers. Is that ok? Will cluster running be affected? Thanks!

1 0

REST API import VM from Export Domain
by christian.peater＠gmx.de 18 Sep '21

18 Sep '21

i'm using OLVM 4.3.10 oVirt and i'm trying to import a VM from the Export Storage Domain with the REST API. curl command is: curl \ -X POST \ --header "Version:4" \ --header "Accept:application/xml" \ --header "Content-type:application/xml" \ --user $_OLVM_USERNAME:$_OLVM_PASSWORD \ --data ' <action> <storage_domain> <name>'$DST_SD'</name> </storage_domain> <cluster> <name>'$CLUSTER'</name> </cluster> <clone>true</clone> <vm> <name>'$VM_NAME'</name> </vm> </action> ' https://$_OLVM_HOSTNAME/ovirt-engine/api/storagedomains/$SRC_SD_ID/vms/$SD_VM_ID/import Response is: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> </p> </body></html> When i use the same syntax to just get a list of importable VMs there is no error and the Response is a xml entity. Any idea?

2 3

oVirt Node - master - CentOS Stream 9 based ISO available for testing
by Sandro Bonazzola 17 Sep '21

17 Sep '21

Hi, I'm still working on it but I have a first ISO ready for giving a first run at https://resources.ovirt.org/pub/ovirt-master-snapshot-static/iso/ovirt-node… Known limitations: - No hosted engine setup available - No ansible available - No collectd support - No cinderlib support Everything else should be there but it's totally untested. Help giving it a try and providing feedback is appreciated. Thanks -- 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.*

3 7

Slow mirrors, installation fails
by Andrea Chierici 17 Sep '21

17 Sep '21

Dear all, I am trying to install a new ovirt deployment with self hosted engine. I've been trying since yesterday but it always fails. On the deployment host I get this error: > [ ERROR ] Hosted Engine deployment failed: please check the logs for > the issue, fix accordingly or re-deploy from scratch. > Log file is located at > /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20210917144651-ecm06v.log I connected to the console of the hosted engine and in dnf.log I found this: > 2021-09-17T15:05:58+0200 WARNING Errors during downloading metadata > for repository 'ovirt-4.4': > - Curl error (28): Timeout was reached for > https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/repodata/541a523f620cf26f… > [Operation too slow. Less than 1000 bytes/sec transferred the last 30 > seconds] > - Curl error (28): Timeout was reached for > https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/repodata/541a523f620cf26f… > [Connection timed out after 30000 milliseconds] > - Curl error (28): Timeout was reached for > https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/repodata/541a523f620cf26f… > [Operation timed out after 30000 milliseconds with 0 out of 0 bytes > received] > - Curl error (28): Timeout was reached for > https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/repodata/repomd.xml > [Operation timed out after 30001 milliseconds with 0 out of 0 bytes > received] > - Curl error (28): Timeout was reached for > https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/repodata/repomd.xml > [Connection timed out after 30000 milliseconds] > [root@testovirt-sgsi log]# yum update > Latest oVirt 4.4 Release 4.5 kB/s | 3.0 kB > 00:00 > Latest oVirt 4.4 Release 0.0 B/s | 0 B 01:30 > Errors during downloading metadata for repository 'ovirt-4.4': > - Curl error (28): Timeout was reached for > https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/repodata/541a523f620cf26f… > [Operation timed out after 30000 milliseconds with 0 out of 0 bytes > received] > - Curl error (28): Timeout was reached for > https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/repodata/541a523f620cf26f… > [Connection timed out after 30000 milliseconds] > - Curl error (28): Timeout was reached for > https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/repodata/90e6cdef058ae65c… > [Operation timed out after 30000 milliseconds with 0 out of 0 bytes > received] > Error: Failed to download metadata for repo 'ovirt-4.4': Yum repo > downloading error: Downloading error(s): > repodata/541a523f620cf26f4ca92baf6ee18403c1b0176d480f479bd7032efbb369e95f-primary.xml.gz > - Cannot download, all mirrors were already tried without success; > repodata/90e6cdef058ae65c35cd44ade10bc112be9262c221e4af3a477fd5063a90a86b-filelists.xml.gz > - Cannot download, all mirrors were already tried without success Indeed the speed of the mirrors seems quite low and even on another ovirt deployment I have, the metadata download speed is around 40kb, while for all other centos repos it is at least 10MB. Am I missing something? Thanks, Andrea -- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --

1 0

about the password of the engine host and worker KVM hosts
by Tommy Sway 17 Sep '21

17 Sep '21

I have successfully installed and deployed OLVM, where the Engine uses a separate physical server and the virtual machines work on other worker servers. Due to the company's internal security policy, I now need to change the root user password for all servers. Is that ok? Will cluster running be affected? Thanks!

4 3