- Users - oVirt List Archives

Authentication with Active Directory
by Alireza Eskandari 02 Aug '22

02 Aug '22

Hi all, I'm trying to connect an active directory to my ovirt for authentication. But the base DN of my active directory is not the default one so I need to specify it in ovirt configuration to find users. How can I configure it? In my current configuration when I try to login, I get this message: server_error: Cannot resolve principal 'xxxx(a)yy.zz' Regards, Alireza

1 0

ovirt-engine manager, certificate issue
by david 02 Aug '22

02 Aug '22

hello I have a problem to log in to ovirt-engine manager in my browser the warning message in the browser display me this text: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed to solve this problem I am offered to run engine-setup and here is a question: the engine-setup will have no impact to the hosts(hypervisors) working? ovirt version 4.4.4.7-1.el8 thanks

7 7

Make QXL the default
by Colin Coe 02 Aug '22

02 Aug '22

Hey all We've just updated to RHV4.4SP1 (aka 4.5) from v4.4 and now our ansible workflows are failing with: cannot run VM. Selected display type is not supported by the operating system The OS are RHEL6 and RHEL7 (no, I can't change this as the software stack only works with these) I couldn't find anything in the ansible ovirt collection to change from VGA to QXL. Any ideas on how I can make QXL the default instead of VGA? Maybe a DB change? Thanks

3 4

Issue with oVirt 4.5 and Data Warehouse installed on a Separate Machine
by Igor Davidoff 02 Aug '22

02 Aug '22

Hello, i have an issue with 'engine-seup' step on DWH (separate server) aufter upgrade from 4.4.10 to 4.5. It looks like the ovirt-engine-setup are looking for rpm-package 'ovirt-engine' instead of 'ovirt-engine-dwh'. the reporting error is: " --== END OF CONFIGURATION ==-- [ INFO ] Stage: Setup validation [ ERROR ] Failed to execute stage 'Setup validation': Command '/usr/bin/rpm' failed to execute [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20220502100751-fqwb07.log [WARNING] Remote engine was not configured to be able to access DWH, please check the logs. [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20220502101130-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed " in Setup log i found: " 2022-05-02 10:11:30,000+0000 DEBUG otopi.context context._executeMethod:127 Stage validation METHOD otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages.Plugin._validation 2022-05-02 10:11:30,001+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.executeRaw:813 execute: ('/usr/bin/rpm', '-q', '--queryformat=%{version}-%{release}', 'ovirt-engine'), executable='None', cwd='None', env=None 2022-05-02 10:11:30,013+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.executeRaw:863 execute-result: ('/usr/bin/rpm', '-q', '--queryformat=%{version}-%{release}', 'ovirt-engine'), rc=1 2022-05-02 10:11:30,013+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.execute:921 execute-output: ('/usr/bin/rpm', '-q', '--queryformat=%{version}-%{release}', 'ovirt-engine') stdout: package ovirt-engine is not installed 2022-05-02 10:11:30,013+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.execute:926 execute-output: ('/usr/bin/rpm', '-q', '--queryformat=%{version}-%{release}', 'ovirt-engine') stderr: 2022-05-02 10:11:30,013+0000 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py", line 463, in _validation oenginecons.Const.ENGINE_PACKAGE_NAME, File "/usr/lib/python3.6/site-packages/otopi/plugin.py", line 931, in execute command=args[0], RuntimeError: Command '/usr/bin/rpm' failed to execute 2022-05-02 10:11:30,015+0000 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Setup validation': Command '/usr/bin/rpm' failed to execute " usually the upgrade of minor versions in 4.4 was just: # yum update ovirt\*setup\* # engine-setup # yum update as it did not work, i tried the fresh installation of centos8 stream and recovery of DWH Database and configuration: # engine-backup --mode=restore --file=backup.bck --provision-all-databases -> no luck the last idea was fresh installation centos8 stream + fresh installation of ovirt-engine-dwh 4.5 (without recovery) -> the same error. the engine side works fine. i compared the current setup logs with the installation and all the minor upgrades of ovirt-engine-dwh before 4.5 and only found the rpm-validation for the package 'ovirt-engine-dwh': " 2022-02-08 16:11:29,846+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.executeRaw:813 execute: ('/usr/bin/rpm', '-q', 'ovirt-engine-dwh'), executable='None', cwd='None', env=None 2022-02-08 16:11:29,877+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.executeRaw:863 execute-result: ('/usr/bin/rpm', '-q', 'ovirt-engine-dwh'), rc=0 2022-02-08 16:11:29,878+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.execute:921 execute-output: ('/usr/bin/rpm', '-q', 'ovirt-engine-dwh') stdout: ovirt-engine-dwh-4.4.10-1.el8.noarch 2022-02-08 16:11:29,878+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages plugin.execute:926 execute-output: ('/usr/bin/rpm', '-q', 'ovirt-engine-dwh') stderr: 2022-02-08 16:11:29,878+0000 DEBUG otopi.transaction transaction.commit:152 committing 'DWH Engine database Transaction' " It looks like engine-setup knows it is the DWH-Server, but is trying to validate the wrong rpm package. Any Ideas, how to work around this. Thank you!

2 5

Obsoleting Packages in 'dnf check-update' on RHEL 8.6 hosts
by Scott Worthington 01 Aug '22

01 Aug '22

Hello, My 4.5.1.3-1.el8 oVirt homelab cluster is running on RHEL 8.6 hosts and a RHEL 8.6 stand-alone engine. During the installation, I followed the instructions for RHEL 8.6: https://ovirt.org/download/install_on_rhel.html After the installation is complete, all packages are up-to-date, and everything is running, I run a 'dnf check-upgrade' and I find there are two packages that are listed under "Obsoleting Packages": """ Last metadata expiration check: 0:43:06 ago on Mon 01 Aug 2022 08:08:50 AM EDT. Obsoleting Packages centos-stream-release.noarch 8.6-1.el8 @@System centos-stream-release.noarch 8.6-1.el8 @@System centos-stream-release.noarch 8.6-1.el8 @@System redhat-release.x86_64 8.6-0.1.el8 @rhel-8-for-x86_64-baseos-rpms """ For the hosts, it makes it appear that the hosts always have an upgrade pending in the oVirt Engine UI. "centos-strea-release.noarch" appears to contain similar files to the original RHEL 8.6 package "redhat-release-8.6.0.1.el8" except for the addition of "centos*" named files. Any thoughts on how to change this behavior so that it doesn't appear to have packages to upgrade because a 'dnf update' does nothing to these "Obsoleting Packages"? Thanks in advance.

1 0

Dark Mode
by Dean L 01 Aug '22

01 Aug '22

Is there a way to place oVirt in Dark Mode? It's one of those things I really like about moVirt. :) Thanks!

1 0

Gluster volume "deleted" by accident --- Is it possible to recover?
by itforums51＠gmail.com 01 Aug '22

01 Aug '22

hi everyone, I have a 3x node ovirt 4.4.6 cluster in HC setup. Today I was intending to extend the data and vmstore volume adding another brick each; then by accident I pressed the "cleanup" button. Basically it looks that the volume were deleted. I am wondering whether there is a process of trying to recover these volumes and therefore all VMs (including the Hosted-Engine). ``` lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert gluster_lv_data gluster_vg_sda4 Vwi---t--- 500.00g gluster_thinpool_gluster_vg_sda4 gluster_lv_data-brick1 gluster_vg_sda4 Vwi-aot--- 500.00g gluster_thinpool_gluster_vg_sda4 0.45 gluster_lv_engine gluster_vg_sda4 -wi-a----- 100.00g gluster_lv_vmstore gluster_vg_sda4 Vwi---t--- 500.00g gluster_thinpool_gluster_vg_sda4 gluster_lv_vmstore-brick1 gluster_vg_sda4 Vwi-aot--- 500.00g gluster_thinpool_gluster_vg_sda4 0.33 gluster_thinpool_gluster_vg_sda4 gluster_vg_sda4 twi-aot--- <7.07t 11.46 0.89 ``` I would appreciate any advice. TIA

2 2

oVirt Survey Summer 2022 responses are now available
by Sandro Bonazzola 01 Aug '22

01 Aug '22

Thanks to the 109 participants in the oVirt Survey Summer 2022! The survey is now over and results are publicly available at https://docs.google.com/forms/d/1eQcbSqC6JQ2mvbPUcD7S_0pZW8hy_De4PCwkBYrP6m… Thanks -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D PERFORMANCE & SCALE 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

Engine update failing 4.5.1.3-1 -> 4.5.2-1
by xavierl＠rogers.com 29 Jul '22

29 Jul '22

Hi there, I'm trying to update my engine version so I can mitigate a bug which was in the previous update and is failing. The log file is proving to be very difficult to pinpoint the cause of the error however I can provide it. Wondering if anyone else has had this issue and if there's a way to fix it while preserving the VMs I have on this single host setup. [ INFO ] Stage: Setup validation During execution engine service will be stopped (OK, Cancel) [OK]: [ INFO ] Hosted Engine HA is in Global Maintenance mode. Setup version: 4.5.2-1.el8 Engine version: 4.5.1.3-1.el8 [ ERROR ] Failed to execute stage 'Setup validation': Setup and (updated) Engine versions must match [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20220728194403-9ev4xe.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20220728194429-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed

3 5

ovirt vms NotResponding related to firewalls
by Bill James 29 Jul '22

29 Jul '22

we recently added a bunch of firewalls around vlans where our VMs live and it may be causing a lot of confusion to ovirt management node? Though I don't know why firewall would cause intermittent problems. We see a lot of errors like: (in engine.log) 2022-07-28 19:39:47,923-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-1) [] VM '6e177451-d43f-4e 91-85ad-6b8f3bcfc4ad'(epayfraud2.j2noc.com) moved from 'NotResponding' --> 'Up' ... 2022-07-28 19:39:53,676-07 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineSch eduled-Thread-58) [] EVENT_ID: VM_NOT_RESPONDING(126), VM epayfraud 2.j2noc.com is not responding. ... 2022-07-28 19:40:36,189-07 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-10) [] VM '6e177451-d43f-4e91-85ad-6b8f3bcfc4ad'( epayfraud2.j2noc.com) moved from 'NotResponding' --> 'Up' I guess my first question is how does ovirt determine if VM is up or not, is it the management node or the host VM is running on and what ports does it use to determine health?

1 1

Six node HCI
by Gaurang Patel 29 Jul '22

29 Jul '22

Hi, I am very new to Ovirt 6 Node Gluster. We can create three node cluster successfully with the 4.5.1 version but after expanding the gluster cluster with additional 3 nodes, Ovirt-engine is going to not responding mode. If you can help me with step by step document would be very greatful to us. Thank in advance. Gaurang Patel DISCLAIMER : The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.

1 0

Re: Veeam Backup for RHV (oVirt)
by markeczzz＠gmail.com 29 Jul '22

29 Jul '22

Ah, I see.. Then, is there any good guide or documentation how to revert from Keycloak to AAA? All I could find is how to move from AAA to Keycloak, but not reverse.

2 4

Import machines
by Demeter Tibor 28 Jul '22

28 Jul '22

Dear Listmembers, Is it possible to import ovirt 4.3's VMs into a new ovirt environment via our old storage domains? I have an old 4.3 self-hosted system with 3 storage domain, but it seems very difficult upgrade until 4.5. I just wondering, what if I do install a complety new system and just attach the old storge domains to that. Is it will work ? If yes, what will do it with our VM-s and networks. Thanks in advance, Regards. Tibor

2 1

Veeam Backup for RHV (oVirt)
by markeczzz＠gmail.com 27 Jul '22

27 Jul '22

Hi! Not really sure if this is right place to ask, but.. I am trying to use Veeam Backup for Red Hat Virtualization on oVirt 4.5.1. I have been using it on version 4.4.10.7 and it works ok there. On Veeam Release page it says that supported OS is RHV 4.4SP1 (oVirt 4.5). When i try to do backup, this is what i get from Veeam backup. No errors in vdsm.log and engine.log.. 2022-07-27 08:08:44.153 00039 [19545] INFO | [LoggingEventsManager_39]: Add to storage LoggingEvent [id: 34248685-a193-4df5-8ff2-838f738e211c, Type: BackupStartedNew] 2022-07-27 08:08:44.168 00039 [19545] INFO | [TaskManager_39]: Create and run new async task. [call method:'RunBackupChain'] 2022-07-27 08:08:44.168 00039 [19545] INFO | [AsyncTask_39]: New AsynTask created [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f', description:'', type:'BACKUP_VM_POLICY'] 2022-07-27 08:08:44.168 00039 [19545] INFO | [AsyncTask_39]: Prepare AsynTask to run [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] 2022-07-27 08:08:44.176 00031 [19545] INFO | [BackupPolicy_31]: Refresh VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' 2022-07-27 08:08:44.176 00031 [19545] INFO | [BackupPolicy_31]: Begin updating list of active VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' [forceRefresh = True] 2022-07-27 08:08:44.176 00031 [19545] INFO | [RhevCluster_31]: Test connection to cluster [IP: engine.example.org, Port: 443, User: admin@ovirt@internalsso] 2022-07-27 08:08:44.189 00039 [19545] INFO | [TaskManager_39]: AsyncTask registered. [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] 2022-07-27 08:08:44.371 00031 [19545] INFO | [RhevCluster_31]: Test connection to cluster success. Status: Success. Message: 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicyManager_31]: Refreshing the policies data... 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: Begin updating list of active VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' [forceRefresh = False] 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: List of active VMs updated for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' [forceRefresh = False]. Number of active VMs '1' 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicyManager_31]: Policies data has been refreshed. 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: List of active VMs updated for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' [forceRefresh = True]. Number of active VMs '1' 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: Found the '1' VMs to backup in policy '6e090c98-d44b-4785-acb4-82a627da5d9b' 2022-07-27 08:08:44.564 00031 [19545] INFO | [BackupPolicy_31]: * Parallel policy runner has started * for policy [Name:'test5', ID: '6e090c98-d44b-4785-acb4-82a627da5d9b' 2022-07-27 08:08:44.564 00031 [19545] INFO | [VeeamBackupServer_31]: Test connection to backup server [IP: 'veeambr.example.org', Port: '10006', User: 'rhvproxy'] 2022-07-27 08:08:44.931 00031 [19545] INFO | [VeeamBackupServer_31]: Test connection to backup server [IP: 'veeambr.example.org', Port: '10006']. Connection status: ConnectionSuccess. Version: 11.0.1.1261 2022-07-27 08:08:45.423 00031 [19545] INFO | [BackupPolicy_31]: Successfully called CreateVeeamPolicySession for job [UID: '6e090c98-d44b-4785-acb4-82a627da5d9b'], session [UID: 'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Successfully called RetainPolicyVms for job [UID: '6e090c98-d44b-4785-acb4-82a627da5d9b'] with VMs: 50513a65-6ccc-479b-9b61-032e0961b016 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Start calculating maxPointsCount 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: End calculating maxPointsCount. Result = 7 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Starting validate repository schedule. Repository [UID: '237e41d6-7c67-4a1f-80bf-d7c73c481209', MaxPointsCount: '7', IsPeriodicFullRequired: 'False'] 2022-07-27 08:08:46.595 00031 [19545] INFO | [BackupPolicy_31]: End validate repository schedule. Result: [IsScheduleValid: 'True', ErrorMessage: ''] 2022-07-27 08:08:46.597 00031 [19545] INFO | [SessionManager_31]: Start registering a new session[Id: 'b6f3f0e1-7aab-41cb-b0e7-10f5b2ed6708'] 2022-07-27 08:08:46.639 00031 [19545] INFO | [SessionManager_31]: Session registered. [Id:'b6f3f0e1-7aab-41cb-b0e7-10f5b2ed6708'] 2022-07-27 08:08:46.639 00031 [19545] INFO | [BackupPolicy_31]: Backup VM [id:'50513a65-6ccc-479b-9b61-032e0961b016'] starting... 2022-07-27 08:08:46.639 00031 [19545] INFO | [BackupPolicy_31]: RetentionMergeDisabled: false 2022-07-27 08:08:46.640 00031 [19545] INFO | [TaskManager_31]: Create new async task. [call method:'DoBackup'] 2022-07-27 08:08:46.640 00031 [19545] INFO | [AsyncTask_31]: New AsynTask created [id:'15a63192-f3d2-4e3a-af56-240f3733bded', description:'', type:'BACKUP_VM'] 2022-07-27 08:08:46.640 00031 [19545] INFO | [AsyncTask_31]: Prepare AsynTask to run [id:'15a63192-f3d2-4e3a-af56-240f3733bded'] 2022-07-27 08:08:46.661 00031 [19545] INFO | [TaskManager_31]: AsyncTask registered. [id:'15a63192-f3d2-4e3a-af56-240f3733bded'] 2022-07-27 08:08:47.295 00031 [19545] ERROR | [BackupPolicy_31]: Backup VM [id:'50513a65-6ccc-479b-9b61-032e0961b016'] failed. Error ('test: VM UUID=50513a65-6ccc-479b-9b61-032e0961b016 was not found: * Line 1, Column 1 Syntax error: value, object or array expected. * Line 1, Column 1 A valid JSON document must be either an array or an object value. ') Are there any changes between version 4.5 and 4.5.1 that are preventing using this? Any solution? Regards,

3 2

oVirt 4.2 host cert expired
by Don Dupuis 27 Jul '22

27 Jul '22

Hello I have an environment with quite a lot of hosts using local storage domains. The engine and hosts cert expired. I ran engine-setup on the ovirt-engine so that the engine cert would get updated and then followed this https://access.redhat.com/solutions/3532921 to manually update the hosts certs so that hopefully the engine can talk to vdsm and then carry out the cert enrollment process, but no luck. I am getting is error in vdsm.log: 2022-07-26 18:32:12,743-0500 INFO (Reactor thread) [ProtocolDetector.AcceptorImpl] Accepted connection from ::ffff: 192.168.50.26:58194 (protocoldetector:61) 2022-07-26 18:32:12,760-0500 ERROR (Reactor thread) [ProtocolDetector.SSLHandshakeDispatcher] ssl handshake: SSLError, address: ::ffff:192.168.50.26 (sslutils:263) and the engine.log: 2022-07-26 03:30:13,242-05 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to host01/192.168.50.72 2022-07-26 03:30:13,257-05 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages General SSLEngine problem 2022-07-26 03:30:13,260-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-12) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM host01 command Get Host Capabilities failed: General SSLEngine problem I substituted host01 for the real FQDN for this post. I can't get the hosts in a mode so that I can put it in maintenance mode and I also want to be carefull about reinstalling because the vms are stored on local storage domain on host. Fingerprints match on the certs and when I sign the vdsmcert on the engine and then copy back to the proper localtions, libvirtd and vdsmd restart fine, just the SSL ERROR. Anyone have any ideas on how to solve this cert issue? Thanks Don

1 1

Intel xeon gold 6346 supported
by atatur.yildirim＠gmail.com 26 Jul '22

26 Jul '22

Hello all, Is intel xeon gold 6346 cpu supported in ovirt, I couldn't exactly determine from the docs. Thank you..

2 3

Support for OpenStack Glance is now deprecated
by francesco＠shellrent.com 25 Jul '22

25 Jul '22

Hi all, as I read in the documentation https://www.ovirt.org/documentation/administration_guide/index.html: "Support for OpenStack Glance is now deprecated. This functionality will be removed in a later release." Do you know any alternative to Glance for a "single point" images archives for creating template that could be integrated with oVirt or do I need to use storage domain for achieve a similar result? Thank you for your time and help, Francesco

1 0

Failed to connect to the host via ssh: root@192.168.4.17: Permission denied (publickey, gssapi-keyex, gssapi-with-mic, password).
by konstantinluschaev＠ya.ru 24 Jul '22

24 Jul '22

An attempt to deploy a new host fails. Deploy I see the following error in the deploy log: 192.168.4.17: Failed to connect to host via ssh: root(a)192.168.4.17 : Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Despite the fact that the root user logs into the host via ssh from the ovirt-engine without any problems. So I understand that ansible scripts cannot get through ssh. Do you have any ideas about this? ovirt-engine version 4.4.10.6-1.el8 Centos Stream 8 host - CentOS Stream 8

3 2

oVirt over gluster: Replacing a dead host
by Gilboa Davara 23 Jul '22

23 Jul '22

Hello all, I'm attempting to replace a dead host in a replica 2 + arbiter gluster setup and replace it with a new host. I've already set up a new host (same hostname..localdomain) and got into the cluster. $ gluster peer status Number of Peers: 2 Hostname: office-wx-hv3-lab-gfs Uuid: 4e13f796-b818-4e07-8523-d84eb0faa4f9 State: Peer in Cluster (Connected) Hostname: office-wx-hv1-lab-gfs.localdomain <------ This is a new host. Uuid: eee17c74-0d93-4f92-b81d-87f6b9c2204d State: Peer in Cluster (Connected) $ gluster volume info GV2Data Volume Name: GV2Data Type: Replicate Volume ID: c1946fc2-ed94-4b9f-9da3-f0f1ee90f303 Status: Stopped Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick <------ This is the dead host. Brick2: office-wx-hv2-lab-gfs:/mnt/LogGFSData/brick Brick3: office-wx-hv3-lab-gfs:/mnt/LogGFSData/brick (arbiter) ... Looking at the docs, it seems that I need to remove the dead brick. $ gluster volume remove-brick GV2Data office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick start Running remove-brick with cluster.force-migration enabled can result in data corruption. It is safer to disable this option so that files that receive writes during migration are not migrated. Files that are not migrated can then be manually copied after the remove-brick commit operation. Do you want to continue with your current cluster.force-migration settings? (y/n) y volume remove-brick start: failed: Removing bricks from replicate configuration is not allowed without reducing replica count explicitly So I guess I need to drop from replica 2 + arbiter to replica 1 + arbiter (?). $ gluster volume remove-brick GV2Data replica 1 office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick start Running remove-brick with cluster.force-migration enabled can result in data corruption. It is safer to disable this option so that files that receive writes during migration are not migrated. Files that are not migrated can then be manually copied after the remove-brick commit operation. Do you want to continue with your current cluster.force-migration settings? (y/n) y volume remove-brick start: failed: need 2(xN) bricks for reducing replica count of the volume from 3 to 1 ... What am I missing? - Gilboa

3 10

Task Run PKI enroll request for vdsm and QEMU failed to execute. Ovirt 4.5.1
by xavierl＠rogers.com 22 Jul '22

22 Jul '22

Hi there, I am currently at a loss as to why I am unable to install additional nodes and am receiving the error: "Task Run PKI enroll request for vdsm and QEMU failed to execute" Running oVirt node 4.5.1 and would appreciate any assistance as there's no other forums discussing this issue. I have Logs ready at request. Cheers

3 4

ovirt-aaa-jdbc-tool and Keycloak
by Gilboa Davara 22 Jul '22

22 Jul '22

Hello all, I have a number of oVirt clusters that were recently upgraded to v.4.5.1. As far as I can see, once keycloak is enabled, local users can no longer login. (only admin@ovirt works). Assuming I need to continue using local AAA users (created using ovirt-aaa-jdbc-tool), should I disable keycloak support? How do I do it? (engine-setup?). - Gilboa

1 0

Creating template from VM oVirt 4.5.1
by markeczzz＠gmail.com 22 Jul '22

22 Jul '22

Hi! I am trying to create Template from VM, but when I click on OK button, nothing happens, no error, nothing. I guess this is this bug, but is there any https://github.com/oVirt/ovirt-engine/pull/360, but I am not sure how to fix it, as I am already at latest version (4.5.1.3-1.el8). Regards,

3 10

Help needed
by less foobar 22 Jul '22

22 Jul '22

I'm installing self hosted engine and there is an error that I can't understand can somebody help me? The logs are here: https://termbin.com/vht61

3 6

HostedEngine Upgrade from 4.4.5.10 fails - dnf distrosync
by simon＠justconnect.ie 22 Jul '22

22 Jul '22

Hi All, No matter what I try I cannot update/upgrade my hosted engine. All mirrors are local and have been updated. I have changed the repo files to Stream and carried out a dnf update --nobest But I cannot go any further. # rpm -q ovirt-engine ovirt-engine-4.4.5.10-1.el8.noarch # cat /etc/centos* [root@ddmcomhartestengine yum.repos.d]# dnf distrosync Last metadata expiration check: 0:02:12 ago on Thu 21 Jul 2022 11:12:18 PM UTC. Error: Problem 1: package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - collectd-5.11.0-2.el8.x86_64 does not belong to a distupgrade repository - problem with installed package collectd-write_syslog-5.11.0-2.el8.x86_64 - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 2: package python3-ansible-runner-1.4.6-1.el8.noarch requires python3dist(pexpect) >= 4.6, but none of the providers can be installed - python3-pexpect-4.7.0-4.el8.noarch does not belong to a distupgrade repository - problem with installed package python3-ansible-runner-1.4.6-1.el8.noarch - package python3-pexpect-4.7.0-4.el8.noarch is filtered out by exclude filtering Problem 3: package python3-ansible-runner-1.4.6-1.el8.noarch requires python3dist(pexpect) >= 4.6, but none of the providers can be installed - cannot install both python3-pexpect-4.3.1-3.el8.noarch and python3-pexpect-4.7.0-4.el8.noarch - package ansible-runner-service-1.0.7-1.el8.noarch requires python3-ansible-runner, but none of the providers can be installed - cannot install the best update candidate for package python3-pexpect-4.7.0-4.el8.noarch - problem with installed package ansible-runner-service-1.0.7-1.el8.noarch - package python3-ansible-runner-1.4.6-1.el8.noarch is filtered out by exclude filtering - package python3-pexpect-4.7.0-4.el8.noarch is filtered out by exclude filtering Problem 4: package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - cannot install the best update candidate for package collectd-5.11.0-2.el8.x86_64 - problem with installed package ovirt-engine-4.4.5.10-1.el8.noarch - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 5: package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package collectd-disk-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-backend-4.4.5.10-1.el8.noarch requires ovirt-engine = 4.4.5.10-1.el8, but none of the providers can be installed - cannot install the best update candidate for package collectd-disk-5.11.0-2.el8.x86_64 - problem with installed package ovirt-engine-backend-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 6: package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package collectd-postgresql-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-dbscripts-4.4.5.10-1.el8.noarch requires ovirt-engine = 4.4.5.10-1.el8, but none of the providers can be installed - cannot install the best update candidate for package collectd-postgresql-5.11.0-2.el8.x86_64 - problem with installed package ovirt-engine-dbscripts-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 7: package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package collectd-write_http-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-restapi-4.4.5.10-1.el8.noarch requires ovirt-engine = 4.4.5.10-1.el8, but none of the providers can be installed - cannot install the best update candidate for package collectd-write_http-5.11.0-2.el8.x86_64 - problem with installed package ovirt-engine-restapi-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 8: cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - package collectd-disk-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-disk, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.5.10-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - collectd-disk-5.11.0-2.el8.x86_64 does not belong to a distupgrade repository - problem with installed package ovirt-engine-setup-plugin-ovirt-engine-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.10.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.10.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.10.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.10.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.2.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.12-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.5.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.6.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.6.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.6.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.7.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.7.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.8.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.8.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.8.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.9.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.9.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.9.5-1.el8.noarch is filtered out by exclude filtering - package collectd-disk-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-disk-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-disk-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-disk-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-disk-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 9: cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - package collectd-postgresql-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-postgresql, but none of the providers can be installed - package ovirt-engine-tools-4.4.5.10-1.el8.noarch requires ovirt-engine = 4.4.5.10-1.el8, but none of the providers can be installed - collectd-postgresql-5.11.0-2.el8.x86_64 does not belong to a distupgrade repository - problem with installed package ovirt-engine-tools-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package collectd-postgresql-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-postgresql-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-postgresql-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-postgresql-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-postgresql-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 10: cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - package collectd-write_http-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_http, but none of the providers can be installed - package ovirt-engine-webadmin-portal-4.4.5.10-1.el8.noarch requires ovirt-engine = 4.4.5.10-1.el8, but none of the providers can be installed - collectd-write_http-5.11.0-2.el8.x86_64 does not belong to a distupgrade repository - problem with installed package ovirt-engine-webadmin-portal-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package collectd-write_http-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_http-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_http-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_http-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_http-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@ddmcomhartestengine yum.repos.d]# If I add --allowerasing then I get the following: [root@ddmcomhartestengine yum.repos.d]# dnf distrosync --allowerasing Last metadata expiration check: 0:00:22 ago on Thu 21 Jul 2022 11:12:18 PM UTC. Dependencies resolved. ================================================================================================================================================================================================ Package Architecture Version Repository Size ================================================================================================================================================================================================ Reinstalling: python3-websocket-client noarch 0.56.0-5.el8 epel 61 k Removing dependent packages: ansible-runner-service noarch 1.0.7-1.el8 @ovirt-4.4-centos-ovirt44 259 k collectd-write_syslog x86_64 5.11.0-2.el8 @ovirt-4.4-centos-opstools 22 k ovirt-engine noarch 4.4.5.10-1.el8 @ovirt-4.4 38 M ovirt-engine-backend noarch 4.4.5.10-1.el8 @ovirt-4.4 8.2 M ovirt-engine-dbscripts noarch 4.4.5.10-1.el8 @ovirt-4.4 1.6 M ovirt-engine-restapi noarch 4.4.5.10-1.el8 @ovirt-4.4 25 M ovirt-engine-setup noarch 4.4.5.10-1.el8 @ovirt-4.4 671 ovirt-engine-setup-plugin-cinderlib noarch 4.4.5.10-1.el8 @ovirt-4.4 66 k ovirt-engine-setup-plugin-imageio noarch 4.4.5.10-1.el8 @ovirt-4.4 21 k ovirt-engine-setup-plugin-ovirt-engine noarch 4.4.5.10-1.el8 @ovirt-4.4 783 k ovirt-engine-setup-plugin-vmconsole-proxy-helper noarch 4.4.5.10-1.el8 @ovirt-4.4 60 k ovirt-engine-tools noarch 4.4.5.10-1.el8 @ovirt-4.4 467 k ovirt-engine-ui-extensions noarch 1.2.5-1.el8 @ovirt-4.4 38 M ovirt-engine-vmconsole-proxy-helper noarch 4.4.5.10-1.el8 @ovirt-4.4 16 k ovirt-engine-webadmin-portal noarch 4.4.5.10-1.el8 @ovirt-4.4 294 M python3-ansible-runner noarch 1.4.6-1.el8 @ovirt-4.4-centos-ovirt44 341 k Downgrading: collectd x86_64 5.9.0-5.el8 epel 716 k collectd-disk x86_64 5.9.0-5.el8 epel 35 k collectd-postgresql x86_64 5.9.0-5.el8 epel 46 k collectd-write_http x86_64 5.9.0-5.el8 epel 43 k javapackages-filesystem noarch 5.3.0-1.module_el8.0.0+11+5b8c10bd appstream 30 k javapackages-tools noarch 5.3.0-1.module_el8.0.0+11+5b8c10bd appstream 44 k nodejs x86_64 1:10.23.1-1.module_el8.4.0+645+9ce14ba2 appstream 8.9 M nodejs-full-i18n x86_64 1:10.23.1-1.module_el8.4.0+645+9ce14ba2 appstream 7.3 M npm x86_64 1:6.14.10-1.10.23.1.1.module_el8.4.0+645+9ce14ba2 appstream 3.7 M python3-bcrypt x86_64 3.1.6-2.el8.1 epel 44 k python3-cairo x86_64 1.16.3-6.el8 appstream 90 k python3-lockfile noarch 1:0.11.0-13.el8.1 epel 38 k python3-paramiko noarch 2.4.3-1.el8 epel 289 k python3-pbr noarch 5.1.2-3.el8 epel 88 k python3-pexpect noarch 4.3.1-3.el8 appstream 138 k python3-psutil x86_64 5.4.3-11.el8 appstream 373 k python3-pyasn1 noarch 0.3.7-6.el8 appstream 126 k python3-pyasn1-modules noarch 0.3.7-6.el8 appstream 110 k python3-pyyaml x86_64 3.12-12.el8 baseos 193 k python3-six noarch 1.11.0-8.el8 baseos 38 k Enabling module streams: javapackages-runtime 201801 Transaction Summary ================================================================================================================================================================================================ Remove 16 Packages Downgrade 20 Packages Total download size: 22 M Is this ok [y/N]: Any ideas please? Thanks Simon...

1 0

cockpit-ovirt-dashboard
by less foobar 21 Jul '22

21 Jul '22

When you try to follow the documentation for rhel 9 you can't install the cockpit-ovirt-dashboard. The package is missing. Even on ovirt version 9 the dashboard is missing from the cockpit interface.

2 2