- Users - oVirt List Archives

[ANN] oVirt 4.4.5 Eighth Release Candidate is now available for testing
by Lev Veyde 04 Mar '21

04 Mar '21

oVirt 4.4.5 Eighth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 Eighth Release Candidate for testing, as of March 4th, 2021. This update is the fifth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.5 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.5 release highlights: http://www.ovirt.org/release/4.4.5/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.5/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- 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

EL7 Host support in 4.4.x
by Vrgotic, Marko 04 Mar '21

04 Mar '21

Hi oVirt, After reviewing the https://access.redhat.com/articles/973163 I wonder is it possible to have a Host running EL7, in oVirt 4.4 to support ability to still run OSs like Win 2008R2, or is it a hard NO? ----- 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.

1 0

Manager login error
by Moses Mbugua 04 Mar '21

04 Mar '21

have tried to resolve this error " Keystore was tampered with, or password was incorrect" but am not able. This has rendered my virtualization manager unusable. This means I can access one of my hosts which has vms l down. any one who has ever faced similar issues? i rarely access it thus mostly an update issue since i can't remember changing anything .redhat virtualization version 4.2.8.9-0.1.el7ev. able to help? ping me we discuss

3 5

What happens in loss of network scenarios?
by David White 04 Mar '21

04 Mar '21

I tested oVirt (4.3? I can't remember) last fall on a single host (hyperconverged). Now, I'm getting ready to deploy to a 3 physical node (possibly 4) hyperconverged cluster, and I guess I'll go ahead and go with 4.4. Although Red Hat's recent shift of CentOS 8 to the Stream model, as well as the announcement that RHV is going away makes me nervous. I really don't see any other virtualization software doing quite the same stuff as oVirt at the moment. One of my questions is around the back end out-of-band network for data replication. What happens if all 3 servers are healthy and the normal network is fine for serving traffic to the VM consumers, but the switching network for data replication goes down? Is it possible to configure oVirt to "fail over" to the front-end network?I'm also wondering if its possible to do away with a switch all together, and just link the physical hosts together directly (like a cross-over cable) for the data replication. I'm also wondering what would happen in the following scenario: - All 3 servers are healthy - The out-of-band data replication network is healthy - 1 or 2 of the servers suddenly lost network connectivity on the front-end network What then? Would everything just keep working, and network traffic be forced to go out the healthy interface(s) on the remaining hosts? Sent with ProtonMail Secure Email.

1 0

Cloud-init confusion
by Shantur Rathore 04 Mar '21

04 Mar '21

Hi Users, I am new to oVirt and having some confusion with cloud-init. I have a VM which supports Cloud Init and when I enable Cloud Init under Initial boot settings of VM, the cloud-init config disk isn't attached to the VM. If I use Run-Once and enable Cloud-Init the config disk is attached to the VM and works as expected. Is cloud-init only supposed to work with Run-Once or am I missing something? Thanks in advance. Shantur

2 2

Template backing disks on different storage
by Shantur Rathore 04 Mar '21

04 Mar '21

Hi Users, I am evaluating oVirt coming from a VMware background. I have a test cluster with 6 machines running oVirt Node providing compute + gluster services. There are 2 storage domains 1. Gluster backed 2. iSCSI SAN I use iSCSI SAN for the templates (backing disks) and would like to use Gluster storage domain for template instances. In VMware I could create a linked clone on one storage linked to a template on another. Is this possible with oVirt? via GUI or API? Thanks in advance, Shantur

1 0

node IPs can't be pingued on a fresh 4.4.4 installation
by Nathanaël Blanchet 04 Mar '21

04 Mar '21

Hello On a fresh installation of a 4.4.4 node, I configured network so as to get dhcp delivered IP for gluster and migration services. After IPs have been delivered, they can't be pingued and vms migrations fail. All work as expected once I reactivate each bridge with nmcli/nmtui... This bug is present on each new node installation. -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 1

Right Glusterfs Config on HA Server
by Marcel d'Heureuse 04 Mar '21

04 Mar '21

Hi Guys or Girls, I have a problem in a productive system. We use three Servers which have a Raid 5 with four Harddrives SATA 8 TB 7200 rpms. The Systems are interconnected for Glusterfs with 1 GB/s. The Network Load between all three servers are between 5 and 8 % of the network. The Glusterfs has a separate VLAN which complete isolated from other networks. Find attached a small drawing. On that server we rum as HA and there are 8 VMs installed. Most of the VMs working well but if there is high load on the system some of the VM can't write the Data in a "good" speed on the disks. The Glusterfs is configured as Replica on the Raid5 disk which is as Jbob in Glusterfs defined. If i take a look on the iostats i can see that the Harddisk have round 50 open connections some of the glusterfs and a lot of the vms. In side the VMs i can see long iowaiting times from 300 up to 600 ms. With is on case of a Posgresql database very long. Should we configure the Raid5 controller out that the controller only should 4 disks with 8 TB and Glusterfs should connect directly to the /dev/sd[b-e]? What do you think? Will SSD HDD will help on performance but the same config with Raid5 and Jbod could be the bigger problem. Thanks Marcel

2 1

4.5 compatibility cluster
by Nathanaël Blanchet 03 Mar '21

03 Mar '21

2 1

Newly uploaded disk stuck in 'Finalizing Failure' status
by n.bouwhuis＠speakup.nl 03 Mar '21

03 Mar '21

Hey there, A few days ago, I tried to create a new template using one of the Ansible playbooks I frequently use. This time, the upload of the disk failed, possibly due to an unrelated error. The disk is now stuck in Ovirt. It has the status 'Finalizing Failure' and it's locked, thus I cannot remove it. Trying to unlock the disk with the 'unlock_entity.sh' helper utility does not help. The utility says it has completed it task successfully but the disk remains in this state. I decided to check the logs, and see that `engine.log` gets spammed with these lines every 10 seconds ``` 2021-03-03 09:05:38,335Z WARN [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-45) [redacted] Failed to stop image transfer session. Ticket does not exist for image '[disk uuid]' ``` How can I force Ovirt to remove this disk? I presume the upload failure itself is a different error, possibly related to our setup. Hence this is not the topic of this thread. I just want to know how I can remove these disks. Thanks, Nick

3 3