- Users - oVirt List Archives

Help recovering cluster
by Joe Sherman 09 Mar '20

09 Mar '20

Hello all, New to the group, apologies for any poor information. I have a home lab with a single host ovirt setup. I actually don't think I ever set it up exactly right, the agent vm was never created, it was running on the host server. But it ran and I had a handful of vm's running on it successfully. I knew I had to rebuild it but was waiting for funds for extra hardware. Then the other day I came home and could no longer access the web portal. Could get to the login page but after entering my auth info it just hangs. I'm honestly not even sure where to start. Does anyone know any good troubleshooting docs? Or any idea what may be happening? I can see the VM images and such in the proper folders so I don't think I have .lost anything. But can't access any of the vm's now. Any help would be appreciated. Joe

3 5

What if anything can be done to improve small file performance with gluster?
by Jayme 08 Mar '20

08 Mar '20

I have 3 server HCI with Gluster replica 3 storage (10GBe and SSD disks). Small file performance inner-vm is pretty terrible compared to a similar spec'ed VM using NFS mount (10GBe network, SSD disk) VM with gluster storage: # dd if=/dev/zero of=test2.img bs=512 count=1000 oflag=dsync 1000+0 records in 1000+0 records out 512000 bytes (512 kB) copied, 53.9616 s, 9.5 kB/s VM with NFS: # dd if=/dev/zero of=test2.img bs=512 count=1000 oflag=dsync 1000+0 records in 1000+0 records out 512000 bytes (512 kB) copied, 2.20059 s, 233 kB/s This is a very big difference, 2 seconds to copy 1000 files on NFS VM VS 53 seconds on the other. Aside from enabling libgfapi is there anything I can tune on the gluster or VM side to improve small file performance? I have seen some guides by Redhat in regards to small file performance but I'm not sure what/if any of it applies to oVirt's implementation of gluster in HCI.

2 9

upgrade from 4.38 to 4.39
by eevans＠digitaldatatechs.com 08 Mar '20

08 Mar '20

I read documentation on upgrade procedures for minor upgrades. Before I begin, I wanted to know of any issues or special procedures I need to follow. Please advise. I appreciate any advice or guidance. Thank you. Eric

3 4

Getting Redhat Yum mirrors issues on some of my network subnet and not on the others
by Eugène Ngontang 06 Mar '20

06 Mar '20

Hi, This is not really an OVirt matter but I'll try my chance if anyone here has already had this kind of issue or could help I've two bare metal servers in two different network subnets with same release version of RHVH/Ovirt. I use an automated script to deploy VMs on both, and provision a docker repository file there on VMs. The issue I'm facing is when I'm trying to query `container-selinux` package. It works on VMs from one of my bare metal servers, and not from the other. first sever's VM: [root@cpu-node0 ~]# /bin/repoquery --show-duplicates --plugins > --disablerepo '' --enablerepo '' --qf > '%{name}|%{epoch}|%{version}|%{release}|%{arch}|%{repoid}' > container-selinux > container-selinux|2|2.107|1.el7_6|noarch|extras > container-selinux|2|2.107|3.el7|noarch|extras > [root@cpu-node0 ~]# Second server's VM : [root@cpu-node0 ~]# /bin/repoquery --show-duplicates --plugins > --disablerepo '' --enablerepo '' --qf > '%{name}|%{epoch}|%{version}|%{release}|%{arch}|%{repoid}' > container-selinux > Could not match packages: failure: repodata/repomd.xml from > docker-engine: [Errno 256] No more mirrors to try. > https://yum.dockerproject.org/repo/main/centos/7/repodata/repomd.xml: > [Errno 14] HTTPS Error 404 - Not Found > [root@cpu-node0 ~]# The yum repo configuration on both VMs running on each bare metal server: [root@cpu-node0 ~]# ll /etc/yum.repos.d/ > total 44 > -rw-r--r--. 1 root root 1664 5 sept. 13:05 CentOS-Base.repo > -rw-r--r--. 1 root root 1309 5 sept. 13:05 CentOS-CR.repo > -rw-r--r--. 1 root root 649 5 sept. 13:05 CentOS-Debuginfo.repo > -rw-r--r--. 1 root root 314 5 sept. 13:05 CentOS-fasttrack.repo > -rw-r--r--. 1 root root 630 5 sept. 13:05 CentOS-Media.repo > -rw-r--r--. 1 root root 1331 5 sept. 13:05 CentOS-Sources.repo > -rw-r--r--. 1 root root 6639 5 sept. 13:05 CentOS-Vault.repo > -rw-r--r--. 1 root root 369 2 mars 23:31 docker.repo > -rw-r--r--. 1 root root 1050 17 sept. 23:25 epel.repo > -rw-r--r--. 1 root root 1149 17 sept. 23:25 epel-testing.repo > [root@cpu-node0 ~]# docker.repo file content on both VMs : [root@cpu-node0 ~]# cat /etc/yum.repos.d/docker.repo > [docker-ce] > name=Docker-CE Repository > baseurl=https://download.docker.com/linux/centos/7/$basearch/stable > enabled=1 > gpgcheck=1 > keepcache=1 > gpgkey=https://download.docker.com/linux/centos/gpg > > [docker-engine] > name=Docker-Engine Repository > baseurl=https://yum.dockerproject.org/repo/main/centos/7 > enabled=1 > gpgcheck=1 > keepcache=1 > gpgkey=https://yum.dockerproject.org/gpg > [root@cpu-node0 ~]# Repo list on the first VM : [root@cpu-node0 ~]# yum repolist > id du dépôt > nom du dépôt > statut > base/7/x86_64 > CentOS-7 - Base > 10 097 > docker-ce/x86_64 > Docker-CE Repository > 68 > !docker-engine > Docker-Engine Repository > 110 > epel/x86_64 > Extra Packages for Enterprise Linux 7 - x86_64 > 13 199 > extras/7/x86_64 > CentOS-7 - Extras > 323 > updates/7/x86_64 > CentOS-7 - Updates > 1 478 > repolist: 25 275 > [root@cpu-node0 ~]# Yum repo list on the second VM: [root@cpu-node0 ~]# yum repolist > https://yum.dockerproject.org/repo/main/centos/7/repodata/repomd.xml: > [Errno 14] HTTPS Error 404 - Not Found > Essai d'un autre miroir. > To address this issue please refer to the below wiki article > > https://wiki.centos.org/yum-errors > > If above article doesn't help to resolve this issue please use > https://bugs.centos.org/. > > docker-ce/x86_64/primary_db > > | 40 kB 00:00:05 > https://yum.dockerproject.org/repo/main/centos/7/repodata/repomd.xml: > [Errno 14] HTTPS Error 404 - Not Found > Essai d'un autre miroir. > id du dépôt > nom du dépôt > statut > base/7/x86_64 > CentOS-7 - Base > 10 097 > docker-ce/x86_64 > Docker-CE Repository > 68 > docker-engine > Docker-Engine Repository > 0 > epel/x86_64 > Extra Packages for Enterprise Linux 7 - x86_64 > 13 199 > extras/7/x86_64 > CentOS-7 - Extras > 323 > updates/7/x86_64 > CentOS-7 - Updates > 1 478 > repolist: 25 165 > [root@cpu-node0 ~]# I also get the message below when trying to curl the repository URL : > > [root@cpu-node0 ~]#curl > https://yum.dockerproject.org/repo/main/centos/7/repodata/repomd.xml > > <!doctype html> > > <html lang="en"> > > <head></head> > > <body> > > <h1>Notice: Shutting down dockerproject.org APT and YUM repos > 2020-03-31</h1> > > <p>Docker will be shutting down the deprecated APT and YUM > repositories hosted at "dockerproject.org" and "dockerproject.com" on the > 31st of March 2020.</p> > > <p>We noticed that this project is referencing one of these > repositories, and recommend updating to use the "download.docker.com" > repository to prevent disruption.</p> > > <p>More info: > https://www.docker.com/blog/changes-dockerproject-org-apt-yum-repositories/ > </p> > > </body> > > </html> Looks like docker does not want anyone to use this repo anymore. Probably they started issuing the error from today I guess. Of course the two VMs do not have `subscription-manager` package installed, neither subscription attached, they don't need actually in our context, but why is there a mirror issue on one VM and not on the other, whose OS and system configuration is the same on both, except that they are locate in two different networks? Can someone have any idea of why this happens please? Kind regards, Eugène NG -- LesCDN <http://lescdn.com> engontang(a)lescdn.com ------------------------------------------------------------ *Aux hommes il faut un chef, et au* * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!*

2 4

qcow on LVM‽ Why‽
by Thorsten Glaser 06 Mar '20

06 Mar '20

Hi *, I’m a bit frustrated, so please excuse any harshness in this mail. Whose idea was it to place qcow on logical volumes anyway? I was shrinking a hard disc: first the filesystems inside the VM, then the partitions inside the VM, then the LV… then I wanted to convert the LV to a compressed qcow2 file for transport, and it told me that the source is corrupted. Huh? I had already wondered why I was unable to inspect the LV on the host the usual way (kpartx -v -a /dev/VG/LV after finding out, with “virsh --readonly -c qemu:///system domblklist VM_NAME”, which LV is the right one). Turns out that ovirt stores qcow on LVs instead of raw images ☹ Well, vgcfgrestore to my rescue: - vgcfgrestore -l VG_NAME - vgcfgrestore -f /etc/… VG_NAME The image was still marked as corrupted, but exported fine. I could not write it back to the LV as preallocated, which seems to be what ovirt does, because qemu-img doesn’t wish to do that when the target is a special device (not a regular file). Meh. Does ovirt handle raw images on LV, and if so, how can we enable this for new VMs? If not, whyever the hell not? And whose “great” idea was this anyway? Thanks in advance, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg ********** Mit der tarent Academy bieten wir auch Trainings und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an. Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt. **********

4 5

The problem with create VM
by garcialiang.anne＠gmail.com 06 Mar '20

06 Mar '20

I began use ovirt recently. I tried create one VM on ovirt plateform. But I nerver start VM. I had the message like: L'hôte xxxxx.xxxx.fr n'a pas pu satisfaire le filtre Network de type interne car réseau d'affichage ${DisplayNames} manquant. I don't understand where is the problem. Could you help me? Thanks Anne

5 4

Windows deployment
by eevans＠digitaldatatechs.com 06 Mar '20

06 Mar '20

I have a Windows Deployment server that works with Hyper-V. I am tryng to see if it will bare metal provision to Ovirt. I have the necessary drivers loaded and initially it gets an IP and starts the installation. When it comes to the screen starting setup, I get an IP error. I have included a screenshot. Has anyone see this before? I also considered provisioning from Foreman but I would rather use what I have instead of recreating the entire installation. Any help would be appreciated. Here is a link to the actual error: ftp://ftp.digitaldatatechs.com/pub/Windows%20Provision.jpg

3 4

subnets
by eevans＠digitaldatatechs.com 05 Mar '20

05 Mar '20

I have a network in place with several subnets, one for iscsi and one for virtual pbx and VoIP phones. I use the iscsi in Ovirt, but I cannot get Ovirt to recognize and use the physical vlan 3 network for phones. If I add it and the subnet, Ovirt will make give it an IP, but it's an isolated network with no connectivity to the other vm's or the Internet. I have read several topics on this but I can't get it to work properly. Any help would be appreciated. Thanks.

3 5

Debian 10 template - cloud init not working
by Sakari Poussa 05 Mar '20

05 Mar '20

Hi, I have tried centos7 & 8, debian 9 and ubuntu 18.04 template based VMs with cloud init (Initial run/use cloud init) and they all work as expected. However, the debian 10 template based VM seems *not* to execute the cloud init at all. It boots but hostname is not set and users / password are not set. You can't log in since there is no users and passwords/keys. Is this a known issue? Or am I missing something? The templates are from ovirt-image-repository storage domain. I have also created newer debian 10.3.0 template via ovirt.image-template ansible role. Results are the same. I am running ovirt 4.4-pre. Thanks, Sakari

2 3

[ANN] oVirt 4.3.9 Third Release Candidate is now available for testing
by Lev Veyde 05 Mar '20

05 Mar '20

The oVirt Project is pleased to announce the availability of the oVirt 4.3.9 Third Release Candidate for testing, as of March 5th, 2020. This update is a release candidate of the ninth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available Additional Resources: * Read more about the oVirt 4.3.9 release highlights: http://www.ovirt.org/release/4.3.9/ * 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.3.9/ [2] http://resources.ovirt.org/pub/ovirt-4.3-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