April 2020 - Devel - oVirt List Archives

libvirt can't start in a non-TLS environment after host install
by Milan Zamazal 02 Apr '20

02 Apr '20

Hi, I've experienced a problem with host deploy and oVirt master last week in an environment with TLS disabled. When I install/reinstall a 4.4 host, it removes the following options from /etc/libvirt/libvirtd.conf: ca_file="/etc/pki/vdsm/certs/cacert.pem" cert_file="/etc/pki/vdsm/certs/vdsmcert.pem" key_file="/etc/pki/vdsm/keys/vdsmkey.pem" As a result, libvirt refuses to start, complaining about missing certificates and keys in their default locations. Does anybody who uses a non-TLS environment experience the same problem? Can it be related to the fact that we require libvirtd-tls service from the split libvirtd services now? (Yes, I know TLS should always be used, but that is a shared development environment where TLS is disabled for whatever reason.) Thanks, Milan

4 5

ovirt-engine has been re-tagged (ovirt-engine-4.4.0_beta2)
by Tal Nisan 02 Apr '20

02 Apr '20

Note: this a retag, the former ovirt-engine-4.4.0_beta2 tag now points to the rebuild

1 0

Why is vdsm enabled by default?
by Yedidyah Bar David 02 Apr '20

02 Apr '20

If I do e.g.: 1. Install CentOS 2. yum install ovirt-releaseSOMETHING 3. yum install vdsm Then reboot the machine, vdsm starts, and for this, it does all kinds of things to the system (such as configure various services using vdsm-tool etc.). Are we sure we want/need this? Why would we want vdsm configured/running at all at this stage, before being added to an engine? In particular, if (especially during development) we have a bug in this configuration process, and then fix it, it might not be enough to upgrade vdsm - the tooling will then also have to fix the changes done by the buggy previous version, or require a full machine reinstall. Thanks and best regards, -- Didi

7 13

Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 1548 - Failure!
by Yedidyah Bar David 02 Apr '20

02 Apr '20

On Wed, Apr 1, 2020 at 6:21 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1548/ Previous build 1547 passed!, after many months of failing, thanks to Evgeny's work in recent weeks. Above one failed. I think the root cause is that the engine tried to connect to vdsm right after successfully finishing ansible host-deploy, but failed. vdsm.log has: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1548… 2020-03-31 22:58:49,773-0400 ERROR (Reactor thread) [vds.dispatcher] uncaptured python exception, closing channel <yajsonrpc.betterAsyncore.Dispatcher connected ('::ffff:192.168.222.76', 46754, 0, 0) at 0x7f416c150a90> (<class 'ssl.SSLError'>:[X509] no certificate or crl found (_ssl.c:3771) [/usr/lib64/python3.6/asyncore.py|readwrite|110] [/usr/lib64/python3.6/asyncore.py|handle_write_event|442] [/usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py|handle_write|74] [/usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py|_delegate_call|168] [/usr/lib/python3.6/site-packages/vdsm/sslutils.py|handle_write|190] [/usr/lib/python3.6/site-packages/vdsm/sslutils.py|_handle_io|194] [/usr/lib/python3.6/site-packages/vdsm/sslutils.py|_set_up_socket|154]) (betterAsyncore:179) Not sure what might have caused this. Can anyone have a look? Thanks. > Build Number: 1548 > Build Status: Failure > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #1548 > [Galit Rosenthal] Fix the repo for suites that weren't moved to no reposync > > > > > ----------------- > Failed Tests: > ----------------- > No tests ran. -- Didi

5 13

what's up with ansible-runner-service-dev package?
by Fedor Gavrilov 01 Apr '20

01 Apr '20

Hi everyone, After I screwed up my dev environment beyond repair I have to set it up again and I see something I haven't last time (CentOS 7): $ sudo yum install ansible-runner-service-dev Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.hosting90.cz * centos-sclo-rh: mirror.hosting90.cz * centos-sclo-sclo: mirror.hosting90.cz * extras: mirror.hosting90.cz * ovirt-master-epel: mirror.hosting90.cz * ovirt-master-snapshot: ftp.nluug.nl * ovirt-master-snapshot-static: ftp.nluug.nl * updates: mirror.hosting90.cz No package ansible-runner-service-dev available. Maybe something's missing from my notes, but where did it go? Should I add some repo? Fedor

9 39

Re: ovirt-imageio error
by Nir Soffer 01 Apr '20

01 Apr '20

On Wed, Apr 1, 2020 at 3:25 PM Dana Elfassy <delfassy(a)redhat.com> wrote: Moving to deverl, since other people may have the same problem. We switched to ovirt-imageio 2.0.2 yesterday. The package should be available from ovirt repositories and for QE. > When I'm trying to install updates I'm getting the following error message: > "Depsolve Error occured: \n Problem: problem with installed package vdsm-4.40.10-1.el8.x86_64\n - package vdsm-4.40.10-1.el8.x86_64 > requires ovirt-imageio-daemon = 1.6.3, but none of the providers can be installed\n - package vdsm-4.40.9-1.el8.x86_64 requires ovirt-imageio-daemon = > 1.6.3, but none of the providers can be installed\n - cannot install both ovirt-imageio-daemon-2.0.2-0.el8.x86_64 and ovirt-imageio-daemon-1.6.3-0.20 > 2003041517.gitefb1267.el8.x86_64\n - cannot install both ovirt-imageio-daemon-2.0.2-0.el8.x86_64 and ovirt-imageio-daemon-1.6.3-0.el8.noarch\n - cann > ot install the best candidate for the job" > > The current version I have is > [root@dhcp-1-31 ~]# rpm -qa | grep "ovirt-imageio" > ovirt-imageio-common-1.6.3-0.202003041517.gitefb1267.el8.x86_64 > ovirt-imageio-daemon-1.6.3-0.202003041517.gitefb1267.el8.x86_64 > > I have tried to remove it (which requires installing ovirt-release-master again), and got the same error Is this centos or rhel system? If this is a rhel system the right place to discuss it is rhev-devel. For centos the packages are available here: https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el8/x86_64/ If you have ovirt-release-master package installed: yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm The package should be available. This is the way we test installation in the CI. Nir

1 1

pep8 & checkstyle are here again to bring an end to humanity
by Fedor Gavrilov 01 Apr '20

01 Apr '20

I can't compile the engine. Not sure should I laugh or cry. But you shouldn't be able to compile too. https://github.com/oVirt/ovirt-engine/commit/3d9d3b0aee17ff20d3303fd9f63297… is to blame, once I cut the line compilation is able to proceed. Not sure how it will go with ansible-runner-service yet... :) Fedor

4 3