June 2022 - Devel - oVirt List Archives

[VDSM] Started getting virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired
by Edward Haas 11 Jan '24

11 Jan '24

Hi, I have a VM which acts as an oVirt host with VDSM installed. I use it for testing without connecting it to Engine. Recently VDSM fails to come up and I see this error: Sep 26 17:58:18 localhost libvirtd: 2018-09-26 14:58:18.978+0000: 12176: error : virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired Any hint on how to generate or fetch a new certificate without the help of Engine? Thanks, Edy.

3 5

Error: Adding new Host to ovirt-engine
by Ahmad Khiet 14 Aug '23

14 Aug '23

Hi, Can't add new host to ovirt engine, because the following error: 2019-06-12 12:23:09,664 p=4134 u=engine | TASK [ovirt-host-deploy-facts : Set facts] ************************************* 2019-06-12 12:23:09,684 p=4134 u=engine | ok: [10.35.1.17] => { "ansible_facts": { "ansible_python_interpreter": "/usr/bin/python2", "host_deploy_vdsm_version": "4.40.0" }, "changed": false } 2019-06-12 12:23:09,697 p=4134 u=engine | TASK [ovirt-provider-ovn-driver : Install ovs] ********************************* 2019-06-12 12:23:09,726 p=4134 u=engine | fatal: [10.35.1.17]: FAILED! => {} MSG: The conditional check 'cluster_switch == "ovs" or (ovn_central is defined and ovn_central | ipaddr and ovn_engine_cluster_version is version_compare('4.2', '>='))' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller The error appears to be in '/home/engine/apps/engine/share/ovirt-engine/playbooks/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - block: - name: Install ovs ^ here 2019-06-12 12:23:09,728 p=4134 u=engine | PLAY RECAP ********************************************************************* 2019-06-12 12:23:09,728 p=4134 u=engine | 10.35.1.17 : ok=3 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 whats missing!? Thanks -- Ahmad Khiet Red Hat <https://www.redhat.com/> akhiet(a)redhat.com M: +972-54-6225629 <https://red.ht/sig>

7 10

github testing: merge with branch, or use PR HEAD?
by Yedidyah Bar David 17 Aug '22

17 Aug '22

Hi all, I was annoyed for some time now by the fact that when I used some github-CI-generated RPMs, with a git hash in their names, I could never find this git hash anywhere - not in my local git repo, nor in github. Why is it so? Because, if I got it right, the default for 'actions/checkout@v2' is to merge the PR HEAD with the branch HEAD. See e.g. [1]: HEAD is now at 7bbb40c9a Merge 026bb9c672bf46786dd6d16f4cbe0ecfa84c531d into 35e217936b5571e9657946b47333a563373047bb Meaning: my patch was 026bb9c, master was 35e2179, and the generated RPMs will have 7bbb40c9a, not to be found anywhere else. If you check the main PR page [3], you can find there '026bb9c', but not '7bbb40c9a'. (Even 026bb9c might require some effort, e.g. "didib force-pushed the add-hook-log-console branch 2 times, most recently from c90e658 to 66ebc88 yesterday". I guess this is the result of github discouraging force-pushes, in direct opposite of gerrit, which had a notion of different patchsets for a single change. I already ranted about this in the past, but that's not the subject of the current message). This is not just an annoyance, it's a real difference in semantics. In gerrit/jenkins days, IIRC most/all projects I worked on, ran CI testing/building on the pushed HEAD, and didn't touch it. Rebase, if at all, happened either explicitly, or at merge time. actions/checkout's default, to auto-merge, is probably meant to be more "careful" - to test what would happen if the code is merged. I agree this makes sense. But I personally think it's almost always ok to test on the pushed HEAD and not rebase/merge _implicitely_. What do you think? It should be easy to change, using [2]: - uses: actions/checkout@v2 with: ref: ${{ github.event.pull_request.head.sha }} No need to reach a complete consensus - can be decided upon per-project/repo. But if you disagree, I'd like to understand why. Thanks. Best regards, [1] https://github.com/oVirt/vdsm/runs/6881311961?check_suite_focus=true [2] https://github.com/marketplace/actions/checkout?version=v2.4.2#checkout-pul… [3] https://github.com/oVirt/vdsm/pull/249 -- Didi

6 16

oVirt website switching to 'main' branch
by Marc Dequènes (Duck) 27 Jun '22

27 Jun '22

Quack, Following Red Hat conscious language initiative we're switching the development branch to 'main' on the ovirt-site repository. This will happen on 2022-06-20 around 10:30-11:30 Japan time. If you encounter any problem after this date please contact me by mail or chat (duck on IRC). Regards. \_o<

2 4

Vdsm: New branch ovirt-4.5.1.z
by Milan Zamazal 17 Jun '22

17 Jun '22

Hi, Vdsm branch ovirt-4.5.1.z for 4.5.1 backports was created. Everything after v4.50.1.3 that should come to 4.5.1 must be backported to the new branch (generally only blockers and exceptions are allowed there). 4.5.2+ development continues on master. Regards, Milan

1 0

Re: [ovirt-users] Re: dnf update fails on ovirt node 4.5.0-2022052513
by Sandro Bonazzola 14 Jun '22

14 Jun '22

Il giorno mar 14 giu 2022 alle ore 11:54 Igor Davidoff < igor.davidoff(a)cloudkleyer.de> ha scritto: > It looks like "..testing" repository is enabled on ISO-Image. The fresh > installed CentOS-oVirt-4.5.repo looks like this: > This is weird. I checked the content of the rpm: $ wget https://cbs.centos.org/kojifiles/packages/centos-release-ovirt45/8.7/1.el8s… $ rpmdev-extract centos-release-ovirt45-8.7-1.el8s.noarch.rpm $ less centos-release-ovirt45-8.7-1.el8s.noarch/etc/yum.repos.d/CentOS-oVirt-4.5.repo and it's disabled there. @Lev Veyde <lveyde(a)redhat.com> two tasks for you here: - can you check how the testing repo got enabled on a freshly installed system? - can you check why rpm size and dnf expected size are not matching? CC devel mailing list in case any other dev can help as well. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Projects missing safe dir config in COPR
by Michal Skrivanek 13 Jun '22

13 Jun '22

Hi, I scanned the current projects and AFAICT these are the active projects that don't have builds configured properly. Please add "git config --global --add safe.directory ..." to the COPR makefile Otherwise COPR build may not work at all or (worse) they build something wrong. Thanks, michal imgbased ioprocess mom ovirt-ansible-collection ovirt-cockpit-sso ovirt-engine-api-metamodel ovirt-engine-api-model ovirt-engine-wildfly ovirt-hosted-engine-ha ovirt-hosted-engine-setup ovirt-lldp-labeler ovirt-log-collector ovirt-node-ng ovirt-openvswitch ovirt-setup-lib ovirt-vmconsole python-ovirt-engine-sdk4

4 3

Please use RPM versions that are fine-enough
by Marcin Sobczyk 09 Jun '22

09 Jun '22

Hi All, I was analyzing a problematic situation with ovirt-web-ui build breaking OST for a day or two. It turned out the problem was about RPM versions not being fine enough. The project used only the date part in their RPM names, so the builds were named like this: 1.8.2-0.20220607.git703b8f7.fc35 1.8.2-0.20220607.git26ac92c.fc35 1.8.2-0.20220607.gitf519b50.fc35 The problem with this approach is that among these versions the one with the "biggest SHA" is considered to be the latest one, which is not always true. The solution in this case would be to use finer RPM versions that include at least the hour and the minute of the build (although I can see most projects use seconds too). I posted [1] to fix this in ovirt-web-ui, but I can see other projects suffer from this problem too (i.e. java-ovirt-engine-sdk4, ovirt-engine-ui-extensions) [2]. Please make sure that you use RPM versions that are fine-enough. Thanks, Marcin [1] https://github.com/oVirt/ovirt-web-ui/pull/1599 [2] https://copr.fedorainfracloud.org/coprs/ovirt/ovirt-master-snapshot/builds/

2 1

how to install Oracle Linux Virtualization Manager 4.4 on oracle Linux 8.2
by jateni.jote＠gmail.com 08 Jun '22

08 Jun '22

I'm attempting to install hosted engine 4.3 on Oracle Linux 7.9, but I've heard that 4.3 is no longer supported and that I won't be able to do so. When I deploy any problem SSL certificate, it fails to pass the Deployment.I need to install fresh installation on OLE 8.2 and 4.4 olvm, however I can't find an installation guide or runbook. Is there anyone who can give me with installation instructions? I've attached my installation run book. According to what I've posted, I require a 4.4 installation manual. yum install yum-utils yum-config-manager --enable ol7_latest yum install oracle-ovirt-release-el7 yum clean all yum-config-manager --enable repository yum-config-manager --disable ovirt-4.2 yum-config-manager --disable ovirt-4.2-extra yum install ovirt-hosted-engine-setup -y yum install ovirt-engine-appliance -y Thank you

4 3

ovirt-engine has been tagged (ovirt-engine-4.5.1)
by Martin Perina 01 Jun '22

01 Jun '22

ovirt-engine has been tagged (ovirt-engine-4.5.1) -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

1 0