- Users - oVirt List Archives

Deploy ovirt-csi in the kubernetes cluster
by ssarang520＠gmail.com 10 Feb '22

10 Feb '22

Hi, I want to deploy ovirt-csi in the kubernetes cluster. But the guide only has how to deploy to openshift. How can I deploy the ovirt-csi in the kubernetes cluster? Is there any way to do that?

5 5

Fibre Channel storage issue
by Timothy J. Wielgos 10 Feb '22

10 Feb '22

Thanks everyone for helping me through the last issue I had. Once I changed bonding mode to 2, everything worked. However, now I have another issue. I'm trying to install this using fibre channel storage. I set up a new lun from my storage array, assigned it to my host, and configured multipathing. All looks good. Then, when I ran the install script, I got the following error: [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Physical device initialization failed. Please check that the device is empty and accessible by the host.]". HTTP response code is 400.[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Physical device initialization failed. Please check that the device is empty and accessible by the host.]\". HTTP response code is 400."} Google says that's because the lun is dirty - maybe reused. I tried doing the suggested - I used dd to write all zeroes to the lun. I used wipefs on the lun. I deleted the lun from the array and created a new one. No matter what I did with that lun, it's still showing up with this error. I then created a second LUN. I mapped it to the host, and attempted to use that lun for storage - and it worked! There must be a dirty config somewhere on this thing that I need to clean up from that first lun. Anybody know what I might have to clean up on this host to clear out that old config?

2 1

OVIRT-Node Engine Deployment Failure due to no URLs in mirrorlist
by aellahib＠gmail.com 09 Feb '22

09 Feb '22

I am running OVIRT-Node and although I updated my mirror list and the hosts are fine. It seems my engine deployment (deploying hyperconverged gluster) is trying to use a different set of mirrors during Engine VM Prep. SO this is the error I see, should I be running a newer RPM on these nodes or something, I am not aware if there is a newer one I should be using for this. [ INFO ] TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package] [ ERROR ] fatal: [localhost -> 192.168.222.193]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No URLs in mirrorlist", "rc": 1, "results": []} [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost -> 192.168.222.193] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} It does let me click PrepareVM despite Deployment Failed -- but at that point /var/tmp is filled to more than 67% so it fails due to no space for engine install despite the good minimum requirements set lol

9 13

What replaces ISO domains how to re-use ISO files on multiple Data Centers?
by Brian Levinsen 08 Feb '22

08 Feb '22

Hello. I have been searching but not been able to find a solution. As far as I could find the Storage Domain Type ISO is deprecated. We have used this for hosting one central location for ISO images. Everywhere I found they say to use a Data Domain. But a Data Domain can not be attached to multiple Data Centers? So how do we in newer versions of ovirt share ISO files with multiple Data Centers? /Brian

1 0

Alternative Perspective - Re: oVirt alternatives
by David White 07 Feb '22

07 Feb '22

At the risk of sounding like a Red Hat or IBM fanboy, I have decided to give Red Hat the benefit of the doubt here, and to not make any decisions about switching off of oVirt until and unless an official announcement is made. In the meantime, I know that I need to move off of Gluster (and I made that decision before the Gluster announcement), and I would need storage with any other solution anyway, so that's where I'm going to focus my own efforts. In the meantime, while I realize that the optics of a company like IBM / Red Hat shutting a project like oVirt down looks bad to the FOSS community, I'm going to push back a little bit. We have had access to a FOSS application that obviously works for a lot of people. No company is required to provide their services for free, and likewise, I'm of the opinion that one needs to be willing to pay (or contribute in some way) for a quality product service. It reminds me of the mantra: "Fast, Cheap, Free - pick two". So here's an alternative perspective: What can the community contribute and do in order to keep the project going? Anyone could fork it, rebrand it, and run with it. I claim to be a software developer, and the uplink in my datacenter is only 100mbps right now (of course I can increase it when needed), so I doubt I could provide much value in terms of hosting or coding. But I do know security. I'm a Linux systems engineer with over 10 years of experience. I know website content management systems. And people have told me that I'm good at documentation. So I think I have a lot of skill sets that I could "offer" (albeit I don't have much time, and as we all know, time is money. I've been dealing with a serious personal matter since beginning of December, and I'm effectively an acting single parent at the moment). I'll end this the way I started: I'm going to wait to see what happens before I personally make any decisions to change my entire underlying virtualization infrastructure. In the meantime, I'll continue to work on what I can control - the underlying storage. And if oVirt does shutdown in the future, I'd love to have a conversation with anyone interested in helping out to fork the project and keep it running. Sent with ProtonMail Secure Email.

5 8

Importing export storage domain after redeploy failing, stating export domain still connected.
by Gilboa Davara 07 Feb '22

07 Feb '22

Hello all, I'm rebuilding one of my gluster clusters after it blew up following an unfortunate expired certificate issue. After I finally remembered to downgrade qemu (grrrr...) and started importing the hold gluster storage domains, one of the export domains failed to import due to "connected to another domain" issue. How can I force detach it from the previous cluster? (I remember something about deleting the lease file - but I'm too brain dead to find it in DDG...). Engine errors: $ cat engine.log | grep c3abcfe6-1062-48e2-8ca4-924b96b8c497 2022-02-07 13:31:24,729+02 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Lock Acquired to object 'EngineLock:{exclusiveLocks='[22eec6d4-f0be-47db-b5d5-678bd84f47c6=STORAGE]', sharedLocks=''}' 2022-02-07 13:31:24,747+02 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Running command: AttachStorageDomainToPoolCommand internal: false. Entities affected : ID: 22eec6d4-f0be-47db-b5d5-678bd84f47c6 Type: StorageAction group MANIPULATE_STORAGE_DOMAIN with role type ADMIN, ID: 257a27cc-87ec-11ec-bc62-00163e3fe79d Type: StoragePoolAction group MANIPULATE_STORAGE_DOMAIN with role type ADMIN 2022-02-07 13:31:24,782+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand] (default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] START, AttachStorageDomainVDSCommand( AttachStorageDomainVDSCommandParameters:{storagePoolId='257a27cc-87ec-11ec-bc62-00163e3fe79d', ignoreFailoverLimit='false', storageDomainId='22eec6d4-f0be-47db-b5d5-678bd84f47c6'}), log id: 777adb39 2022-02-07 13:31:48,281+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command AttachStorageDomainVDS failed: Storage domain already attached to pool: 'domain=22eec6d4-f0be-47db-b5d5-678bd84f47c6, pool=2cb812a0-4a95-11eb-b3bc-00163e6a0a7c' 2022-02-07 13:31:48,281+02 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand] (default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Command 'AttachStorageDomainVDSCommand( AttachStorageDomainVDSCommandParameters:{storagePoolId='257a27cc-87ec-11ec-bc62-00163e3fe79d', ignoreFailoverLimit='false', storageDomainId='22eec6d4-f0be-47db-b5d5-678bd84f47c6'})' execution failed: IRSGenericException: IRSErrorException: Storage domain already attached to pool: 'domain=22eec6d4-f0be-47db-b5d5-678bd84f47c6, pool=2cb812a0-4a95-11eb-b3bc-00163e6a0a7c' 2022-02-07 13:31:48,281+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand] (default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] FINISH, AttachStorageDomainVDSCommand, return: , log id: 777adb39 2022-02-07 13:31:48,281+02 ERROR [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Command 'org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.IrsOperationFailedNoFailoverException: IRSGenericException: IRSErrorException: Storage domain already attached to pool: 'domain=22eec6d4-f0be-47db-b5d5-678bd84f47c6, pool=2cb812a0-4a95-11eb-b3bc-00163e6a0a7c' (Failed with error StorageDomainAlreadyAttached and code 380) 2022-02-07 13:31:48,283+02 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Command [id=ec43c2c1-3441-4d91-9bd2-98280e9c0eaa]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap; snapshot: StoragePoolIsoMapId:{storagePoolId='257a27cc-87ec-11ec-bc62-00163e3fe79d', storageId='22eec6d4-f0be-47db-b5d5-678bd84f47c6'}. 2022-02-07 13:31:48,290+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] EVENT_ID: USER_ATTACH_STORAGE_DOMAIN_TO_POOL_FAILED(963), Failed to attach Storage Domain local_export_storage_1 to Data Center Default. (User: gilboa@internal-authz) 2022-02-07 13:31:48,294+02 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Lock freed to object 'EngineLock:{exclusiveLocks='[22eec6d4-f0be-47db-b5d5-678bd84f47c6=STORAGE]', sharedLocks=''}' Thanks, Gilboa

1 0

how to search event not matching a user
by Gianluca Cecchi 07 Feb '22

07 Feb '22

Hello, every event in Advanced view has a field "User". I'm trying to compose a search in web admin of events with user different from myuser@internal It seems I'm not able to get what I want. I also tried to base attempts on an old 2019 thread (on 4.3.6) where this queries worked: Disks: name=engine* or name=host* Disks: alias=engine* or alias=host* but now on 4.4.8 gives nothing even if matched. Any hint and also documentation reference about the correct syntax to use in 4.4.x? Thanks, Gianluca

3 3

What happened to oVirt engine-setup?
by Richard W.M. Jones 07 Feb '22

07 Feb '22

A while back I had oVirt 4.4.7 installed which I used for testing. For some reason that installation has died in some way, so I'm trying to install a fresh new oVirt 4.4.10. Last time I installed ovirt, it was very easy - I provisioned a couple of machines, ran engine-setup in one, answered a few questions and after a few minutes the engine was installed. Somehow this has changed and now it's really far more complicated, involving some ansible things and wanting to create VMs and ssh everywhere. Can I go back to the old/easy way of installing oVirt engine? And if so, what happened to the instructions for that? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org

4 6

VM Image is Locked after cleaning up of problematic snapshot.
by Muhammad Aidilfitri Bin Saleh 06 Feb '22

06 Feb '22

Hello Everyone, I requires your input as the VM that is currently Hosted on Ovirt 4.4.4.5 is showing a locked Icon in the status column. I am unable to perform any actions on this particular VM as it shows that the "Snapshot is currently being created for VM <VMName> There was a failed snapshot attempt executed earlier but I have gone through the steps to identified and unlock the said images and snapshot using the build tools /usr/share/ovirt-engine/setup/dbutils. I even went into the DB to identified the failed snapshot but still no luck. I have restarted the ovirt-engine service and also the Standalone VM hosting this Ovirt-Engine but still not able to release the VM. I have also performed the ovirt-setup but still no luck on this portion. Any assistance is appreciated.

2 1

Hosted Engine down and not visible on any host
by milan.mithbaokar＠gmail.com 04 Feb '22

04 Feb '22

Hi, We have a 4 node ovirt cluster running at 4.4.1.5. We are running it on iSCSI shared Storage. The hosted engine is running on its separate iSCSI shared storage. Hosted Engine went down all of a sudden and no where to be found on any of the nodes when I do virsh list --all All other VM's are showed in the list but cannot see the hosted engine? when we try to bring hosted engine up using "hosted-engine --vm-start" it errors out with message "vm does not exist". The shared iscsi storage ip on which the HE vm was running is pingable, but when we perform "hosted-engine --connect-storage" we are getting request timeouts after 60 seconds. Any ideas to restore back the hosted engine and the cluster highly appreciated.

2 1

Installing a windows vm from importing an OVA Template
by moizr＠emiratesnbd.com 04 Feb '22

04 Feb '22

We are trying to create a windows vm on OLVM/OVirt. Below are the steps we followed - Exported an OVF of a plain windows vm from vmware. - Imported it as an OVA to OLVM - Start the VM after change OS type to Windows 2016. As soon as we select Windows 2016 the server doesnt start but works when we make it as other OS. We want to automated provisioning and setup of the vm through sysprep but the vm doesnt start once we select OS as Windows on the template or any vm created out of that template.

3 3

Unclear how to add local (POSIX) storage
by Richard W.M. Jones 04 Feb '22

04 Feb '22

I'm following the instructions here: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… I've also added an extra virtual disk to my host node which appears as /dev/sdb. Although the disk is partitioned, /dev/sdb1 is not created. Is udev broken in oVirt node? I cannot see anywhere in the dialog where you specify the name of the device (eg. "/dev/sdb1"). So how's it supposed to work? It doesn't work, giving an information-free error message: Error while executing action Add Storage Connection: Problem while trying to mount target Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org

3 15

Ignore CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION ?
by Richard W.M. Jones 04 Feb '22

04 Feb '22

2022-02-01 19:05:01,952Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) [330886aa] EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host ovirt4410-host moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all The host is a nested VM running on old hardware. I don't care that it's not supported - this is just for testing copying and it'll literally never even need to run a VM. Is there a way to ignore this and continue? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org

7 17

Erasure Coding Storage Support
by alishirv＠pm.me 04 Feb '22

04 Feb '22

Hello everyone, I'm new to oVirt. I want to set up a cost-efficient and fault-tolerant virtualization environment. Our VMs have low to medium IOPS, 70% of VMs have low IOPS and about 30% of them require about 5K IOPS. All the disks are NVMe. I found that the most cost-efficient storage plan in the current oVirt is a two-way replica with an arbiter and its storage overhead is more than 100%. As far as I know, we can use erasure coding with less storage overhead. Is there any plan to support erasure coding in oVirt? Would you even recommend erasure coding for VM workloads? Best regards, Ali

3 4

Tried updated version of ovirt-node-ng-installer/4.4.10-202202021
by denismalkomail＠gmail.com 03 Feb '22

03 Feb '22

Hello team! I faced the same mirror issue for two days. I saw you pushed a new iso image and tried it, but still the same. I use this one https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4.1… Error message: ``` ERROR ] fatal: [localhost -> 192.168.222.253]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No URLs in mirrorlist", "rc": 1, "results": []} ``` Did you merge PR with mirror changes? Best regards, Denis

3 3

How to clean stale engine from "hosted-engine unknow stale-data"
by Ayansh Rocks 03 Feb '22

03 Feb '22

Hi All, How to clean stale hosted engine from the database. I want to remove host id=3 Ovirt - 4.4.9 [root@iondelsvr14 vdsm]# hosted-engine --vm-status --== Host iondelsvr10.iontrading.com (id: 1) status ==-- Host ID : 1 Host timestamp : 2632783 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : iondelsvr10.iontrading.com Local maintenance : False stopped : False crc32 : 882bb390 conf_on_shared_storage : True local_conf_timestamp : 2632783 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=2632783 (Thu Feb 3 09:00:14 2022) host-id=1 score=3400 vm_conf_refresh_time=2632783 (Thu Feb 3 09:00:14 2022) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False --== Host iondelsvr11.iontrading.com (id: 2) status ==-- Host ID : 2 Host timestamp : 6215454 Score : 3400 Engine status : {"vm": "up", "health": "good", "detail": "Up"} Hostname : iondelsvr11.iontrading.com Local maintenance : False stopped : False crc32 : 30153e90 conf_on_shared_storage : True local_conf_timestamp : 6215454 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=6215454 (Thu Feb 3 09:00:16 2022) host-id=2 score=3400 vm_conf_refresh_time=6215454 (Thu Feb 3 09:00:16 2022) conf_on_shared_storage=True maintenance=False state=EngineUp stopped=False --== Host iondelsvr12.iontrading.com (id: 3) status ==-- Host ID : 3 Host timestamp : 734 Score : 1800 Engine status : unknown stale-data Hostname : iondelsvr12.iontrading.com Local maintenance : False stopped : False crc32 : 062e92e9 conf_on_shared_storage : True local_conf_timestamp : 734 Status up-to-date : False Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=734 (Fri Jan 28 17:35:18 2022) host-id=3 score=1800 vm_conf_refresh_time=734 (Fri Jan 28 17:35:18 2022) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False

3 9

[ANN] oVirt Node 4.4.10.1 Async update
by Lev Veyde 03 Feb '22

03 Feb '22

On February 2nd 2022 the oVirt project released an async update of oVirt Node (4.4.10.1) delivering fixes for the following issues: Bug 2048888 <https://bugzilla.redhat.com/show_bug.cgi?id=2048888> - Bad repositories on fresh install of oVirt Node Bug 2046038 <https://bugzilla.redhat.com/show_bug.cgi?id=2046038> - CVE-2021-4034 <https://access.redhat.com/security/cve/CVE-2021-4034> polkit: Local privilege escalation in pkexec due to incorrect handling of argument vector [ovirt-4.4] Several bug fixes and improvements from CentOS Stream. Here’s the full list of changes: ovirt-node-ng-4.4.10 ovirt-node-ng-4.4.10.1 NetworkManager 1.36.0-0.3.el8 1.36.0-0.4.el8 NetworkManager-config-server 1.36.0-0.3.el8 1.36.0-0.4.el8 NetworkManager-libnm 1.36.0-0.3.el8 1.36.0-0.4.el8 NetworkManager-ovs 1.36.0-0.3.el8 1.36.0-0.4.el8 NetworkManager-team 1.36.0-0.3.el8 1.36.0-0.4.el8 NetworkManager-tui 1.36.0-0.3.el8 1.36.0-0.4.el8 audispd-plugins 3.0-0.17.20191104git1c2f876.el8 3.0.7-1.el8 audit 3.0-0.17.20191104git1c2f876.el8 3.0.7-1.el8 audit-libs 3.0-0.17.20191104git1c2f876.el8 3.0.7-1.el8 bind-export-libs 9.11.26-6.el8 9.11.36-2.el8 bind-libs 9.11.26-6.el8 9.11.36-2.el8 bind-libs-lite 9.11.26-6.el8 9.11.36-2.el8 bind-license 9.11.26-6.el8 9.11.36-2.el8 bind-utils 9.11.26-6.el8 9.11.36-2.el8 binutils 2.30-112.el8 2.30-113.el8 centos-gpg-keys 8-3.el8 8-4.el8 centos-stream-repos 8-3.el8 8-4.el8 clevis 15-6.el8 15-8.el8 clevis-dracut 15-6.el8 15-8.el8 clevis-luks 15-6.el8 15-8.el8 clevis-systemd 15-6.el8 15-8.el8 cockpit 260-1.el8 261-1.el8 cockpit-bridge 260-1.el8 261-1.el8 cockpit-storaged 259-1.el8 261-1.el8 cockpit-system 260-1.el8 261-1.el8 cockpit-ws 260-1.el8 261-1.el8 collectd 5.11.0-2.el8 5.12.0-7.el8s collectd-disk 5.11.0-2.el8 5.12.0-7.el8s collectd-netlink 5.11.0-2.el8 5.12.0-7.el8s collectd-virt 5.11.0-2.el8 5.12.0-7.el8s collectd-write_http 5.11.0-2.el8 5.12.0-7.el8s collectd-write_syslog 5.11.0-2.el8 5.12.0-7.el8s cups-libs 2.2.6-41.el8 2.2.6-42.el8 device-mapper-multipath 0.8.4-20.el8 0.8.4-21.el8 device-mapper-multipath-libs 0.8.4-20.el8 0.8.4-21.el8 dhcp-client 4.3.6-45.el8 4.3.6-47.el8.0.1 dhcp-common 4.3.6-45.el8 4.3.6-47.el8.0.1 dhcp-libs 4.3.6-45.el8 4.3.6-47.el8.0.1 dnf-plugins-core 4.0.21-7.el8 4.0.21-8.el8 fence-agents-all 4.2.1-83.el8 4.2.1-85.el8 fence-agents-amt-ws 4.2.1-83.el8 4.2.1-85.el8 fence-agents-apc 4.2.1-83.el8 4.2.1-85.el8 fence-agents-apc-snmp 4.2.1-83.el8 4.2.1-85.el8 fence-agents-bladecenter 4.2.1-83.el8 4.2.1-85.el8 fence-agents-brocade 4.2.1-83.el8 4.2.1-85.el8 fence-agents-cisco-mds 4.2.1-83.el8 4.2.1-85.el8 fence-agents-cisco-ucs 4.2.1-83.el8 4.2.1-85.el8 fence-agents-common 4.2.1-83.el8 4.2.1-85.el8 fence-agents-compute 4.2.1-83.el8 4.2.1-85.el8 fence-agents-drac5 4.2.1-83.el8 4.2.1-85.el8 fence-agents-eaton-snmp 4.2.1-83.el8 4.2.1-85.el8 fence-agents-emerson 4.2.1-83.el8 4.2.1-85.el8 fence-agents-eps 4.2.1-83.el8 4.2.1-85.el8 fence-agents-heuristics-ping 4.2.1-83.el8 4.2.1-85.el8 fence-agents-hpblade 4.2.1-83.el8 4.2.1-85.el8 fence-agents-ibm-powervs 4.2.1-83.el8 fence-agents-ibm-vpc 4.2.1-83.el8 fence-agents-ibmblade 4.2.1-83.el8 4.2.1-85.el8 fence-agents-ifmib 4.2.1-83.el8 4.2.1-85.el8 fence-agents-ilo-moonshot 4.2.1-83.el8 4.2.1-85.el8 fence-agents-ilo-mp 4.2.1-83.el8 4.2.1-85.el8 fence-agents-ilo-ssh 4.2.1-83.el8 4.2.1-85.el8 fence-agents-ilo2 4.2.1-83.el8 4.2.1-85.el8 fence-agents-intelmodular 4.2.1-83.el8 4.2.1-85.el8 fence-agents-ipdu 4.2.1-83.el8 4.2.1-85.el8 fence-agents-ipmilan 4.2.1-83.el8 4.2.1-85.el8 fence-agents-kdump 4.2.1-83.el8 4.2.1-85.el8 fence-agents-mpath 4.2.1-83.el8 4.2.1-85.el8 fence-agents-redfish 4.2.1-83.el8 4.2.1-85.el8 fence-agents-rhevm 4.2.1-83.el8 4.2.1-85.el8 fence-agents-rsa 4.2.1-83.el8 4.2.1-85.el8 fence-agents-rsb 4.2.1-83.el8 4.2.1-85.el8 fence-agents-sbd 4.2.1-83.el8 4.2.1-85.el8 fence-agents-scsi 4.2.1-83.el8 4.2.1-85.el8 fence-agents-vmware-rest 4.2.1-83.el8 4.2.1-85.el8 fence-agents-vmware-soap 4.2.1-83.el8 4.2.1-85.el8 fence-agents-wti 4.2.1-83.el8 4.2.1-85.el8 glibc 2.28-181.el8 2.28-184.el8 glibc-common 2.28-181.el8 2.28-184.el8 glibc-langpack-en 2.28-181.el8 2.28-184.el8 glusterfs 8.6-2.el8 8.6-2.el8s glusterfs-cli 8.6-2.el8 8.6-2.el8s glusterfs-client-xlators 8.6-2.el8 8.6-2.el8s glusterfs-events 8.6-2.el8 8.6-2.el8s glusterfs-fuse 8.6-2.el8 8.6-2.el8s glusterfs-geo-replication 8.6-2.el8 8.6-2.el8s glusterfs-selinux 2.0.1-1.el8 2.0.1-1.el8s glusterfs-server 8.6-2.el8 8.6-2.el8s iproute 5.15.0-1.el8 5.15.0-2.el8 iproute-tc 5.15.0-1.el8 5.15.0-2.el8 kexec-tools 2.0.20-67.el8 2.0.20-68.el8 kpartx 0.8.4-20.el8 0.8.4-21.el8 libarchive 3.3.3-1.el8 3.3.3-3.el8_5 libblkid 2.32.1-28.el8 2.32.1-32.el8 libbpf 0.4.0-2.el8 0.4.0-3.el8 libfdisk 2.32.1-28.el8 2.32.1-32.el8 libgcc 8.5.0-7.el8 8.5.0-10.el8 libgfapi0 8.6-2.el8 8.6-2.el8s libgfchangelog0 8.6-2.el8 8.6-2.el8s libgfrpc0 8.6-2.el8 8.6-2.el8s libgfxdr0 8.6-2.el8 8.6-2.el8s libglusterd0 8.6-2.el8 8.6-2.el8s libglusterfs0 8.6-2.el8 8.6-2.el8s libgomp 8.5.0-7.el8 8.5.0-10.el8 libmount 2.32.1-28.el8 2.32.1-32.el8 libnftnl 1.1.5-4.el8 1.1.5-5.el8 libsmartcols 2.32.1-28.el8 2.32.1-32.el8 libstdc++ 8.5.0-7.el8 8.5.0-10.el8 libsysfs 2.1.0-24.el8 2.1.0-25.el8 libuuid 2.32.1-28.el8 2.32.1-32.el8 libwbclient 4.15.3-0.el8 4.15.4-0.el8 llvm-compat-libs 12.0.1-4.module_el8.6.0+1041+0c503ac4 llvm-libs 13.0.0-3.module_el8.6.0+1029+6594c364 mdevctl 0.81-1.el8 1.1.0-2.el8 mesa-dri-drivers 21.3.0-1.el8 21.3.4-1.el8 mesa-filesystem 21.3.0-1.el8 21.3.4-1.el8 mesa-libEGL 21.3.0-1.el8 21.3.4-1.el8 mesa-libGL 21.3.0-1.el8 21.3.4-1.el8 mesa-libgbm 21.3.0-1.el8 21.3.4-1.el8 mesa-libglapi 21.3.0-1.el8 21.3.4-1.el8 nispor 1.2.2-1.el8 1.2.3-1.el8 nmstate 1.2.0-1.el8 1.2.1-0.2.alpha2.el8 nmstate-plugin-ovsdb 1.2.0-1.el8 1.2.1-0.2.alpha2.el8 ovirt-node-ng-image-update-placeholder 4.4.10-1.el8 4.4.10.1-1.el8 ovirt-release-host-node 4.4.10-1.el8 4.4.10.1-1.el8 ovirt-release44 4.4.10-1.el8 4.4.10.1-1.el8 pacemaker-cluster-libs 2.1.2-2.el8 2.1.2-4.el8 pacemaker-libs 2.1.2-2.el8 2.1.2-4.el8 pacemaker-schemas 2.1.2-2.el8 2.1.2-4.el8 platform-python 3.6.8-44.el8 3.6.8-45.el8 policycoreutils 2.9-17.el8 2.9-18.el8 policycoreutils-python-utils 2.9-17.el8 2.9-18.el8 polkit 0.115-12.el8 0.115-13.el8_5.1 polkit-libs 0.115-12.el8 0.115-13.el8_5.1 postfix 3.5.8-2.el8 3.5.8-3.el8 python3-audit 3.0-0.17.20191104git1c2f876.el8 3.0.7-1.el8 python3-bind 9.11.26-6.el8 9.11.36-2.el8 python3-cloud-what 1.28.24-1.el8 1.28.25-1.el8 python3-dnf-plugin-versionlock 4.0.21-7.el8 4.0.21-8.el8 python3-dnf-plugins-core 4.0.21-7.el8 4.0.21-8.el8 python3-ethtool 0.14-3.el8 0.14-4.el8 python3-gluster 8.6-2.el8 8.6-2.el8s python3-libnmstate 1.2.0-1.el8 1.2.1-0.2.alpha2.el8 python3-libs 3.6.8-44.el8 3.6.8-45.el8 python3-lxml 4.2.3-3.el8 4.2.3-4.el8 python3-nispor 1.2.2-1.el8 1.2.3-1.el8 python3-policycoreutils 2.9-17.el8 2.9-18.el8 python3-subscription-manager-rhsm 1.28.24-1.el8 1.28.25-1.el8 python3-syspurpose 1.28.24-1.el8 1.28.25-1.el8 rsyslog 8.2102.0-6.el8 8.2102.0-7.el8 rsyslog-elasticsearch 8.2102.0-6.el8 8.2102.0-7.el8 rsyslog-mmjsonparse 8.2102.0-6.el8 8.2102.0-7.el8 rsyslog-mmnormalize 8.2102.0-6.el8 8.2102.0-7.el8 rsyslog-openssl 8.2102.0-6.el8 8.2102.0-7.el8 samba-client-libs 4.15.3-0.el8 4.15.4-0.el8 samba-common 4.15.3-0.el8 4.15.4-0.el8 samba-common-libs 4.15.3-0.el8 4.15.4-0.el8 selinux-policy 3.14.3-86.el8 3.14.3-89.el8 selinux-policy-targeted 3.14.3-86.el8 3.14.3-89.el8 sos 4.2-11.el8 4.2-13.el8 subscription-manager-rhsm-certificates 1.28.24-1.el8 1.28.25-1.el8 sysfsutils 2.1.0-24.el8 2.1.0-25.el8 systemd 239-51.el8_5.2 239-56.el8 systemd-container 239-51.el8_5.2 239-56.el8 systemd-libs 239-51.el8_5.2 239-56.el8 systemd-pam 239-51.el8_5.2 239-56.el8 systemd-udev 239-51.el8_5.2 239-56.el8 unzip 6.0-45.el8 6.0-46.el8 util-linux 2.32.1-28.el8 2.32.1-32.el8 vim-minimal 8.0.1763-16.el8_5.3 8.0.1763-16.el8_5.4 virt-install 3.2.0-2.el8 3.2.0-3.el8 virt-manager-common 3.2.0-2.el8 3.2.0-3.el8 An updated ovirt-appliance will be released soon as well. Thanks in advance, -- 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>

3 9

help install oVirt Engine on CentOS 9 Stream
by david 03 Feb '22

03 Feb '22

hi all can't install oVirt engine on Centos Stream 9 # dnf repolist repo id repo name appstream CentOS Stream 9 - AppStream baseos CentOS Stream 9 - BaseOS extras-common CentOS Stream 9 - Extras packages ovirt-4.4 Latest oVirt 4.4 Release # dnf install ovirt-engine Last metadata expiration check: 0:15:25 ago on Thu 03 Feb 2022 10:41:41 AM +04. No match for argument: ovirt-engine Error: Unable to find a match: ovirt-engine # yum search ovirt Last metadata expiration check: 0:07:44 ago on Thu 03 Feb 2022 10:41:41 AM +04. ======================================================================================================= Name & Summary Matched: ovirt ovirt-hosted-engine-setup.noarch : oVirt Hosted Engine setup tool ovirt-imageio-client.x86_64 : oVirt imageio client library ovirt-imageio-common.x86_64 : oVirt imageio common resources ovirt-imageio-common-debuginfo.x86_64 : Debug information for package ovirt-imageio-common ovirt-imageio-daemon.x86_64 : oVirt imageio daemon ovirt-imageio-debugsource.x86_64 : Debug sources for package ovirt-imageio ovirt-release44.noarch : The oVirt repository configuration ============================================================================================================ Name Matched: ovirt how to fox it ? thanks!

2 1

help install oVirt Engine on Centos 9 Stream
by david 03 Feb '22

03 Feb '22

hi all can't install oVirt engine on Centos Stream 9 # dnf repolist repo id repo name appstream CentOS Stream 9 - AppStream baseos CentOS Stream 9 - BaseOS extras-common CentOS Stream 9 - Extras packages ovirt-4.4 Latest oVirt 4.4 Release # dnf install ovirt-engine Last metadata expiration check: 0:15:25 ago on Thu 03 Feb 2022 10:41:41 AM +04. No match for argument: ovirt-engine Error: Unable to find a match: ovirt-engine # yum search ovirt Last metadata expiration check: 0:07:44 ago on Thu 03 Feb 2022 10:41:41 AM +04. ======================================================================================================= Name & Summary Matched: ovirt ovirt-hosted-engine-setup.noarch : oVirt Hosted Engine setup tool ovirt-imageio-client.x86_64 : oVirt imageio client library ovirt-imageio-common.x86_64 : oVirt imageio common resources ovirt-imageio-common-debuginfo.x86_64 : Debug information for package ovirt-imageio-common ovirt-imageio-daemon.x86_64 : oVirt imageio daemon ovirt-imageio-debugsource.x86_64 : Debug sources for package ovirt-imageio ovirt-release44.noarch : The oVirt repository configuration ============================================================================================================ Name Matched: ovirt how to fix it ? thanks

1 0

Ovirt host issue
by Ayansh Rocks 03 Feb '22

03 Feb '22

Hi All, I was adding ovirt host into the cluster(along with the engine deploy option) but somehow due to network issues it failed and then I removed the host from the cluster. But I got the below error. What should I do ? Ovirt Release - 4.4.9 Unconfiguring OVN on host iondelsvr12.iontrading.com might have failed. Please ensure that the host is removed from the OVN Southbound database by using '/usr/share/ovirt-provider-ovn/scripts/remove_chassis.sh iondelsvr12.iontrading.com' manually. Thanks

2 1

gluster and virtualization
by eevans＠digitaldatatechs.com 02 Feb '22

02 Feb '22

My setup is 3 ovirt nodes that run gluster independently of the engine server, even thought the engine still controls it. So 4 nodes, one engine and 3 clustered nodes. This has been and running with no issues except this: But now my arbiter node will not load the gluster drive when virtualization is enable in the BIOS. I've been scratching my head on this and need some direction. I am attaching the error. https://1drv.ms/u/s!AvgvEzKKSZHbhMRQmUHDvv_Xv7dkhw?e=QGdfYR Keep in mind, this error does not occur is VT is turned off..it boots normally. Thanks in advance.

3 2

Host needs to be reinstalled after configuring power management
by Andrew DeMaria 02 Feb '22

02 Feb '22

Hi, I am running ovirt 4.3 and have found the following action item immediately after configuring power management for a host: Host needs to be reinstalled as important configuration changes were applied on it. The thing is - I've just freshly installed this host and it seems strange that I need to reinstall it. Is there a better way to install a host and configure power management without having to reinstall it after? Thanks, Andrew

4 3

migration infinite loop
by Renaud RAKOTOMALALA 02 Feb '22

02 Feb '22

Hi, I switch an host in "PreparingForMaintenance" state to prepare an upgrade. In this stage the host migrating all VM but failed on one due to a network's congestion. Because the host try to migrate this VM and the constant failure of the migration, we enter in an infinite loop. How can I stop this loop ? I’m not able to cancel the mainteance mode with the WebUI. Any idea ? Thanks -- Renaud

1 0

Jenkins upgrade
by Denis Volkov 02 Feb '22

02 Feb '22

Hello I'm planning to upgrade jenkins.ovirt.org to latest LTS version (2.319.2). I moved jenkins to maintenance mode, so no new jobs can be started at the moment. Planned upgrade start time 10AM UTC. Planned downtime - 30 minutes. -- Denis Volkov

1 2

Cinderlib RBD ceph template issues
by Sketch 01 Feb '22

01 Feb '22

This is on oVirt 4.4.8, engine on CS8, hosts on C8, cluster and DC are both set to 4.6. With a newly configured cinderlib/ceph RBD setup. I can create new VM images, and copy existing VM images, but I can't copy existing template images to RBD. When I do, I try, I get this error in cinderlib.log (see below), which sounds like the disk already exists there, but it definitely does not. This leaves me unable to create new VMs on RBD, only migrate existing VM disks. 2021-09-01 04:31:05,881 - cinder.volume.driver - INFO - Driver hasn't implemented _init_vendor_properties() 2021-09-01 04:31:05,882 - cinderlib-client - INFO - Creating volume '0e8b9aca-1eb1-4837-ac9e-cb3d8f4c1676', with size '500' GB [5c5d0a6b] 2021-09-01 04:31:05,943 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Entity '<class 'cinder.db.sqlalchemy.models.Volume'>' has no property 'glance_metadata' [5c5d0a6b] 2021-09-01 04:31:05,944 - cinder - CRITICAL - Unhandled error Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 455, in create self._raise_with_resource() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 222, in _raise_with_resource six.reraise(*exc_info) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 448, in create model_update = self.backend.driver.create_volume(self._ovo) File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 986, in create_volume features=client.features) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 190, in doit result = proxy_call(self._autowrap, f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 148, in proxy_call rv = execute(f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 129, in execute six.reraise(c, e, tb) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 83, in tworker rv = meth(*args, **kwargs) File "rbd.pyx", line 629, in rbd.RBD.create rbd.ImageExists: [errno 17] RBD image already exists (error creating image) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/base.py", line 399, in _entity_descriptor return getattr(entity, key) AttributeError: type object 'Volume' has no attribute 'glance_metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 170, in main args.command(args) File "./cinderlib-client.py", line 208, in create_volume backend.create_volume(int(args.size), id=args.volume_id) File "/usr/lib/python3.6/site-packages/cinderlib/cinderlib.py", line 175, in create_volume vol.create() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 457, in create self.save() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 628, in save self.persistence.set_volume(self) File "/usr/lib/python3.6/site-packages/cinderlib/persistence/dbms.py", line 254, in set_volume self.db.volume_update(objects.CONTEXT, volume.id, changed) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 236, in wrapper return f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 184, in wrapper return f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 2570, in volume_update result = query.filter_by(id=volume_id).update(values) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/query.py", line 3818, in update update_op.exec_() File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1670, in exec_ self._do_pre_synchronize() File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1743, in _do_pre_synchronize self._additional_evaluators(evaluator_compiler) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1912, in _additional_evaluators values = self._resolved_values_keys_as_propnames File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1831, in _resolved_values_keys_as_propnames for k, v in self._resolved_values: File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1818, in _resolved_values desc = _entity_descriptor(self.mapper, k) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/base.py", line 402, in _entity_descriptor "Entity '%s' has no property '%s'" % (description, key) sqlalchemy.exc.InvalidRequestError: Entity '<class 'cinder.db.sqlalchemy.models.Volume'>' has no property 'glance_metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 390, in <module> sys.exit(main(sys.argv[1:])) File "./cinderlib-client.py", line 176, in main sys.stderr.write(traceback.format_exc(e)) File "/usr/lib64/python3.6/traceback.py", line 167, in format_exc return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 121, in format_exception type(value), value, tb, limit=limit).format(chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 509, in __init__ capture_locals=capture_locals) File "/usr/lib64/python3.6/traceback.py", line 338, in extract if limit >= 0: TypeError: '>=' not supported between instances of 'InvalidRequestError' and 'int'

3 4

Ovirt host error [Cannot configure LVM filter]
by Ayansh Rocks 01 Feb '22

01 Feb '22

Hello All, I was adding few new hosts into the ovirt cluster but a couple of them gave this error. Ovirt Release - 4.4.10 Installing Host iondelsvr14.iontrading.com. Check for LVM filter configuration error: Cannot configure LVM filter on host, please run: vdsm-tool config-lvm-filter. However, few of them are able to configure it. Thanks

2 3

gerrit.ovirt.org upgrade
by Denis Volkov 01 Feb '22

01 Feb '22

Hello Gerrit.ovirt.org will be upgraded later today. Approximate start time is 4PM UTC. During the upgrade service will be shut down and so will not be available. -- Denis Volkov

3 10

Incorrect percentages vol dashboard client
by Ilya Fedotov 01 Feb '22

01 Feb '22

Hello, ovirt [image: image.png] I have a difficult situation with the representation of the calculation of the volume of disk data. I copied some of the information about it. How can used 130% of the information ? oVirt VM Portal - Version 1.7.2-1 - oVirt API Version 4.4 Thanks for replay. with br, Ilya Fedotov

2 2

no snaphot but engines complains there is one when trying to remove disk
by Nathanaël Blanchet 01 Feb '22

01 Feb '22

Hi all, A colleague launched this morning a snapshot creation, there was no error message but he wasn't able to start the vm anymore, with this issue : VM PSI-SYB-DEV is down with error. Exit message: Unable to get volume size for domain a5be6cae-f0c8-452f-b7cd-70d0e5eed710 volume 109fac1e-c2e3-4ba6-9867-5d1c94d3a447.. I tried many things but nothing works: it is impossible to remove this disk, or copy it, or clone the vm : Cannot detach Virtual Disk. The disk is already configured in a snapshot. In order to detach it, remove the disk's snapshots. There is no snaphost listed into webui or api (so not snapshot id), while disk_snapshots exists into the associated storage domain. So I tried to remove disks snapshot direvctly with API followind the DELETE method |DELETE /api/storagedomains/{storage_id}/disksnapshots/{image_id}| [Cannot remove Disk Snapshot. VM\'s Snapshot does not exist.] In conclusion: vm_disks can't be removed because of the non existent associated vm's snapshot id. I tried to remove vm_snapshots disks references directly into the postgres DB but I didn't find the correct table. What can I do now? Your precious help is welcome. -- Nathanaël Blanchet Supervision réseau SIRE 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

3 9

oVirt 4.4.10 Async update #2
by Sandro Bonazzola 30 Jan '22

30 Jan '22

On January 26th 2022 the oVirt project released an async update to the following packages: - ovirt-engine 4.4.10.6 Fixing the following bugs: - [BZ 2044277 <https://bugzilla.redhat.com/show_bug.cgi?id=2044277>] - Replace ovirt-engine-extension-logger-log4j with internal ovirt-engine implementation Package ovirt-engine-extension-logger-log4j has been obsoleted and replaced by internal ovirt-engine implementation in oVirt Engine 4.4.10.6. During upgrade from previous oVirt versions to oVirt 4.4.10 ovirt-engine-extension-logger-log4j package is uninstalled if it was previously installed. If you used ovirt-engine-extension-logger-log4j in previous oVirt versions, you will need to manually remove existing ovirt-engine-extension-logger-log4j configuration files and configure the new feature of sending log records to remote syslog service according to the Administration Guide. Also after successful upgrade to oVirt 4.4.10 you can manually uninstall log4j12 package without breaking oVirt setup: $ dnf remove log4j12 - [BZ 2044257 <https://bugzilla.redhat.com/show_bug.cgi?id=2044257>] - Bump snmp4j library version to remove dependency on log4j oVirt Engine 4.4.10.6 is requiring snmp4j >= 3.6.4, which no longer depends on log4j library -- 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.*

5 7

Problems with OVirt 4.3 on old IBM HS22 blades
by manieq.net＠gmail.com 28 Jan '22

28 Jan '22

Hi all, I'm pretty new to OVirt so forgive me if this problems is trivial... I received an old IBM BladeCenter H chassis with a few HS22 blades. Some of them are successfully working in my Ovirt farm, but some not. The NonOperational nodes are not used because of missing Westmere model. I use 4.3.10 wersion because 4.4 did not supported some old HW (net adapters, IIRC). The problem is that many blades are almost identical. For example ("Hosts" page --> "General" tab --> "Hardware" section): * BLADE 1 (not working): Manufacturer:IBM Family:System x Product Name:BladeCenter HS22 -[7870H4G]- Version:07 UUID:e36b6686-d111-11df-9dce-e41f13cb90d0 Serial Number:06FP476 CPU Model Name:Intel(R) Xeon(R) CPU X5670 @ 2.93GHz CPU Type:Intel Nehalem IBRS SSBD Family CPU Sockets:2 CPU Cores per Socket:6 CPU Threads per Core:2 (SMT Enabled) * BLADE 2 (working fine): Manufacturer: IBM Family: System x Product Name: BladeCenter HS22 -[7870H4G]- Version: 07 UUID: 30f2fcc8-d0ce-11df-bc12-e41f13cb90cc Serial Number: 06FP469 CPU Model Name: Intel(R) Xeon(R) CPU X5670 @ 2.93GHz CPU Type: Intel Westmere IBRS SSBD Family CPU Sockets: 2 CPU Cores per Socket: 6 CPU Threads per Core: 2 (SMT Enabled) They have same CPU, same HW model, even S/N shows they were produced in the same time. How is it possible to identify X5670 so differently? Any hints/suggestions what to check/change? "Software" section of BLADE 2 (the good one): OS Version: RHEL - 7 - 8.2003.0.el7.centos OS Description: oVirt Node 4.3.10 Kernel Version: 3.10.0 - 1127.8.2.el7.x86_64 KVM Version: 2.12.0 - 44.1.el7_8.1 LIBVIRT Version: libvirt-4.5.0-33.el7_8.1 VDSM Version: vdsm-4.30.46-1.el7 SPICE Version: 0.14.0 - 9.el7 GlusterFS Version: glusterfs-6.9-1.el7 CEPH Version: librbd1-10.2.5-4.el7 Open vSwitch Version: openvswitch-2.11.0-4.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1, SSBD: 3 VNC Encryption: Disabled Best regards, Mariusz

3 2

Re: [ovirt-devel] Re: how to UI/API certificates with a valid one (ex: let's encrypt) ? ( as open shift required one )
by Guillaume Pavese 26 Jan '22

26 Jan '22

Hello, I too have a problem using custom cert with OCP provisioning on oVirt I followed the following documentation to update the default cert with my letsencrypt one : https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/ht… This documentation is similar to the one linked by Yedidyah Bar David : https://www.ovirt.org/documentation/administration_guide/index.html#appe-Re… After following these steps, I can verify in my browser that the engine is now behind the new custom certificate from letsencrypt. However, the old certificate is still served by the url : https://engine.fqdn/ovirt-engine/services/pki-resource?resource=ca-certific… When running openshift-install create install-config, the certificate that is automaticlly retrived from engine.fqdn:443 is the old one, not the new custom one. Are there missing steps in the above procedures? Best, Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group On Tue, Jan 25, 2022 at 1:57 AM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > Il giorno dom 23 gen 2022 alle ore 08:15 Eric Tiquet < > eric.tiquet(a)gmail.com> ha scritto: > >> Hello community, >> Would like to use ovirt & openshift, a this might be trivial but I am >> juste blocked at 'step two'. >> (As openshift refuse to use the ovirt without valid certificates and the >> insecure workaround does'not work) >> >> I can't find any usefull information to setup the UI/API certificates. ( >> ex: there is no apache...) >> Could someone please point me to the correct tuto's or instruction ? >> > > This is the development mailing list. For looking for help on oVirt, I > recommend asking on user mailing list instead: > https://lists.ovirt.org/archives/list/users@ovirt.org/ . > I assume you are following > https://docs.okd.io/4.9/installing/installing_rhv/installing-rhv-default.ht… > > If the documentation there is not clear enough, I would recommend opening > an issue on https://github.com/openshift/openshift-docs/issues or > discussing it on https://github.com/openshift/okd/discussions > > > >> >> With kind regards, >> Eric >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-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/devel@ovirt.org/message/A6S264FUJVUNO… >> > > > -- > > 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.* > > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-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/devel@ovirt.org/message/Y4XAESPURFI2T… > -- 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

New oVirt setup with OVN : Hypervisor with LACP bond : queries
by ravi k 26 Jan '22

26 Jan '22

Hello team, Thank you for all the wonderful work you've been doing. I'm starting out new with oVirt and OVN. So please excuse me if the questions are too naive. We intend to do a POC to check if we can migrate VMs off our current VMware to oVirt. The intention is to migrate the VMs with the same IP into oVirt. We've setup oVirt with three hypervisors. All of them have four ethernet adapters. We have SDN implemented in our network and LACP bonds are created at the switch level. So we've created two bonds, bond0 and bond1 in each hypervisor. bond0 has the logical networks with vlan tagging created like bond0.101, bond0.102 etc. As a part of the POC we also want to explore OVN as well to check if we can implement a zero trust security policy. Here are the questions now :) 1. We would like to migrate VMs with the current IP into oVirt. Is it possible to achieve this? I've been reading notes and pages that mention about extending the physical network into OVN. But it's a bit confusing on how to implement it. How do we connect OVN to the physical network? Does the fact that we have a SDN make it easier to get this done? I am still reading the ovn-architecture page. It is mentioned that the gateway is the component that extends a tunnel-based logical network into a physical network. 2. We have the IP for the hypervisor assigned on a logical network(ovirtmgmt) in bond0. I read in https://lists.ovirt.org/archives/list/users@ovirt.org/thread/CIE6MZ47GRCEX4… that oVirt does not care about how the IP is configured when creating the tunnels. 3. Once we have OVN setup, ovn logical networks created and VMs created/migrated, how do we establish the zero trust policy? From what I've read there are ACLs and security groups. Any pointers on where to explore more about implementing it. If you've read till here, thank you for your patience. Regards, ravi

3 7

VM Migrations failing to newly upgraded host
by k.gunasekhar＠non.keysight.com 25 Jan '22

25 Jan '22

I am able to power on vms on newly upgraded host, But not able to migrate VMs from other hosts to new host or newly upgraded hosts to other hosts. This was worked fine before upgraded. i see below logs Unable to read from monitor: Connection reset by peer internal error: qemu unexpectedly closed the monitor: 2022-01-24T17:51:46.598571Z qemu-kvm: get_pci_config_device: Bad config > 2022-01-24T17:51:46.598627Z qemu-kvm: Failed to load PCIDevice:config 2022-01-24T17:51:46.598635Z qemu-kvm: Failed to load pcie-root-port:parent_obj.parent_obj.parent_obj 2022-01-24T17:51:46.598642Z qemu-kvm: error while loading state for instance 0x0 of device '0000:00:02.0/pcie-root-port' 2022-01-24T17:51:46.598830Z qemu-kvm: load of migration failed: Invalid argument Guest agent is not responding: QEMU guest agent is not connected Guest agent is not responding: QEMU guest agent is not connected Guest agent is not responding: QEMU guest agent is not connected OS Version: RHEL - 8.6 - 1.el8 OS Description: CentOS Stream 8 Kernel Version: 4.18.0 - 358.el8.x86_64 KVM Version: 6.1.0 - 5.module_el8.6.0+1040+0ae94936 LIBVIRT Version: libvirt-7.10.0-1.module_el8.6.0+1046+bd8eec5e VDSM Version: vdsm-4.40.100.2-1.el8 SPICE Version: 0.14.3 - 4.el8 GlusterFS Version: [N/A] CEPH Version: librbd1-16.2.7-1.el8s Open vSwitch Version: openvswitch-2.11-1.el8 Nmstate Version: nmstate-1.2.1-0.1.alpha1.el8

3 2

Migration failed due to an Error: Fatal error during migration
by Gunasekhar Kothapalli 25 Jan '22

25 Jan '22

I am able to power on vms on newly upgraded host, But not able to migrate VMs from other hosts to new host or newly upgraded hosts to other hosts. This was worked fine before upgraded. Host logs ============================================================================== Unable to read from monitor: Connection reset by peer internal error: qemu unexpectedly closed the monitor: 2022-01-24T17:51:46.598571Z qemu-kvm: get_pci_config_device: Bad config > 2022-01-24T17:51:46.598627Z qemu-kvm: Failed to load PCIDevice:config 2022-01-24T17:51:46.598635Z qemu-kvm: Failed to load pcie-root-port:parent_obj.parent_obj.parent_obj 2022-01-24T17:51:46.598642Z qemu-kvm: error while loading state for instance 0x0 of device '0000:00:02.0/pcie-root-port' 2022-01-24T17:51:46.598830Z qemu-kvm: load of migration failed: Invalid argument Guest agent is not responding: QEMU guest agent is not connected Guest agent is not responding: QEMU guest agent is not connected Guest agent is not responding: QEMU guest agent is not connected Engine Logs =========================================================== 2022-01-24 11:31:25,080-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-21) [] Adding VM '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) to re-run list 2022-01-24 11:31:25,099-07 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2331914) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal error during migration (VM: zzz2019, Source: lcoskvmp07.cos.is.keysight.com, Destination: lcoskvmp03.cos.is.keysight.com) 2022-01-24 18:39:47,897-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-771) [a78e85d4-068a-41c1-a8fa-b3acd8c69317] EVENT_ID: VM_MIGRATION_START(62), Migration started (VM: zzz2019, Source: lcoskvmp07.cos.is.keysight.com, Destination: lcoskvmp03.cos.is.keysight.com, User: k.gunasekhar@non.keysight.com@KEYSIGHT). 2022-01-24 18:40:01,417-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-27) [] VM '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) was unexpectedly detected as 'Down' on VDS 'ee23b44d-976d-4889-8769-59b56e4b23c0'(lcoskvmp03.cos.is.keysight.com) (expected on '0d58953f-b3cc-4bac-b3b2-08baeeee1bca') 2022-01-24 18:40:01,589-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-27) [] VM '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) was unexpectedly detected as 'Down' on VDS 'ee23b44d-976d-4889-8769-59b56e4b23c0'(lcoskvmp03.cos.is.keysight.com) (expected on '0d58953f-b3cc-4bac-b3b2-08baeeee1bca') 2022-01-24 18:40:01,589-07 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-27) [] Migration of VM 'zzz2019' to host 'lcoskvmp03.cos.is.keysight.com' failed: VM destroyed during the startup. 2022-01-24 18:40:01,591-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-17) [] VM '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) moved from 'MigratingFrom' --> 'Up' 2022-01-24 18:40:01,591-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-17) [] Adding VM '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) to re-run list 2022-01-24 18:40:01,611-07 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2348837) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal error during migration (VM: zzz2019, Source: lcoskvmp07.cos.is.keysight.com, Destination: lcoskvmp03.cos.is.keysight.com) [root@lcosovirt02 ovirt-engine]#

3 3

Import an exported VM using Ansible
by paolo＠airaldi.it 25 Jan '22

25 Jan '22

Hello everybody! I'm trying to automate a copy of a VM from one Datacenter to another using an Ansible.playbook. I'm able to: - Create a snapshot of the source VM - create a clone from the snapshot - remove the snapshot - attach an Export Domain - export the clone to the Export Domain - remove the clone - detach the Export domain from the source Datacenter and attach to the destination. Unfortunately I cannot find a module to: - import the VM from the Export Domain - delete the VM image from the Export Domain. Any hint on how to do that? Thanks in advance. Cheers. Paolo PS: if someone is interested I can share the playbook.

4 3

Can't upgrade ovirt 4.4.3 to 4.4.9
by jihwahn1018＠naver.com 25 Jan '22

25 Jan '22

Hello, I tried to upgrade ovirt to 4.4.9 from 4.4.3 when i do 'engine-setup' i get error -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [ ERROR ] Failed to execute stage 'Misc configuration': Command '/usr/share/ovirt-engine-dwh/dbscripts/schema.sh' failed to execute [ INFO ] DNF Performing DNF transaction rollback [ ERROR ] DNF module 'dnf.history' has no attribute 'open_history' -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- from the log i found that column "count_threads_as_cores" does not exist --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 193375 2022-01-18 16:36:26,309+0900 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.db.schema plugin.execute :926 execute-output: ['/usr/share/ovirt-engine-dwh/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u ', 'ovirt_engine_history', '-d', 'ovirt_engine_history', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setu p-20220118162426-z0o4xg.log', '-c', 'apply'] stderr: 193376 psql:/usr/share/ovirt-engine-dwh/dbscripts/create_views_4_4.sql:148: ERROR: column "count_threads_as_cores" does not exist 193377 LINE 10: count_threads_as_cores as count_threads_as_cores, 193378 ^ 193379 FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine-dwh/dbscripts/create_views_4_4.sql 193380 193381 2022-01-18 16:36:26,309+0900 DEBUG otopi.context context._executeMethod:145 method exception 193382 Traceback (most recent call last): 193383 File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod 193384 method['method']() 193385 File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-dwh/db/schema.py", line 367, in _misc 193386 odwhcons.DBEnv.PGPASS_FILE 193387 File "/usr/lib/python3.6/site-packages/otopi/plugin.py", line 931, in execute 193388 command=args[0], 193389 RuntimeError: Command '/usr/share/ovirt-engine-dwh/dbscripts/schema.sh' failed to execute 193390 2022-01-18 16:36:26,330+0900 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc con figuration': Command '/usr/share/ovirt-engine-dwh/dbscripts/schema.sh' failed to execute 193391 2022-01-18 16:36:26,330+0900 DEBUG otopi.transaction transaction.abort:119 aborting 'DNF Transaction' 193392 2022-01-18 16:36:26,331+0900 DEBUG otopi.plugins.otopi.packagers.dnfpackager dnfpackager.verbose:75 DNF Closi ng transaction with rollback 193393 2022-01-18 16:36:26,731+0900 INFO otopi.plugins.otopi.packagers.dnfpackager dnfpackager.info:79 DNF Performin g DNF transaction rollback 193394 2022-01-18 16:36:27,570+0900 ERROR otopi.plugins.otopi.packagers.dnfpackager dnfpackager.error:84 DNF module 'dnf.history' has no attribute 'open_history' 193395 2022-01-18 16:36:27,571+0900 DEBUG otopi.transaction transaction.abort:125 Unexpected exception from abort() of 'DNF Transaction' -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- when i search for this problem, i found that column "count_threads_as_cores" is added from ovirt-engine 4.4.6.7. and ovirt-dwh 4.4.7. do i need to update 4.4.3 to 4.4.6( or 4.4.7) then 4.4.6(or 4.4.7) to 4.4.9? Thanks, Jihwan

4 9

HostedEngine deployment fails
by Christoph Köhler 24 Jan '22

24 Jan '22

Hello, on CentOS Stream the deployment of HE fails with the following message: [ INFO ] TASK [ovirt.ovirt.engine_setup : Gather facts on installed packages] [ INFO ] ok: [localhost -> 192.168.1.239] [ INFO ] TASK [ovirt.ovirt.engine_setup : Fail when firewall manager is not installed] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.engine_setup : Install required packages for oVirt Engine deployment] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package] [ ERROR ] fatal: [localhost -> 192.168.1.239]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'ovirt-4.4-centos-ceph-pacific': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", "rc": 1, "results": []} It's because we have to use a proxy. It is configured on the host but setup does not deliver it into the appliance (temporarily HE). So what to do? Howto tell setup to use a proxy in HE appliance? Thank you for hits! Chris

3 2

About go-ovirt Library
by Yusuf Papurcu 24 Jan '22

24 Jan '22

After v4.3.4 this package is unable to get via go modules. Please check this out.

2 1

Re: Failed HostedEngine Deployment
by Strahil Nikolov 24 Jan '22

24 Jan '22

yum downgrade qemu-kvm-block-gluster-6.0.0-33.el8s libvirt-daemon-driver-qemu-6.0.0-33.el8s qemu-kvm-common-6.0.0-33.el8s qemu-kvm-hw-usbredir-6.0.0-33.el8s qemu-kvm-ui-opengl-6.0.0-33.el8s qemu-kvm-block-rbd-6.0.0-33.el8s qemu-img-6.0.0-33.el8s qemu-kvm-6.0.0-33.el8s qemu-kvm-block-curl-6.0.0-33.el8s qemu-kvm-block-ssh-6.0.0-33.el8s qemu-kvm-ui-spice-6.0.0-33.el8s ipxe-roms-qemu-6.0.0-33.el8s qemu-kvm-core-6.0.0-33.el8s qemu-kvm-docs-6.0.0-33.el8s qemu-kvm-block-6.0.0-33.el8s Best Regards,Strahil Nikolov On Sun, Jan 23, 2022 at 22:47, Robert Tongue<phunyguy(a)neverserio.us> wrote: #yiv7072323153 P {margin-top:0;margin-bottom:0;}Ahh, I did some repoquery commands can see a good bit of qemu* packages are coming from appstream rather than ovirt-4.4-centos-stream-advanced-virtualization. What's the recommanded fix?From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Sunday, January 23, 2022 3:41 PM To: users <users(a)ovirt.org>; Robert Tongue <phunyguy(a)neverserio.us> Subject: Re: [ovirt-users] Failed HostedEngine Deployment I've seen this. Ensure that all qemu-related packages are coming from centos-advanced-virtualization repo (6.0.0-33.el8s.x86_64). There is a known issue with the latest packages in the CentOS Stream. Also, you can set the following alias on the Hypervisours: alias virsh='virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf' Best Regards, Strahil Nikolov В неделя, 23 януари 2022 г., 21:14:20 Гринуич+2, Robert Tongue <phunyguy(a)neverserio.us> написа: Greetings oVirt people, I am having a problem with the hosted-engine deployment, and unfortunately after a weekend spent trying to get this far, I am finally stuck, and cannot figure out how to fix this. I am starting with 1 host, and will have 4 when this is finished. Storage is GlusterFS, hyperconverged, but I am managing that myself outside of oVirt. It's a single-node GlusterFS volume, which I will expand out across the other 4 nodes as well. I get all the way through the initial hosted-engine deployment (via the cockpit interface) pre-storage, then get most of the way through the storage portion of it. It fails at starting the HostedEngine VM in its final state after copying the VM disk to shared storage. This is where it gets weird. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Engine VM IP address is while the engine's he_fqdn ovirt.deleted.domain resolves to 192.168.x.x. If you are using DHCP, check your DHCP reservation configuration"} I've masked out the domain and IP for obvious reasons. However I think this deployment error isn't really the reason for the failure, it's just where it is at when it fails. The HostedEngine VM is starting, but not actually booting. I was able to change the VNC password with `hosted-engine --add-console-password`, and see the local console display with that, however it just displays "The guest has not initialized the display (yet)". I also did: # hosted-engine --consoleThe engine VM is running on this hostEscape character is ^] Yet that doesn't move any further, nor allow any input. The VM does not respond on the network. I am thinking it's just not making it to the initial BIOS screen and booting at all. What would cause that? Here is the glusterfs volume for clarity. # gluster volume info storage Volume Name: storageType: DistributeVolume ID: e9544310-8890-43e3-b49c-6e8c7472dbbbStatus: StartedSnapshot Count: 0Number of Bricks: 1Transport-type: tcpBricks:Brick1: node1:/var/glusterfs/storage/1Options Reconfigured:storage.owner-gid: 36storage.owner-uid: 36network.ping-timeout: 5performance.client-io-threads: onserver.event-threads: 4client.event-threads: 4cluster.choose-local: offuser.cifs: offfeatures.shard: oncluster.shd-wait-qlength: 1024cluster.locking-scheme: fullcluster.data-self-heal-algorithm: fullcluster.server-quorum-type: servercluster.quorum-type: autocluster.eager-lock: enableperformance.strict-o-direct: onnetwork.remote-dio: disableperformance.low-prio-threads: 32performance.io-cache: offperformance.read-ahead: offperformance.quick-read: offstorage.fips-mode-rchecksum: ontransport.address-family: inetnfs.disable: on # cat /proc/cpuinfoprocessor : 0vendor_id : GenuineIntelcpu family : 6model : 58model name : Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHzstepping : 9microcode : 0x21cpu MHz : 4000.000cache size : 8192 KBphysical id : 0siblings : 8core id : 0cpu cores : 4apicid : 0initial apicid : 0fpu : yesfpu_exception : yescpuid level : 13wp : yesflags : 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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1dbugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbdsbogomips : 7199.86clflush size : 64cache_alignment: 64address sizes : 36 bits physical, 48 bits virtualpower management: [ plus 7 more ] Thanks for any insight that can be provided. _______________________________________________ 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/JZQYGXQP5DO4H…

2 1

Major problems after upgrading 2 (of 4) Red Hat hosts to 4.4.10
by David White 23 Jan '22

23 Jan '22

I have a Hyperconverged cluster with 4 hosts. Gluster is replicated across 2 hosts, and a 3rd host is an arbiter node. The 4th host is compute only. I updated the compute-only node, as well as the arbiter node, early this morning. I didn't touch either of the actual storage nodes.That said, I forgot to upgrade the engine. oVirt Manager thinks that all but 1 of the hosts in the cluster are unhealthy. However, all 4 hosts are online. oVirt Manager (Engine) also keeps deactivating at least 1, if not 2 of the 3 (total) bricks behind each volume. Even though the Engine thinks that only 1 host is healthy, VMs are clearly running on some of the other hosts. However, in troubleshooting, some of the customer VMs were turned off, and oVirt is refusing to start those VMs, because it only recognizes that 1 of the hosts is healthy -- and that host's resources are maxed out. This afternoon, I went ahead and upgraded (and rebooted) the Engine VM, so it is now up-to-date. Unfortunately, that didn't resolve the issue. So I took one of the "unhealthy" hosts which didn't have any VMs on it (which was the host that is our compute-only server hosting no gluster data), and I used oVirt to "reinstall" the oVirt software. That didn't resolve the issue for that host. How can I troubleshoot this? I need: - To figure out why oVirt keeps trying to deactivate volumes - From the command line, `gluster peer status` show all nodes connected, and all volumes appear to be healthy - More importantly, I need to get these VMs that are currently down back online. Is there a way to somehow force oVirt to launch the VMs on the "unhealthy" nodes? What logs should I be looking at? Any help would be greatly appreciated . Sent with ProtonMail Secure Email.

2 5

Re: Failed HostedEngine Deployment
by Strahil Nikolov 23 Jan '22

23 Jan '22

I've seen this. Ensure that all qemu-related packages are coming from centos-advanced-virtualization repo (6.0.0-33.el8s.x86_64). There is a known issue with the latest packages in the CentOS Stream. Also, you can set the following alias on the Hypervisours: alias virsh='virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf' Best Regards, Strahil Nikolov В неделя, 23 януари 2022 г., 21:14:20 Гринуич+2, Robert Tongue <phunyguy(a)neverserio.us> написа: #yiv4464233184 P {margin-top:0;margin-bottom:0;}Greetings oVirt people, I am having a problem with the hosted-engine deployment, and unfortunately after a weekend spent trying to get this far, I am finally stuck, and cannot figure out how to fix this. I am starting with 1 host, and will have 4 when this is finished. Storage is GlusterFS, hyperconverged, but I am managing that myself outside of oVirt. It's a single-node GlusterFS volume, which I will expand out across the other 4 nodes as well. I get all the way through the initial hosted-engine deployment (via the cockpit interface) pre-storage, then get most of the way through the storage portion of it. It fails at starting the HostedEngine VM in its final state after copying the VM disk to shared storage. This is where it gets weird. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Engine VM IP address is while the engine's he_fqdn ovirt.deleted.domain resolves to 192.168.x.x. If you are using DHCP, check your DHCP reservation configuration"} I've masked out the domain and IP for obvious reasons. However I think this deployment error isn't really the reason for the failure, it's just where it is at when it fails. The HostedEngine VM is starting, but not actually booting. I was able to change the VNC password with `hosted-engine --add-console-password`, and see the local console display with that, however it just displays "The guest has not initialized the display (yet)". I also did: # hosted-engine --consoleThe engine VM is running on this hostEscape character is ^] Yet that doesn't move any further, nor allow any input. The VM does not respond on the network. I am thinking it's just not making it to the initial BIOS screen and booting at all. What would cause that? Here is the glusterfs volume for clarity. # gluster volume info storage Volume Name: storageType: DistributeVolume ID: e9544310-8890-43e3-b49c-6e8c7472dbbbStatus: StartedSnapshot Count: 0Number of Bricks: 1Transport-type: tcpBricks:Brick1: node1:/var/glusterfs/storage/1Options Reconfigured:storage.owner-gid: 36storage.owner-uid: 36network.ping-timeout: 5performance.client-io-threads: onserver.event-threads: 4client.event-threads: 4cluster.choose-local: offuser.cifs: offfeatures.shard: oncluster.shd-wait-qlength: 1024cluster.locking-scheme: fullcluster.data-self-heal-algorithm: fullcluster.server-quorum-type: servercluster.quorum-type: autocluster.eager-lock: enableperformance.strict-o-direct: onnetwork.remote-dio: disableperformance.low-prio-threads: 32performance.io-cache: offperformance.read-ahead: offperformance.quick-read: offstorage.fips-mode-rchecksum: ontransport.address-family: inetnfs.disable: on # cat /proc/cpuinfoprocessor : 0vendor_id : GenuineIntelcpu family : 6model : 58model name : Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHzstepping : 9microcode : 0x21cpu MHz : 4000.000cache size : 8192 KBphysical id : 0siblings : 8core id : 0cpu cores : 4apicid : 0initial apicid : 0fpu : yesfpu_exception : yescpuid level : 13wp : yesflags : 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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1dbugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbdsbogomips : 7199.86clflush size : 64cache_alignment: 64address sizes : 36 bits physical, 48 bits virtualpower management: [ plus 7 more ] Thanks for any insight that can be provided. _______________________________________________ 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/JZQYGXQP5DO4H…

2 2

Failed HostedEngine Deployment
by Robert Tongue 23 Jan '22

23 Jan '22

Greetings oVirt people, I am having a problem with the hosted-engine deployment, and unfortunately after a weekend spent trying to get this far, I am finally stuck, and cannot figure out how to fix this. I am starting with 1 host, and will have 4 when this is finished. Storage is GlusterFS, hyperconverged, but I am managing that myself outside of oVirt. It's a single-node GlusterFS volume, which I will expand out across the other 4 nodes as well. I get all the way through the initial hosted-engine deployment (via the cockpit interface) pre-storage, then get most of the way through the storage portion of it. It fails at starting the HostedEngine VM in its final state after copying the VM disk to shared storage. This is where it gets weird. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Engine VM IP address is while the engine's he_fqdn ovirt.deleted.domain resolves to 192.168.x.x. If you are using DHCP, check your DHCP reservation configuration"} I've masked out the domain and IP for obvious reasons. However I think this deployment error isn't really the reason for the failure, it's just where it is at when it fails. The HostedEngine VM is starting, but not actually booting. I was able to change the VNC password with `hosted-engine --add-console-password`, and see the local console display with that, however it just displays "The guest has not initialized the display (yet)". I also did: # hosted-engine --console The engine VM is running on this host Escape character is ^] Yet that doesn't move any further, nor allow any input. The VM does not respond on the network. I am thinking it's just not making it to the initial BIOS screen and booting at all. What would cause that? Here is the glusterfs volume for clarity. # gluster volume info storage Volume Name: storage Type: Distribute Volume ID: e9544310-8890-43e3-b49c-6e8c7472dbbb Status: Started Snapshot Count: 0 Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: node1:/var/glusterfs/storage/1 Options Reconfigured: storage.owner-gid: 36 storage.owner-uid: 36 network.ping-timeout: 5 performance.client-io-threads: on server.event-threads: 4 client.event-threads: 4 cluster.choose-local: off user.cifs: off features.shard: on cluster.shd-wait-qlength: 1024 cluster.locking-scheme: full cluster.data-self-heal-algorithm: full cluster.server-quorum-type: server cluster.quorum-type: auto cluster.eager-lock: enable performance.strict-o-direct: on network.remote-dio: disable performance.low-prio-threads: 32 performance.io-cache: off performance.read-ahead: off performance.quick-read: off storage.fips-mode-rchecksum: on transport.address-family: inet nfs.disable: on # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHz stepping : 9 microcode : 0x21 cpu MHz : 4000.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds bogomips : 7199.86 clflush size : 64 cache_alignment: 64 address sizes : 36 bits physical, 48 bits virtual power management: [ plus 7 more ] Thanks for any insight that can be provided.

1 0

How does the Stream based management engine transition to RHV?
by Thomas Hoberg 23 Jan '22

23 Jan '22

In the recent days, I've been trying to validate the transition from CentOS 8 to Alma, Rocky, Oracle and perhaps soon Liberty Linux for existing HCI clusters. I am using nested virtualization on a VMware workstation host, because I understand snapshoting and linked clones much better on VMware, even if I've tested nested virtualization to some degree with oVirt as well. It makes moving forth and back between distros and restarting failed oVirt deployments much easier and more reliable than ovirt-hosted-engine-cleanup. Installing oVirt 4.10 on TrueCentOS systems, which had been freshly switched to Alma, Rocky and Oracle went relatively well, apart from Oracle pushing UEK kernels, which break VDO (and some Python2 mishaps). I'm still testing transitioning pre-existing TrueCentOS HCI glusters to Alma, Rocky and Oracle. While that solves the issue of having the hosts running a mature OS which is downstream of RHEL, there is still an issue with the management engine being based on the upstream stream release: It doesn't have the vulnerability managment baked in, which is required even for labs use in an enterprise. So I'd like to ask our Redhat friends here: How does this work when releases of oVirt transition to RHV? Do you backport oVirt changes from Stream to RHEL? When bugs are found in that process, are they then fed back into oVirt or into the oVirt-to-RHEV proces?

2 1

CentOS 8.4 Linux hosts from 4.4.8 to Rocky Linux 4.4.10
by Gianluca Cecchi 23 Jan '22

23 Jan '22

Hello, after updating the external engine from CentOS 8.4 and 4.4.8 to Rocky Linux 8.5 and 4.4.9 as outlined here: https://lists.ovirt.org/archives/list/users@ovirt.org/message/YUDJRC22SQPAP… I went further and updated also the hosts. Environment is with an external engine and 3 CentOS Linux 8.4 hosts in 4.4.8 with iSCSI storage domain. Preliminarily I upgraded the engine to 4.4.10 (not yet the just released async) without problems. Then, one host at a time: . put host into maintenance from web admin UI Management --> Maintenance . In a terminal f host set proxy for my environment needs export https_proxy=http://my_proxy:my_proxy_port export http_proxy=http://my_proxy:my_proxy_port (not sure if this necessary...) . in the same terminal execute migration script ./migrate2rocky.sh -r . executed Management --> SSH Management --> SSH Restart from web admin ui the host comes on in maintenance mode . selected Installation --> Check for Upgrade but the host is detected as already update . for further security and to be sure that all upgrade steps are applied I executed Installation --> Reinstall I deselected - activate host after install - reboot host after install It went ok so . executed Management --> SSH Management --> SSH Restart from web admin ui the host comes on in maintenance mode . Management --> Activate . Empty another host moving its VMs to the just updated host and continue in the same way, also electing as new SPM the updated host All went smoothly and without VMs disruption. Let's see how it goes next days with the light workload I have on this testing environment. Currently the async 1 of 4.4.10 is not catched up by engine-upgrade-check command.. I'm going to retry applying again during the next few days. Gianluca

2 1

mdadm vs. JBOD
by jonas＠rabe.ch 22 Jan '22

22 Jan '22

Hi, We are currently building a three node hyper-converged cluster based on oVirt Node and Gluster. While discussing the different storage layout we couldn't get to a final decision. Currently our servers are equipped as follows: - servers 1 & 2: - Two 800GB disks for OS - 100GB RAID1 used as LVM PV for OS - Nine 7.68TB disks for Gluster - 60TB RAID 5 used as LVM PV for Gluster - server 3 - Two 800GB disks for OS & Gluster - 100GB RAID 1 used as LVM PV for OS - 700GB RAID 1 used as LVM PV for Gluster Unfortunately I couldn't find much information about mdadm on this topic. The hyper-convergence guides ([1], [2]) seem to assume that there is either a hardware RAID in place or JBOD is used. Is there some documentation available on what to consider when using mdadm? Or would it be more sensible to just use JBOD and then add redundancy on the LVM or Gluster level? If choosing to go with mdadm, what option should I choose in the bricks wizard screen (RAID 5 or JBOD)? [1]: https://ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_Hyper… [2]: https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infras…

3 4

oVirt 4.4.10 Async update #1
by Sandro Bonazzola 21 Jan '22

21 Jan '22

On January 21st 2022 the oVirt project released an async update to the following packages: ovirt-engine 4.4.10.5 Fixing the following bugs: - [BZ 1854038 <https://bugzilla.redhat.com/1854038>] - Download or upload disk (SDK) fails due to 'Timed out waiting for transfer XXX to finalize' - [BZ 2013430 <https://bugzilla.redhat.com/2013430>] - oVirt 4.4. FIPS install leaves UUID blank in grub after setting kernel option - [BZ 2037216 <https://bugzilla.redhat.com/show_bug.cgi?id=2037216>] - VM imported from configuration is stuck in WaitForLaunch once removed quickly after power-off -- 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

oVirt 4.4.10 is now generally available
by Sandro Bonazzola 21 Jan '22

21 Jan '22

oVirt 4.4.10 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.10 , as of January 18th, 2022. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.10 Release? This update is the ninth in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.5 (or similar) - CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.5 (or similar) - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 Some of the RFEs with high user impact are listed below: - Bug 2012135 <https://bugzilla.redhat.com/show_bug.cgi?id=2012135> - [RFE] Provide option to unmap multiple LUNs using ovirt_remove_stale_lun ansible role Some of the Bugs with high user impact are listed below: - Bug 1710323 <https://bugzilla.redhat.com/show_bug.cgi?id=1710323> - Microsoft failover cluster is not working with FC direct LUN on Windows 2016 server and Windows 2019 - Bug 2023224 <https://bugzilla.redhat.com/show_bug.cgi?id=2023224> - multipath -f fails with "map in use" error while removing the LUNs using "ovirt_remove_stale_lun" - Bug 2027260 <https://bugzilla.redhat.com/show_bug.cgi?id=2027260> - Cold backup fail in various ways - backup is reported ready before add_bitmap jobs complete - Bug 1897114 <https://bugzilla.redhat.com/show_bug.cgi?id=1897114> - Add additional logging information to be able to understand why host is stuck in Unassigned state - Bug 1978655 <https://bugzilla.redhat.com/show_bug.cgi?id=1978655> - ELK integration fails due to missing configuration parameters - Bug 2032919 <https://bugzilla.redhat.com/show_bug.cgi?id=2032919> - Unable to add EL 7 host into oVirt Engine in clusters 4.2/4.3 oVirt Node has been updated, including: - oVirt 4.4.10: https://www.ovirt.org/release/4.4.10/ - CentOS Stream 8 latest updates - Full list of changes: --- ovirt-node-ng-image-4.4.9.3.manifest-rpm 2021-12-15 15:40:13.501764699 +0100 +++ ovirt-node-ng-image-4.4.10.manifest-rpm 2022-01-19 08:09:36.668868583 +0100 @@ -2,7 +2,6 @@ -ModemManager-glib-1.18.2-1.el8.x86_64 -NetworkManager-1.36.0-0.2.el8.x86_64 -NetworkManager-config-server-1.36.0-0.2.el8.noarch -NetworkManager-libnm-1.36.0-0.2.el8.x86_64 -NetworkManager-ovs-1.36.0-0.2.el8.x86_64 -NetworkManager-team-1.36.0-0.2.el8.x86_64 -NetworkManager-tui-1.36.0-0.2.el8.x86_64 +NetworkManager-1.36.0-0.3.el8.x86_64 +NetworkManager-config-server-1.36.0-0.3.el8.noarch +NetworkManager-libnm-1.36.0-0.3.el8.x86_64 +NetworkManager-ovs-1.36.0-0.3.el8.x86_64 +NetworkManager-team-1.36.0-0.3.el8.x86_64 +NetworkManager-tui-1.36.0-0.3.el8.x86_64 @@ -23 +22 @@ -alsa-lib-1.2.5-4.el8.x86_64 +alsa-lib-1.2.6.1-1.el8.x86_64 @@ -29,2 +28,2 @@ -augeas-1.12.0-6.el8.x86_64 -augeas-libs-1.12.0-6.el8.x86_64 +augeas-1.12.0-7.el8.x86_64 +augeas-libs-1.12.0-7.el8.x86_64 @@ -34 +33 @@ -autofs-5.1.4-74.el8.x86_64 +autofs-5.1.4-77.el8.x86_64 @@ -44 +43 @@ -binutils-2.30-111.el8.x86_64 +binutils-2.30-112.el8.x86_64 @@ -46 +45 @@ -blivet-data-3.4.0-7.el8.noarch +blivet-data-3.4.0-8.el8.noarch @@ -58 +57 @@ -ceph-common-16.2.6-1.el8s.x86_64 +ceph-common-16.2.7-1.el8s.x86_64 @@ -63,6 +62,6 @@ -clevis-15-4.el8.x86_64 -clevis-dracut-15-4.el8.x86_64 -clevis-luks-15-4.el8.x86_64 -clevis-systemd-15-4.el8.x86_64 -cockpit-258-1.el8.x86_64 -cockpit-bridge-258-1.el8.x86_64 +clevis-15-6.el8.x86_64 +clevis-dracut-15-6.el8.x86_64 +clevis-luks-15-6.el8.x86_64 +clevis-systemd-15-6.el8.x86_64 +cockpit-260-1.el8.x86_64 +cockpit-bridge-260-1.el8.x86_64 @@ -70,3 +69,3 @@ -cockpit-storaged-255-1.el8.noarch -cockpit-system-258-1.el8.noarch -cockpit-ws-258-1.el8.x86_64 +cockpit-storaged-259-1.el8.noarch +cockpit-system-260-1.el8.noarch +cockpit-ws-260-1.el8.x86_64 @@ -116 +115 @@ -dmidecode-3.2-10.el8.x86_64 +dmidecode-3.3-1.el8.x86_64 @@ -193 +192 @@ -fwupd-1.5.9-1.el8_4.x86_64 +fwupd-1.7.1-1.el8.x86_64 @@ -196 +195 @@ -gdb-headless-8.2-17.el8.x86_64 +gdb-headless-8.2-18.el8.x86_64 @@ -206,4 +205,3 @@ -glibc-2.28-174.el8.x86_64 -glibc-common-2.28-174.el8.x86_64 -glibc-gconv-extra-2.28-174.el8.x86_64 -glibc-langpack-en-2.28-174.el8.x86_64 +glibc-2.28-181.el8.x86_64 +glibc-common-2.28-181.el8.x86_64 +glibc-langpack-en-2.28-181.el8.x86_64 @@ -244 +242 @@ -gssproxy-0.8.0-19.el8.x86_64 +gssproxy-0.8.0-20.el8.x86_64 @@ -253 +251 @@ -hwdata-0.314-8.10.el8.noarch +hwdata-0.314-8.11.el8.noarch @@ -260,4 +258,4 @@ -ipa-client-4.9.6-6.module_el8.5.0+947+fabc681e.x86_64 -ipa-client-common-4.9.6-6.module_el8.5.0+947+fabc681e.noarch -ipa-common-4.9.6-6.module_el8.5.0+947+fabc681e.noarch -ipa-selinux-4.9.6-6.module_el8.5.0+947+fabc681e.noarch +ipa-client-4.9.8-2.module_el8.6.0+1054+cdb51b28.x86_64 +ipa-client-common-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch +ipa-common-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch +ipa-selinux-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch @@ -275 +273 @@ -iputils-20180629-7.el8.x86_64 +iputils-20180629-8.el8.x86_64 @@ -303,6 +301,6 @@ -kernel-4.18.0-348.2.1.el8_5.x86_64 -kernel-core-4.18.0-348.2.1.el8_5.x86_64 -kernel-modules-4.18.0-348.2.1.el8_5.x86_64 -kernel-tools-4.18.0-348.2.1.el8_5.x86_64 -kernel-tools-libs-4.18.0-348.2.1.el8_5.x86_64 -kexec-tools-2.0.20-63.el8.x86_64 +kernel-4.18.0-358.el8.x86_64 +kernel-core-4.18.0-358.el8.x86_64 +kernel-modules-4.18.0-358.el8.x86_64 +kernel-tools-4.18.0-358.el8.x86_64 +kernel-tools-libs-4.18.0-358.el8.x86_64 +kexec-tools-2.0.20-67.el8.x86_64 @@ -312 +310 @@ -kmod-kvdo-6.2.5.72-81.el8.x86_64 +kmod-kvdo-6.2.6.3-82.el8.x86_64 @@ -359 +357 @@ -libcephfs2-16.2.6-1.el8s.x86_64 +libcephfs2-16.2.7-1.el8s.x86_64 @@ -381 +379 @@ -libgcc-8.5.0-6.el8.x86_64 +libgcc-8.5.0-7.el8.x86_64 @@ -393 +391 @@ -libgomp-8.5.0-6.el8.x86_64 +libgomp-8.5.0-7.el8.x86_64 @@ -401 +399 @@ -libibverbs-37.1-1.el8.x86_64 +libibverbs-37.2-1.el8.x86_64 @@ -405 +403 @@ -libipa_hbac-2.5.2-2.el8_5.1.x86_64 +libipa_hbac-2.6.1-2.el8.x86_64 @@ -418 +415,0 @@ -libmbim-1.26.0-2.el8.x86_64 @@ -434 +431 @@ -libosinfo-1.9.0-1.el8.x86_64 +libosinfo-1.9.0-2.el8.x86_64 @@ -441 +437,0 @@ -libpmemobj-1.6.1-1.el8.x86_64 @@ -447 +442,0 @@ -libqmi-1.30.2-1.el8.x86_64 @@ -449,3 +444,3 @@ -librados2-16.2.6-1.el8s.x86_64 -libradosstriper1-16.2.6-1.el8s.x86_64 -librbd1-16.2.6-1.el8s.x86_64 +librados2-16.2.7-1.el8s.x86_64 +libradosstriper1-16.2.7-1.el8s.x86_64 +librbd1-16.2.7-1.el8s.x86_64 @@ -453 +448 @@ -librdmacm-37.1-1.el8.x86_64 +librdmacm-37.2-1.el8.x86_64 @@ -463 +458 @@ -librgw2-16.2.6-1.el8s.x86_64 +librgw2-16.2.7-1.el8s.x86_64 @@ -477,7 +472,7 @@ -libsss_autofs-2.5.2-2.el8_5.1.x86_64 -libsss_certmap-2.5.2-2.el8_5.1.x86_64 -libsss_idmap-2.5.2-2.el8_5.1.x86_64 -libsss_nss_idmap-2.5.2-2.el8_5.1.x86_64 -libsss_simpleifp-2.5.2-2.el8_5.1.x86_64 -libsss_sudo-2.5.2-2.el8_5.1.x86_64 -libstdc++-8.5.0-6.el8.x86_64 +libsss_autofs-2.6.1-2.el8.x86_64 +libsss_certmap-2.6.1-2.el8.x86_64 +libsss_idmap-2.6.1-2.el8.x86_64 +libsss_nss_idmap-2.6.1-2.el8.x86_64 +libsss_simpleifp-2.6.1-2.el8.x86_64 +libsss_sudo-2.6.1-2.el8.x86_64 +libstdc++-8.5.0-7.el8.x86_64 @@ -536 +531 @@ -libwbclient-4.14.5-2.el8.x86_64 +libwbclient-4.15.3-0.el8.x86_64 @@ -570 +565 @@ -mdadm-4.2-rc2.el8.x86_64 +mdadm-4.2-rc3.el8.x86_64 @@ -598,4 +593,4 @@ -net-snmp-5.8-23.el8.x86_64 -net-snmp-agent-libs-5.8-23.el8.x86_64 -net-snmp-libs-5.8-23.el8.x86_64 -net-snmp-utils-5.8-23.el8.x86_64 +net-snmp-5.8-24.el8.x86_64 +net-snmp-agent-libs-5.8-24.el8.x86_64 +net-snmp-libs-5.8-24.el8.x86_64 +net-snmp-utils-5.8-24.el8.x86_64 @@ -609,2 +604,2 @@ -nmstate-1.2.0-0.1.alpha2.el8.x86_64 -nmstate-plugin-ovsdb-1.2.0-0.1.alpha2.el8.noarch +nmstate-1.2.0-1.el8.x86_64 +nmstate-plugin-ovsdb-1.2.0-1.el8.noarch @@ -640 +635 @@ -osinfo-db-20210903-1.el8.noarch +osinfo-db-20211216-1.el8.noarch @@ -643 +638 @@ -ovirt-ansible-collection-1.6.5-1.el8.noarch +ovirt-ansible-collection-1.6.6-1.el8.noarch @@ -646 +641 @@ -ovirt-hosted-engine-ha-2.4.9-1.el8.noarch +ovirt-hosted-engine-ha-2.4.10-1.el8.noarch @@ -651 +646 @@ -ovirt-node-ng-image-update-placeholder-4.4.9.3-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.10-1.el8.noarch @@ -659,2 +654,2 @@ -ovirt-release-host-node-4.4.9.3-1.el8.noarch -ovirt-release44-4.4.9.3-1.el8.noarch +ovirt-release-host-node-4.4.10-1.el8.noarch +ovirt-release44-4.4.10-1.el8.noarch @@ -667,3 +662,3 @@ -pacemaker-cluster-libs-2.1.2-1.el8.x86_64 -pacemaker-libs-2.1.2-1.el8.x86_64 -pacemaker-schemas-2.1.2-1.el8.noarch +pacemaker-cluster-libs-2.1.2-2.el8.x86_64 +pacemaker-libs-2.1.2-2.el8.x86_64 +pacemaker-schemas-2.1.2-2.el8.noarch @@ -677 +672 @@ -pcsc-lite-1.8.23-4.1.el8_4.x86_64 +pcsc-lite-1.9.5-1.el8.x86_64 @@ -679 +674 @@ -pcsc-lite-libs-1.8.23-4.1.el8_4.x86_64 +pcsc-lite-libs-1.9.5-1.el8.x86_64 @@ -747 +742 @@ -python3-blivet-3.4.0-7.el8.noarch +python3-blivet-3.4.0-8.el8.noarch @@ -750,3 +745,3 @@ -python3-ceph-argparse-16.2.6-1.el8s.x86_64 -python3-ceph-common-16.2.6-1.el8s.x86_64 -python3-cephfs-16.2.6-1.el8s.x86_64 +python3-ceph-argparse-16.2.7-1.el8s.x86_64 +python3-ceph-common-16.2.7-1.el8s.x86_64 +python3-cephfs-16.2.7-1.el8s.x86_64 @@ -755 +750,2 @@ -python3-cloud-what-1.28.21-3.el8.x86_64 +python3-click-6.7-8.el8.noarch +python3-cloud-what-1.28.24-1.el8.x86_64 @@ -787,2 +783,2 @@ -python3-ipaclient-4.9.6-6.module_el8.5.0+947+fabc681e.noarch -python3-ipalib-4.9.6-6.module_el8.5.0+947+fabc681e.noarch +python3-ipaclient-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch +python3-ipalib-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch @@ -797,2 +793,2 @@ -python3-libipa_hbac-2.5.2-2.el8_5.1.x86_64 -python3-libnmstate-1.2.0-0.1.alpha2.el8.noarch +python3-libipa_hbac-2.6.1-2.el8.x86_64 +python3-libnmstate-1.2.0-1.el8.noarch @@ -805 +801 @@ -python3-linux-procfs-0.6.3-4.el8.noarch +python3-linux-procfs-0.7.0-1.el8.noarch @@ -837 +833 @@ -python3-perf-4.18.0-348.2.1.el8_5.x86_64 +python3-perf-4.18.0-358.el8.x86_64 @@ -860,2 +856,2 @@ -python3-rados-16.2.6-1.el8s.x86_64 -python3-rbd-16.2.6-1.el8s.x86_64 +python3-rados-16.2.7-1.el8s.x86_64 +python3-rbd-16.2.7-1.el8s.x86_64 @@ -865 +861 @@ -python3-rgw-16.2.6-1.el8s.x86_64 +python3-rgw-16.2.7-1.el8s.x86_64 @@ -867 +863 @@ -python3-rpm-4.14.3-19.el8.x86_64 +python3-rpm-4.14.3-21.el8.x86_64 @@ -875,3 +871,3 @@ -python3-sss-2.5.2-2.el8_5.1.x86_64 -python3-sss-murmur-2.5.2-2.el8_5.1.x86_64 -python3-sssdconfig-2.5.2-2.el8_5.1.noarch +python3-sss-2.6.1-2.el8.x86_64 +python3-sss-murmur-2.6.1-2.el8.x86_64 +python3-sssdconfig-2.6.1-2.el8.noarch @@ -879 +875 @@ -python3-subscription-manager-rhsm-1.28.21-3.el8.x86_64 +python3-subscription-manager-rhsm-1.28.24-1.el8.x86_64 @@ -881 +877 @@ -python3-syspurpose-1.28.21-3.el8.x86_64 +python3-syspurpose-1.28.24-1.el8.x86_64 @@ -914,4 +910,4 @@ -rpm-4.14.3-19.el8.x86_64 -rpm-build-libs-4.14.3-19.el8.x86_64 -rpm-libs-4.14.3-19.el8.x86_64 -rpm-plugin-selinux-4.14.3-19.el8.x86_64 +rpm-4.14.3-21.el8.x86_64 +rpm-build-libs-4.14.3-21.el8.x86_64 +rpm-libs-4.14.3-21.el8.x86_64 +rpm-plugin-selinux-4.14.3-21.el8.x86_64 @@ -925,3 +921,3 @@ -samba-client-libs-4.14.5-2.el8.x86_64 -samba-common-4.14.5-2.el8.noarch -samba-common-libs-4.14.5-2.el8.x86_64 +samba-client-libs-4.15.3-0.el8.x86_64 +samba-common-4.15.3-0.el8.noarch +samba-common-libs-4.15.3-0.el8.x86_64 @@ -931,2 +927,2 @@ -sbd-1.5.0-2.el8.x86_64 -scap-security-guide-0.1.57-5.el8.noarch +sbd-1.5.1-1.el8.x86_64 +scap-security-guide-0.1.59-1.el8.noarch @@ -937,2 +933,2 @@ -selinux-policy-3.14.3-85.el8.noarch -selinux-policy-targeted-3.14.3-85.el8.noarch +selinux-policy-3.14.3-86.el8.noarch +selinux-policy-targeted-3.14.3-86.el8.noarch @@ -950 +946 @@ -sos-4.2-7.el8.noarch +sos-4.2-11.el8.noarch @@ -956,9 +952,9 @@ -sssd-client-2.5.2-2.el8_5.1.x86_64 -sssd-common-2.5.2-2.el8_5.1.x86_64 -sssd-common-pac-2.5.2-2.el8_5.1.x86_64 -sssd-dbus-2.5.2-2.el8_5.1.x86_64 -sssd-ipa-2.5.2-2.el8_5.1.x86_64 -sssd-kcm-2.5.2-2.el8_5.1.x86_64 -sssd-krb5-common-2.5.2-2.el8_5.1.x86_64 -sssd-tools-2.5.2-2.el8_5.1.x86_64 -subscription-manager-rhsm-certificates-1.28.21-3.el8.x86_64 +sssd-client-2.6.1-2.el8.x86_64 +sssd-common-2.6.1-2.el8.x86_64 +sssd-common-pac-2.6.1-2.el8.x86_64 +sssd-dbus-2.6.1-2.el8.x86_64 +sssd-ipa-2.6.1-2.el8.x86_64 +sssd-kcm-2.6.1-2.el8.x86_64 +sssd-krb5-common-2.6.1-2.el8.x86_64 +sssd-tools-2.6.1-2.el8.x86_64 +subscription-manager-rhsm-certificates-1.28.24-1.el8.x86_64 @@ -976,5 +972,5 @@ -systemd-239-51.el8.x86_64 -systemd-container-239-51.el8.x86_64 -systemd-libs-239-51.el8.x86_64 -systemd-pam-239-51.el8.x86_64 -systemd-udev-239-51.el8.x86_64 +systemd-239-51.el8_5.2.x86_64 +systemd-container-239-51.el8_5.2.x86_64 +systemd-libs-239-51.el8_5.2.x86_64 +systemd-pam-239-51.el8_5.2.x86_64 +systemd-udev-239-51.el8_5.2.x86_64 @@ -982 +978 @@ -tcpdump-4.9.3-2.el8.x86_64 +tcpdump-4.9.3-3.el8.x86_64 @@ -993 +989 @@ -usbredir-0.8.0-1.el8.x86_64 +usbredir-0.12.0-1.el8.x86_64 @@ -997,11 +993,11 @@ -vdsm-4.40.90.4-1.el8.x86_64 -vdsm-api-4.40.90.4-1.el8.noarch -vdsm-client-4.40.90.4-1.el8.noarch -vdsm-common-4.40.90.4-1.el8.noarch -vdsm-gluster-4.40.90.4-1.el8.x86_64 -vdsm-http-4.40.90.4-1.el8.noarch -vdsm-jsonrpc-4.40.90.4-1.el8.noarch -vdsm-network-4.40.90.4-1.el8.x86_64 -vdsm-python-4.40.90.4-1.el8.noarch -vdsm-yajsonrpc-4.40.90.4-1.el8.noarch -vim-minimal-8.0.1763-16.el8_5.2.x86_64 +vdsm-4.40.100.2-1.el8.x86_64 +vdsm-api-4.40.100.2-1.el8.noarch +vdsm-client-4.40.100.2-1.el8.noarch +vdsm-common-4.40.100.2-1.el8.noarch +vdsm-gluster-4.40.100.2-1.el8.x86_64 +vdsm-http-4.40.100.2-1.el8.noarch +vdsm-jsonrpc-4.40.100.2-1.el8.noarch +vdsm-network-4.40.100.2-1.el8.x86_64 +vdsm-python-4.40.100.2-1.el8.noarch +vdsm-yajsonrpc-4.40.100.2-1.el8.noarch +vim-minimal-8.0.1763-16.el8_5.3.x86_64 @@ -1011 +1007 @@ -virt-what-1.18-12.el8.x86_64 +virt-what-1.18-13.el8.x86_64 See the release notes [1] for installation instructions and a list of new features and bugs fixed. Additional resources: - Read more about the oVirt 4.4.10 release highlights: https://www.ovirt.org/release/4.4.10/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ [1] https://www.ovirt.org/release/4.4.10/ -- 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 4

Re: support of AMD EPYC 3rd Genneration Milan
by Sandro Bonazzola 20 Jan '22

20 Jan '22

Il giorno sab 8 gen 2022 alle ore 18:47 samuel.xhu(a)horebdata.cn < samuel.xhu(a)horebdata.cn> ha scritto: > Helllo, Ovirt experts, > > Does Ovirt now support the use of AMD EPYC 3rd Genneration Milan CPU? and > if yes, from which version? > > AMD EPYC Milan CPU should be supported by Advanced Virtualization since June 2021, included in oVirt Node 4.4.6.1 and newer. Within oVirt I think it's recognized as "EPYC" without real distinction between Milan, Rome or others. +Arik Hadas <ahadas(a)redhat.com> ? -- 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 2

oVirt nodes keeps updating and rebooting
by Harry O 20 Jan '22

20 Jan '22

Hi, After HE deployment my oVirt nodes keeps updating and rebooting, even though I disabled node update in the beginning of deployment wizard. Why is this and how can I stop it form happening?

2 1