April 2023 - Users - oVirt List Archives

ovirt-engine - developer mode installation
by yongshengmaa＠126.com 19 Apr '23

19 Apr '23

Hello , I'm doing a developer mode installation for ovirt-engine. I'd like to install it based on CentOS 8 Stream, but no matched version of postgresql packages are provided. Which CentOS version should I start this work? Sincerely, Yongsheng

2 9

Hosted deployment difficulties, am I missing anything?
by Xavier Lauzon 17 Apr '23

17 Apr '23

Hi everyone, Last week I had a server go down, which was the only node in my deployment handling the hosted engine (ironically, this happened right when we were planning to move the he to HA). As a result, we have been trying to redeploy the engine but have had no success. We have tried installing on every ovirt node ng stable version from 4.4.10-4.5.4.el8 and .el9. Unfortunately, each time we try to deploy the engine from scratch, we receive either of two errors depending on the version. Some versions fail to create the default network, which can be manually fixed but leads to the following error. The deployment goes until the "Waiting for host to be up" stage; however, it fails without any information as to why. I've sifted through virtually all the logs but can't find the root cause. I am aware of an ongoing issue in the ansible collection (https://github.com/oVirt/ovirt-ansible-collection/issues/695) however, even the fix outlined there does not seem to solve this issue. Additionally, I have headed the recent advice from Sandro to switch to the nightly version. Unfortunately, this has also not been working on either ovirt node or CentOS 9/8, and today has resulted in the following error: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "cmd": ["virsh", "net-dumpxml", "default"], "delta": "0:00:00.077767", "end": "2023-04-17 17:00:05.980049", "msg": "non-zero return code", "rc": 1, "start": "2023-04-17 17:00:05.902282", "stderr": "error: failed to get network 'default'\nerror: Network not found: no network with matching name 'default'", "stderr_lines": ["error: failed to get network 'default'", "error: Network not found: no network with matching name 'default'"], "stdout": "", "stdout_lines": []} [ ERROR ] Failed to execute stage 'Closing up': Failed getting local_vm_dir Please let me know what additional information needs to be provided; I am more than happy to do so. Is there something I'm missing here? Is there a version that is confirmed to be working at the moment? I am grateful for anyone who takes the time to look into my issue, Xavier Lauzon

1 0

oVirt Installation script
by destfinal＠googlemail.com 17 Apr '23

17 Apr '23

Hi, I am trying to install a self-hosted oVirt cluster using this page - https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engin…. Right from the beginning the documentation states "Self-hosted engine installation is automated using Ansible" and "installation script" all over. But I could not find any link in this regard in this page or elsewhere. Am I missing to see it in the doc? Can somebody please help? Thanks

2 4

How to build network load graphs
by Артур Кириллов 17 Apr '23

17 Apr '23

After updating Overt to 4.5.4, the network load graphs disappeared. Q: How is charting organized? What certificates are involved in data exchange?

1 0

/tmp/lvm.log keeps growing in Host
by kanehisa＠ktcsp.net 16 Apr '23

16 Apr '23

I don't understand why lvm.log is placed in /tmp directory without rotation. I noticed this fact when I got the following event notification every 2 hours. EventID ：24 Message ：Critical, Low disk space. Host ovirt01 has less than 500 MB of free space left on: /tmp. Low disk space might cause an issue upgrading this host. As a workaround, I added a log rotation setting to /tmp/lvm.log, but is this the correct way? I should have understood the contents of the Python program below before asking the question, but please forgive me because I am not very knowledgeable about Python. # cat /usr/lib/python3.6/site-packages/blivet/devicelibs/lvm.py | grep lvm.log config_string += "log {level=7 file=/tmp/lvm.log syslog=0}" Thanks in advance!! Further information is below [root@ovirt01 ~]# cat /etc/os-release NAME="CentOS Stream" VERSION="8" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8.7.2206.0" VARIANT="oVirt Node 4.5.4" VARIANT_ID="ovirt-node" PRETTY_NAME="oVirt Node 4.5.4" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://www.ovirt.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" PLATFORM_ID="platform:el8" [root@ovirt01 ~]# uname -a Linux ovirt01 4.18.0-408.el8.x86_64 #1 SMP Mon Jul 18 17:42:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux [root@ovirt01 ~]# df -h | grep -E " /tmp|Filesystem" Filesystem Size Used Avail Use% Mounted on /dev/mapper/onn_ovirt01-tmp 1014M 515M 499M 51% /tmp [root@ovirt01 ~]# stat /tmp/lvm.log File: /tmp/lvm.log Size: 463915707 Blocks: 906088 IO Block: 4096 regular file Device: fd0eh/64782d Inode: 137 Links: 1 Access: (0600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ root) Context: system_u:object_r:lvm_tmp_t:s0 Access: 2023-02-03 10:30:06.605936740 +0900 Modify: 2023-02-03 09:52:19.712301285 +0900 Change: 2023-02-03 09:52:19.712301285 +0900 Birth: 2023-01-16 01:06:02.768495837 +0900

2 1

Upgrade failing
by notify.sina＠gmail.com 16 Apr '23

16 Apr '23

Hi all Attempting an upgrade in an attempt to fix/paper over expired certificate issues, but ran into this on my ovirt-engine [root@ovirt ~]# dnf upgrade --nobest -y Ceph packages for x86_64 5.1 MB/s | 478 kB 00:00 CentOS Stream 8 - AppStream 73 MB/s | 29 MB 00:00 CentOS Stream 8 - BaseOS 52 MB/s | 30 MB 00:00 CentOS Stream 8 - Extras 130 kB/s | 18 kB 00:00 CentOS Stream 8 - PowerTools 19 MB/s | 5.8 MB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 21 MB/s | 14 MB 00:00 Extra Packages for Enterprise Linux Modular 8 - x86_64 1.0 MB/s | 733 kB 00:00 Extra Packages for Enterprise Linux 8 - Next - x86_64 549 kB/s | 407 kB 00:00 Latest oVirt 4.4 Release 575 kB/s | 2.7 MB 00:04 Extra Packages for Enterprise Linux 8 - x86_64 21 MB/s | 14 MB 00:00 CentOS-8 - Gluster 8 192 B/s | 38 B 00:00 Error: Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No URLs in mirrorlist And there are others when I try to disable specific repos. How do I fix this?

1 0

4.5.2 hosted-engine deployment failed
by j9678＠hotmail.com 15 Apr '23

15 Apr '23

The engine deployment failed with message "Host is not up, please check logs, perhaps also on the engine machine" after "Wait for the host to be up". I couldn't find any particular error in setup log, it just failed without pointing out any reason. I've tried on ovirt node (el9 and el8) and RHEL 8.7.

2 1

Ovirt FQDN is not routing correctly and problems with CentOS 9
by aleksiallula＠gmail.com 15 Apr '23

15 Apr '23

I tried to configure ovirt for FQDN with local server but can not get it to work. This is what I added to /etc/hosts: 10.0.0.50 server.ovirt.com 10.0.0.51 server.ovirt2.com My hostname is server.ovirt.com and my IP address is 10.0.0.50. 10.0.0.51 is the hosted engine IP. I have added server.ovirt.com to "DNS search domains" of network card. I ask at the same time: is the difference between hosted engine and hyperconverged that with hyperconverged I could add the host to existing hosted engine ? First I tried to install OVirt to CentOS 9, but there is no "virtualization" menu at the OVirt main menu. So, I can not add the hosted engine setup. Now I try to setup the OVirt for CentOS 8 with this manual: https://anthonyspiteri.net/ovirt-kvm-homelab-1 and https://anthonyspiteri.net/ovirt-kvm-homelab-2. Any ideas how can I setup the FQDN and OVirt to work with CentOS 8 or 9 ? Is there some working repository where I can download the hosted engine version OVirt for CentOS 9 ?

1 0

How can i power on virtual machine automatically
by pivu＠mail.ru 13 Apr '23

13 Apr '23

Tell me please. How can i power on virtual machine automatically when Host power on? I do not see any settings for it. oVirt 4.2

2 1

Re: unable to connect to the graphic server with VNC graphics protocol
by Devin A. Bougie 12 Apr '23

12 Apr '23

Hi Murilo, Yes, when trying with noVNC we get: Something went wrong, connection is closed This is getting pretty urgent for us, so any help connecting to the console of VMs running on EL9 hosts would be greatly appreciated. Thanks for following up, Devin > On Apr 8, 2023, at 4:17 AM, Murilo Morais <murilo(a)evocorp.com.br> wrote: > > Devin, good morning! All good? I hope so. > > Have you tried accessing VNC through noVNC? > > Em sex., 7 de abr. de 2023 às 16:22, Devin A. Bougie <devin.bougie(a)cornell.edu> escreveu: > Hello, > > After upgrading our cluster to oVirt 4.5 on EL9 hosts, we had to switch from QXL and SPICE to VGA and VNC as EL9 dropped support for SPICE. However, we are now unable to view the console using Windows, Linux, or MacOS. > > For example, after downloading and opening console.vv file with Remote Viewer (virt-viewer) on Linux, we see: > Unable to connect to the graphic server. > > Any help connecting to a VM using a VGA/VNC console from Windows, Mac, or Linux would be greatly appreciated. > > Many thanks, > Devin > _______________________________________________ > 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/XWSCMSYHKEQVP…

2 2

I want to configure DHCP on my host. How do I do that?
by leezzzb12＠gmail.com 12 Apr '23

12 Apr '23

oVirt Version: 4.5 oVirt Engine : 1 unit oVirt Host : 3 units Virtual network configured ovirtmgmt, dhcp. dhcp gave vlan tagging as 50 and checked virtual machine network. Each host is configured to have two networks, ovirtmgmt and dhcp. I also set ipv4 to use DHCP, ipv6 also to use DHCP in the dhcp network. But no matter how long I wait on the host, I can't get the ipv4 and ipv6 IPs. 1. What did I do wrong? I've seen that using ovirt_provider_ovn you can configure DHCP. But I don't know how to configure it. 2. Is there a guide on how to configure it? 3. /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf is configured as follows: The [DHCP] section is missing, is this required? 4. If you use ovirtmgmt (default network, static IP) when creating a virtual machine, is it correct that you cannot receive an IP? Please help me.

1 0

virt-viewer - working alternative
by lars.stolpe＠bvg.de 11 Apr '23

11 Apr '23

Hi all, i tryed to use virt-viewer 11 (Windows) with oVirt 4.4 . I also tryed virt-viewer 10, 9, 8, and 7. The older versions can't handle ISO residing in data domains, the latest version is crashing if try the media button. Almost all links on the website are dead, no user guide, no prerequisites list... Since virt-viewer is not working properly and seems to be abandoned, i'm looking for a working alternative. Is there a working way to get a console of the virtual machines running in oVirt 4.4?

3 4

label settings
by ziyi Liu 11 Apr '23

11 Apr '23

I have many users and each user manages different devices, I made a label for the corresponding device and distributed the label to the corresponding user. The user needs to manually activate the label every time he logs in. How to activate the label by default?

1 0

4.4.9 -> 4.4.10 Cannot start or migrate any VM (hotpluggable cpus requested exceeds the maximum cpus supported by KVM)
by Jillian Morgan 10 Apr '23

10 Apr '23

After upgrading the engine from 4.4.9 to 4.4.10, and then upgrading one host, any attempt to migrate a VM to that host or start a VM on that host results in the following error: Number of hotpluggable cpus requested (16) exceeds the maximum cpus supported by KVM (8) While the version of qemu is the same across hosts, ( qemu-kvm-6.0.0-33.el8s.x86_64), I traced the difference to the upgraded kernel on the new host. I have always run elrepo's kernel-ml on these hosts to support bcache which RHEL's kernel doesn't support. The working hosts still run kernel-ml-5.15.12. The upgraded host ran kernel-ml-5.17.0. In case anyone else runs kernel-ml, have you run into this issue? Does anyone know why KVM's KVM_CAP_MAX_VCPUS value is lowered on the new kernel? Does anyone know how to query the KVM capabilities from userspace without writing a program leveraging kvm_ioctl()'s? Related to this, it seems that ovirt and/or libvirtd always runs qmu-kvm with an -smp argument of "maxcpus=16". This causes qemu's built-in check to fail on the new kernel which is supporting max_vpus of 8. Why does ovirt always request maxcpus=16? And yes, before you say it, I know you're going to say that running kernel-ml isn't supported. -- Jillian Morgan (she/her) 🏳️‍⚧️ Systems & Networking Specialist Primordial Software Group & I.T. Consultancy https://www.primordial.ca

2 1

unable to connect to the graphic server with VNC graphics protocol
by Devin A. Bougie 07 Apr '23

07 Apr '23

Hello, After upgrading our cluster to oVirt 4.5 on EL9 hosts, we had to switch from QXL and SPICE to VGA and VNC as EL9 dropped support for SPICE. However, we are now unable to view the console using Windows, Linux, or MacOS. For example, after downloading and opening console.vv file with Remote Viewer (virt-viewer) on Linux, we see: Unable to connect to the graphic server. Any help connecting to a VM using a VGA/VNC console from Windows, Mac, or Linux would be greatly appreciated. Many thanks, Devin

1 0

Ovirt CSI driver and volume snapshot
by Nathanaël Blanchet 07 Apr '23

07 Apr '23

Hello, Given that currently ovirt CSI driver doesn't support volume snapshot and consequently openshift virtualization doesn't support live snaphost, is there a chance that openshift virtualization supports volume snapshot with a ovirt CSI storage backend in the future?

1 0

Future of ovirt - end-of-life RHV
by Margit Meyer 06 Apr '23

06 Apr '23

What about the future of ovirt when RHV comes to end-of-life? Is there a chance for further usage? RedHat OpenShift will not be an option for us.... Margit

3 3

Renewing certificates - How it affects running vms?
by markeczzz＠gmail.com 06 Apr '23

06 Apr '23

Hi! Simple question - does procedure to renew certificates affects running virtual machines? I have a question regarding renewing certificates that are about to expire. I have a cluster with 5 hosts and a self-hosted engine. I have already updated the host certificates by logging in to each host, migrating virtual machines from that host to another, putting it into maintenance mode, and enrolling certificates via the web interface. Now, I have a question regarding renewing Engine certificates (self signed). I know the procedure is to log in to the host where the hosted engine is running (Host1 in my case), put it into global maintenance mode via the command "hosted-engine --set-maintenance --mode=global," and then log in to the Engine and run the command "engine-setup --offline" to renew it. My question is, will these two commands affect the running virtual machines on Host1 (where the hosted-engine is also hosted) and virtual machines on other hosts? Will they be shut down? Should I migrate virtual machines first from Host1 to some other host and then run the commands? I have a lot of virtual machines that i can't shut down or restart, any way to do it without that? Regards,

2 1

Failure to deploy oVirt node with security profile (PCIDSS)
by Guillaume Pavese 06 Apr '23

06 Apr '23

Hi oVirt community I tried with el8 & el9 oVirt Node 4.5.4 isos, But in both cases, the installation failed when selecting the PCI-DSS security profile. Please see screenshots attached According to 4.5.0 release note this is a supported feature : *BZ 2030226 [RFE] oVirt hypervisors should support running on hosts with the PCI-DSS security profile applied* *The oVirt Hypervisor is now capable of running on machine with PCI-DSS security profile.* https://bugzilla.redhat.com/show_bug.cgi?id=2030226 As the RFE says that deployment works, I guess this is a regression somewhere between 4.5.0 & 4.5.4 Is there a chance that this bug gets fixed? Is it up to the community? In the meantime, what can we do to deploy hosts with a PCI-DSS profile? Best regards, Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group -- Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. <https://interactiv-group.com/disclaimer.html>

2 1

Issue with hyper-converged node and rhel9
by Robert Pouliot 04 Apr '23

04 Apr '23

Hi, I have a 3 node cluster with gluster (2 rhel 8.7 and one rhel 9.1). I updated one of my nodes to rhel9 and I'm unable to start any VM that's running on gluster volumes on the rhel9 node or move a running VM on the rhel9 node. However, I'm able to start a node stored on a NFS node on the rhel9 node. According to gluster (10.3) all 3 nodes are working fine. I don't want to render my setup useless, that's why I didn't move the 2 other nodes. wells = rhel9 node. In the event log I'm getting the following error: Failed to sync storage devices from host wells VDSM wells command GetStorageDeviceListVDS failed: Internal JSON-RPC error Here is a part of the vdsm.log: 2023-04-03 23:25:01,242-0400 INFO (vm/69f6480f) [vds] prepared volume path: (clientIF:506) 2023-04-03 23:25:01,243-0400 INFO (vm/69f6480f) [vdsm.api] START prepareImage(sdUUID='a874a247-d8de-4951-86e8-99aaeda1a510', spUUID='595abf38-2c6d-11eb-9ba9-3ca82afed888', imgUUID='69de5e2b-dfb7-4e47-93d0-65ed4f978017', leafUUID='e66df35e-1254-48ef-bb83-ae8957fe8651', allowIllegal=False) from=internal, task_id=bf3e89e0-5d4e-47a1-8d86-3933c5004d25 (api:31) 2023-04-03 23:25:01,243-0400 INFO (vm/69f6480f) [vdsm.api] FINISH prepareImage error=Unknown pool id, pool not connected: ('595abf38-2c6d-11eb-9ba9-3ca82afed888',) from=internal, task_id=bf3e89e0-5d4e-47a1-8d86-3933c5004d25 (api:35) 2023-04-03 23:25:01,244-0400 INFO (vm/69f6480f) [storage.taskmanager.task] (Task='bf3e89e0-5d4e-47a1-8d86-3933c5004d25') aborting: Task is aborted: "value=Unknown pool id, pool not connected: ('595abf38-2c6d-11eb-9ba9-3ca82afed888',) abortedcode=309" (task:1165) 2023-04-03 23:25:01,244-0400 INFO (vm/69f6480f) [storage.dispatcher] FINISH prepareImage error=Unknown pool id, pool not connected: ('595abf38-2c6d-11eb-9ba9-3ca82afed888',) (dispatcher:64) 2023-04-03 23:25:01,244-0400 ERROR (vm/69f6480f) [virt.vm] (vmId='69f6480f-5ee0-4210-84b9-58b4dbb4e423') The vm start process failed (vm:1001) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/virt/vm.py", line 928, in _startUnderlyingVm self._run() File "/usr/lib/python3.9/site-packages/vdsm/virt/vm.py", line 2769, in _run self._devices = self._make_devices() File "/usr/lib/python3.9/site-packages/vdsm/virt/vm.py", line 2649, in _make_devices disk_objs = self._perform_host_local_adjustment() File "/usr/lib/python3.9/site-packages/vdsm/virt/vm.py", line 2687, in _perform_host_local_adjustment self._preparePathsForDrives(disk_params) File "/usr/lib/python3.9/site-packages/vdsm/virt/vm.py", line 1109, in _preparePathsForDrives drive['path'] = self.cif.prepareVolumePath( File "/usr/lib/python3.9/site-packages/vdsm/clientIF.py", line 418, in prepareVolumePath raise vm.VolumeError(drive) vdsm.virt.vm.VolumeError: Bad volume specification {'device': 'disk', 'type': 'disk', 'diskType': 'file', 'specParams': {}, 'alias': 'ua-69de5e2b-dfb7-4e47-93d0-65ed4f978017', 'address': {'bus': '0', 'controller': '0', 'target': '0', 'type': 'drive', 'unit': '0'}, 'domainID': 'a874a247-d8de-4951-86e8-99aaeda1a510', 'guestName': '/dev/sdb', 'imageID': '69de5e2b-dfb7-4e47-93d0-65ed4f978017', 'poolID': '595abf38-2c6d-11eb-9ba9-3ca82afed888', 'volumeID': 'e66df35e-1254-48ef-bb83-ae8957fe8651', 'managed': False, 'volumeChain': [{'domainID': 'a874a247-d8de-4951-86e8-99aaeda1a510', 'imageID': '69de5e2b-dfb7-4e47-93d0-65ed4f978017', 'leaseOffset': 0, 'leasePath': '/rhev/data-center/mnt/glusterSD/192.168.8.11:_GlusterVolLow/a874a247-d8de-4951-86e8-99aaeda1a510/images/69de5e2b-dfb7-4e47-93d0-65ed4f978017/e66df35e-1254-48ef-bb83-ae8957fe8651.lease', 'path': '/rhev/data-center/mnt/glusterSD/192.168.8.11:_GlusterVolLow/a874a247-d8de-4951-86e8-99aaeda1a510/images/69de5e2b-dfb7-4e47-93d0-65ed4f978017/e66df35e-1254-48ef-bb83-ae8957fe8651', 'volumeID': 'e66df35e-1254-48ef-bb83-ae8957fe8651'}], 'path': '/rhev/data-center/mnt/glusterSD/192.168.8.11:_GlusterVolLow/a874a247-d8de-4951-86e8-99aaeda1a510/images/69de5e2b-dfb7-4e47-93d0-65ed4f978017/e66df35e-1254-48ef-bb83-ae8957fe8651', 'discard': False, 'format': 'raw', 'propagateErrors': 'off', 'cache': 'none', 'iface': 'scsi', 'name': 'sda', 'bootOrder': '1', 'serial': '69de5e2b-dfb7-4e47-93d0-65ed4f978017', 'index': 0, 'reqsize': '0', 'truesize': '5331688448', 'apparentsize': '42949672960'} 2023-04-03 23:25:01,244-0400 INFO (vm/69f6480f) [virt.vm] (vmId='69f6480f-5ee0-4210-84b9-58b4dbb4e423') Changed state to Down: Bad volume specification {'device': 'disk', 'type': 'disk', 'diskType': 'file', 'specParams': {}, 'alias': 'ua-69de5e2b-dfb7-4e47-93d0-65ed4f978017', 'address': {'bus': '0', 'controller': '0', 'target': '0', 'type': 'drive', 'unit': '0'}, 'domainID': 'a874a247-d8de-4951-86e8-99aaeda1a510', 'guestName': '/dev/sdb', 'imageID': '69de5e2b-dfb7-4e47-93d0-65ed4f978017', 'poolID': '595abf38-2c6d-11eb-9ba9-3ca82afed888', 'volumeID': 'e66df35e-1254-48ef-bb83-ae8957fe8651', 'managed': False, 'volumeChain': [{'domainID': 'a874a247-d8de-4951-86e8-99aaeda1a510', 'imageID': '69de5e2b-dfb7-4e47-93d0-65ed4f978017', 'leaseOffset': 0, 'leasePath': '/rhev/data-center/mnt/glusterSD/192.168.8.11:_GlusterVolLow/a874a247-d8de-4951-86e8-99aaeda1a510/images/69de5e2b-dfb7-4e47-93d0-65ed4f978017/e66df35e-1254-48ef-bb83-ae8957fe8651.lease', 'path': '/rhev/data-center/mnt/glusterSD/192.168.8.11:_GlusterVolLow/a874a247-d8de-4951-86e8-99aaeda1a510/images/69de5e2b-dfb7-4e47-93d0-65ed4f978017/e66df35e-1254-48ef-bb83-ae8957fe8651', 'volumeID': 'e66df35e-1254-48ef-bb83-ae8957fe8651'}], 'path': '/rhev/data-center/mnt/glusterSD/192.168.8.11:_GlusterVolLow/a874a247-d8de-4951-86e8-99aaeda1a510/images/69de5e2b-dfb7-4e47-93d0-65ed4f978017/e66df35e-1254-48ef-bb83-ae8957fe8651', 'discard': False, 'format': 'raw', 'propagateErrors': 'off', 'cache': 'none', 'iface': 'scsi', 'name': 'sda', 'bootOrder': '1', 'serial': '69de5e2b-dfb7-4e47-93d0-65ed4f978017', 'index': 0, 'reqsize': '0', 'truesize': '5331688448', 'apparentsize': '42949672960'} (code=1) (vm:1743) 2023-04-03 23:25:01,245-0400 INFO (vm/69f6480f) [virt.vm] (vmId='69f6480f-5ee0-4210-84b9-58b4dbb4e423') Stopping connection (guestagent:421) 2023-04-03 23:25:01,252-0400 INFO (jsonrpc/7) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:192.168.2.24,56838, vmId=69f6480f-5ee0-4210-84b9-58b4dbb4e423 (api:31) 2023-04-03 23:25:01,252-0400 INFO (jsonrpc/7) [virt.vm] (vmId='69f6480f-5ee0-4210-84b9-58b4dbb4e423') Release VM resources (vm:5324)

1 0

ovirt 4.6 compatibility with el8
by Nathanaël Blanchet 01 Apr '23

01 Apr '23

Hello community! I noticed that rhel9 doesn't not support anymore ISP2532-based 8Gb Fibre Channel HBA. Given that all of my ovirt hosts are ISP2532-based, I d'like to know if ovirt 4.6 will be still compatible with el8 or will only support el9. -- Nathanaël Blanchet Administrateur Systèmes et Réseaux Service Informatique et REseau (SIRE) Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 1

oVirt hosted-engine deployment times out while "Wait for the host to be up"
by brwsergmslst＠gmail.com 01 Apr '23

01 Apr '23

Hi all, I am currently trying to deploy the hosted-engine without success. Unfortunately I cannot see what I am missing here. It'd be nice if you could put an eye on it and help me out. Below is an excerpt of the logfile generated. ``` 2023-03-22 20:34:10,417+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Get active list of active firewalld zones] 2023-03-22 20:34:12,222+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost] 2023-03-22 20:34:13,527+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Configure libvirt firewalld zone] 2023-03-22 20:34:20,246+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost] 2023-03-22 20:34:21,550+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Reload firewall-cmd] 2023-03-22 20:34:23,957+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost] 2023-03-22 20:34:25,462+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Add host] 2023-03-22 20:34:27,469+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost] 2023-03-22 20:34:28,672+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Include after_add_host tasks files] 2023-03-22 20:34:30,678+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 TASK [ovirt.ovirt.hosted_engine_setup : Let the user connect to the bootstrap engine VM to manually fix host configuration] 2023-03-22 20:34:31,882+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 skipping: [localhost] 2023-03-22 20:34:32,987+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] 2023-03-22 20:34:33,890+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 skipping: [localhost] 2023-03-22 20:34:34,893+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] 2023-03-22 20:34:36,096+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost] 2023-03-22 20:34:37,100+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Always revoke the SSO token] 2023-03-22 20:34:38,705+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost] 2023-03-22 20:34:40,111+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] 2023-03-22 20:34:41,015+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost] 2023-03-22 20:34:42,020+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] 2023-03-22 20:34:44,028+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost] 2023-03-22 20:34:45,032+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] 2023-03-22 20:56:33,746+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'changed': False, 'ovirt_hosts': [{'href': '/ovirt-engine/api/hosts/17ad8088-c9e9-433f-90b9-ce8023a625e6', 'comment': '', ' id': '17ad8088-c9e9-433f-90b9-ce8023a625e6', 'name': 'vhost-tmp01.example.com', 'address': 'vhost-tmp01.example.com', 'affinity_labels': [], 'auto_numa_status': 'unknown', 'certificate': {'organization': 'example.com', 'subject': 'O=example.com,CN=vhost-tmp01.example.com'}, 'cluster': {'href': '/ovirt-engine/api/clusters/4effacb7-e5dd-4e52-86c9-90ebd2aafa0d', 'id': '4effacb7-e5dd-4e52-86c9-90ebd2aafa0d'}, 'cpu ': {'speed': 0.0, 'topology': {}}, 'cpu_units': [], 'device_passthrough': {'enabled': False}, 'devices': [], 'external_network_provider_configurations': [], 'external_status': 'ok', 'hardware_information': {'supported_rng_sources': []}, 'h ooks': [], 'katello_errata': [], 'kdump_status': 'unknown', 'ksm': {'enabled': False}, 'max_scheduling_memory': 0, 'memory': 0, 'network_attachments': [], 'nics': [], 'numa_nodes': [], 'numa_supported': False, 'os': {'custom_kernel_cmdline ': ''}, 'ovn_configured': False, 'permissions': [], 'port': 54321, 'power_management': {'automatic_pm_enabled': True, 'enabled': False, 'kdump_detection': True, 'pm_proxies': []}, 'protocol': 'stomp', 'reinstallation_required': False, 'se_linux': {}, 'spm': {'priority': 5, 'status': 'none'}, 'ssh': {'fingerprint': 'SHA256:IDhzMTO49OoNIHmLGnOIGwTn8LQB/lYrJdUnak144Q4', 'port': 22, 'public_key': 'ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNWbUlwbIiSliqc6OCFwG4w6/OaJb63JijJ1okaj6Y3gqNPO2XZWDTfwraIqm0S0SGlVk/g0oYcYIQ/0hU5Q+bE='}, 'statistics': [], 'status': 'install_failed', 'storage_connection_extensions': [], 'summary': {'total': 0}, 'tags': [], 'transparent_huge_pages': {'enabled': False}, 'type': 'rhel', 'unmanaged_networks': [], 'update_available': False, 'vgpu_placement': 'consolidated'}], 'invocation': {'module_args': {'pattern': 'name=vhost-tmp01.example.com', 'fetch_nested': False, 'nested_attributes': [], 'follow': [], 'all_content': False, 'cluster _version': None}}, '_ansible_no_log': None, 'attempts': 120} 2023-03-22 20:56:33,847+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 ignored: [localhost]: FAILED! => {"attempts": 120, "changed": false, "ovirt_hosts": [{"address": "vhost-tmp01.example.com", "affinity_labels": [], "auto_numa_status": "unknown", "certificate": {"organization": "example.com", "subject": "O=example.com,CN=vhost-tmp01.example.com"}, "cluster": {"href": "/ovirt-engine/api/clusters/4effacb7-e5dd-4e52-86c9-90ebd2aafa0d", "id": "4effacb7-e5dd-4e52-86c9-90ebd2aafa0d"}, "comment": "", "cpu": {"speed": 0.0, "topology": {}}, "cpu_units": [], "device_passthrough": {"enabled": false}, "devices": [], "external_network_provider_configurations": [], "external_status": "ok", "hardware_information": {"supported_rng_sources": []}, "hooks": [], "href": "/ovirt-engine/api/hosts/17ad8088-c9e9-433f-90b9-ce8023a625e6", "id": "17ad8088-c9e9-433f-90b9-ce8023a625e6", "katello_errata": [], "kdump_status": "unknown", "ksm": {"enabled": false}, "max_ scheduling_memory": 0, "memory": 0, "name": "vhost-tmp01.example.com", "network_attachments": [], "nics": [], "numa_nodes": [], "numa_supported": false, "os": {"custom_kernel_cmdline": ""}, "ovn_configured": false, "permissions": [], "port": 54321, "power_management": {"automatic_pm_enabled": true, "enabled": false, "kdump_detection": true, "pm_proxies": []}, "protocol": "stomp", "reinstallation_required": false, "se_linux": {}, "spm": {"priority": 5, "status": "none"}, "ssh": {"fingerprint": "SHA256:IDhzMTO49OoNIHmLGnOIGwTn8LQB/lYrJdUnak144Q4", "port": 22, "public_key": "ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNWbUlwbIiSliqc6OCFwG4w6/OaJb63JijJ1okaj6Y3gqNPO2XZWDTfwraIqm0S0SGlVk/g0oYcYIQ/0hU5Q+bE="}, "statistics": [], "status": "install_failed", "storage_connection_extensions": [], "summary": {"total": 0}, "tags": [], "transparent_huge_pages": {"enabled": false}, "type": "rhel", "unmanaged_networks": [], "update_available": false, "vgpu_placement": " consolidated"}]} 2023-03-22 20:56:34,750+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] 2023-03-22 20:56:35,655+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'msg': 'Host is not up, please check logs, perhaps also on the engine machine', '_ansible_no_log': None, 'changed': False} 2023-03-22 20:56:35,755+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} ``` Thank you in advance. Best regards

1 1