- Users - oVirt List Archives

4.4.5 Release timeline
by David White 15 Mar '21

15 Mar '21

Hello, Reviewing https://ovirt.org/release/4.4.5/, I see that the target release date was set to March 9. However, glancing at https://bugzilla.redhat.com/buglist.cgi?quicksearch=ALL%20target_milestone%…, I see a number of outstanding open tickets. Do the maintainers anticipate that 4.4.5 will be released soon? I'm trying to decide if I should wait for 4.4.5 to be released, or if I should go with 4.4.4, as I am getting ready to do a fresh install for a 3-node hyperconverged cluster, and need to begin setting up VMs and configuring things very soon. Sent with ProtonMail Secure Email.

2 1

RHV is allocating more space than it should
by Łukasz Kołaciński 15 Mar '21

15 Mar '21

Hello, I have a question about restoring virtual machines. Why is ovirt/rhv allocating ~10% more space than it should. For example, we have a 10 GB disk, and after restore the size is 11 GB. This only happens with a SPARSE disk type on ISCSI storage. Is it a normal behavior? Regards, Łukasz Kołaciński Junior Java Developer e-mail: l.kolacinski(a)storware.eu<mailto:l.kolacinski@storware.eu> <mailto:m.helbert@storware.eu> [STORWARE]<http://www.storware.eu/> ul. Leszno 8/44 01-192 Warszawa www.storware.eu <https://www.storware.eu/> [facebook]<https://www.facebook.com/storware> [twitter]<https://twitter.com/storware> [linkedin]<https://www.linkedin.com/company/storware> [Storware_Stopka_09]<https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa 000510131 , NIP 5213672602. Wiadomość ta jest przeznaczona jedynie dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie tej wiadomości z wszelkich komputerów. This message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you have received this message in error, please contact the sender and remove the material from all of your computer systems.

1 0

Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue
by Marko Vrgotic 15 Mar '21

15 Mar '21

Hi Didi, Have you received all logs I sent? I did send all requested. Just wondering if you were able to find something. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Date: Monday, 8 March 2021 at 15:55 To: Yedidyah Bar David <didi(a)redhat.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue The broker log, these lines are pretty much repeating: MainThread::WARNING::2021-03-03 09:19:12,086::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' MainThread::INFO::2021-03-03 09:19:12,829::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started MainThread::INFO::2021-03-03 09:19:12,829::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/sub monitors MainThread::INFO::2021-03-03 09:19:12,829::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load MainThread::INFO::2021-03-03 09:19:12,834::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network MainThread::INFO::2021-03-03 09:19:12,836::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain MainThread::INFO::2021-03-03 09:19:12,836::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Finished loading submonitors MainThread::WARNING::2021-03-03 09:19:12,836::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' MainThread::INFO::2021-03-03 09:19:13,574::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started MainThread::INFO::2021-03-03 09:19:13,575::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors MainThread::INFO::2021-03-03 09:19:13,575::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load MainThread::INFO::2021-03-03 09:19:13,577::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine MainThread::INFO::2021-03-03 09:19:13,578::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Date: Monday, 8 March 2021 at 15:34 To: Yedidyah Bar David <didi(a)redhat.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue Hi Didi, Please find the attached logs from Host and Engine. Host ovirt-sj-02 HE Undeploy 2021-03-08 14:15:52 till 2021-03-08 14:18:24 Host ovirt-sj-02 HE Deploy 2021-03-08 14:20:51 till 2021-03-08 14:23:22 I do see errors in the agent and broker and vdsm, but I do not see why it happened. Thank you for helping, let me know if any additional files are needed. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Yedidyah Bar David <didi(a)redhat.com> Date: Monday, 8 March 2021 at 09:25 To: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue ***CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender!!!*** Hi, On Mon, Mar 8, 2021 at 10:13 AM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > I cannot find the reason why the re-Deployment on this Hosts fails, as it was already deployed on it before. > > No errors, found int the deployment, but it seems half done, based on messages I sent in previous email. Please check/share all relevant logs. Thanks. Can be all of /var/log from engine and hosts, and at least: /var/log/ovirt-engine/engine.log /var/log/vdsm/* /var/log/ovirt-hosted-engine-ha/* Best regards, -- Didi

1 0

doubt about CentOS 8.3 hypervisor and ansible version
by Gianluca Cecchi 15 Mar '21

15 Mar '21

Hello, I have a CentOS 8.3 + updates host in a 4.4.4 environment. The web admin gui shows that it needs to upgrade to some packages. The check event in web admin gui says: Check for available updates on host ov300 was completed successfully with message 'nss.x86_64, grub2-tools-efi.x86_64, bind-utils.x86_64, dracut-network.x86_64, libvirt-daemon-driver-qemu.x86_64, qemu-kvm-common.x86_64, libvirt-daemon-driver-storage-scsi.x86_64, libvirt-daemon-driver-nodedev.x86_64, nss-sysinit.x86_64, grub2-tools-minimal.x86_64 and 74 others. To see all packages check engine.log.'. If I go to engine in file ovirt-host-mgmt-ansible-check-.....log I get: "yum_result" : "bind-export-libs.x86_64\nbind-libs.x86_64\nbind-libs-lite.x86_64\nbind-lic ense.noarch\nbind-utils.x86_64\nbpftool.x86_64\nbuildah.x86_64\ncockpit-podman.noarch\nconmon.x86_64 \ncontainer-selinux.noarch\ncontainernetworking-plugins.x86_64\ncontainers-common.x86_64\ncriu.x86_6 4\ndbxtool.x86_64\ndracut.x86_64\ndracut-config-rescue.x86_64\ndracut-network.x86_64\ndracut-squash. x86_64\nfuse-overlayfs.x86_64\ngrub2-common.noarch\ngrub2-efi-x64.x86_64\ngrub2-tools.x86_64\ngrub2- tools-extra.x86_64\ngrub2-tools-minimal.x86_64\nkernel.x86_64\nkernel-core.x86_64\nkernel-modules.x8 6_64\nkernel-tools.x86_64\nkernel-tools-libs.x86_64\nkmod-megaraid_sas.x86_64\nlibtpms.x86_64\nlibvi rt-admin.x86_64\nlibvirt-bash-completion.x86_64\nlibvirt-client.x86_64\nlibvirt-daemon.x86_64\nlibvi rt-daemon-config-network.x86_64\nlibvirt-daemon-config-nwfilter.x86_64\nlibvirt-daemon-driver-interf ace.x86_64\nlibvirt-daemon-driver-network.x86_64\nlibvirt-daemon-driver-nodedev.x86_64\nlibvirt-daem on-driver-nwfilter.x86_64\nlibvirt-daemon-driver-qemu.x86_64\nlibvirt-daemon-driver-secret.x86_64\nl ibvirt-daemon-driver-storage.x86_64\nlibvirt-daemon-driver-storage-core.x86_64\nlibvirt-daemon-drive r-storage-disk.x86_64\nlibvirt-daemon-driver-storage-gluster.x86_64\nlibvirt-daemon-driver-storage-i scsi.x86_64\nlibvirt-daemon-driver-storage-iscsi-direct.x86_64\nlibvirt-daemon-driver-storage-logica l.x86_64\nlibvirt-daemon-driver-storage-mpath.x86_64\nlibvirt-daemon-driver-storage-rbd.x86_64\nlibv irt-daemon-driver-storage-scsi.x86_64\nlibvirt-daemon-kvm.x86_64\nlibvirt-libs.x86_64\nlibvirt-lock- sanlock.x86_64\nmicrocode_ctl.x86_64\nnss.x86_64\nnss-softokn.x86_64\nnss-softokn-freebl.x86_64\nnss -sysinit.x86_64\nnss-tools.x86_64\nnss-util.x86_64\npodman.x86_64\npodman-catatonit.x86_64\npython3- bind.noarch\npython3-libvirt.x86_64\npython3-perf.x86_64\nqemu-img.x86_64\nqemu-kvm.x86_64\nqemu-kvm -block-curl.x86_64\nqemu-kvm-block-gluster.x86_64\nqemu-kvm-block-iscsi.x86_64\nqemu-kvm-block-rbd.x 86_64\nqemu-kvm-block-ssh.x86_64\nqemu-kvm-common.x86_64\nqemu-kvm-core.x86_64\nrunc.x86_64\nslirp4n etns.x86_64\nswtpm.x86_64\nswtpm-libs.x86_64\nswtpm-tools.x86_64\nvirt-v2v.x86_64\ngrub2-tools.x86_64\ngrub2-tools-efi.x86_64\ngrub2-tools-extra.x86_64\ngrub2-tools-minimal.x86_64\n" I upgrade the host from the gui (without restart). So far so good. But now if I connect to the host I get: [root@ov300 ~]# yum update Last metadata expiration check: 0:05:42 ago on Mon 15 Mar 2021 09:36:31 AM CET. Dependencies resolved. ==================================================================================================== Package Architecture Version Repository Size ==================================================================================================== Upgrading: ansible noarch 2.9.18-2.el8 ovirt-4.4-centos-ovirt44 17 M Transaction Summary ==================================================================================================== Upgrade 1 Package Total size: 17 M Is this ok [y/N]: Current version: [root@ov300 ~]# rpm -q ansible ansible-2.9.16-2.el8.noarch [root@ov300 ~]# Any suggestions on what is the right thing to do? Why the ansible package was not updated and why it was not put into a sort of black list if it is correct to do so? Thanks, Gianluca

1 0

Unsure where to post this
by Jason Alexander Hazen Valliant-Saunders 14 Mar '21

14 Mar '21

Hello Ovirt Users; I'm attempting to Deploy Ovirt-engine and having a rough go of it with 4.4.4 I've installed oVirt 4.4.4 onto a USB key (64GB) on an HP DL 380 G8, Storage is via NFS and Free NAS (30TB) over 10GB Ethernet (Chelsio) - I had to install drivers using these commands: Chelsio T320 10GB/s Card Mods 1. rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org 2. yum install https://www.elrepo.org/elrepo-release-8.el8.elrepo.noarch.rpm 3. yum install kmod-cxgb3 for some reason I've had services failing on my Newly installed Ovirt Node The oVirt Imiage IO Deamon refuses to start: I believe this is the reason I cannot run "hosted-engine --deploy" (fails towards the end) For a bit it was the VSDM service now it's the image IO Deamon. intuition tells me that maybe Ovirt does not play well with Chelsio 10GB cards?? As always any help is appreciated. Regards, Hazen

2 1

login to self hosted endine during deployment
by jost.rakovec＠snt.si 14 Mar '21

14 Mar '21

Is it possible to ssh or any other way connect to self hosted engine during deployment, since anssible is using ssh? I would like to check something? something like this: ssh -C -o ControlMaster=auto -o ControlPersist=60s -o User="root" -o ConnectTimeout=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ControlPath=/root/.ansible/cp/45a9ce675c -tt olvman.example.local /bin/sh -c Thanks

3 3

Gluster volume engine stuck in healing with 1 unsynched entry & HostedEngine paused
by souvaliotimaria＠mail.com 11 Mar '21

11 Mar '21

Hello everyone, Any help would be greatly appreciated in the following problem. In my lab, the day before yesterday, we had power issues, with a UPS going off-line and following the power outage of the NFS/DNS server I have set up to serve ovirt with isos and as a DNS server (our other DNS servers are located as VMs within the oVirt environment). We found a broadcast storm on the switch (due to a faulty NIC on the aformentioned UPS) that the ovirt nodes are connected and later on had to re-establish several of the virtual connections as well. The above led to one of the hosts becoming NonResponsive, two machines becoming unresponsive and three VMs shuting down. The oVirt environment, version 4.3.5.2, is a replica 2 + arbiter 1 environment and runs GlusterFS with the recommended volumes of data, engine and vmstore. So far, the times there was some kind of a problem, usually oVirt was able to solve it by its own. This time, however, after we recovered from the above state, the volumes of data and vmstore successfully healing , the volume engine became stuck to the healing process (Up, unsynched entries, needs healing), and from the web GUI I see that the VM HostedEngine is paused due to a storage I/O error while the output of virsh list --all command shows that the HostedEngine is running.. How is that happening? I tried to manually trigger the healing process for the volume but nothing with gluster volume heal engine The command gluster volume heal engine info shows the following [root@ov-no3 ~]# gluster volume heal engine info Brick ov-no1.ariadne-t.local:/gluster_bricks/engine/engine Status: Connected Number of entries: 0 Brick ov-no2.ariadne-t.local:/gluster_bricks/engine/engine /80f6e393-9718-4738-a14a-64cf43c3d8c2/images/d5de54b6-9f8e-4fba-819b-ebf6780757d2/a48555f4-be23-4467-8a54-400ae7baf9d7 Status: Connected Number of entries: 1 Brick ov-no3.ariadne-t.local:/gluster_bricks/engine/engine /80f6e393-9718-4738-a14a-64cf43c3d8c2/images/d5de54b6-9f8e-4fba-819b-ebf6780757d2/a48555f4-be23-4467-8a54-400ae7baf9d7 Status: Connected Number of entries: 1 This morning I came upon this Reddit post https://www.reddit.com/r/gluster/comments/fl3yb7/entries_stuck_in_heal_pend… where it seems that after a graceful reboot one of the ovirt hosts, the gluster came back online after it completed the appropriate healing processes. The thing is from what I have read that when there are unsynched entries in the gluster a host cannot be put into maintenance mode so that it can be rebooted, correct? Should I try to restart the glusterd service. Could someone tell me what I should do? Thank you all for your time and help, Maria Souvalioti

5 21

VM CPU Pinning
by lavi.buchnik＠exlibrisgroup.com 11 Mar '21

11 Mar '21

Hi, When trying to pin a VM CPU's to Physical CPU's, I'm getting this error in case the number of physical CPU slots are > 35 (e.g. 40): Error attempting to pin CPUs. Full error: Fault reason is "Operation Failed". Fault detail is "[size must be between 0 and 4000, Attribute: vmStatic.cpuPinning]". HTTP response code is "400". HTTP response message is "Bad Request". It is working for me up to 35 physical CPU's. but above it, I get that error. Can you please tell what this error means and how to overcome it? Version we are using is: 4.3.6.6-1.0.9.el7 Thanks, Lavi

2 4

Update Package Conflict
by penguin pages 10 Mar '21

10 Mar '21

Fresh install of minimal CentOS8 Then deploy: - EPEL - Add ovirt repo https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm Install all nodes: - cockpit-ovirt-dashboard - gluster-ansible-roles - vdsm-gluster - ovirt-host - ovirt-ansible-roles - ovirt-ansible-infra Install on "first node of cluster" - ovirt-engine-appliance Now each node is stuck with same package conflict error: (and this blocks GUI "upgrades") [root@medusa ~]# yum update Last metadata expiration check: 0:55:35 ago on Wed 10 Mar 2021 08:14:22 AM EST. Error: Problem 1: package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-bridge-238.1-1.el8.x86_64 conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package ovirt-host-4.4.1-4.el8.x86_64 - cannot install the best update candidate for package cockpit-bridge-217-1.el8.x86_64 Problem 2: problem with installed package ovirt-host-4.4.1-4.el8.x86_64 - package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-system-238.1-1.el8.noarch obsoletes cockpit-dashboard provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package cockpit-dashboard-217-1.el8.noarch Problem 3: package ovirt-hosted-engine-setup-2.4.9-1.el8.noarch requires ovirt-host >= 4.4.0, but none of the providers can be installed - package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-1.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-2.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-3.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-system-238.1-1.el8.noarch obsoletes cockpit-dashboard provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package ovirt-hosted-engine-setup-2.4.9-1.el8.noarch - cannot install the best update candidate for package cockpit-system-217-1.el8.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@medusa ~]# yum update --allowerasing Last metadata expiration check: 0:55:56 ago on Wed 10 Mar 2021 08:14:22 AM EST. Dependencies resolved. ========================================================================================================================================================================================================================================= Package Architecture Version Repository Size ========================================================================================================================================================================================================================================= Upgrading: cockpit-bridge x86_64 238.1-1.el8 baseos 535 k cockpit-system noarch 238.1-1.el8 baseos 3.4 M replacing cockpit-dashboard.noarch 217-1.el8 Removing dependent packages: cockpit-ovirt-dashboard noarch 0.14.17-1.el8 @ovirt-4.4 16 M ovirt-host x86_64 4.4.1-4.el8 @ovirt-4.4 11 k ovirt-hosted-engine-setup noarch 2.4.9-1.el8 @ovirt-4.4 1.3 M Transaction Summary ========================================================================================================================================================================================================================================= Upgrade 2 Packages Remove 3 Packages ## Initially I assumed this was a path I was taking that was not standard.. but now I think this is some ovirt vs CentOS package repo issue. Any work arounds or root cause to fix this from repo conflict?

3 6

How to replace a failed oVirt Hyperconverged Host
by Ramon Sierra 10 Mar '21

10 Mar '21

Hi, We have a three hosts hyperconverged ovirt setup. A few weeks ago one of the hosts failed and we lost a RAID5 array on it. We removed it from the cluster and repaired. We are trying to setup and add it back to the cluster but we are not clear on how to proceed. There is a replica 2 with 1 arbiter Gluster setup on the cluster and I have no idea on how to recreate the LVM partitions, gluster bricks, and then add it to the cluster in order to start the healing process. Any help on how to proceed with this scenario will be very welcome. Ramon

2 1