January 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

gerrit.ovirt.org upgrade
by Denis Volkov 01 Feb '22

01 Feb '22

Hello Gerrit.ovirt.org will be upgraded later today. Approximate start time is 4PM UTC. During the upgrade service will be shut down and so will not be available. -- Denis Volkov

3 10

oVirt 4.4.10 Async update #2
by Sandro Bonazzola 30 Jan '22

30 Jan '22

On January 26th 2022 the oVirt project released an async update to the following packages: - ovirt-engine 4.4.10.6 Fixing the following bugs: - [BZ 2044277 <https://bugzilla.redhat.com/show_bug.cgi?id=2044277>] - Replace ovirt-engine-extension-logger-log4j with internal ovirt-engine implementation Package ovirt-engine-extension-logger-log4j has been obsoleted and replaced by internal ovirt-engine implementation in oVirt Engine 4.4.10.6. During upgrade from previous oVirt versions to oVirt 4.4.10 ovirt-engine-extension-logger-log4j package is uninstalled if it was previously installed. If you used ovirt-engine-extension-logger-log4j in previous oVirt versions, you will need to manually remove existing ovirt-engine-extension-logger-log4j configuration files and configure the new feature of sending log records to remote syslog service according to the Administration Guide. Also after successful upgrade to oVirt 4.4.10 you can manually uninstall log4j12 package without breaking oVirt setup: $ dnf remove log4j12 - [BZ 2044257 <https://bugzilla.redhat.com/show_bug.cgi?id=2044257>] - Bump snmp4j library version to remove dependency on log4j oVirt Engine 4.4.10.6 is requiring snmp4j >= 3.6.4, which no longer depends on log4j library -- 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.*

3 2

github action for artifact collection
by Harel Braha 26 Jan '22

26 Jan '22

Hi, There is a new GitHub action created by Janos and Ales for creating zip files with artifacts[1]. It is required to use this action since it will ensure uniform naming conventions across all our projects. In addition, this naming will be necessary when testing patches with ost after fully integrating with Github. You can find examples of how this action can be used here[2]. [1]https://github.com/oVirt/upload-rpms-action [2]https://www.ovirt.org/develop/developer-guide/migrating_to_github.html

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.10.6)
by Martin Perina 26 Jan '22

26 Jan '22

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

1 0

how to UI/API certificates with a valid one (ex: let's encrypt) ? ( as open shift required one )
by Eric Tiquet 24 Jan '22

24 Jan '22

Hello community, Would like to use ovirt & openshift, a this might be trivial but I am juste blocked at 'step two'. (As openshift refuse to use the ovirt without valid certificates and the insecure workaround does'not work) I can't find any usefull information to setup the UI/API certificates. ( ex: there is no apache...) Could someone please point me to the correct tuto's or instruction ? With kind regards, Eric

3 2

Fwd: [CentOS-virt] qemu-kvm-core features moved to separate packages in CentOS 9 Stream
by Sandro Bonazzola 24 Jan '22

24 Jan '22

FYI ---------- Forwarded message --------- Da: Miroslav Rezanina <mrezanin(a)redhat.com> Date: lun 24 gen 2022 alle ore 12:25 Subject: [CentOS-virt] qemu-kvm-core features moved to separate packages in CentOS 9 Stream To: <centos-virt(a)centos.org> Hi all, There's currently MR [1] on review with changes making the packing layout more close to fedora. This change unfortunately causes users using qemu-kvm-core package (not qemu-kvm) to lose some functionality as some submodules will be moved to separate packages so anyone using these features has to install such package in addition to qemu-kvm-core package. This change won't affect qemu-kvm usage as this package will keep these packages as dependency. These changes are going to be submitted soon so anyone using CentOS 9 Streams qemu-kvm-core package should check whether the functionality is still provided by core package after the change or additional subpackage is needed. [1] https://gitlab.com/redhat/centos-stream/src/qemu-kvm/-/merge_requests/60 -- MIroslav Rezanina Virtualization Team - Maintainer _______________________________________________ CentOS-virt mailing list CentOS-virt(a)centos.org https://lists.centos.org/mailman/listinfo/centos-virt -- 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

ovirt new web hook: https://snyk.io/webhook/github/
by Sandro Bonazzola 24 Jan '22

24 Jan '22

Hi, I noticed today that all the repos in oVirt organization have a webhook to https://snyk.io/webhook/github/ which seems to be some security scanner. I couldn't find any reference about why we have such hook, can anybody explain why it's there? thanks -- 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.*

2 1

ovirt-engine git repository is going to be moved to GitHub on Friday Jan 21st
by Martin Perina 21 Jan '22

21 Jan '22

Hi, We are going to move ovirt-engine git repository from Gerrit <https://gerrit.ovirt.org/admin/repos/ovirt-engine> to GitHub <https://github.com/ovirt/ovirt-engine> this Friday Jan 21st. The mirroring from gerrit to github is going to be disabled at 10:00 CET and ovirt-engine repository on Gerrit <https://gerrit.ovirt.org/admin/repos/ovirt-engine> is going to be changed to read-only, so all open patches on gerrit will need to be converted to GitHub PRs by their owners. If you haven't worked with GitHub previously please check Working with oVirt on GitHub <https://www.ovirt.org/develop/dev-process/working-with-github.html>. Feel free to reply to this email if you have any additional questions or concerns. Thanks, Martin -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

1 1