October 2022 - Users - oVirt List Archives

New hosted engine installation, fails to login to the Administration Portal
by Ada 25 Oct '22

25 Oct '22

1 0

ovirt 4.5.3 and missing python3.9 packages
by Nathanaël Blanchet 25 Oct '22

25 Oct '22

Hi, When running hosted-engine --deploy with the el8 ovirt-node, ansible 2.13 uses python3.9 by default. But the installation fails two times because of missing netaddr and jmespath module for python3.9. I suppose the issue is not present in el9 because default python 3.9 presence. The workaround is to install those two packages with pip: dnf install python39-pip --enabelrepo appstream pip3.9 install netaddr jmespath Why not default installing those two packages ?

1 0

Re: OVS Task Error when Add EL Host
by Ada 25 Oct '22

25 Oct '22

2 1

Re: admin user locked out (OVN invalid_grant)
by Mounir MOHELLEBI 25 Oct '22

25 Oct '22

Hi there !!, Can you tel me exactly what is the command you executed to Run /usr/share/ovirt-engine/bin/ovirt-register-sso-client-tool.sh with Client Id: ovirt-provider-ovn Client CA Certificate File Location: /etc/pki/ovirt-engine/certs/engine.cer ??? I executed the following command "/usr/share/ovirt-engine/bin/ovirt-register-sso-client-tool.sh ovirt-provider-ovn" but I obtained this ouput: Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false Oct 25, 2022 8:17:39 AM org.ovirt.engine.ssoreg.core.SsoRegistrationToolExecutor main INFO: ========================================================================= Oct 25, 2022 8:17:39 AM org.ovirt.engine.ssoreg.core.SsoRegistrationToolExecutor main INFO: ================== oVirt Sso Client Registration Tool =================== Oct 25, 2022 8:17:39 AM org.ovirt.engine.ssoreg.core.SsoRegistrationToolExecutor main INFO: ========================================================================= Oct 25, 2022 8:17:39 AM org.ovirt.engine.ssoreg.core.SsoRegistrationToolExecutor main SEVERE: Parameter required but not found: client-id Can you tell how to execute this command properly and how can I find the correct client-id ?? Best regards, MOHELLEBI Mounir Ingénieur système | CIAR Assurances Spa Phone : +213 (0) 21 692 275 | 021 692 527 | 021 691 597 | 021 694 923 Mobile: + 213 561 604 771 Site: https://www.laciar.com Email: m.mohellebi(a)laciar.com<mailto:m.mohellebi@laciar.com> Adresse : 11, Chemin des Crêtes ll Paradou ll Hydra ll Alger ll Algerie IMPORTANT : Ce courriel est une communication confidentielle et l'information qu'il contient est réservée à l'usage exclusif du destinataire. Si vous n'êtes pas le destinataire visé, vous n'avez aucun droit d'utiliser cette information, de la copier, de la distribuer ou de la diffuser. Si cette communication vous a été transmise par erreur, veuillez la détruire et nous en aviser immédiatement par courriel. Nous vous remercions pour votre aide. The information contained and transmitted in this email is confidential, and is intended only for the named recipient to which it is addressed. The content of this email may not have been sent with the authority of the company. If the reader of this message is not the named recipient or a person responsible for delivering it to the named recipient, you are notified that the review, dissemination, distribution, transmission, printing or copying, forwarding, or any other use of this message or any part of it, including any attachments, is strictly prohibited. ________________________________

1 0

Local (Deployment) VM Can't Reach "centos-ceph-pacific" Repo
by Matthew J Black 24 Oct '22

24 Oct '22

Hi All, OK, new issue: :-( If I'm reading things right the local (deployment) vm can't get to the centos-ceph-pacific repo. The repo is installed on the host machine (along with all of the relevant dependant repos). I thought that local 192.168.222.0/24 network was nated out the virbr0 virtual bridge - am I wrong in this (ie do we need to update/change our routing tables/whatever)? Here is the (relevant part) of the log: ~~~ 2022-10-11 16:22:14,749+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package] 2022-10-11 16:26:03,643+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'results': [], 'rc': 1, 'msg': "Failed to download metadata for repo 'centos-ceph-pacific': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", 'invocation': {'module_args': {'name': ['ovirt-engine'], 'state': 'present', 'allow_downgrade': False, 'autoremove': False, 'bugfix': False, 'cacheonly': False, 'disable_gpg_check': False, 'disable_plugin': [], 'disablerepo': [], 'download_only': False, 'enable_plugin': [], 'enablerepo': [], 'exclude': [], 'installroot': '/', 'install_repoquery': True, 'install_weak_deps': True, 'security': False, 'skip_broken': False, 'update_cache': False, 'update_only': False, 'validate_certs': True, 'lock_timeout': 30, 'allowerasing': False, 'nobest': False, 'conf_file': None, 'disable_excludes': None, 'download_dir': None, 'list': None, 'releasever': None}}, '_ansible_no_log': False, 'changed': False, ' _ansible_delegated_vars': {'ansible_host': '192.168.222.77', 'ansible_port': None, 'ansible_user': 'root', 'ansible_connection': 'smart'}} 2022-10-11 16:26:03,744+1100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost -> 192.168.222.77]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'centos-ceph-pacific': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", "rc": 1, "results": []} 2022-10-11 16:26:04,045+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] 2022-10-11 16:26:04,947+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost -> 192.168.222.77] 2022-10-11 16:26:05,449+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] 2022-10-11 16:26:05,950+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost -> localhost] 2022-10-11 16:26:06,352+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] 2022-10-11 16:26:06,953+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost -> localhost] 2022-10-11 16:26:07,355+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] 2022-10-11 16:26:07,856+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost] 2022-10-11 16:26:08,357+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] 2022-10-11 16:26:08,959+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost -> localhost] 2022-10-11 16:26:09,460+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] 2022-10-11 16:26:09,862+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost -> localhost] 2022-10-11 16:26:10,363+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] 2022-10-11 16:26:20,986+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost -> localhost] 2022-10-11 16:26:21,388+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] 2022-10-11 16:26:27,901+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost] 2022-10-11 16:26:28,403+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Change ownership of copied engine logs] 2022-10-11 16:26:29,005+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost -> localhost] 2022-10-11 16:26:29,506+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] 2022-10-11 16:26:29,908+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'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', '_ansible_no_log': False, 'changed': False} 2022-10-11 16:26:30,008+1100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 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"} 2022-10-11 16:26:30,410+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 PLAY RECAP [localhost] : ok: 161 changed: 59 unreachable: 0 skipped: 80 failed: 1 2022-10-11 16:26:30,510+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:226 ansible-playbook rc: 2 2022-10-11 16:26:30,510+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:233 ansible-playbook stdout: 2022-10-11 16:26:30,510+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:236 ansible-playbook stderr: 2022-10-11 16:26:30,510+1100 DEBUG otopi.plugins.gr_he_ansiblesetup.core.misc misc._closeup:475 {'otopi_host_net': {'ansible_facts': {'otopi_host_net': ['bond0.40', 'ens1', 'bond0.20']}, '_ansible_no_log': False, 'changed': False}, 'otopi_localvm_dir': {'changed': True, 'path': '/var/tmp/localvmfq67djtv', 'uid': 0, 'gid': 0, 'owner': 'root', 'group': 'root', 'mode': '0700', 'state': 'directory', 'secontext': 'unconfined_u:object_r:user_tmp_t:s0', 'size': 6, 'invocation': {'module_args': {'state': 'directory', 'path': '/var/tmp', 'prefix': 'localvm', 'suffix': ''}}, '_ansible_no_log': False}, 'otopi_appliance_disk_size': {'ansible_facts': {'virtual_size': '53689188352'}, '_ansible_no_log': False, 'changed': False}, 'ansible-playbook_rc': 2} 2022-10-11 16:26:30,511+1100 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 509, in _closeup raise RuntimeError(_('Failed executing ansible-playbook')) RuntimeError: Failed executing ansible-playbook 2022-10-11 16:26:30,511+1100 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Failed executing ansible-playbook 2022-10-11 16:26:30,512+1100 DEBUG otopi.context context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN 2022-10-11 16:26:30,512+1100 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/error=bool:'True' 2022-10-11 16:26:30,512+1100 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/exceptionInfo=list:'[(<class 'RuntimeError'>, RuntimeError('Failed executing ansible-playbook',), <traceback object at 0x7efe2a39fa08>)]' 2022-10-11 16:26:30,512+1100 DEBUG otopi.context context.dumpEnvironment:775 ENV OVEHOSTED_CORE/localVMDir=str:'/var/tmp/localvmfq67djtv' 2022-10-11 16:26:30,512+1100 DEBUG otopi.context context.dumpEnvironment:775 ENV OVEHOSTED_STORAGE/ovfSizeGB=int:'51' 2022-10-11 16:26:30,513+1100 DEBUG otopi.context context.dumpEnvironment:779 ENVIRONMENT DUMP - END ~~~ Anyone got any ideas - thanks: Dulux-Oz

1 2

Failed to delete snapshot
by Jirka Simon 24 Oct '22

24 Oct '22

Hello there. we have troubles with one VM ad it's snapshot here is short log from engine.log 2022-08-23 09:02:38,735+02 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1265784) [4d79272b-ffac-4b2b-a987-8c19577cd8c4] CommandAsyncTask:: HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity '5842cafc-60d4-4131-8da1-8a909123f08c' 2022-08-23 09:02:41,435+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [4d79272b -ffac-4b2b-a987-8c19577cd8c4] Command id: 'ead3fbba-7439-4337-8aaf-1d6cf65bbb15 failed child command status for step 'REDUCE_IMAGE' 2022-08-23 09:02:41,435+02 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [ 4d79272b-ffac-4b2b-a987-8c19577cd8c4] Command 'RemoveSnapshotSingleDiskLive' id: 'ead3fbba-7439-4337-8aaf-1d6cf65bbb15' child commands '[5b33d970-6ea0-4b8b-bc31-607afd8af1ca, 185d3fec-8c76- 44d3-a0a1-fe8fff331354, 308baf9d-1fc5-43a1-a624-b5f08f7bec1b, f11f3550-4356-417e-af10-a3afb2051dec, 5842cafc-60d4-4131-8da1-8a909123f08c]' executions were completed, status 'FAILED' 2022-08-23 09:02:42,445+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) [4d79272b -ffac-4b2b-a987-8c19577cd8c4] Merging of snapshot '6634db4e-23d8-4849-a008-864f15d28c3d' images 'd24a9199-741b-49cb-96d2-0d76fcd21f48'..'48af3301-0cbb-4a6e-97d1-7299e7de883f' failed. Images have been marked illegal and can no longer be previewed or reverted to. Please retry Live Merge on the snapshot to complete the operation. 2022-08-23 09:02:42,451+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) [4d79272b -ffac-4b2b-a987-8c19577cd8c4] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' with failure. 2022-08-23 09:02:42,457+02 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) [4d79272b-ffac -4b2b-a987-8c19577cd8c4] Command 'RemoveSnapshot' id: '73340ac8-07d7-4de2-bfeb-8062fa1e8cfd' child commands '[ead3fbba-7439-4337-8aaf-1d6cf65bbb15]' executions were completed, status 'FAILE D' 2022-08-23 09:02:43,470+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-22) [4d79272b-ffac-4b2b-a98 7-8c19577cd8c4] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 2022-08-23 09:02:43,490+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-22) [4d79272b-ff ac-4b2b-a987-8c19577cd8c4] EVENT_ID: USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot 'vProtect 2022-08-05 22:33:44.088143' for VM 'web1.wiki.prod.hq.sldev.cz-2'. Snapshot can't be deleted, and VM is not possible to clone. thank you for any help. Jirka

7 12

Help - Unable to break bond interface from Ovrit Engine
by Amrit Thakur 23 Oct '22

23 Oct '22

Hi, Currently I am using ovirt 4.3 version with two clusters. Previously I used a bond interface with two NICs for NFS storage. Now I want to use iscsi with multipathing but I didn't find any option to break the bond interface from the ovirt engine GUI. So my question is, is there any way to break the bond interface or if I remove bond interface from node os level, will it sync with the ovirt engine after restart os or vdsm service ? Thank You

2 1

RPM issues updating Ovirt 4.5.2 to 4.5.3
by David Johnson 21 Oct '22

21 Oct '22

Good afternoon all, We are trying to update our cluster from 4.5.2 to see if we can resolve some issues with the VM Web console not functioning on VM's that run on one of the hosts. So there's two problems here, if we can resolve the one (dependency resolution) we are hoping that we can resolve the other with a reinstall of the software. *Symptoms:* 1. On VM's running one one host, the VM web console does not work. The console.vv downloads to the desktop and we can attempt to launch it. On launch, it immediately exits. The web console works on the VM's on the other host. 2. Attempting to update or reinstall the software to any host via the ovirt Compute -> Hosts -> Installation -> Reinstall, or Upgrade menu, we get a dependency resolution error: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64 It appears that the 4.5.2 build is running on an older release of openvswitch? Please advise. *Environment:* Production environment: Ovirt 4.5.2.4-1.el8 1 Standalone engine (upgraded to 3 hosts *Log excerpts* *VM Web Console Not Starting:* Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for fe80::f0ca:56ff:fe8c:7bb8 on veth8a5345f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for veth8a5345f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for fe80::d879:d5ff:fee4:1855 on vethc9bd12f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for vethc9bd12f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for fe80::42:15ff:fe5a:679 on br-1feb13c47a4f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 172.22.0.1 on br-1feb13c47a4f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for br-1feb13c47a4f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 172.19.0.1 on docker_gwbridge. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for docker_gwbridge. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 172.17.0.1 on docker0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for docker0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 172.18.0.1 on br-4209e789b982. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for br-4209e789b982. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for virbr0-nic. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for virbr0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 192.168.2.163 on eth0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for eth0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for lo. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Host name conflict, retrying with cen-76-alc-qa-4236 Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for fe80::f0ca:56ff:fe8c:7bb8 on veth8a5345f.*. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for fe80::d879:d5ff:fee4:1855 on vethc9bd12f.*. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for fe80::42:15ff:fe5a:679 on br-1feb13c47a4f.*. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 172.22.0.1 on br-1feb13c47a4f.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 172.19.0.1 on docker_gwbridge.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 172.17.0.1 on docker0.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 172.18.0.1 on br-4209e789b982.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for fe80::3a72:e773:4d49:55ba on eth0.*. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 192.168.2.163 on eth0.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Server startup complete. Host name is cen-76-alc-qa-4236.local. Local service cookie is 3875159144. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering HINFO record with values 'X86_64'/'LINUX'. Oct 18 13:22:02 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:02.828860278-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.695827803-05:00" level=error msg="agent: session failed" backoff=8s error="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\"" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.695994815-05:00" level=info msg="parsed scheme: \"\"" module=grpc Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.696023188-05:00" level=info msg="scheme \"\" not registered, fallback to default scheme" module=grpc Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.696208750-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{192.168.2.162:2377 <nil> 0 <nil>}] <nil> <nil>}" module=grpc Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.696239844-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.696294355-05:00" level=info msg="manager selected by agent for new session: {z80ib665fps13yuqtzqqnltr6 192.168.2.162:2377}" module=node/agent node.id=iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.696355540-05:00" level=info msg="waiting 6.545410435s before registering session" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.697629711-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:05 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:05.699785481-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:07 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:07.247677166-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:10 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:10.062182617-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.242738688-05:00" level=error msg="agent: session failed" backoff=8s error="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\"" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.242918867-05:00" level=info msg="parsed scheme: \"\"" module=grpc Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.242954837-05:00" level=info msg="scheme \"\" not registered, fallback to default scheme" module=grpc Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.243141828-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{192.168.2.162:2377 <nil> 0 <nil>}] <nil> <nil>}" module=grpc Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.243170522-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.243226320-05:00" level=info msg="manager selected by agent for new session: {z80ib665fps13yuqtzqqnltr6 192.168.2.162:2377}" module=node/agent node.id=iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.243290968-05:00" level=info msg="waiting 3.202102632s before registering session" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.244389573-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:12 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:12.246550975-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.073299399-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.446614366-05:00" level=error msg="agent: session failed" backoff=8s error="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\"" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.446832560-05:00" level=info msg="parsed scheme: \"\"" module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.446863564-05:00" level=info msg="scheme \"\" not registered, fallback to default scheme" module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.447060785-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{192.168.2.162:2377 <nil> 0 <nil>}] <nil> <nil>}" module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.447089843-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.447142554-05:00" level=info msg="manager selected by agent for new session: {z80ib665fps13yuqtzqqnltr6 192.168.2.162:2377}" module=node/agent node.id=iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.447206125-05:00" level=info msg="waiting 3.65571267s before registering session" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.448787529-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:15 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:15.450286831-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:17 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:17.254956187-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103309534-05:00" level=error msg="agent: session failed" backoff=8s error="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\"" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103525940-05:00" level=info msg="parsed scheme: \"\"" module=grpc Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103557034-05:00" level=info msg="scheme \"\" not registered, fallback to default scheme" module=grpc Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103843903-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{192.168.2.162:2377 <nil> 0 <nil>}] <nil> <nil>}" module=grpc Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103880439-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103970819-05:00" level=info msg="manager selected by agent for new session: {z80ib665fps13yuqtzqqnltr6 192.168.2.162:2377}" module=node/agent node.id=iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.104034386-05:00" level=info msg="waiting 3.770112424s before registering session" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.105363177-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:19 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:19.107464606-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:20 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:20.460645439-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc *Host log from update attempt:* 2022-10-17 13:57:22 CDT - { "uuid" : "71edb069-f43c-452b-8528-a0c3d6625fd1", "counter" : 175, "stdout" : "fatal: [192.168.2.18]: FAILED! => {\"changed\": false, \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem 1: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-52.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-53.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-56.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-6.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-72.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-75.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-80.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-81.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-88.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-2.15-4.el8.noarch\\n - cannot install the best update candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\\n Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be installed\\n - cannot install the best update candidate for package python3-openvswitch2.15-2.15.0-117.el8s.x86_64\\n - cannot install the best update candidate for package openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\\n Problem 3: package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none of the providers can be installed\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-82.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-21.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-17.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-29.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\\n - cannot install the best update candidate for package ovn-2021-21.12.0-82.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\\n Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires ovn-2021-host, but none of the providers can be installed\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-82.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-21.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-40.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-17.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-29.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-11.el8s.x86_64\\n - cannot install the best update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch\", \"rc\": 1, \"results\": []}", "start_line" : 171, "end_line" : 172, "runner_ident" : "e370b346-b9e8-4a0c-8595-9a717b14c901", "event" : "runner_on_failed", "pid" : 3151, "created" : "2022-10-17T18:57:22.572472", "parent_uuid" : "64006a61-d37f-a54d-f807-000000000042", "event_data" : { "playbook" : "ovirt-host-upgrade.yml", "playbook_uuid" : "b4383145-d80b-4cf6-83a2-550febf56e5c", "play" : "all", "play_uuid" : "64006a61-d37f-a54d-f807-000000000006", "play_pattern" : "all", "task" : "Upgrade packages", "task_uuid" : "64006a61-d37f-a54d-f807-000000000042", "task_action" : "yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-upgrade/tasks/main.yml:49", "role" : "ovirt-host-upgrade", "host" : "192.168.2.18", "remote_addr" : "192.168.2.18", "res" : { "failures" : [ ], "results" : [ ], "rc" : 1, "msg" : "Depsolve Error occurred: \n Problem 1: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-52.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-53.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-56.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-6.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-72.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-75.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-80.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-81.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-88.el8s.x86_64\n - cannot install the best update candidate for package ovirt-openvswitch-2.15-4.el8.noarch\n - cannot install the best update candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\n Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-119.el8s.x86_64\n - package openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be installed\n - cannot install the best update candidate for package python3-openvswitch2.15-2.15.0-117.el8s.x86_64\n - cannot install the best update candidate for package openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\n Problem 3: package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none of the providers can be installed\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-82.el8s.x86_64\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-21.el8s.x86_64\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-17.el8s.x86_64\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-29.el8s.x86_64\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\n - cannot install the best update candidate for package ovn-2021-21.12.0-82.el8s.x86_64\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\n Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires ovn-2021-host, but none of the providers can be installed\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-82.el8s.x86_64\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-21.el8s.x86_64\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-40.el8s.x86_64\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-17.el8s.x86_64\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-29.el8s.x86_64\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-11.el8s.x86_64\n - cannot install the best update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch", "invocation" : { "module_args" : { "name" : [ "*" ], "state" : "latest", "allow_downgrade" : false, "autoremove" : false, "bugfix" : false, "cacheonly" : false, "disable_gpg_check" : false, "disable_plugin" : [ ], "disablerepo" : [ ], "download_only" : false, "enable_plugin" : [ ], "enablerepo" : [ ], "exclude" : [ ], "installroot" : "/", "install_repoquery" : true, "install_weak_deps" : true, "security" : false, "skip_broken" : false, "update_cache" : false, "update_only" : false, "validate_certs" : true, "lock_timeout" : 30, "allowerasing" : false, "nobest" : false, "conf_file" : null, "disable_excludes" : null, "download_dir" : null, "list" : null, "releasever" : null } }, "_ansible_no_log" : false, "changed" : false }, "start" : "2022-10-17T18:57:19.992530", "end" : "2022-10-17T18:57:22.572294", "duration" : 2.579764, "ignore_errors" : null, "event_loop" : null, "uuid" : "71edb069-f43c-452b-8528-a0c3d6625fd1" } } *David Johnson*

6 11

LDAP auth and group members
by Jiří Sléžka 21 Oct '22

21 Oct '22

Hi, I have configured oVirt authentication against our MicroFocus/Novell eDirectory (edir) ldap. It is working fine on per user base. Now I am tried to set permissions per group but it seems does not work. My CRO.properties --- include = <rfc2307-edir.properties> vars.server = ldap.******** vars.port = 389 vars.user = cn=******************* vars.password = ******************* pool.default.serverset.single.server = ${global:vars.server} pool.default.serverset.single.port = ${global:vars.port} pool.default.auth.simple.bindDN = ${global:vars.user} pool.default.auth.simple.password = ${global:vars.password} pool.default.ssl.startTLS = true pool.default.socketfactory.resolver.supportIPv6 = false sequence-init.init.100-my-edir-init-vars = my-edir-init-vars sequence.my-edir-init-vars.010.description = set baseDN sequence.my-edir-init-vars.010.type = var-set sequence.my-edir-init-vars.010.var-set.variable = simple_baseDN sequence.my-edir-init-vars.010.var-set.value = o=su search.default.search-request.derefPolicy = ALWAYS --- I am able search groups in manager but users with permissions per group are unable to login with "The user *********** with profile [CRO] is not authorized to perform login". When I try debug it with ovirt-engine-extensions-tool aaa login-user --profile=CRO --user-name=******* I can see common attributes (name, email,...) in PrincipalRecord but not any record mentioned group membership. Group which holds this user has posixGroup objectClass and member attributes which points to dn of users. There were also similar post in this list in 2019 which unfortunately was not much specific with solution https://lists.ovirt.org/archives/list/users@ovirt.org/thread/PBQXDJGOZ2ET34… Could any suggest how to better debug this or how to modify group search filter in my profile to work with member attribute? Thanks in advance, Jiri

1 0

oVirt Node 4.5.3.1 Async update
by Sandro Bonazzola 21 Oct '22

21 Oct '22

oVirt Node 4.5.3.1 Async update On October 20th 2022 the oVirt project released an async update of oVirt Node (4.5.3.1) delivering a fix for OVS/OVN package conflict issue. The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. -- 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

Re: Users Digest, Vol 133, Issue 36
by David Johnson 20 Oct '22

20 Oct '22

> We can try this at our next maintenance window, probably in a week or so > From: Lev Veyde <lveyde(a)redhat.com> > To: Brett Maton <matonb(a)ltresources.co.uk> > Cc: "mmoon(a)maxistechnology.com" <mmoon(a)maxistechnology.com>, " > users(a)ovirt.org" <users(a)ovirt.org> > Bcc: > Date: Wed, 19 Oct 2022 17:36:59 +0300 > Subject: [ovirt-users] Re: Ovirt host update bug > Hi, > > We built a new centos-release-ovirt package that supposed to fix that > issue (on non manually fixed machine): > > https://cbs.centos.org/kojifiles/packages/centos-release-ovirt45/8.7/3.el8s… > > Could somebody please test that it indeed fixes the issue? > > Thanks in advance, > > On Wed, Oct 19, 2022 at 2:27 PM Brett Maton <matonb(a)ltresources.co.uk> > wrote: > >> Thanks Ales, >> >> That fixed it for me, I don't think *rdo-ovn-central* is mentioned in link >> but that was the final missing exclude for me. >> >> Regards, >> Brett >> >> ------------------------------ >> *From:* Ales Musil <amusil(a)redhat.com> >> *Sent:* 19 October 2022 11:50 >> *To:* Brett Maton <matonb(a)ltresources.co.uk> >> *Cc:* Lev Veyde <lveyde(a)redhat.com>; mmoon(a)maxistechnology.com < >> mmoon(a)maxistechnology.com>; users(a)ovirt.org <users(a)ovirt.org> >> *Subject:* Re: [ovirt-users] Re: Ovirt host update bug >> >> Hi, >> >> you need to specify also "rdo-ovn-host", "python3-rdo-openvswitch" and " >> rdo-ovn-central" in the excluded. >> See >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RIHO32QA3NT6Y… >> >> Best regards, >> Ales >> >> On Wed, Oct 19, 2022 at 12:35 PM Brett Maton <matonb(a)ltresources.co.uk> >> wrote: >> >> I'm seeing the same error >> >> Repo config: >> >> # grep 'ovirt-45-centos-stream-openstack-yoga' >> /etc/yum.repos.d/CentOS-oVirt-4.5.repo -B1 -A15 >> >> [ovirt-45-centos-stream-openstack-yoga] >> name=CentOS Stream $releasever - oVirt 4.5 - OpenStack Yoga Repository >> # baseurl= >> http://mirror.centos.org/centos/$stream/cloud/$basearch/openstack-yoga/ >> mirrorlist= >> http://mirrorlist.centos.org/?release=$stream&arch=$basearch&repo=cloud-ope… >> gpgcheck=1 >> gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Cloud >> enabled=1 >> module_hotfixes=1 >> exclude= >> # ansible-2.9.27-4.el8 shipped in yoga repo is breaking dependencies on >> oVirt side >> ansible >> ansible-test >> * rdo-openvswitch* >> * rdo-ovn* >> >> >> Update attempt: >> >> # yum clean all >> 187 files removed >> >> # dnf update >> CentOS-8-stream - Ceph Pacific >> 781 kB/s | 456 kB 00:00 >> CentOS-8-stream - Gluster 10 >> 175 kB/s | 40 kB 00:00 >> CentOS-8 - NFV OpenvSwitch >> 364 kB/s | 168 kB 00:00 >> CentOS-OpsTools - collectd >> 169 kB/s | 41 kB 00:00 >> CentOS Stream 8 - AppStream >> 24 MB/s | 25 MB 00:01 >> CentOS Stream 8 - BaseOS >> 23 MB/s | 25 MB 00:01 >> CentOS Stream 8 - Extras >> 39 kB/s | 18 kB 00:00 >> CentOS Stream 8 - Extras common packages >> 24 kB/s | 4.9 kB 00:00 >> CentOS Stream 8 - PowerTools >> 9.7 MB/s | 5.1 MB 00:00 >> CentOS Stream 8 - oVirt 4.5 >> 4.1 MB/s | 1.2 MB 00:00 >> CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository >> 3.4 MB/s | 2.2 MB 00:00 >> oVirt upstream for CentOS Stream 8 - oVirt 4.5 >> 47 kB/s | 408 kB 00:08 >> Extra Packages for Enterprise Linux 8 - x86_64 >> 11 MB/s | 13 MB 00:01 >> Extra Packages for Enterprise Linux Modular 8 - x86_64 >> 830 kB/s | 733 kB 00:00 >> Extra Packages for Enterprise Linux 8 - Next - x86_64 >> 1.5 MB/s | 1.4 MB 00:00 >> Error: >> Problem 1: package rdo-ovn-central-2:22.06-3.el8.noarch requires rdo-ovn >> = 2:22.06-3.el8, but none of the providers can be installed >> - cannot install the best update candidate for package >> ovn-2021-central-21.12.0-82.el8s.x86_64 >> - package rdo-ovn-2:22.06-3.el8.noarch is filtered out by exclude >> filtering >> Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch requires >> rdo-openvswitch = 2:2.17-3.el8, but none of the providers can be installed >> - cannot install the best update candidate for package >> python3-openvswitch2.15-2.15.0-119.el8s.x86_64 >> - package rdo-openvswitch-2:2.17-3.el8.noarch is filtered out by >> exclude filtering >> (try to add '--skip-broken' to skip uninstallable packages or '--nobest' >> to use not only best candidate packages) >> >> >> Regards, >> Brett >> ------------------------------ >> *From:* Lev Veyde <lveyde(a)redhat.com> >> *Sent:* 19 October 2022 11:14 >> *To:* mmoon(a)maxistechnology.com <mmoon(a)maxistechnology.com> >> *Cc:* users(a)ovirt.org <users(a)ovirt.org> >> *Subject:* [ovirt-users] Re: Ovirt host update bug >> >> Checked with the networking and looks like the issue is with the >> conflicting OVS/OVN packages released on the OpenStack channel. >> >> Fixing that on our side will require releasing a new version, but one can >> try to fix it manually by modifying the >> /etc/yum.repos.d/CentOS-oVirt-4.5.repo file. >> >> 1. Find the [ovirt-45-centos-stream-openstack-yoga] section >> 2. At the end of the section look for ansible-test under exclude= >> 3. Add *rdo-openvswitch* and *rdo-ovn* each on their own line, in same >> way as *ansible* and *ansible-test* that already exists >> >> >> >> On Wed, Oct 19, 2022 at 1:49 AM <mmoon(a)maxistechnology.com> wrote: >> >> Hey I'm having an issue, curious if anyone can help >> >> I'm trying to update my ovirt cluster from 4.5.2.4-1.el8 to 4.5.3.1 but >> have run into a problem with the update installer. >> >> The environment is: >> >> Static hostname: ovirt2.xxx.xxx >> Icon name: computer-desktop >> Chassis: desktop >> Machine ID: 0eb1fcff65214fb399c9d2ffaf1f5a29 >> Boot ID: dbc7438e4d464209ac79452410cf60e7 >> Operating System: CentOS Stream 8 >> CPE OS Name: cpe:/o:centos:centos:8 >> Kernel: Linux 4.18.0-408.el8.x86_64 >> Architecture: x86-64 >> >> >> >> Filesystem 1K-blocks Used Available Use% Mounted on >> devtmpfs 8023804 0 8023804 0% /dev >> tmpfs 8055520 24 8055496 1% /dev/shm >> tmpfs 8055520 99708 7955812 2% /run >> tmpfs 8055520 0 8055520 0% /sys/fs/cgroup >> /dev/mapper/cs-root 73364480 11401568 61962912 16% / >> /dev/mapper/cs-home 166691304 1467260 165224044 1% /home >> /dev/sda2 1038336 262972 775364 26% /boot >> /dev/sda1 613184 7416 605768 2% /boot/efi >> tmpfs 1611104 12 1611092 1% /run/user/42 >> tmpfs 1611104 4 1611100 1% /run/user/1000 >> >> >> There are 3 hosts, which can all detect and begin the update, getting >> most of the way through it, before failing and returning it to a state of >> non-operation. The log file says that the host is unable to resolve the >> virtual switch dependency >> log excerpt: >> "stdout" : "fatal: [192.168.2.18]: FAILED! => {\"changed\": false, >> \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem 1: >> package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but >> none of the providers can be installed\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-117.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-106.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-110.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-115.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2 >> .17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-23.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-24.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-27.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-30.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-32.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-35.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-37.el8s.x86_64\\n - packag >> e rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-39.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-41.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-47.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-48.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-51.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-52.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-53.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < >> 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-56.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-6.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-72.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-75.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-80.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-81.el8s.x86_64\\n - package >> rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 >> provided by openvswitch2.15-2.15.0-88.el8s.x86_64\\n - cannot >> install the best update candidate for package >> ovirt-openvswitch-2.15-4.el8.noarch\\n - cannot install the best update >> candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\\n Problem 2: >> package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes >> python3-openvswitch2.15 < 2.17 provided by >> python3-openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package >> openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires >> python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be >> installed\\n - cannot install the best update candidate for package >> python3-openvswitch2.15-2.15.0-117.el8s.x86_64\\n - cannot install the >> best update candidate for package >> openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\\n Problem 3: package >> ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none >> of the providers can be installed\\n - package >> rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by >> ovn-2021-21.12.0-82.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarc >> h obsoletes ovn-2021 < 22.06 provided by >> ovn-2021-21.03.0-21.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch >> obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64\\n >> - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided >> by ovn-2021-21.06.0-17.el8s.x86_64\\n - package >> rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by >> ovn-2021-21.06.0-29.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch >> obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\\n >> - cannot install the best update candidate for package >> ovn-2021-21.12.0-82.el8s.x86_64\\n - cannot install the best update >> candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\\n >> Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires >> ovn-2021-host, but none of the providers can be installed\\n - package >> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided >> by ovn-2021-host-21.12.0-82.el8s.x86_64\\n - pa >> ckage rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 >> provided by ovn-2021-host-21.03.0-21.el8s.x86_64\\n - package >> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided >> by ovn-2021-host-21.03.0-40.el8s.x86_64\\n - package >> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided >> by ovn-2021-host-21.06.0-17.el8s.x86_64\\n - package >> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided >> by ovn-2021-host-21.06.0-29.el8s.x86_64\\n - package >> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided >> by ovn-2021-host-21.12.0-11.el8s.x86_64\\n - cannot install the best >> update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\\n - >> cannot install the best update candidate for package >> ovirt-openvswitch-ovn-host-2.15-4.el8.noarch\", \"rc\": 1, \"results\": >> []}", >> >> On one host, when I attempt to open the ovirt web console from the gui it >> won't open, and virtual machines on that particular host are unable to run >> an ovirt web console as well: citing handshake error failure. >> log excerpt for host web console: >> >> Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=24 >> name='cen-79-dmz-02' uuid=82fefcfa-bce0-4397-a575-48d3d08fdb61 is tainted: >> custom-ga-command >> Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=25 >> name='win-10-utl' uuid=11f71942-1d88-40a0-a6c5-45e7718afbcf is tainted: >> custom-ga-command >> >> Oct 17 03:37:01 ovirt-host-05 ovs-appctl[37436]: >> ovs|00001|unixctl|WARN|failed to connect to >> /var/run/ovn/ovn-controller.18617.ctl >> >> Thank you in advance >> _______________________________________________ >> 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/5USJX6G7ZAZWD… >> >> >> >> -- >> >> 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> >> _______________________________________________ >> 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/HM7YY77DZQICX… >> >> >> >> -- >> >> Ales Musil >> >> Senior Software Engineer - OVN Core >> >> Red Hat EMEA <https://www.redhat.com> >> >> amusil(a)redhat.com IM: amusil >> <https://red.ht/sig> >> > > > -- > > 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> > _______________________________________________ > 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/ >

1 0

Registration of account on Zanata
by Anton Fadeev 19 Oct '22

19 Oct '22

Hello! I want to join to the localization group of oVirt Project. Can you help me?

3 2

Re: Ovirt host update bug
by Lev Veyde 19 Oct '22

19 Oct '22

Hi, We built a new centos-release-ovirt package that supposed to fix that issue (on non manually fixed machine): https://cbs.centos.org/kojifiles/packages/centos-release-ovirt45/8.7/3.el8s… Could somebody please test that it indeed fixes the issue? Thanks in advance, On Wed, Oct 19, 2022 at 2:27 PM Brett Maton <matonb(a)ltresources.co.uk> wrote: > Thanks Ales, > > That fixed it for me, I don't think *rdo-ovn-central* is mentioned in link > but that was the final missing exclude for me. > > Regards, > Brett > > ------------------------------ > *From:* Ales Musil <amusil(a)redhat.com> > *Sent:* 19 October 2022 11:50 > *To:* Brett Maton <matonb(a)ltresources.co.uk> > *Cc:* Lev Veyde <lveyde(a)redhat.com>; mmoon(a)maxistechnology.com < > mmoon(a)maxistechnology.com>; users(a)ovirt.org <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Re: Ovirt host update bug > > Hi, > > you need to specify also "rdo-ovn-host", "python3-rdo-openvswitch" and " > rdo-ovn-central" in the excluded. > See > https://lists.ovirt.org/archives/list/users@ovirt.org/message/RIHO32QA3NT6Y… > > Best regards, > Ales > > On Wed, Oct 19, 2022 at 12:35 PM Brett Maton <matonb(a)ltresources.co.uk> > wrote: > > I'm seeing the same error > > Repo config: > > # grep 'ovirt-45-centos-stream-openstack-yoga' > /etc/yum.repos.d/CentOS-oVirt-4.5.repo -B1 -A15 > > [ovirt-45-centos-stream-openstack-yoga] > name=CentOS Stream $releasever - oVirt 4.5 - OpenStack Yoga Repository > # baseurl= > http://mirror.centos.org/centos/$stream/cloud/$basearch/openstack-yoga/ > mirrorlist= > http://mirrorlist.centos.org/?release=$stream&arch=$basearch&repo=cloud-ope… > gpgcheck=1 > gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Cloud > enabled=1 > module_hotfixes=1 > exclude= > # ansible-2.9.27-4.el8 shipped in yoga repo is breaking dependencies on > oVirt side > ansible > ansible-test > * rdo-openvswitch* > * rdo-ovn* > > > Update attempt: > > # yum clean all > 187 files removed > > # dnf update > CentOS-8-stream - Ceph Pacific > 781 kB/s | 456 kB 00:00 > CentOS-8-stream - Gluster 10 > 175 kB/s | 40 kB 00:00 > CentOS-8 - NFV OpenvSwitch > 364 kB/s | 168 kB 00:00 > CentOS-OpsTools - collectd > 169 kB/s | 41 kB 00:00 > CentOS Stream 8 - AppStream > 24 MB/s | 25 MB 00:01 > CentOS Stream 8 - BaseOS > 23 MB/s | 25 MB 00:01 > CentOS Stream 8 - Extras > 39 kB/s | 18 kB 00:00 > CentOS Stream 8 - Extras common packages > 24 kB/s | 4.9 kB 00:00 > CentOS Stream 8 - PowerTools > 9.7 MB/s | 5.1 MB 00:00 > CentOS Stream 8 - oVirt 4.5 > 4.1 MB/s | 1.2 MB 00:00 > CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository > 3.4 MB/s | 2.2 MB 00:00 > oVirt upstream for CentOS Stream 8 - oVirt 4.5 > 47 kB/s | 408 kB 00:08 > Extra Packages for Enterprise Linux 8 - x86_64 > 11 MB/s | 13 MB 00:01 > Extra Packages for Enterprise Linux Modular 8 - x86_64 > 830 kB/s | 733 kB 00:00 > Extra Packages for Enterprise Linux 8 - Next - x86_64 > 1.5 MB/s | 1.4 MB 00:00 > Error: > Problem 1: package rdo-ovn-central-2:22.06-3.el8.noarch requires rdo-ovn > = 2:22.06-3.el8, but none of the providers can be installed > - cannot install the best update candidate for package > ovn-2021-central-21.12.0-82.el8s.x86_64 > - package rdo-ovn-2:22.06-3.el8.noarch is filtered out by exclude > filtering > Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch requires > rdo-openvswitch = 2:2.17-3.el8, but none of the providers can be installed > - cannot install the best update candidate for package > python3-openvswitch2.15-2.15.0-119.el8s.x86_64 > - package rdo-openvswitch-2:2.17-3.el8.noarch is filtered out by exclude > filtering > (try to add '--skip-broken' to skip uninstallable packages or '--nobest' > to use not only best candidate packages) > > > Regards, > Brett > ------------------------------ > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* 19 October 2022 11:14 > *To:* mmoon(a)maxistechnology.com <mmoon(a)maxistechnology.com> > *Cc:* users(a)ovirt.org <users(a)ovirt.org> > *Subject:* [ovirt-users] Re: Ovirt host update bug > > Checked with the networking and looks like the issue is with the > conflicting OVS/OVN packages released on the OpenStack channel. > > Fixing that on our side will require releasing a new version, but one can > try to fix it manually by modifying the > /etc/yum.repos.d/CentOS-oVirt-4.5.repo file. > > 1. Find the [ovirt-45-centos-stream-openstack-yoga] section > 2. At the end of the section look for ansible-test under exclude= > 3. Add *rdo-openvswitch* and *rdo-ovn* each on their own line, in same > way as *ansible* and *ansible-test* that already exists > > > > On Wed, Oct 19, 2022 at 1:49 AM <mmoon(a)maxistechnology.com> wrote: > > Hey I'm having an issue, curious if anyone can help > > I'm trying to update my ovirt cluster from 4.5.2.4-1.el8 to 4.5.3.1 but > have run into a problem with the update installer. > > The environment is: > > Static hostname: ovirt2.xxx.xxx > Icon name: computer-desktop > Chassis: desktop > Machine ID: 0eb1fcff65214fb399c9d2ffaf1f5a29 > Boot ID: dbc7438e4d464209ac79452410cf60e7 > Operating System: CentOS Stream 8 > CPE OS Name: cpe:/o:centos:centos:8 > Kernel: Linux 4.18.0-408.el8.x86_64 > Architecture: x86-64 > > > > Filesystem 1K-blocks Used Available Use% Mounted on > devtmpfs 8023804 0 8023804 0% /dev > tmpfs 8055520 24 8055496 1% /dev/shm > tmpfs 8055520 99708 7955812 2% /run > tmpfs 8055520 0 8055520 0% /sys/fs/cgroup > /dev/mapper/cs-root 73364480 11401568 61962912 16% / > /dev/mapper/cs-home 166691304 1467260 165224044 1% /home > /dev/sda2 1038336 262972 775364 26% /boot > /dev/sda1 613184 7416 605768 2% /boot/efi > tmpfs 1611104 12 1611092 1% /run/user/42 > tmpfs 1611104 4 1611100 1% /run/user/1000 > > > There are 3 hosts, which can all detect and begin the update, getting most > of the way through it, before failing and returning it to a state of > non-operation. The log file says that the host is unable to resolve the > virtual switch dependency > log excerpt: > "stdout" : "fatal: [192.168.2.18]: FAILED! => {\"changed\": false, > \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem 1: > package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but > none of the providers can be installed\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-117.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-106.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-110.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-115.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2 > .17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-23.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-24.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-27.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-30.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-32.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-35.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-37.el8s.x86_64\\n - packag > e rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-39.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-41.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-47.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-48.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-51.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-52.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-53.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < > 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-56.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-6.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-72.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-75.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-80.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-81.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-88.el8s.x86_64\\n - cannot > install the best update candidate for package > ovirt-openvswitch-2.15-4.el8.noarch\\n - cannot install the best update > candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\\n Problem 2: > package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes > python3-openvswitch2.15 < 2.17 provided by > python3-openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package > openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires > python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be > installed\\n - cannot install the best update candidate for package > python3-openvswitch2.15-2.15.0-117.el8s.x86_64\\n - cannot install the > best update candidate for package > openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\\n Problem 3: package > ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none > of the providers can be installed\\n - package > rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by > ovn-2021-21.12.0-82.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarc > h obsoletes ovn-2021 < 22.06 provided by > ovn-2021-21.03.0-21.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch > obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64\\n > - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided > by ovn-2021-21.06.0-17.el8s.x86_64\\n - package > rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by > ovn-2021-21.06.0-29.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch > obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\\n > - cannot install the best update candidate for package > ovn-2021-21.12.0-82.el8s.x86_64\\n - cannot install the best update > candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\\n > Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires > ovn-2021-host, but none of the providers can be installed\\n - package > rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided > by ovn-2021-host-21.12.0-82.el8s.x86_64\\n - pa > ckage rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 > provided by ovn-2021-host-21.03.0-21.el8s.x86_64\\n - package > rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided > by ovn-2021-host-21.03.0-40.el8s.x86_64\\n - package > rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided > by ovn-2021-host-21.06.0-17.el8s.x86_64\\n - package > rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided > by ovn-2021-host-21.06.0-29.el8s.x86_64\\n - package > rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided > by ovn-2021-host-21.12.0-11.el8s.x86_64\\n - cannot install the best > update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\\n - > cannot install the best update candidate for package > ovirt-openvswitch-ovn-host-2.15-4.el8.noarch\", \"rc\": 1, \"results\": > []}", > > On one host, when I attempt to open the ovirt web console from the gui it > won't open, and virtual machines on that particular host are unable to run > an ovirt web console as well: citing handshake error failure. > log excerpt for host web console: > > Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=24 > name='cen-79-dmz-02' uuid=82fefcfa-bce0-4397-a575-48d3d08fdb61 is tainted: > custom-ga-command > Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=25 > name='win-10-utl' uuid=11f71942-1d88-40a0-a6c5-45e7718afbcf is tainted: > custom-ga-command > > Oct 17 03:37:01 ovirt-host-05 ovs-appctl[37436]: > ovs|00001|unixctl|WARN|failed to connect to > /var/run/ovn/ovn-controller.18617.ctl > > Thank you in advance > _______________________________________________ > 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/5USJX6G7ZAZWD… > > > > -- > > 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> > _______________________________________________ > 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/HM7YY77DZQICX… > > > > -- > > Ales Musil > > Senior Software Engineer - OVN Core > > Red Hat EMEA <https://www.redhat.com> > > amusil(a)redhat.com IM: amusil > <https://red.ht/sig> > -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Engine's certification is about to expire at .... Please renew the engine's certification.
by nicolas＠devels.es 19 Oct '22

19 Oct '22

Hi, I'm running oVirt 4.4 and recently I got a message in the events list like this: Engine's certification is about to expire at 2022-10-30. Please renew the engine's certification. What does that exactly mean? And how can it be renewed? I'm using a custom TLS certificate both for web access and websocket proxy. Does it need to be renewed anyways? Thanks.

3 4

Re: Ovirt host update bug
by Ales Musil 19 Oct '22

19 Oct '22

Hi, you need to specify also "rdo-ovn-host", "python3-rdo-openvswitch" and " rdo-ovn-central" in the excluded. See https://lists.ovirt.org/archives/list/users@ovirt.org/message/RIHO32QA3NT6Y… Best regards, Ales On Wed, Oct 19, 2022 at 12:35 PM Brett Maton <matonb(a)ltresources.co.uk> wrote: > I'm seeing the same error > > Repo config: > > # grep 'ovirt-45-centos-stream-openstack-yoga' > /etc/yum.repos.d/CentOS-oVirt-4.5.repo -B1 -A15 > > [ovirt-45-centos-stream-openstack-yoga] > name=CentOS Stream $releasever - oVirt 4.5 - OpenStack Yoga Repository > # baseurl= > http://mirror.centos.org/centos/$stream/cloud/$basearch/openstack-yoga/ > mirrorlist= > http://mirrorlist.centos.org/?release=$stream&arch=$basearch&repo=cloud-ope… > gpgcheck=1 > gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Cloud > enabled=1 > module_hotfixes=1 > exclude= > # ansible-2.9.27-4.el8 shipped in yoga repo is breaking dependencies on > oVirt side > ansible > ansible-test > * rdo-openvswitch* > * rdo-ovn* > > > Update attempt: > > # yum clean all > 187 files removed > > # dnf update > CentOS-8-stream - Ceph Pacific > 781 kB/s | 456 kB 00:00 > CentOS-8-stream - Gluster 10 > 175 kB/s | 40 kB 00:00 > CentOS-8 - NFV OpenvSwitch > 364 kB/s | 168 kB 00:00 > CentOS-OpsTools - collectd > 169 kB/s | 41 kB 00:00 > CentOS Stream 8 - AppStream > 24 MB/s | 25 MB 00:01 > CentOS Stream 8 - BaseOS > 23 MB/s | 25 MB 00:01 > CentOS Stream 8 - Extras > 39 kB/s | 18 kB 00:00 > CentOS Stream 8 - Extras common packages > 24 kB/s | 4.9 kB 00:00 > CentOS Stream 8 - PowerTools > 9.7 MB/s | 5.1 MB 00:00 > CentOS Stream 8 - oVirt 4.5 > 4.1 MB/s | 1.2 MB 00:00 > CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository > 3.4 MB/s | 2.2 MB 00:00 > oVirt upstream for CentOS Stream 8 - oVirt 4.5 > 47 kB/s | 408 kB 00:08 > Extra Packages for Enterprise Linux 8 - x86_64 > 11 MB/s | 13 MB 00:01 > Extra Packages for Enterprise Linux Modular 8 - x86_64 > 830 kB/s | 733 kB 00:00 > Extra Packages for Enterprise Linux 8 - Next - x86_64 > 1.5 MB/s | 1.4 MB 00:00 > Error: > Problem 1: package rdo-ovn-central-2:22.06-3.el8.noarch requires rdo-ovn > = 2:22.06-3.el8, but none of the providers can be installed > - cannot install the best update candidate for package > ovn-2021-central-21.12.0-82.el8s.x86_64 > - package rdo-ovn-2:22.06-3.el8.noarch is filtered out by exclude > filtering > Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch requires > rdo-openvswitch = 2:2.17-3.el8, but none of the providers can be installed > - cannot install the best update candidate for package > python3-openvswitch2.15-2.15.0-119.el8s.x86_64 > - package rdo-openvswitch-2:2.17-3.el8.noarch is filtered out by exclude > filtering > (try to add '--skip-broken' to skip uninstallable packages or '--nobest' > to use not only best candidate packages) > > > Regards, > Brett > ------------------------------ > *From:* Lev Veyde <lveyde(a)redhat.com> > *Sent:* 19 October 2022 11:14 > *To:* mmoon(a)maxistechnology.com <mmoon(a)maxistechnology.com> > *Cc:* users(a)ovirt.org <users(a)ovirt.org> > *Subject:* [ovirt-users] Re: Ovirt host update bug > > Checked with the networking and looks like the issue is with the > conflicting OVS/OVN packages released on the OpenStack channel. > > Fixing that on our side will require releasing a new version, but one can > try to fix it manually by modifying the > /etc/yum.repos.d/CentOS-oVirt-4.5.repo file. > > 1. Find the [ovirt-45-centos-stream-openstack-yoga] section > 2. At the end of the section look for ansible-test under exclude= > 3. Add *rdo-openvswitch* and *rdo-ovn* each on their own line, in same > way as *ansible* and *ansible-test* that already exists > > > > On Wed, Oct 19, 2022 at 1:49 AM <mmoon(a)maxistechnology.com> wrote: > > Hey I'm having an issue, curious if anyone can help > > I'm trying to update my ovirt cluster from 4.5.2.4-1.el8 to 4.5.3.1 but > have run into a problem with the update installer. > > The environment is: > > Static hostname: ovirt2.xxx.xxx > Icon name: computer-desktop > Chassis: desktop > Machine ID: 0eb1fcff65214fb399c9d2ffaf1f5a29 > Boot ID: dbc7438e4d464209ac79452410cf60e7 > Operating System: CentOS Stream 8 > CPE OS Name: cpe:/o:centos:centos:8 > Kernel: Linux 4.18.0-408.el8.x86_64 > Architecture: x86-64 > > > > Filesystem 1K-blocks Used Available Use% Mounted on > devtmpfs 8023804 0 8023804 0% /dev > tmpfs 8055520 24 8055496 1% /dev/shm > tmpfs 8055520 99708 7955812 2% /run > tmpfs 8055520 0 8055520 0% /sys/fs/cgroup > /dev/mapper/cs-root 73364480 11401568 61962912 16% / > /dev/mapper/cs-home 166691304 1467260 165224044 1% /home > /dev/sda2 1038336 262972 775364 26% /boot > /dev/sda1 613184 7416 605768 2% /boot/efi > tmpfs 1611104 12 1611092 1% /run/user/42 > tmpfs 1611104 4 1611100 1% /run/user/1000 > > > There are 3 hosts, which can all detect and begin the update, getting most > of the way through it, before failing and returning it to a state of > non-operation. The log file says that the host is unable to resolve the > virtual switch dependency > log excerpt: > "stdout" : "fatal: [192.168.2.18]: FAILED! => {\"changed\": false, > \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem 1: > package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but > none of the providers can be installed\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-117.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-106.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-110.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-115.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2 > .17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-23.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-24.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-27.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-30.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-32.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-35.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-37.el8s.x86_64\\n - packag > e rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-39.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-41.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-47.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-48.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-51.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-52.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-53.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < > 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-56.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-6.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-72.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-75.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-80.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-81.el8s.x86_64\\n - package > rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 > provided by openvswitch2.15-2.15.0-88.el8s.x86_64\\n - cannot > install the best update candidate for package > ovirt-openvswitch-2.15-4.el8.noarch\\n - cannot install the best update > candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\\n Problem 2: > package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes > python3-openvswitch2.15 < 2.17 provided by > python3-openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package > openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires > python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be > installed\\n - cannot install the best update candidate for package > python3-openvswitch2.15-2.15.0-117.el8s.x86_64\\n - cannot install the > best update candidate for package > openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\\n Problem 3: package > ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none > of the providers can be installed\\n - package > rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by > ovn-2021-21.12.0-82.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarc > h obsoletes ovn-2021 < 22.06 provided by > ovn-2021-21.03.0-21.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch > obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64\\n > - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided > by ovn-2021-21.06.0-17.el8s.x86_64\\n - package > rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by > ovn-2021-21.06.0-29.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch > obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\\n > - cannot install the best update candidate for package > ovn-2021-21.12.0-82.el8s.x86_64\\n - cannot install the best update > candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\\n > Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires > ovn-2021-host, but none of the providers can be installed\\n - package > rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided > by ovn-2021-host-21.12.0-82.el8s.x86_64\\n - pa > ckage rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 > provided by ovn-2021-host-21.03.0-21.el8s.x86_64\\n - package > rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided > by ovn-2021-host-21.03.0-40.el8s.x86_64\\n - package > rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided > by ovn-2021-host-21.06.0-17.el8s.x86_64\\n - package > rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided > by ovn-2021-host-21.06.0-29.el8s.x86_64\\n - package > rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided > by ovn-2021-host-21.12.0-11.el8s.x86_64\\n - cannot install the best > update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\\n - > cannot install the best update candidate for package > ovirt-openvswitch-ovn-host-2.15-4.el8.noarch\", \"rc\": 1, \"results\": > []}", > > On one host, when I attempt to open the ovirt web console from the gui it > won't open, and virtual machines on that particular host are unable to run > an ovirt web console as well: citing handshake error failure. > log excerpt for host web console: > > Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=24 > name='cen-79-dmz-02' uuid=82fefcfa-bce0-4397-a575-48d3d08fdb61 is tainted: > custom-ga-command > Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=25 > name='win-10-utl' uuid=11f71942-1d88-40a0-a6c5-45e7718afbcf is tainted: > custom-ga-command > > Oct 17 03:37:01 ovirt-host-05 ovs-appctl[37436]: > ovs|00001|unixctl|WARN|failed to connect to > /var/run/ovn/ovn-controller.18617.ctl > > Thank you in advance > _______________________________________________ > 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/5USJX6G7ZAZWD… > > > > -- > > 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> > _______________________________________________ > 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/HM7YY77DZQICX… > -- Ales Musil Senior Software Engineer - OVN Core Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

2 1

Ovirt host update bug
by mmoon＠maxistechnology.com 19 Oct '22

19 Oct '22

Hey I'm having an issue, curious if anyone can help I'm trying to update my ovirt cluster from 4.5.2.4-1.el8 to 4.5.3.1 but have run into a problem with the update installer. The environment is: Static hostname: ovirt2.xxx.xxx Icon name: computer-desktop Chassis: desktop Machine ID: 0eb1fcff65214fb399c9d2ffaf1f5a29 Boot ID: dbc7438e4d464209ac79452410cf60e7 Operating System: CentOS Stream 8 CPE OS Name: cpe:/o:centos:centos:8 Kernel: Linux 4.18.0-408.el8.x86_64 Architecture: x86-64 Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 8023804 0 8023804 0% /dev tmpfs 8055520 24 8055496 1% /dev/shm tmpfs 8055520 99708 7955812 2% /run tmpfs 8055520 0 8055520 0% /sys/fs/cgroup /dev/mapper/cs-root 73364480 11401568 61962912 16% / /dev/mapper/cs-home 166691304 1467260 165224044 1% /home /dev/sda2 1038336 262972 775364 26% /boot /dev/sda1 613184 7416 605768 2% /boot/efi tmpfs 1611104 12 1611092 1% /run/user/42 tmpfs 1611104 4 1611100 1% /run/user/1000 There are 3 hosts, which can all detect and begin the update, getting most of the way through it, before failing and returning it to a state of non-operation. The log file says that the host is unable to resolve the virtual switch dependency log excerpt: "stdout" : "fatal: [192.168.2.18]: FAILED! => {\"changed\": false, \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem 1: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2 .17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64\\n - packag e rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-52.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-53.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-56.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-6.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-72.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-75.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-80.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-81.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-88.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-2.15-4.el8.noarch\\n - cannot install the best update candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\\n Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be installed\\n - cannot install the best update candidate for package python3-openvswitch2.15-2.15.0-117.el8s.x86_64\\n - cannot install the best update candidate for package openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\\n Problem 3: package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none of the providers can be installed\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-82.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarc h obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-21.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-17.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-29.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\\n - cannot install the best update candidate for package ovn-2021-21.12.0-82.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\\n Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires ovn-2021-host, but none of the providers can be installed\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-82.el8s.x86_64\\n - pa ckage rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-21.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-40.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-17.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-29.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-11.el8s.x86_64\\n - cannot install the best update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch\", \"rc\": 1, \"results\": []}", On one host, when I attempt to open the ovirt web console from the gui it won't open, and virtual machines on that particular host are unable to run an ovirt web console as well: citing handshake error failure. log excerpt for host web console: Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=24 name='cen-79-dmz-02' uuid=82fefcfa-bce0-4397-a575-48d3d08fdb61 is tainted: custom-ga-command Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=25 name='win-10-utl' uuid=11f71942-1d88-40a0-a6c5-45e7718afbcf is tainted: custom-ga-command Oct 17 03:37:01 ovirt-host-05 ovs-appctl[37436]: ovs|00001|unixctl|WARN|failed to connect to /var/run/ovn/ovn-controller.18617.ctl Thank you in advance

3 3

hosted-engine-setup --deploy fail on Centos Stream 8
by andrea.crisanti＠uniroma1.it 19 Oct '22

19 Oct '22

Hy, I am trying to install ovirt 4.5 on a 4-host cluster running Centos Stream 8, but the engine does not start and the whole process fails. Here is my procedure dnf install centos-release-ovirt45 dnf module reset virt dnf module enable virt:rhel dnf install ovirt-engine-appliance dnf install ovirt-hosted-engine-setup The latest version of ansible [ansible-core 2.13] uses python3.9 and the installation fails because some python3.9 modules are missing [python39-netaddr, python39-jmespath] and cannot be installed [conflict python3-jmespath]. So I downgraded ansible to ansible-core 2.12 dnf downgrade ansible-core Now hosted-engine-setup --deploy --4 goes proceed further but stops because it cannot start the engine [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} I looked into the log file /var/log//ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20221007132728-yp7cd1.log and I found the following error: 2022-10-07 13:28:30,881+0200 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "changed": false, "cmd": [ "virsh", "net-undefine", "default" ], "delta": "0:00:00.039258", "end": "2022-10-07 13:28:30.710401", "invocation": { "module_args": { "_raw_params": "virsh net-undefine default", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": false } }, "msg": "non-zero return code", "rc": 1, "start": "2022-10-07 13:28:30.671143", "stderr": "error: failed to get network 'default'\nerror: Network not found: no network with matching name 'default'", "stderr_lines": [ "error: failed to get network 'default'", "error: Network not found: no network with matching name 'default'" ], "stdout": "", "stdout_lines": [] }, "ansible_task": "Update libvirt default network configuration, undefine", "ansible_type": "task", "status": "FAILED", "task_duration": 0 } Needless to say firewalld and libvirtd are both up and virsh net-list gives: Name State Autostart Persistent ------------------------------------------------ ;vdsmdummy; active no no default active no yes I googled around without success. Has anyone had similar problems? End of past July I installed Ovirt on another cluster running Centos Stream 8 following the procedure I just described with no problem. If needed I can post all log files. Thanks for the help. Best Andrea

3 4

Get Vlan IDs from multiple VMs
by chry3＠hotmail.com 19 Oct '22

19 Oct '22

Hello, I´m exrtracting diferent VM informations from diferent VMs that are deployed on a server that I need to proccess later. I already have informations such as IPs, macs cpu cores etc, but I would like to get the VLAN id from each of the VMs. How can I do that? How can I get the network profile that my VM is using? Kind Regards.

1 1

Adding documentation - Migrating from a self-hosted engine to a standalone
by David White 18 Oct '22

18 Oct '22

Hi. I'm working on adding instructions to the documentation for how to migrate from a self-hosted engine to a stand alone manager. This will be the first time I've contributed anything to this project (or any larger open source project for that matter), so before I get too far in the weeds, I wanted to run this by the community so as not to waste my time if this is a bad idea. My general high level documentation is pasted at the bottom of this email. These are the steps that I took when I did my own migration. (Note to self: Need to add a step at the end to log into the Manager and disable the Gluster service by going to Computer --> Clusters --> (Edit the cluster) --> Uncheck the "Enable Gluster Service" checkbox. And I've forked the ovirt-site repo and started working on the documentation here: https://github.com/dmwhite823/ovirt-site/tree/migrate-engine-to-standalone I still have a ways to go before I'm ready to request a PR, but I'm open to any & all feedback. I think that I'm done with most of the changes necessary to ovirt-site/source/documentation/migrating_from_a_self-hosted_engine_to_a_standalone_manager/index.adoc, but I'm unclear why there's also a master.adoc file. Note that I copied files into the new directory of migrating_from_a_self-hosted_engine_to_a_standalone_manager from the already existing migrating_from_a_standalone_manager_to_a_self-hosted_engine structure directory, and am editing the files in the new directory. Will this be useful / helpful? Would others on the team like to contribute to improving these instructions prior to issuing a PR to the ovirt-site git repo? Am I even doing this right? 🤣 Thanks, David High level overview of steps required (pasted below): Pre-req: Make sure VMs are not using HA lease of a gluster domain 1) Migrate all storage off Gluster 2) Remove all gluster volumes from oVirt 3) Put cluster into global maintenance hosted-engine --set-maintenance --mode=global 4) On new VM: Install CentOS Stream & add ovirt repos dnf install centos-release-ovirt45 dnf module enable javapackages-tools pki-deps postgresql:12 mod_auth_openidc:2.3 nodejs:14 Stop & Disable the engine # systemctl stop ovirt-engine # systemctl disable ovirt-engine Setup DNS in /etc/hosts if you don't have local DNS servers Backup the engine # engine-backup --mode=backup --file=file_name --log=log_file_name Restore # engine-backup --mode=restore --file=engine-backup-09172022-1 --log=restore --restore-permissions Run engine-setup # engine-setup

1 0

oVirt 4.5.3 is now generally available
by Lev Veyde 18 Oct '22

18 Oct '22

The oVirt project is excited to announce the general availability of oVirt 4.5.3, as of October 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 on top of oVirt 4.4. Important notes before you install / upgrade Some of the features included in oVirt 4.5.3 require content that is available in RHEL 8.6 (or newer) and derivatives. NOTE: If you’re going to install oVirt 4.5.3 on RHEL or similar, please read Installing on RHEL or derivatives <https://ovirt.org/download/install_on_rhel.html> first. Documentation Be sure to follow instructions for oVirt 4.5! - 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.5.3 Release? This release is available now on x86_64 architecture for: - CentOS Stream 8 - RHEL 8.6 and derivatives This release supports Hypervisor Hosts on x86_64: - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 - RHEL 8.6 and derivatives This release also supports Hypervisor Hosts on x86_64 as tech preview without secure boot: - CentOS Stream 9 - RHEL 9.0 and derivatives - oVirt Node NG based on CentOS Stream 9 Builds are also available for ppc64le and aarch64. Known issues: - On EL9 with UEFI secure boot, vdsm fails to decode DMI data due to Bug 2081648 <https://bugzilla.redhat.com/show_bug.cgi?id=2081648> - python-dmidecode module fails to decode DMI data Security fixes included in oVirt 4.5.3 compared to latest oVirt 4.5.2: Bug list <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir…> Some of the RFEs with high user impact are listed below: Bug list <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir…> Some of the Bugs with high user impact are listed below: Bug list <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir…> oVirt Node will be released shortly after the release will reach the CentOS mirrors. See the release notes for installation instructions and a list of new features and bugs fixed. Additional resources: - Read more about the oVirt 4.5.3 release highlights: https://www.ovirt.org/release/4.5.3/ - 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/ -- 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>

2 2

Network Interface Already In USe - Self-Hosted Install
by Matthew J Black 18 Oct '22

18 Oct '22

Hi Guys & Girls, <begin_rant> OK, so I am really, *really* starting to get fed up with this. I know this is probably my fault, but even if it is then the oVirt documentation isn't helping in any way (being... "less than clear"). What I would really like is instead of having to rely on the "black box" that is Ansible, what I'd like is a simple set of clear cut instructions, Step-By-Step, so that we actually *know* what was going on when attempting to do a Self-Hosted install. After all, oVirt's "competition" doesn't make things so difficult... <end_rant> Now that I've got that on my chest, I'm trying to do a straight forward Self-Hosted Install. I've followed the instructions in the oVirt doco pretty much to the letter, and I'm still having problems. My (pre-install) set-up: - A freshly installed server (oVirt_Node_1) running Rocky Linux 8.6 with 3 NICs - NIC_1, NIC_2, & NIC_3. - There are three VLANs - VLAN_A (172.16.1.0/24), VLAN_B (172.16.2.0/24), & VLAN_C (172.16.3.0/24). - NIC_1 & NIC_2 are formed into a bond (bond_1). - bond_1 is an 802.3ad bond. - bond_1 has 2 sub-interfaces - bond_1.a & bond_1.b - Interface bond_1.a in in VLAN_A. - Interface bond_1.b is in VLAN_B. - NIC_3 is sitting in VLAN_C. - VLAN_A is the everyday "working" VLAN where the rest of the servers all sit (ie DNS Servers, Local Repository Server, etc, etc, etc), and where the oVirt Engine (OVE) will sit. - VLAN B is for data throughput to and from the Ceph iSCSI Gateways in our Ceph Storage Cluster. This is a dedicated isolated VLAN with no gateway (ie only the oVirt Hosting Nodes and the Ceph iSCSI Gateways are on this VLAN). - VLAN C is for OOB management traffic. This is a dedicated isolated VLAN with no gateway. Everything is working. Everything can ping properly back and forth within the individual VLANs and VLAN_A can ping out to the Internet via its gateway (172.16.1.1). Because we don't require iSCSI connectivity for the OVE (its on a working local Gluster TSP volume) the iSCSI hasn't *yet* been implemented. After trying to do the install using our Local Repository Mirror (after discovering and mirroring all the required repositories), I gave up on that because for a "one-off" install it wasn't worth the time and effort it was taking, especially when it "seems" that the Ansible playbook wants the "original" repositories anyway - but that's another rant/issue. So, I'm using all the original repositories as per the oVirt doco, including the special instructions for Rocky Linux and RHEL-derivatives in general, and using the defaults for the answers to the deployment script (except where there are no defaults) - and now I've got the following error: ~~~ [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "cmd": ["virsh", "net-start", "default"], "delta": "0:00:00.031972", "end": "2022-10-04 16:41:38.603454", "msg": "non-zero return code", "rc": 1, "start": "2022-10-04 16:41:38.571482", "stderr": "error: Failed to start network default\nerror: internal error: Network is already in use by interface bond_1.a", "stderr_lines": ["error: Failed to start network default", "error: internal error: Network is already in use by interface bond_1.a"], "stdout": "", "stdout_lines": []} [ ERROR ] Failed to execute stage 'Closing up': Failed getting local_vm_dir ~~~ The relevant lines from the log file (at least I think these are the relevant lines): ~~~ 2022-10-04 16:41:35,712+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Update libvirt default network configuration, undefine] 2022-10-04 16:41:37,017+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'changed': False, 'stdout': '', 'stderr': "error: failed to get network 'default'\nerror: Network not found: no network with matching name 'default'", 'rc': 1, 'cmd': ['virsh', 'net-undefine', 'default'], 'start': '2022-10-04 16:41:35.806251', 'end': '2022-10-04 16:41:36.839780', 'delta': '0:00:01.033529', 'msg': 'non-zero return code', 'invocation': {'module_args': {'_raw_params': 'virsh net-undefine default', '_uses_shell': False, 'warn': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': ["error: failed to get network 'default'", "error: Network not found: no network with matching name 'default'"], '_ansible_no_log': False} 2022-10-04 16:41:37,118+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 ignored: [localhost]: FAILED! => {"changed": false, "cmd": ["virsh", "net-undefine", "default"], "delta": "0:00:01.033529", "end": "2022-10-04 16:41:36.839780", "msg": "non-zero return code", "rc": 1, "start": "2022-10-04 16:41:35.806251", "stderr": "error: failed to get network 'default'\nerror: Network not found: no network with matching name 'default'", "stderr_lines": ["error: failed to get network 'default'", "error: Network not found: no network with matching name 'default'"], "stdout": "", "stdout_lines": []} 2022-10-04 16:41:37,219+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Update libvirt default network configuration, define] 2022-10-04 16:41:38,421+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost] 2022-10-04 16:41:38,522+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Activate default libvirt network] 2022-10-04 16:41:38,823+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'changed': False, 'stdout': '', 'stderr': 'error: Failed to start network default\nerror: internal error: Network is already in use by interface bond_1.a', 'rc': 1, 'cmd': ['virsh', 'net-start', 'default'], 'start': '2022-10-04 16:41:38.571482', 'end': '2022-10-04 16:41:38.603454', 'delta': '0:00:00.031972', 'msg': 'non-zero return code', 'invocation': {'module_args': {'_raw_params': 'virsh net-start default', '_uses_shell': False, 'warn': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': ['error: Failed to start network default', 'error: internal error: Network is already in use by interface bond_1.a'], '_ansible_no_log': False} 2022-10-04 16:41:38,924+1100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "cmd": ["virsh", "net-start", "default"], "delta": "0:00:00.031972", "end": "2022-10-04 16:41:38.603454", "msg": "non-zero return code", "rc": 1, "start": "2022-10-04 16:41:38.571482", "stderr": "error: Failed to start network default\nerror: internal error: Network is already in use by interface bond_1.a", "stderr_lines": ["error: Failed to start network default", "error: internal error: Network is already in use by interface bond_1.a"], "stdout": "", "stdout_lines": []} 2022-10-04 16:41:39,125+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 PLAY RECAP [localhost] : ok: 106 changed: 32 unreachable: 0 skipped: 61 failed: 1 2022-10-04 16:41:39,226+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:226 ansible-playbook rc: 2 2022-10-04 16:41:39,226+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:233 ansible-playbook stdout: 2022-10-04 16:41:39,226+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:236 ansible-playbook stderr: 2022-10-04 16:41:39,226+1100 DEBUG otopi.plugins.gr_he_ansiblesetup.core.misc misc._closeup:475 {'otopi_host_net': {'ansible_facts': {'otopi_host_net': ['ens0p1', 'bond_1.a', 'bond_1.b']}, '_ansible_no_log': False, 'changed': False}, 'ansible-playbook_rc': 2} 2022-10-04 16:41:39,226+1100 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 485, in _closeup raise RuntimeError(_('Failed getting local_vm_dir')) RuntimeError: Failed getting local_vm_dir 2022-10-04 16:41:39,227+1100 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Failed getting local_vm_dir 2022-10-04 16:41:39,228+1100 DEBUG otopi.context context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN 2022-10-04 16:41:39,228+1100 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/error=bool:'True' 2022-10-04 16:41:39,228+1100 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/exceptionInfo=list:'[(<class 'RuntimeError'>, RuntimeError('Failed getting local_vm_dir',), <traceback object at 0x7f5210013088>)]' 2022-10-04 16:41:39,228+1100 DEBUG otopi.context context.dumpEnvironment:779 ENVIRONMENT DUMP - END ~~~ So, would someone please help me in getting this sorted - I mean, how are we supposed to do this install if the interface we need to connect to the box in the first place can't be used because it's "already in use"? Cheers Dulux-Oz

2 3

Hyperconverged install fails to add second and third hosts
by Calvin Ellison 18 Oct '22

18 Oct '22

Hello fellow users, I'm having trouble sending up a brand new cluster using Equinix Metal. The three servers are their "n3.xlarge.x86" model, which uses an Intel Xeon Gold 6314U CPU in a Supermicro SSG-110P-NTR10-EI018 server. The entire Hyperconverged installation process appears to complete without error, but when I log into the manager only one host is listed and only that host's Gluster brick appears in the UI. The only hint of a problem in the UI is in the Tasks pane: two failed tasks to add the other hosts. Where do I get started troubleshooting? Calvin Ellison Systems Architect calvin.ellison(a)voxox.com +1 (213) 285-0555 <http://voxox.com> <https://www.facebook.com/VOXOX/> <https://www.instagram.com/voxoxofficial/> <https://www.linkedin.com/company/3573541/admin/> <https://twitter.com/Voxox> The information contained herein is confidential and privileged information or work product intended only for the individual or entity to whom it is addressed. Any unauthorized use, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately.

2 1

install ovirt on maas provider
by Charles Kozler 15 Oct '22

15 Oct '22

Hello - I am attempting to install ovirt hosted engine (engine running as a VM in a cluster). I have configured 10 servers at a metal-as-a-service provider. The server wiring has been configured to our specifications, however, the MaaS provider requires bond0 to be setup previously and the two interface VLAN's preconfigured on the OS. I am not new to setting up ovirt though my experience has changed every installation and this is a new type of deployment for me (maas+ovirt) so I have some questions. bond0.2034 = Uplink to WAN switch bond0.3071 = Uplink to LAN internal switch (will need to become ovirtmgmt) The gluster storage links are separate and not in scope for this conversation right now as I am just trying to establish my first host and engine. Historically, ovirt has been a bit aggressive in how it sets up its networks at install (in my experience) and when any network came preconfigured it would typically drop it entirely which then means I lose my SSH as ovirt decided what to do. I am still TBD on whether or not I have drac/oob access to these systems so lets assume for now I do not. That all being said I am looking to see if anyone can tell me what to expect with my current configuration. I cannot risk running the hosted engine install and having ansible drop my network without my first confirming OOB availability so any suggestions

1 0

Error during deployment of ovirt-engine
by Jonas 14 Oct '22

14 Oct '22

Hello all I'm trying to deploy an oVirt Engine through the cockpit interface. Unfortunately the deployment fails with the following error: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set admin username] [ INFO ] ok: [localhost -> 192.168.222.95] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for ovirt-engine service to start] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Open a port on firewalld] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Expose engine VM webui over a local port via ssh port forwarding] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Evaluate temporary bootstrap engine VM URL] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Display the temporary bootstrap engine VM URL] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Detect VLAN ID] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set Engine public key as authorized key without validating the TLS/SSL certificates] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ ERROR ] ovirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials. [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": false, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials."} [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [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] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost] I can login just fine to the VM over SSH but when I try to login over the web interface as admin, the password is not accepted. I tried both complex and simple passwords for root/admin but none worked so far. This previous discussion did not solve my problems: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/HMLCEG2LPSWFOV… Thank you, Jonas

5 11

There is no glusterfs management dashboard in the Cockpit background
by ziyi Liu 13 Oct '22

13 Oct '22

I have many data centers, the first data center contains the engine, the glusterfs management dashboard can be seen in the Cockpit background, but the glusterfs management dashboard cannot be seen in the second data center, Create the second data center step: I create a data center in the engine, then set up a glusterfs cluster in the Cockpit background, and finally mount the glusterfs volume in the engine. Is there something wrong with the way I add it?

1 0

Re: OVS Task Error when Add EL Host
by erdosi.peter＠kifu.gov.hu 13 Oct '22

13 Oct '22

Actually, there are some strange stuff going on a newly deployed HE: [root@poc ~]# yum update Failed to set locale, defaulting to C.UTF-8 Last metadata expiration check: 0:34:52 ago on Fri Oct 14 01:09:57 2022. Error: Problem 1: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-52.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-53.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-56.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-6.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-72.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-75.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-80.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-81.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-88.el8s.x86_64 - cannot install the best update candidate for package ovirt-openvswitch-2.15-4.el8.noarch - cannot install the best update candidate for package openvswitch2.15-2.15.0-119.el8s.x86_64 Problem 2: package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none of the providers can be installed - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-82.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-21.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-17.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-29.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64 - cannot install the best update candidate for package ovn-2021-21.12.0-82.el8s.x86_64 - cannot install the best update candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch Problem 3: package ovirt-openvswitch-ovn-central-2.15-4.el8.noarch requires ovn-2021-central, but none of the providers can be installed - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.12.0-82.el8s.x86_64 - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.03.0-21.el8s.x86_64 - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.03.0-40.el8s.x86_64 - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.06.0-17.el8s.x86_64 - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.06.0-29.el8s.x86_64 - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.12.0-11.el8s.x86_64 - cannot install the best update candidate for package ovn-2021-central-21.12.0-82.el8s.x86_64 - cannot install the best update candidate for package ovirt-openvswitch-ovn-central-2.15-4.el8.noarch Problem 4: package ovirt-python-openvswitch-2.15-4.el8.noarch requires python3-openvswitch2.15, but none of the providers can be installed - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-119.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-106.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-110.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-115.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-117.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-22.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-23.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-24.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-27.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-30.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-32.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-35.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-37.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-39.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-41.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-47.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-48.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-51.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-52.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-53.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-54.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-56.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-6.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-72.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-75.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-80.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-81.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-88.el8s.x86_64 - cannot install the best update candidate for package python3-openvswitch2.15-2.15.0-119.el8s.x86_64 - cannot install the best update candidate for package ovirt-python-openvswitch-2.15-4.el8.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Maybe this can give a clue to someone. I used this iso: ovirt-node-ng-installer-4.5.2-2022081013.el8

1 0

Re: OVS Task Error when Add EL Host
by erdosi.peter＠kifu.gov.hu 13 Oct '22

13 Oct '22

I have a same issue with an installation today (oVirt 4.5.2, based on Centos Stream 8)

1 0

Disks in "Finalizing" state on Web Inteface
by markeczzz＠gmail.com 13 Oct '22

13 Oct '22

Hi! I have few vm-s that have disk status in "Finalizing" This VMs are working normally, but on web interface status is always "Finalizing" and progress bar is not moving. (It's in this state for days now) I can create snapshots and backups of them without problems and everything works ok. Is there any way that I can check why are this disks in that state? Regards,

1 0

Cannot run VM. The Custom Compatibility Version of VM ... (4.3) is not supported in Data Center compatibility version 4.4.
by nicolas＠devels.es 13 Oct '22

13 Oct '22

Hi, I'm running oVirt 4.4 and recently I changed the Data Center compatibility version from 4.3 to 4.4. Now turns out that some Pools are unable to restart machines, returning this error: Cannot run VM. The Custom Compatibility Version of VM ... (4.3) is not supported in Data Center compatibility version 4.4. I cannot edit manually the custom compatibility version of VMs, as pools won't allow that. Is there any manual way to fix it? I tried to do it via Python SDK but it doesn't seem to work... vm = vms_serv.list(name='X')[0] ver = vm.custom_compatibility_version ver.minor = 4 vm.custom_compatibility_version = ver vmsv = sys_serv.vms_service().vm_service(id=vm.id) vmsv.upfate(vm=vm) It doesn't seem to do any difference, though. Any help is really appreciated, as many our users can't use theis VMs. Thanks.

1 1

Ovirt support on el9
by Nathanaël Blanchet 13 Oct '22

13 Oct '22

Hello, is there a plan for an official el9 support ?

1 0

Upgrading from ovirt 4.5 rhel8 to rhel9
by Robert Pouliot 12 Oct '22

12 Oct '22

Hi, my setup is 3 physical servers with glusterfs. One of them had ovirt-engine. Usually my upgrade was (from 4.2, 4.3, 4.4, 4.5): engine-backup reinstall OS yum install ovirt-engine engine-backup: restore engine-setup. My main server was RHEL 8.6, ovirt 4.52. I did the backup, install AlmaLinux 9. But the package doesn't exist anymore with rhel9. Is the engine on bare-metal still available with rhel9? If not, is it possible to install the appliance with the saved config file with a different hostname and IP for the appliance? Thanks

1 0

Invalid GPG keys for rhel9 package
by Robert Pouliot 12 Oct '22

12 Oct '22

Hi, OS used is AlmaLinux 9.0. I tried to install the appliance with "hosted-engine", but unfortunately it complained about invalid GPG keys. The last 2 lines of the Key block seem strange. How can I fix this? I get the following message: [root@master ~]# yum install ovirt-engine-appliance Last metadata expiration check: 3:08:01 ago on Wed 12 Oct 2022 05:38:43 PM EDT. Dependencies resolved. ==================================================================================================================================== Package Architecture Version Repository Size ==================================================================================================================================== Installing: ovirt-engine-appliance x86_64 4.5-20220419160254.1.el9 ovirt-45-upstream 1.6 G Transaction Summary ==================================================================================================================================== Install 1 Package Total download size: 1.6 G Installed size: 1.6 G Is this ok [y/N]: y Downloading Packages: ovirt-engine-appliance-4.5-20220419160254.1.el9.x86_64.rpm 17 MB/s | 1.6 GB 01:36 ------------------------------------------------------------------------------------------------------------------------------------ Total 15 MB/s | 1.6 GB 01:45 oVirt upstream for CentOS Stream 9 - oVirt 4.5 682 kB/s | 2.9 kB 00:00 Importing GPG key 0xFE590CB7: Userid : "oVirt <infra(a)ovirt.org>" Fingerprint: 31A5 D783 7FAD 7CB2 86CD 3469 AB8C 4F9D FE59 0CB7 From : /etc/pki/rpm-gpg/RPM-GPG-KEY-oVirt-4.5 Is this ok [y/N]: y Key import failed (code 2). Failing package is: ovirt-engine-appliance-4.5-20220419160254.1.el9.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oVirt-4.5 The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'yum clean packages'. Error: GPG check FAILED Here is a part of the GPG key: -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2.0.22 (GNU/Linux) mQENBFM3+3YBCADTLqGw5hI0whRPeN0hSjpaZ2yNNtVzgqj8/EFQ9IfR7GasHz/4 kkT3cpKXZygo0AIVEe5dkrcYXF+9C6bowiuGZG+9G6j8MXneunRv7S0mv1mnx7MW [snip] FFm7Fr9czelRSW+NCUvvtKKFG612VvwSSU/u8DarGdLnrKxJ5ito7Pd+n3ZB1YVy sfxDvnYN =SxBW -----END PGP PUBLIC KEY BLOCK-----

1 0

VM Disk extend not reflected in VM oS
by simon＠justconnect.ie 12 Oct '22

12 Oct '22

Hi All, I extended a VM disk via oVirt Manager (4.4.8) without error, but when I checked the VM (fdisk & lsblk) the size has not changed. Any help as always would be appreciated. Kind Regards Simon...

5 11

Geo-replication configuration problem
by dan_agache＠yahoo.com 12 Oct '22

12 Oct '22

Hello, I have two GlusterFS clusters with Centos 9 Stream managed by oVirt 4.5 (standalone Manager with local databases) and when I want to configure geo-replication I receive this error message: Oct 10 15:15:15 myhostname vdsm[222665]: ERROR TypeError raised by dispatched function Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/rpc/Bridge.py", line 194, in _dynamicMethod result = fn(*methodArgs) File "/usr/lib/python3.9/site-packages/vdsm/gluster/apiwrapper.py", line 300, in geoRepKeysUpdate return self._gluster.geoRepKeysUpdate(userName, geoRepPubKeys) File "/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 95, in wrapper rv = func(*args, **kwargs) File "/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 720, in geoRepKeysUpdate self.svdsmProxy.glusterUpdateGeoRepKeys(userName, geoRepPubKeys) File "/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda> getattr(self._supervdsmProxy._svdsm, self._funcName)(*args, File "<string>", line 2, in glusterUpdateGeoRepKeys File "/usr/lib64/python3.9/multiprocessing/managers.py", line 825, in _callmethod raise convert_to_error(kind, result) TypeError: a bytes-like object is required, not 'str' Oct 10 15:15:15 myhostname vdsm[222665]: ERROR Internal server error Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/rpc/Bridge.py", line 194, in _dynamicMethod result = fn(*methodArgs) File "/usr/lib/python3.9/site-packages/vdsm/gluster/apiwrapper.py", line 300, in geoRepKeysUpdate return self._gluster.geoRepKeysUpdate(userName, geoRepPubKeys) File "/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 95, in wrapper rv = func(*args, **kwargs) File "/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 720, in geoRepKeysUpdate self.svdsmProxy.glusterUpdateGeoRepKeys(userName, geoRepPubKeys) File "/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda> getattr(self._supervdsmProxy._svdsm, self._funcName)(*args, File "<string>", line 2, in glusterUpdateGeoRepKeys File "/usr/lib64/python3.9/multiprocessing/managers.py", line 825, in _callmethod raise convert_to_error(kind, result) TypeError: a bytes-like object is required, not 'str' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/yajsonrpc/__init__.py", line 349, in _handle_request res = method(**params) File "/usr/lib/python3.9/site-packages/vdsm/rpc/Bridge.py", line 201, in _dynamicMethod raise InvalidCall(fn, methodArgs, e) vdsm.rpc.Bridge.InvalidCall: Attempt to call function: <bound method GlusterVolume.geoRepKeysUpdate of <vdsm.gluster.apiwrapper.GlusterVolume object at 0x7efd082d3400>> with arguments: ('geoaccount', ['command="/usr/libexec/glusterfs/gsyncd" ssh-rsa ...']) error: a bytes-like object is required, not 'str' Can you tell me what is wrong? Thank you, Dan

1 1

Re: OVS Task Error when Add EL Host
by aleksandar＠dualsoft.net 12 Oct '22

12 Oct '22

Hello, I am facing the same issue on multiple Operating Systems (Rocky Linux 8,9, oVirt Node 4.5.2). Did you maybe find a solution for this problem? All best, Aleksandar

1 0

How to configure HA virtual machine on hosts without IPMI
by samuel.xhu＠horebdata.cn 12 Oct '22

12 Oct '22

Dear Ovirt folks, I am thinking of deploly an experimental Ovirt 3-node Cluster on servers without IPMI. As far i know, Ovirts needs each host to have fence agent working for any HA virtual machine. My question is, are there any other ways in Ovirt to support fencing without using IPMI? thanks a lot, Samuel Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed (成就他人)

4 6

Re: OVS Task Error when Add EL Host
by Rui Crespo 11 Oct '22

11 Oct '22

Hi, I'm having the exact same problem doing a fresh install of RHEL and setting up (command line: hosted-engine --deploy --4) the ovirt-engine. I assume it must have been some kind of update to the base OS - (in my case RHEL 8.6 (Ootpa), because i have done previous installations with this exact OS and centos-release-ovirt45 repos without having an issues. The failed task is: TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] and, on the hosted-engine log: /var/log/ovirt-hosted-engine-setup/engine-logs-2022-10-11T18:43:29Z/log/ovirt-engine/host-deploy I see: "stdout" : "fatal: [xxxxx]: FAILED! => {\"msg\": \"The conditional check 'cluster_switch == \\\"ovs\\\" or (ovn_central is defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller\\n\\nThe error appears to be in '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may\\nbe elsewhere in the file depending on the exact syntax problem.\\n\\nThe offending line appears to be:\\n\\n- block:\\n - name: Install ovs\\n ^ here\\n\"}",

1 0

SSL error on oVirt 4.2.4
by Don Dupuis 11 Oct '22

11 Oct '22

Hello I have oVirt cluster with 25 hypervisors that has been running fine for a couple of years and today all of a sudden engine was getting ssl errors talking to the hypervisors. Error in engine.log is: 2022-10-10 16:20:23,562-05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-47) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Received fatal alert: unknown_ca Certificates don't seem expired and I ran the command: openssl x509 -noout -in /etc/pki/ovirt-engine/ca.pem -fingerprint openssl x509 -noout -in /etc/pki/vdsm/certs/cacert.pem -fingerprint # openssl x509 -noout -in /etc/pki/vdsm/libvirt-spice/ca-cert.pem -fingerprint # openssl x509 -noout -in /etc/pki/vdsm/libvirt-vnc/ca-cert.pem -fingerprint # openssl x509 -noout -in /etc/pki/CA/cacert.pem -fingerprint Those commands show that the fingerprints are the same. openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/engine.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/apache.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/websocket-proxy.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/jboss.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/imageio-proxy.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer These verification commands come back as OK. I am having trouble finding my problem. Does anyone have any suggestions? I am not finding any hits on google and unknown_ca. Also the vdsm log on hypervisors has this: 2022-10-10 15:54:42,843-0500 ERROR (Reactor thread) [ProtocolDetector.SSLHandshakeDispatcher] ssl handshake: SSLError, address: ::ffff:192.168.50.26 (sslutils:263) Thanks Don

1 1

Re: Snapshot not working
by Facundo Badaracco 11 Oct '22

11 Oct '22

Sorry for my ignorance. But, im trying since a few days to upload the requested logs, but it keeping me saying they are too big. How con i upload them? El vie, 7 de oct. de 2022 19:09, Facundo Badaracco <varekoarfa(a)gmail.com> escribió: > sorry for the delay. > > there are the engine.log, vdsm.log from spm and the host where the vm is > running. > > thx in advance! > > ---------- Forwarded message --------- > De: Facundo Badaracco <varekoarfa(a)gmail.com> > Date: jue, 6 oct 2022 a la(s) 20:22 > Subject: Re: [ovirt-users] Re: Snapshot not working > To: Benny Zlotnik <bzlotnik(a)redhat.com> > > > sorry for the delay. > > there are the engine.log, vdsm.log from spm and the host where the vm is > running. > > thx in advance! > > El jue, 6 oct 2022 a la(s) 20:03, Facundo Badaracco (varekoarfa(a)gmail.com) > escribió: > >> sorry for the delay. >> >> there are the engine.log, vdsm.log from spm and the host where the vm is >> running. >> >> thx in advance! >> >> >> El jue, 6 oct 2022 a la(s) 05:30, Benny Zlotnik (bzlotnik(a)redhat.com) >> escribió: >> >>> Can you provide relevant ovirt-engine and vdsm logs (SPM and host where >>> VM runs) >>> >>> On Tue, Oct 4, 2022 at 7:49 PM Facundo Badaracco <varekoarfa(a)gmail.com> >>> wrote: >>> > >>> > Someone? Any hint? >>> > >>> > El jue, 29 de sep. de 2022 10:58, Facundo Badaracco < >>> varekoarfa(a)gmail.com> escribió: >>> >> >>> >> hi everyone, >>> >> >>> >> I have a glusterFS replica x3 node. >>> >> >>> >> I can't create snapshot. when I create it, if I select to save the >>> memory, then in the disks section only appears the snapshot of the memory >>> and in locked state. If instead, I remove the option to make snapshot of >>> the memory, it does not make the snapshot saying "failed". >>> >> >>> >> Any idea? >>> > >>> > _______________________________________________ >>> > 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/5LQQKPQC6LRNE… >>> >>>

1 0

Convert raw images to qcow format
by Jonas 11 Oct '22

11 Oct '22

Hi there I want to create incremental backups of a few imported VMs, but the VM disks are in the raw disk format which does not support incremental backup. Is there a way to convert existing disks from raw to qcow in oVirt? Since qemu-img can do this,I assume there must be a way.. Thank you Jonas

2 1

Pre-Installing OpenVSwitch For oVirt Self-Hoster Install - Issues?
by Matthew J Black 11 Oct '22

11 Oct '22

Hi All, Is anyone aware of any issues (ie "gotchas") with pre-installing OpenVSwitch in preparation for an oVirt Self-Hosted install? We're trying to work around an error we're getting with `hosted-engine --deploy` which spits out: `error: Failed to start network default\nerror: internal error: Network is already in use by interface bond1.a`. What we're thinking is if we pre-create the OVS Network (ie ovirtmgmt) then `hosted-engine --deploy` won't baulk and fail to install. We've been grinding away at this and other issues for several weeks now and we're getting pretty desperate at this stage, to the point that we're starting to seriously consider giving up on oVirt completely - which would be a shame because it seems to be made for the job we want to do, but if we can't get it installed, let along working, then what's the point? (Plus I hate the thought of all the wasted time and effort - but that may just be the "suck cost fallacy" at work). Anyway, if anyone has any insights we'd appreciate them. Cheers Dulux-Oz

1 1

Re: OVS Task Error when Add EL Host
by Łukasz Pelczyk 09 Oct '22

09 Oct '22

I just hit the same error. Initially I got it on the beginning of installation (both netaddr and jmespath were not found). Seems that python3.9 is used so initially I solved it via pip3.9 install. Alternatively you can get the rpm packages from epel. The same issues is on ovirt VM side. As a workaround I started deployment with pause (hosted-engine --deploy --ansible-extra-vars=he_pause_host=true). With that you can ssh to the instance, and manually run pip install which got me: 'Successfully installed jmespath-1.0.1 netaddr-0.8.0'. This is just a workaround and proper fix should be reflected in engine VM image, or on the repos side.

1 0

Re: OVS Task Error when Add EL Host
by Martin Perina 07 Oct '22

07 Oct '22

Hi, please try to downgrade ansible-core-2.13 to 2.12, oVirt doesn't support 2.13 on EL8 yet. Regards, Martin On Thu, Oct 6, 2022 at 3:23 PM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > Hi, > > > > Getting strange error when adding EL Host (Using CentOS Stream 8) : > > The conditional check 'cluster_switch == \\\"ovs\\\" or (ovn_central is > defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter > requires python's netaddr be installed on the ansible controller\\n\\nThe > error appears to be in > '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': > line 3, column 5, but may\\nbe elsewhere in the file depending on the exact > syntax problem.\\n\\nThe offending line appears to be:\\n\\n- block:\\n - > name: Install ovs\\n ^ here\\n\"}", > > "msg" : "The conditional check 'cluster_switch == \"ovs\" or > (ovn_central is defined and ovn_central | ipaddr)' failed. The error was: > The ipaddr filter requires python's netaddr be installed on the ansible > controller\n\nThe error appears to be in > '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': > line 3, column 5, but may\nbe elsewhere in the file depending on the exact > syntax problem.\n\nThe offending line appears to be:\n\n- block:\n - name: > Install ovs\n ^ here\n" > > > > Already checking the python-netaddr and its already installed on the > system (both python3-netaddr and python38-netaddr). > > Using oVirt 4.5. Anybody getting this same issue ? > > > > Thanks before. > > Regards, > > Nur Imam Febrianto > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows > > > _______________________________________________ > 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/EGVQEKGAA6O2X… > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

2 1

Question: How does ovirt storage domain differ from VMFS?
by jstk888＠gmail.com 07 Oct '22

07 Oct '22

Hello, I was asked the other day what file system oVirt uses to store virtual machine images and how it differed from VMware VMFS. I had to admit that I didn't quite understand this aspect of oVirt. I've had a look around but haven't found an answer. I was wondering if someone could explain at a high level, how the underlying oVirt VM storage domain differs from VMFS? What file system is used? Does it use a file system at all? Thank you.

2 1

OVS Task Error when Add EL Host
by Nur Imam Febrianto 06 Oct '22

06 Oct '22

Hi, Getting strange error when adding EL Host (Using CentOS Stream 8) : The conditional check 'cluster_switch == \\\"ovs\\\" or (ovn_central is defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller\\n\\nThe error appears to be in '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may\\nbe elsewhere in the file depending on the exact syntax problem.\\n\\nThe offending line appears to be:\\n\\n- block:\\n - name: Install ovs\\n ^ here\\n\"}", "msg" : "The conditional check 'cluster_switch == \"ovs\" or (ovn_central is defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller\n\nThe error appears to be in '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n- block:\n - name: Install ovs\n ^ here\n" Already checking the python-netaddr and its already installed on the system (both python3-netaddr and python38-netaddr). Using oVirt 4.5. Anybody getting this same issue ? Thanks before. Regards, Nur Imam Febrianto Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

1 0

Snapshot not working
by Facundo Badaracco 06 Oct '22

06 Oct '22

hi everyone, I have a glusterFS replica x3 node. I can't create snapshot. when I create it, if I select to save the memory, then in the disks section only appears the snapshot of the memory and in locked state. If instead, I remove the option to make snapshot of the memory, it does not make the snapshot saying "failed". Any idea?

2 2

Issues with snapshot and template
by David Johnson 06 Oct '22

06 Oct '22

Good morning all, Thank you in advance. My current environment is ovirt 4.5.2.4-1.el8, running on centos 7.9. I'm looking for advice on resolving two issues that have just come to light: *Issue #1*: When I attempt to create a template from the oVirt GUI, I click the "Make Template" button, enter the name for the new template, then click the "OK" button. The OK button highlights, but nothing happens. *There are no entries showing activity in the engine.log.* *Issue #2:* When I delete a snapshot, after the snapshot is deleted, I receive this error message from the GUI: [image: image.png] *ui.log entry:* 2022-10-05 11:01:42,014-05 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-243) [] Permutation name: 872EE01DC49AC3F81586694F1584D19D 2022-10-05 11:01:42,014-05 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-243) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read properties of null (reading 'wV') at org.ovirt.engine.ui.uicommonweb.models.vms.VmSnapshotListModel.$updateActionAvailability(VmSnapshotListModel.java:834) at org.ovirt.engine.ui.uicommonweb.models.vms.VmSnapshotListModel.onSelectedItemChanged(VmSnapshotListModel.java:262) at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel.$setItems(SearchableListModel.java:714) at org.ovirt.engine.ui.uicommonweb.models.vms.VmSnapshotListModel.$updateItems(VmSnapshotListModel.java:225) at org.ovirt.engine.ui.uicommonweb.models.vms.VmSnapshotListModel.setItems(VmSnapshotListModel.java:205) at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel$SetItemsAsyncQuery$1.$onSuccess(SearchableListModel.java:878) at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel$SetItemsAsyncQuery$1.onSuccess(SearchableListModel.java:878) at org.ovirt.engine.ui.frontend.Frontend$1.$onSuccess(Frontend.java:239) at org.ovirt.engine.ui.frontend.Frontend$1.onSuccess(Frontend.java:239) at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.$onSuccess(OperationProcessor.java:133) at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.onSuccess(OperationProcessor.java:133) at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.$onSuccess(GWTRPCCommunicationProvider.java:270) at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.onSuccess(GWTRPCCommunicationProvider.java:270) at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:198) at com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:233) at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409) at Unknown.eval(webadmin-0.js) at com.google.gwt.core.client.impl.Impl.apply(Impl.java:306) at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:345) at Unknown.eval(webadmin-0.js) *David Johnson*

2 1

Re: oVirt 4.5 self-hosted network not working
by Paul-Erik Törrönen 05 Oct '22

05 Oct '22

On 2022-08-25 22:56, Facundo Badaracco wrote: > Have u checked the IP of the engine VM? Yes. It is what I configured during the setup, and which I use when I ssh from the host to the engine VM. Sorry, I should have mentioned this in my previous message. Poltsi

2 4

oVirt 4.5.2 /var growing rapidly due to ovirt_engine_history db
by sohail_akhter3＠hotmail.com 05 Oct '22

05 Oct '22

Hi, We have recently upgrade our oVirt environment to 4.5.2 version. Environment is based on hosted-engine. Since we have upgrade we noticed rapid incrase in /var partition in engine VM. It is increasing very rapidly. If we vacuum ovirt_engine_history db, /var size reduces but next day size will increase again upto 5-10%. We did db vacuuming couple of time but not sure we it is increasing so rapidly. Here is the partial output of vacuuming that was done on 26-08-22. Table "host_interface_hourly_history" had more entries to be removed. Rest of the table had not much entries. Previously table "host_interface_samples_history" had entries to be removed. Any Idea what can be the reason for that? # dwh-vacuum -f -v SELECT pg_catalog.set_config('search_path', '', false); vacuumdb: vacuuming database "ovirt_engine_history" RESET search_path; SELECT c.relname, ns.nspname FROM pg_catalog.pg_class c JOIN pg_catalog.pg_namespace ns ON c.relnamespace OPERATOR(pg_catalog.=) ns.oid LEFT JOIN pg_catalog.pg_class t ON c.reltoastrelid OPERATOR(pg_catalog.=) t.oid WHERE c.relkind OPERATOR(pg_catalog.=) ANY (array['r', 'm']) ORDER BY c.relpages DESC; SELECT pg_catalog.set_config('search_path', '', false); VACUUM (FULL, VERBOSE) public.host_interface_samples_history; INFO: vacuuming "public.host_interface_samples_history" INFO: "host_interface_samples_history": found 3135 removable, 84609901 nonremovable row versions in 1564960 pages DETAIL: 0 dead row versions cannot be removed yet. CPU: user: 41.88 s, system: 14.93 s, elapsed: 422.83 s. VACUUM (FULL, VERBOSE) public.host_interface_hourly_history; INFO: vacuuming "public.host_interface_hourly_history" INFO: "host_interface_hourly_history": found 252422 removable, 39904650 nonremovable row versions in 473269 pages Please let me know if any further information is required. Regards Sohail

2 4

Re: Export to Data Domain (with TPM)
by Milan Zamazal 05 Oct '22

05 Oct '22

Christopher Law <chris(a)chrislaw.me> writes: > Anyone explain why I can't export a Virtual Machine with a TPM? Is > this something to do with the TPM data? I'm exporting the VM to some > cold storage. What's the deal here how can I export it and keep the > TPM data or do I have to disable TPM on it first? > > oVirt Error message when trying to export a VM to a Data Domain that has a TPM. > Export VM Failed > Cannot add VM. TPM device is required by the guest OS Hi, it is a Windows VM, right? It is a bug, I filed https://github.com/oVirt/ovirt-engine/issues/702 . The export should work. A workaround could be temporarily switching the VM operating system in the VM properties to Red Hat Enterprise Linux 9 before exporting but I'm not sure it won't change some other VM properties, be careful if you attempt it. Regards, Milan

2 1