- Users - oVirt List Archives

Host restarting with error
by Murilo Morais 03 Nov '22

03 Nov '22

Good morning gentlemen. I have a weird problem with a setup I finished. I'm using oVirt 4.4 Hosted Engine with NFS as Storage Domain, it happens that, if the Storage disconnects, in a few minutes the machine restarts and the red LED lights up as if there had been a crash. I managed to capture a screenshot of this moment once, OOM-Killer killed modprobe which doesn't make much sense as there is no VM other than the Hosted Engine and there is 128G of RAM on the machine.

1 0

VNC console connection fails [ovirt 4.5.3.1-1.el8]
by andre.liebe＠gematik.de 02 Nov '22

02 Nov '22

Hello list, is there anybody else out there having problems to connect to a vm console via vnc or is it just me? We are running ovirt-engine 4.5.3.1-1.el8 on up to date ovirt-nodes. I can connect to every virtual machine by spice, but am unable to connect via vnc due to a tls handshake error. Remote-viever just shows "Failed to complete handshake Error in the pull function" (on windows and linux clients). Wireshark tls handshake capture looks supicious to me, server hello message is just 182 bytes long and doesn't coantain a server certificate. Is this normal? sincerely André

2 1

Re: OVS Task Error when Add EL Host
by Federico Cucinella 02 Nov '22

02 Nov '22

Had the same issue, solved by upgrading the hosted-engine

1 0

How can I download multiple disks using wget or curl?
by wodel youchi 31 Oct '22

31 Oct '22

Hi, VM disks can be downloaded from the Manager UI. How can I achieve the same result using curl or wget or something else? I have several disks that I wish to download via script. Could you help with that? Regards.

3 2

mom-vdsm service is failing after update to 4.5.3.2-1.el8
by Jirka Simon 31 Oct '22

31 Oct '22

Hello there, we just updated oVirt engine to 4.5.3.2-1.el8 which was smooth, but then when we start to update all nodes, after restart mom-vdsm service is failing to start mom-vdsm rpm -q vdsm vdsm-4.50.3.4-1.el8.x86_64 (VDSM was updated from 4.50.2.2-1.el8 ) rpm -q mom mom-0.6.3-1.el8.noarch (MOM was not updated duting tha last update) here is error from /var/log/vdsm/mom.log 2022-10-28 13:17:18,105 - mom - INFO - MOM starting 2022-10-28 13:17:18,138 - mom.HostMonitor - INFO - Host Monitor starting 2022-10-28 13:17:18,138 - mom - INFO - hypervisor interface vdsmjsonrpcclient 2022-10-28 13:17:18,179 - mom.HostMonitor - INFO - HostMonitor is ready 2022-10-28 13:17:18,242 - mom.GuestManager - INFO - Guest Manager starting: multi-thread 2022-10-28 13:17:18,247 - mom.Policy - INFO - Loaded policy '00-defines' 2022-10-28 13:17:18,247 - mom - ERROR - Failed to initialize MOM threads Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/mom/__init__.py", line 35, in run host_monitor, guest_manager) File "/usr/lib/python3.6/site-packages/mom/PolicyEngine.py", line 42, in __init__ self.load_policy() File "/usr/lib/python3.6/site-packages/mom/PolicyEngine.py", line 71, in load_policy read_policy(fname, name.split('.policy')[0]) File "/usr/lib/python3.6/site-packages/mom/PolicyEngine.py", line 53, in read_policy return self.policy.set_policy(policy_name, policyStr) File "/usr/lib/python3.6/site-packages/mom/Policy/Policy.py", line 64, in set_policy self.code = get_code(Evaluator(), self._cat_policies()) File "/usr/lib/python3.6/site-packages/mom/Policy/Parser.py", line 543, in get_code tokens = scanner.tokenize(string) File "/usr/lib/python3.6/site-packages/mom/Policy/Parser.py", line 72, in tokenize GenericScanner.tokenize(self, input) File "/usr/lib/python3.6/site-packages/mom/Policy/spark.py", line 78, in tokenize add_lines = self.index2func[i](groups[i], line) TypeError: t_default() takes 2 positional arguments but 3 were given any tip what could be the reason ? Thaak you Jirka

2 2

Nightly build to stable
by Erdősi Péter 29 Oct '22

29 Oct '22

Hi, I've installed the Version 4.5.4-0.2.master.20221007083550.gitb24d914c24.el8 few days before (since the stable not working at the time) Is there any way to make this installation following the stable updates if the 4.5.4 became stable? Regards, Peter -- *Erdősi Péter * /Informatikus, IKT Fejlesztési Főosztály / *Kormányzati Informatikai Fejlesztési Ügynökség * cím: 1134 Budapest, Váci út 35. tel: +36 1 450 3080 e-mail: erdosi.peter(a)kifu.gov.hu <mailto:erdosi.peter@kifu.gov.hu> KIFÜ - www.kifu.gov.hu <http://kifu.gov.hu/kifu/>

1 0

Start Hosted Engine - new installation 4.5.3.1
by nowak.pawel.mail＠gmail.com 28 Oct '22

28 Oct '22

Hi, I am trying to configure "Hosted Engine Deployment". I get a message "The ipaddr filter requires python's netaddr be installed on the ansible controller". I think I have the necessary components installed. How to solve the problem?

4 4

[4.4.7] The latest guest agent needs to be installed and running on the guest
by Christoph Timm 28 Oct '22

28 Oct '22

Hi list, I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs have issues to report the performance information via the guest agent. I see the following message on the VMs: The latest guest agent needs to be installed and running on the guest The qemu-guest agent is installed on VMs (the VM OS is CentOS 8). Any advice how to troubleshoot this? I can see the stats will be presented in the GUI, if I migrate the VM to a different host. Best regards Christoph

4 8

Wrong engine version grts installed
by ada per 28 Oct '22

28 Oct '22

Hello, Both node version 4.5.3 and 4.5.2 ate installing the master version. The version of the engine that gets installed is 4.5.4-0.2.master.20221025103923.git936a8fcd09.el8 I do not understand why master version was installed, as I wanted the stable version.

4 13

Linux direct boot kernel/initrd from Data Domain
by Francesco Zaccaria 26 Oct '22

26 Oct '22

Hi, I'm using Ansible ovirt_vm module for automating VM Linux direct boot, but it seems kernel/initrd are not working if uploaded to Data Domain. Same problem starting VM from Ansible playbook and from OLVM web portal. I uploaded kernel/initrd (extracted from Oracle Linux 8.6 ISO) on a Data Domain, both via webconsole and REST APIs; according to doc (http://ovirt.github.io/ovirt-engine-api-model/master/#types/operating_syste…) kernel/initrd can be on ISO storage domain, but it's a deprecated OLVM feature. I have an OLVM cluster (Version 4.4.8.6) with 1 manager, 2 hosts and 2 Fibre Channel Data Domains (I always use first one for VMs). Uploading kernel/initrd on hosts installation works like a charm: kernel_path: /tmp/vmlinuz initrd_path: /tmp/initrd.img kernel_params: "inst.ks.sendmac inst.ks=https://[webserver]ks.cfg ip={{ item.static_ip }}::{{ item.gateway }}:{{ vm_netmask }}::{{ item.nic_name }}:off net.ifnames=0 {% for ip in dns_server %} nameserver={{ ip }} {% endfor %}" kernel_params_persist: false While using Data Domain is not working (disk ID is needed because of alias names not unique): kernel_path: iso://69146b00-4779-47b3-95eb-d2c9bb84e588 initrd_path: iso://6212fb79-e4bb-42ca-ac5c-1da0d0dba7dc At VM booting I get this error, reporting path which is present just on first host (why not on both?): Exit message: unable to set security context 'system_u:object_r:virt_content_t:s0' on '/rhev/data-center/mnt/blockSD/38730c94-68b1-4fde-8a31-8c3870925996/images/69146b00-4779-47b3-95eb-d2c9bb84e588/9797758e-d038-4a50-a188-e3601ad0e539': No such file or directory. Finally, using same full ISO CD attached to VM: kernel_path: iso://b9e8fad1-9884-46a4-8203-9ac73b69ecac initrd_path: iso://b9e8fad1-9884-46a4-8203-9ac73b69ecac I get permission denied (link seems missing, though image is correctly used when booting from CD): Exit message: internal error: process exited while connecting to monitor: 2022-10-26T11:07:07.779657Z qemu-system-x86_64: -blockdev {"driver":"host_device","filename":"/rhev/data-center/mnt/blockSD/38730c94-68b1-4fde-8a31-8c3870925996/images/b9e8fad1-9884-46a4-8203-9ac73b69ecac/48b92374-b4cb-45f6-b388-883abbf691c2","node-name":"libvirt-5-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/rhev/data-center/mnt/blockSD/38730c94-68b1-4fde-8a31-8c3870925996/images/b9e8fad1-9884-46a4-8203-9ac73b69ecac/48b92374-b4cb-45f6-b388-883abbf691c2': Permission denied. I found similar issue opened https://lists.ovirt.org/archives/list/users@ovirt.org/thread/IDIDY6ZLZCRMVM… could the problem be ISO path with Data Storage? https://github.com/oVirt/ovirt-engine/blob/936a8fcd09a4047c03b6cb5bf77709e0…

1 0

build OVA file from ovf file + files with RAW disks
by goosesk blabla 26 Oct '22

26 Oct '22

Hi, for backup VM i use script to create snapshot and then attach disks of VM to backupVM where i do copy of this disk . Also i backup OVF file. for restore , i just upload disk to corupted VM and attach. But ,, if i want to make some easy restore GUI,, it will be easier if i build OVA file from restored OVF and raw disks and then through API just import VM from OVA. The problem is i cannot find any correct way to to build correct OVA file for OVIRT. is there some playbook or script or way ho to do ? thank you Jan

2 1

Async release for ovirt-engine (4.5.3.2) and mom (0.6.4) is now available
by Lev Veyde 26 Oct '22

26 Oct '22

The oVirt Team has just released a new version of ovirt-engine package (4.5.3.2) and mom (0.6.4) that fixes important bugs: - Bug 2137207 <https://bugzilla.redhat.com/2137207> - The RemoveDisk job finishes before the disk was removed from the DB - Bug 2137532 <https://bugzilla.redhat.com/2137532> - MoM functionality is broken in mom-0.6.3-1 - Failed to initialize MOM threads The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. -- 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

Unable to delete snapshots on vm
by roanne.philip＠voxtelecom.co.za 26 Oct '22

26 Oct '22

Hi I am unable to delete snapshots on VM The error below "Cannot remove Snapshot. Snapshot is currently being created for VM" I have checked with ./taskcleaner.sh no tasks and with ./unlock_entity.sh no locked disks,vm,sanpshots ect But on ovirt UI there is an lock icon on the vm further i have checked the DB engine=# select * from job order by start_time desc; job_id | action_type | description | status | owner_id | visible | start_time | end_time | last_update_time | correlation_id | is_external | is_auto_cleared | engine_session_seq_id --------------------------------------+----------------+------------------------------------------------+--------+--------------------------------------+---------+----------------------------+----------------------------+----------------------------+------------------------------------- -+-------------+-----------------+----------------------- 9aea9f99-406f-45ab-9fe1-8d861b7b00c3 | RemoveSnapshot | Removing Snapshot 01/10/2022 of VM QRADAR_SIEM | FAILED | d6720431-c743-41ca-83e7-34901bc0df88 | t | 2022-10-18 14:00:37.295+02 | 2022-10-18 14:00:37.307+02 | 2022-10-18 14:00:37.307+02 | fb369cc6-8dae-4d57-9017-ae93a0b0237b | f | t | 60043 (1 row) no other running tasks can someone please assist how to get the running snapshot task if there isn't any

3 18

Re: New hosted engine installation, fails to login to the Administration Portal
by Jacob Møller Nielsen 26 Oct '22

26 Oct '22

Hi It seems the old authentication method for local users is or will be depreciated. (internal-authz) It is replaced by internalkeycloak-authz method. I can’t find any way to add local users, but only to use external (LDAP,AD etc..) Please update this if you find a way to do local users. First Name Last Name User Name Authorization provider Namespace E-mail [cid:image001.png@01D8E938.611B0230] admin admin<javascript:;> internal-authz * [cid:image001.png@01D8E938.611B0230] admin@ovirt<javascript:;> internalkeycloak-authz * [cid:image001.png@01D8E938.611B0230] Test Test test<javascript:;> internal-authz * jmn Best Regards [cid:b4r-logo200px_462d7941-ffe2-4f69-8c53-aade89528399.jpg] Jacob Møller Nielsen Senior IT Solution Specialist Mobile +45 30 50 07 20<tel:+45%2030%2050%2007%2020> E-mail jmn(a)b4restore.com<mailto:jmn@b4restore.com> Web www.b4restore.com<http://www.b4restore.com> [cid:linkedin_a3dd4789-eec6-4d7c-8d20-670718e518a6.png]<https://www.linkedin.com/company/b4restore-a-s/> [cid:twitter_14d6b75a-f4b7-45ec-ba88-75a90e22a7be.png] <https://twitter.com/b4restore> [cid:facebook_915c5beb-e98f-46ec-bd13-f86d9235df9b.png] <https://www.facebook.com/B4Restore> [cid:email_d9cf36a4-1bfe-4032-9d73-17a7eb3d40d3.png] <https://www.b4restore.com/en/about-us/newsletter>

1 0

Zanata access request
by Vladimir Talankin 26 Oct '22

26 Oct '22

Hello! I'm writing on behalf of the HOSTVM support team. HOSTVM is a virtualization platform based on Ovirt. For the purposes of improving UI languages, can you please provide us with account details for Zanata ( https://zanata.ovirt.org/)? If any additional information is needed, just let me know. Thank you. Regards, Vladimir

3 5

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

26 Oct '22

1 0

URGENT HELP NEEDED!! Hosts are in non-operational state.
by eugene＠knorydev.com 26 Oct '22

26 Oct '22

Oct 25, 2022, 4:10:01 PM - Failed to connect Host <hostname> to Storage Pool <storage pool> Oct 25, 2022, 4:10:01 PM - Host <hostname> cannot access the Storage Domain(s) VM_Data attached to the <data center>. Setting Host state to Non-Operational. Oct 25, 2022, 4:10:01 PM - Host <hostname> reports about one of the Active Storage Domains as Problematic. Oct 25, 2022, 4:09:52 PM - Activation of host <hostname> initiated by <user>. Hi All, Today morning, noticed that my 1st and 2nd host is in non-operational status and saw that my storage pool isn't being mounted and whenever I try to press Activate under Management, the above error happens. I have multiple VM running and I can't bring it up if it goes down, and it is my production server for my company. Any advise on how to check on this or what logs to look & provide to resolve this? The person who deployed this setup is no longer in my company and I have no one else to seek help for this issue.

4 4

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 25 Oct '22

25 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