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

oVirt 4.4.10 Async update #1
by Sandro Bonazzola 21 Jan '22

21 Jan '22

On January 21st 2022 the oVirt project released an async update to the following packages: ovirt-engine 4.4.10.5 Fixing the following bugs: - [BZ 1854038 <https://bugzilla.redhat.com/1854038>] - Download or upload disk (SDK) fails due to 'Timed out waiting for transfer XXX to finalize' - [BZ 2013430 <https://bugzilla.redhat.com/2013430>] - oVirt 4.4. FIPS install leaves UUID blank in grub after setting kernel option - [BZ 2037216 <https://bugzilla.redhat.com/show_bug.cgi?id=2037216>] - VM imported from configuration is stuck in WaitForLaunch once removed quickly after power-off -- 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-engine has been tagged (ovirt-engine-4.4.10.5)
by Martin Perina 21 Jan '22

21 Jan '22

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

1 0

Documenting release process for upcoming 4.5.0
by Sandro Bonazzola 20 Jan '22

20 Jan '22

Hi, I tried to summarize the release process for the upcoming 4.5.0 releases here: https://github.com/oVirt/ovirt-site/pull/2692 Feedback, improvements, suggestions, comments are welcome. -- 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

SELinux broken - ?
by lejeczek 19 Jan '22

19 Jan '22

Hi guys I had to remove as a work-around: -> $ dnf remove openvswitch Dependencies resolved. =============================================================================================== Package Arch Version Repository Size =============================================================================================== Removing: ovirt-openvswitch noarch 2.15-2.el9 @ovirt-master-centos-stream-ovirt45-testing 0 Removing unused dependencies: openvswitch-selinux-extra-policy noarch 1.0-30.el9s @ovirt-master-centos-stream-nfv-openvswitch2-testing 25 k openvswitch2.15 x86_64 2.15.0-56.el9s @ovirt-master-centos-stream-nfv-openvswitch2-testing 50 M Transaction Summary for its modules brake few things, eg.: -> $ rpm -iv --force ipa-selinux-4.9.8-1.el9.noarch.rpm Verifying packages... Preparing packages... ipa-selinux-4.9.8-1.el9.noarch Failed to resolve allow statement at /var/lib/selinux/targeted/tmp/modules/400/openvswitch-custom/cil:74 Failed to resolve AST /usr/sbin/semodule: Failed! uavc: op=load_policy lsm=selinux seqno=3 res=1 which brakes a few more, etc. thanks, L

2 1

oVirt 4.4.10 is now generally available
by Sandro Bonazzola 19 Jan '22

19 Jan '22

oVirt 4.4.10 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.10 , as of January 18th, 2022. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) 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>. What’s new in oVirt 4.4.10 Release? This update is the ninth in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.5 (or similar) - CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.5 (or similar) - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 Some of the RFEs with high user impact are listed below: - Bug 2012135 <https://bugzilla.redhat.com/show_bug.cgi?id=2012135> - [RFE] Provide option to unmap multiple LUNs using ovirt_remove_stale_lun ansible role Some of the Bugs with high user impact are listed below: - Bug 1710323 <https://bugzilla.redhat.com/show_bug.cgi?id=1710323> - Microsoft failover cluster is not working with FC direct LUN on Windows 2016 server and Windows 2019 - Bug 2023224 <https://bugzilla.redhat.com/show_bug.cgi?id=2023224> - multipath -f fails with "map in use" error while removing the LUNs using "ovirt_remove_stale_lun" - Bug 2027260 <https://bugzilla.redhat.com/show_bug.cgi?id=2027260> - Cold backup fail in various ways - backup is reported ready before add_bitmap jobs complete - Bug 1897114 <https://bugzilla.redhat.com/show_bug.cgi?id=1897114> - Add additional logging information to be able to understand why host is stuck in Unassigned state - Bug 1978655 <https://bugzilla.redhat.com/show_bug.cgi?id=1978655> - ELK integration fails due to missing configuration parameters - Bug 2032919 <https://bugzilla.redhat.com/show_bug.cgi?id=2032919> - Unable to add EL 7 host into oVirt Engine in clusters 4.2/4.3 oVirt Node has been updated, including: - oVirt 4.4.10: https://www.ovirt.org/release/4.4.10/ - CentOS Stream 8 latest updates - Full list of changes: --- ovirt-node-ng-image-4.4.9.3.manifest-rpm 2021-12-15 15:40:13.501764699 +0100 +++ ovirt-node-ng-image-4.4.10.manifest-rpm 2022-01-19 08:09:36.668868583 +0100 @@ -2,7 +2,6 @@ -ModemManager-glib-1.18.2-1.el8.x86_64 -NetworkManager-1.36.0-0.2.el8.x86_64 -NetworkManager-config-server-1.36.0-0.2.el8.noarch -NetworkManager-libnm-1.36.0-0.2.el8.x86_64 -NetworkManager-ovs-1.36.0-0.2.el8.x86_64 -NetworkManager-team-1.36.0-0.2.el8.x86_64 -NetworkManager-tui-1.36.0-0.2.el8.x86_64 +NetworkManager-1.36.0-0.3.el8.x86_64 +NetworkManager-config-server-1.36.0-0.3.el8.noarch +NetworkManager-libnm-1.36.0-0.3.el8.x86_64 +NetworkManager-ovs-1.36.0-0.3.el8.x86_64 +NetworkManager-team-1.36.0-0.3.el8.x86_64 +NetworkManager-tui-1.36.0-0.3.el8.x86_64 @@ -23 +22 @@ -alsa-lib-1.2.5-4.el8.x86_64 +alsa-lib-1.2.6.1-1.el8.x86_64 @@ -29,2 +28,2 @@ -augeas-1.12.0-6.el8.x86_64 -augeas-libs-1.12.0-6.el8.x86_64 +augeas-1.12.0-7.el8.x86_64 +augeas-libs-1.12.0-7.el8.x86_64 @@ -34 +33 @@ -autofs-5.1.4-74.el8.x86_64 +autofs-5.1.4-77.el8.x86_64 @@ -44 +43 @@ -binutils-2.30-111.el8.x86_64 +binutils-2.30-112.el8.x86_64 @@ -46 +45 @@ -blivet-data-3.4.0-7.el8.noarch +blivet-data-3.4.0-8.el8.noarch @@ -58 +57 @@ -ceph-common-16.2.6-1.el8s.x86_64 +ceph-common-16.2.7-1.el8s.x86_64 @@ -63,6 +62,6 @@ -clevis-15-4.el8.x86_64 -clevis-dracut-15-4.el8.x86_64 -clevis-luks-15-4.el8.x86_64 -clevis-systemd-15-4.el8.x86_64 -cockpit-258-1.el8.x86_64 -cockpit-bridge-258-1.el8.x86_64 +clevis-15-6.el8.x86_64 +clevis-dracut-15-6.el8.x86_64 +clevis-luks-15-6.el8.x86_64 +clevis-systemd-15-6.el8.x86_64 +cockpit-260-1.el8.x86_64 +cockpit-bridge-260-1.el8.x86_64 @@ -70,3 +69,3 @@ -cockpit-storaged-255-1.el8.noarch -cockpit-system-258-1.el8.noarch -cockpit-ws-258-1.el8.x86_64 +cockpit-storaged-259-1.el8.noarch +cockpit-system-260-1.el8.noarch +cockpit-ws-260-1.el8.x86_64 @@ -116 +115 @@ -dmidecode-3.2-10.el8.x86_64 +dmidecode-3.3-1.el8.x86_64 @@ -193 +192 @@ -fwupd-1.5.9-1.el8_4.x86_64 +fwupd-1.7.1-1.el8.x86_64 @@ -196 +195 @@ -gdb-headless-8.2-17.el8.x86_64 +gdb-headless-8.2-18.el8.x86_64 @@ -206,4 +205,3 @@ -glibc-2.28-174.el8.x86_64 -glibc-common-2.28-174.el8.x86_64 -glibc-gconv-extra-2.28-174.el8.x86_64 -glibc-langpack-en-2.28-174.el8.x86_64 +glibc-2.28-181.el8.x86_64 +glibc-common-2.28-181.el8.x86_64 +glibc-langpack-en-2.28-181.el8.x86_64 @@ -244 +242 @@ -gssproxy-0.8.0-19.el8.x86_64 +gssproxy-0.8.0-20.el8.x86_64 @@ -253 +251 @@ -hwdata-0.314-8.10.el8.noarch +hwdata-0.314-8.11.el8.noarch @@ -260,4 +258,4 @@ -ipa-client-4.9.6-6.module_el8.5.0+947+fabc681e.x86_64 -ipa-client-common-4.9.6-6.module_el8.5.0+947+fabc681e.noarch -ipa-common-4.9.6-6.module_el8.5.0+947+fabc681e.noarch -ipa-selinux-4.9.6-6.module_el8.5.0+947+fabc681e.noarch +ipa-client-4.9.8-2.module_el8.6.0+1054+cdb51b28.x86_64 +ipa-client-common-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch +ipa-common-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch +ipa-selinux-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch @@ -275 +273 @@ -iputils-20180629-7.el8.x86_64 +iputils-20180629-8.el8.x86_64 @@ -303,6 +301,6 @@ -kernel-4.18.0-348.2.1.el8_5.x86_64 -kernel-core-4.18.0-348.2.1.el8_5.x86_64 -kernel-modules-4.18.0-348.2.1.el8_5.x86_64 -kernel-tools-4.18.0-348.2.1.el8_5.x86_64 -kernel-tools-libs-4.18.0-348.2.1.el8_5.x86_64 -kexec-tools-2.0.20-63.el8.x86_64 +kernel-4.18.0-358.el8.x86_64 +kernel-core-4.18.0-358.el8.x86_64 +kernel-modules-4.18.0-358.el8.x86_64 +kernel-tools-4.18.0-358.el8.x86_64 +kernel-tools-libs-4.18.0-358.el8.x86_64 +kexec-tools-2.0.20-67.el8.x86_64 @@ -312 +310 @@ -kmod-kvdo-6.2.5.72-81.el8.x86_64 +kmod-kvdo-6.2.6.3-82.el8.x86_64 @@ -359 +357 @@ -libcephfs2-16.2.6-1.el8s.x86_64 +libcephfs2-16.2.7-1.el8s.x86_64 @@ -381 +379 @@ -libgcc-8.5.0-6.el8.x86_64 +libgcc-8.5.0-7.el8.x86_64 @@ -393 +391 @@ -libgomp-8.5.0-6.el8.x86_64 +libgomp-8.5.0-7.el8.x86_64 @@ -401 +399 @@ -libibverbs-37.1-1.el8.x86_64 +libibverbs-37.2-1.el8.x86_64 @@ -405 +403 @@ -libipa_hbac-2.5.2-2.el8_5.1.x86_64 +libipa_hbac-2.6.1-2.el8.x86_64 @@ -418 +415,0 @@ -libmbim-1.26.0-2.el8.x86_64 @@ -434 +431 @@ -libosinfo-1.9.0-1.el8.x86_64 +libosinfo-1.9.0-2.el8.x86_64 @@ -441 +437,0 @@ -libpmemobj-1.6.1-1.el8.x86_64 @@ -447 +442,0 @@ -libqmi-1.30.2-1.el8.x86_64 @@ -449,3 +444,3 @@ -librados2-16.2.6-1.el8s.x86_64 -libradosstriper1-16.2.6-1.el8s.x86_64 -librbd1-16.2.6-1.el8s.x86_64 +librados2-16.2.7-1.el8s.x86_64 +libradosstriper1-16.2.7-1.el8s.x86_64 +librbd1-16.2.7-1.el8s.x86_64 @@ -453 +448 @@ -librdmacm-37.1-1.el8.x86_64 +librdmacm-37.2-1.el8.x86_64 @@ -463 +458 @@ -librgw2-16.2.6-1.el8s.x86_64 +librgw2-16.2.7-1.el8s.x86_64 @@ -477,7 +472,7 @@ -libsss_autofs-2.5.2-2.el8_5.1.x86_64 -libsss_certmap-2.5.2-2.el8_5.1.x86_64 -libsss_idmap-2.5.2-2.el8_5.1.x86_64 -libsss_nss_idmap-2.5.2-2.el8_5.1.x86_64 -libsss_simpleifp-2.5.2-2.el8_5.1.x86_64 -libsss_sudo-2.5.2-2.el8_5.1.x86_64 -libstdc++-8.5.0-6.el8.x86_64 +libsss_autofs-2.6.1-2.el8.x86_64 +libsss_certmap-2.6.1-2.el8.x86_64 +libsss_idmap-2.6.1-2.el8.x86_64 +libsss_nss_idmap-2.6.1-2.el8.x86_64 +libsss_simpleifp-2.6.1-2.el8.x86_64 +libsss_sudo-2.6.1-2.el8.x86_64 +libstdc++-8.5.0-7.el8.x86_64 @@ -536 +531 @@ -libwbclient-4.14.5-2.el8.x86_64 +libwbclient-4.15.3-0.el8.x86_64 @@ -570 +565 @@ -mdadm-4.2-rc2.el8.x86_64 +mdadm-4.2-rc3.el8.x86_64 @@ -598,4 +593,4 @@ -net-snmp-5.8-23.el8.x86_64 -net-snmp-agent-libs-5.8-23.el8.x86_64 -net-snmp-libs-5.8-23.el8.x86_64 -net-snmp-utils-5.8-23.el8.x86_64 +net-snmp-5.8-24.el8.x86_64 +net-snmp-agent-libs-5.8-24.el8.x86_64 +net-snmp-libs-5.8-24.el8.x86_64 +net-snmp-utils-5.8-24.el8.x86_64 @@ -609,2 +604,2 @@ -nmstate-1.2.0-0.1.alpha2.el8.x86_64 -nmstate-plugin-ovsdb-1.2.0-0.1.alpha2.el8.noarch +nmstate-1.2.0-1.el8.x86_64 +nmstate-plugin-ovsdb-1.2.0-1.el8.noarch @@ -640 +635 @@ -osinfo-db-20210903-1.el8.noarch +osinfo-db-20211216-1.el8.noarch @@ -643 +638 @@ -ovirt-ansible-collection-1.6.5-1.el8.noarch +ovirt-ansible-collection-1.6.6-1.el8.noarch @@ -646 +641 @@ -ovirt-hosted-engine-ha-2.4.9-1.el8.noarch +ovirt-hosted-engine-ha-2.4.10-1.el8.noarch @@ -651 +646 @@ -ovirt-node-ng-image-update-placeholder-4.4.9.3-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.10-1.el8.noarch @@ -659,2 +654,2 @@ -ovirt-release-host-node-4.4.9.3-1.el8.noarch -ovirt-release44-4.4.9.3-1.el8.noarch +ovirt-release-host-node-4.4.10-1.el8.noarch +ovirt-release44-4.4.10-1.el8.noarch @@ -667,3 +662,3 @@ -pacemaker-cluster-libs-2.1.2-1.el8.x86_64 -pacemaker-libs-2.1.2-1.el8.x86_64 -pacemaker-schemas-2.1.2-1.el8.noarch +pacemaker-cluster-libs-2.1.2-2.el8.x86_64 +pacemaker-libs-2.1.2-2.el8.x86_64 +pacemaker-schemas-2.1.2-2.el8.noarch @@ -677 +672 @@ -pcsc-lite-1.8.23-4.1.el8_4.x86_64 +pcsc-lite-1.9.5-1.el8.x86_64 @@ -679 +674 @@ -pcsc-lite-libs-1.8.23-4.1.el8_4.x86_64 +pcsc-lite-libs-1.9.5-1.el8.x86_64 @@ -747 +742 @@ -python3-blivet-3.4.0-7.el8.noarch +python3-blivet-3.4.0-8.el8.noarch @@ -750,3 +745,3 @@ -python3-ceph-argparse-16.2.6-1.el8s.x86_64 -python3-ceph-common-16.2.6-1.el8s.x86_64 -python3-cephfs-16.2.6-1.el8s.x86_64 +python3-ceph-argparse-16.2.7-1.el8s.x86_64 +python3-ceph-common-16.2.7-1.el8s.x86_64 +python3-cephfs-16.2.7-1.el8s.x86_64 @@ -755 +750,2 @@ -python3-cloud-what-1.28.21-3.el8.x86_64 +python3-click-6.7-8.el8.noarch +python3-cloud-what-1.28.24-1.el8.x86_64 @@ -787,2 +783,2 @@ -python3-ipaclient-4.9.6-6.module_el8.5.0+947+fabc681e.noarch -python3-ipalib-4.9.6-6.module_el8.5.0+947+fabc681e.noarch +python3-ipaclient-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch +python3-ipalib-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch @@ -797,2 +793,2 @@ -python3-libipa_hbac-2.5.2-2.el8_5.1.x86_64 -python3-libnmstate-1.2.0-0.1.alpha2.el8.noarch +python3-libipa_hbac-2.6.1-2.el8.x86_64 +python3-libnmstate-1.2.0-1.el8.noarch @@ -805 +801 @@ -python3-linux-procfs-0.6.3-4.el8.noarch +python3-linux-procfs-0.7.0-1.el8.noarch @@ -837 +833 @@ -python3-perf-4.18.0-348.2.1.el8_5.x86_64 +python3-perf-4.18.0-358.el8.x86_64 @@ -860,2 +856,2 @@ -python3-rados-16.2.6-1.el8s.x86_64 -python3-rbd-16.2.6-1.el8s.x86_64 +python3-rados-16.2.7-1.el8s.x86_64 +python3-rbd-16.2.7-1.el8s.x86_64 @@ -865 +861 @@ -python3-rgw-16.2.6-1.el8s.x86_64 +python3-rgw-16.2.7-1.el8s.x86_64 @@ -867 +863 @@ -python3-rpm-4.14.3-19.el8.x86_64 +python3-rpm-4.14.3-21.el8.x86_64 @@ -875,3 +871,3 @@ -python3-sss-2.5.2-2.el8_5.1.x86_64 -python3-sss-murmur-2.5.2-2.el8_5.1.x86_64 -python3-sssdconfig-2.5.2-2.el8_5.1.noarch +python3-sss-2.6.1-2.el8.x86_64 +python3-sss-murmur-2.6.1-2.el8.x86_64 +python3-sssdconfig-2.6.1-2.el8.noarch @@ -879 +875 @@ -python3-subscription-manager-rhsm-1.28.21-3.el8.x86_64 +python3-subscription-manager-rhsm-1.28.24-1.el8.x86_64 @@ -881 +877 @@ -python3-syspurpose-1.28.21-3.el8.x86_64 +python3-syspurpose-1.28.24-1.el8.x86_64 @@ -914,4 +910,4 @@ -rpm-4.14.3-19.el8.x86_64 -rpm-build-libs-4.14.3-19.el8.x86_64 -rpm-libs-4.14.3-19.el8.x86_64 -rpm-plugin-selinux-4.14.3-19.el8.x86_64 +rpm-4.14.3-21.el8.x86_64 +rpm-build-libs-4.14.3-21.el8.x86_64 +rpm-libs-4.14.3-21.el8.x86_64 +rpm-plugin-selinux-4.14.3-21.el8.x86_64 @@ -925,3 +921,3 @@ -samba-client-libs-4.14.5-2.el8.x86_64 -samba-common-4.14.5-2.el8.noarch -samba-common-libs-4.14.5-2.el8.x86_64 +samba-client-libs-4.15.3-0.el8.x86_64 +samba-common-4.15.3-0.el8.noarch +samba-common-libs-4.15.3-0.el8.x86_64 @@ -931,2 +927,2 @@ -sbd-1.5.0-2.el8.x86_64 -scap-security-guide-0.1.57-5.el8.noarch +sbd-1.5.1-1.el8.x86_64 +scap-security-guide-0.1.59-1.el8.noarch @@ -937,2 +933,2 @@ -selinux-policy-3.14.3-85.el8.noarch -selinux-policy-targeted-3.14.3-85.el8.noarch +selinux-policy-3.14.3-86.el8.noarch +selinux-policy-targeted-3.14.3-86.el8.noarch @@ -950 +946 @@ -sos-4.2-7.el8.noarch +sos-4.2-11.el8.noarch @@ -956,9 +952,9 @@ -sssd-client-2.5.2-2.el8_5.1.x86_64 -sssd-common-2.5.2-2.el8_5.1.x86_64 -sssd-common-pac-2.5.2-2.el8_5.1.x86_64 -sssd-dbus-2.5.2-2.el8_5.1.x86_64 -sssd-ipa-2.5.2-2.el8_5.1.x86_64 -sssd-kcm-2.5.2-2.el8_5.1.x86_64 -sssd-krb5-common-2.5.2-2.el8_5.1.x86_64 -sssd-tools-2.5.2-2.el8_5.1.x86_64 -subscription-manager-rhsm-certificates-1.28.21-3.el8.x86_64 +sssd-client-2.6.1-2.el8.x86_64 +sssd-common-2.6.1-2.el8.x86_64 +sssd-common-pac-2.6.1-2.el8.x86_64 +sssd-dbus-2.6.1-2.el8.x86_64 +sssd-ipa-2.6.1-2.el8.x86_64 +sssd-kcm-2.6.1-2.el8.x86_64 +sssd-krb5-common-2.6.1-2.el8.x86_64 +sssd-tools-2.6.1-2.el8.x86_64 +subscription-manager-rhsm-certificates-1.28.24-1.el8.x86_64 @@ -976,5 +972,5 @@ -systemd-239-51.el8.x86_64 -systemd-container-239-51.el8.x86_64 -systemd-libs-239-51.el8.x86_64 -systemd-pam-239-51.el8.x86_64 -systemd-udev-239-51.el8.x86_64 +systemd-239-51.el8_5.2.x86_64 +systemd-container-239-51.el8_5.2.x86_64 +systemd-libs-239-51.el8_5.2.x86_64 +systemd-pam-239-51.el8_5.2.x86_64 +systemd-udev-239-51.el8_5.2.x86_64 @@ -982 +978 @@ -tcpdump-4.9.3-2.el8.x86_64 +tcpdump-4.9.3-3.el8.x86_64 @@ -993 +989 @@ -usbredir-0.8.0-1.el8.x86_64 +usbredir-0.12.0-1.el8.x86_64 @@ -997,11 +993,11 @@ -vdsm-4.40.90.4-1.el8.x86_64 -vdsm-api-4.40.90.4-1.el8.noarch -vdsm-client-4.40.90.4-1.el8.noarch -vdsm-common-4.40.90.4-1.el8.noarch -vdsm-gluster-4.40.90.4-1.el8.x86_64 -vdsm-http-4.40.90.4-1.el8.noarch -vdsm-jsonrpc-4.40.90.4-1.el8.noarch -vdsm-network-4.40.90.4-1.el8.x86_64 -vdsm-python-4.40.90.4-1.el8.noarch -vdsm-yajsonrpc-4.40.90.4-1.el8.noarch -vim-minimal-8.0.1763-16.el8_5.2.x86_64 +vdsm-4.40.100.2-1.el8.x86_64 +vdsm-api-4.40.100.2-1.el8.noarch +vdsm-client-4.40.100.2-1.el8.noarch +vdsm-common-4.40.100.2-1.el8.noarch +vdsm-gluster-4.40.100.2-1.el8.x86_64 +vdsm-http-4.40.100.2-1.el8.noarch +vdsm-jsonrpc-4.40.100.2-1.el8.noarch +vdsm-network-4.40.100.2-1.el8.x86_64 +vdsm-python-4.40.100.2-1.el8.noarch +vdsm-yajsonrpc-4.40.100.2-1.el8.noarch +vim-minimal-8.0.1763-16.el8_5.3.x86_64 @@ -1011 +1007 @@ -virt-what-1.18-12.el8.x86_64 +virt-what-1.18-13.el8.x86_64 See the release notes [1] for installation instructions and a list of new features and bugs fixed. Additional resources: - Read more about the oVirt 4.4.10 release highlights: https://www.ovirt.org/release/4.4.10/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ [1] https://www.ovirt.org/release/4.4.10/ -- 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

Important: two-factor authentication on GitHub
by Janos Bonic 17 Jan '22

17 Jan '22

Dear oVirt contributors, As we are moving to GitHub for our main development platform and CI we are also securing the oVirt organization. If you are a member of the oVirt organization on GitHub please make sure that you *enable two factor authentication on your GitHub account by the 20th of January*. If you don't enable 2FA the security enforcement will drop you from the organization automatically. Should this happen to you please let me or Sandro know via a private mail so we can re-add you. Janos

3 2

imageio failure (was: [oVirt/ovirt-release] Failed repoclosure job (Issue #71))
by Yedidyah Bar David 16 Jan '22

16 Jan '22

On Sun, Jan 16, 2022 at 9:11 AM github-actions[bot] <notifications(a)github.com> wrote: > > ❌ The repoclosure CI job is still failing. Please investigate. https://github.com/oVirt/ovirt-release/runs/4830975790?check_suite_focus=tr… Copr repo for ovirt-master-snapshot owned by ov 168 kB/s | 3.3 kB 00:00 Error: Repoclosure ended with unresolved dependencies. package: ovirt-imageio-client-2.4.1-0.202201152029.gite226a5f.el8.x86_64 from copr:copr.fedorainfracloud.org:ovirt:ovirt-master-snapshot unresolved deps: ovirt-imageio-common = 2.4.1-0.202201152029.gite226a5f.el8 package: ovirt-imageio-daemon-2.4.1-0.202201152029.gite226a5f.el8.x86_64 from copr:copr.fedorainfracloud.org:ovirt:ovirt-master-snapshot unresolved deps: ovirt-imageio-common = 2.4.1-0.202201152029.gite226a5f.el8 Error: Process completed with exit code 1. I also see a failure here, not sure it's related: https://copr.fedorainfracloud.org/coprs/ovirt/ovirt-master-snapshot/package… https://copr.fedorainfracloud.org/coprs/ovirt/ovirt-master-snapshot/build/3… https://download.copr.fedorainfracloud.org/results/ovirt/ovirt-master-snaps… ERROR: Command failed: # /usr/bin/systemd-nspawn -q -M e2c8282d0fd84261a27858b46be976be -D /var/lib/mock/centos-stream-9-x86_64-bootstrap-1642278641.264613/root -a --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.ifotg3xd:/etc/resolv.conf --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/var/lib/mock/centos-stream-9-x86_64-1642278641.264613/root/installation-homedir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$ --setenv=LANG=C.UTF-8 --setenv=LC_MESSAGES=C.UTF-8 --setenv=LD_PRELOAD=/var/tmp/tmp.mock.jav2ocjj/$LIB/nosync.so --setenv=SYSTEMD_NSPAWN_TMPFS_TMP=0 --resolv-conf=off /usr/bin/dnf builddep --installroot /var/lib/mock/centos-stream-9-x86_64-1642278641.264613/root/ --releasever 9 --setopt=deltarpm=False --allowerasing --disableplugin=local --disableplugin=spacewalk --disableplugin=versionlock --disableplugin=local --disableplugin=spacewalk --disableplugin=versionlock /var/lib/mock/centos-stream-9-x86_64-1642278641.264613/root//builddir/build/SRPMS/ovirt-imageio-2.4.1-0.202201152029.gite226a5f.el9.src.rpm --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 29 kB/s | 3.3 kB 00:00 Additional repo https_buildlogs_centos_org_cent 18 kB/s | 3.0 kB 00:00 Additional repo https_download_copr_fedorainfra 31 kB/s | 3.3 kB 00:00 Error: Problem: cannot install the best candidate for the job - nothing provides libgomp = 11.2.1-7.4.el9 needed by gcc-11.2.1-7.4.el9.x86_64 - nothing provides libgcc >= 11.2.1-7.4.el9 needed by gcc-11.2.1-7.4.el9.x86_64 If that's indeed the issue, it's probably in the OS, not oVirt, and hopefully temporary. Didn't check further (yet?). Best regards, -- Didi

2 3

ovirt-engine has been tagged (ovirt-engine-4.4.10.4)
by Martin Perina 13 Jan '22

13 Jan '22

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

2 1

git backup
by Yedidyah Bar David 12 Jan '22

12 Jan '22

Hi all, With the decision and on-going process to migrate from gerrit to github, we do not anymore have a backup - github used to be a backup for gerrit, automatically synced. Do we want a backup for github? Some options: 1. Do nothing. github as-is might be good enough, and it also has an archive program [1]. AFAICT, right now none of the partners in this program allow 'git clone'. There are plans to allow that in the future. 2. Do something custom like we did so far with gerrit->github. 3. Find some service. Searching for 'github backup' finds lots of options. I didn't check any. Thoughts? [1] https://archiveprogram.github.com/ Best regards, -- Didi

4 5

ovirt-engine has been tagged (ovirt-engine-4.4.10.3)
by Sandro Bonazzola 12 Jan '22

12 Jan '22

ovirt-engine has been tagged (ovirt-engine-4.4.10.3) -- 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-release-master - snapshot rpm
by lejeczek 12 Jan '22

12 Jan '22

Hi guys I see 'ovirt-release-master' updates not too rarely, example: .. ovirt-release-master noarch 4.5.0-0.0.master.20220111162025.gitc1cee60.el9 copr:copr.fedorainfracloud.org:ovirt:ovirt-master-snapshot 20 k .. Not knowing how this all works - what is that worth? What does it do really? No other packages get updated from oVirt repos. Care to shed bit of light? many thanks, L.

2 4

Re: Change in ovirt-engine[master]: packaging: engine-setup: Use otopi's checkForSafeUpdate
by Yedidyah Bar David 12 Jan '22

12 Jan '22

On Wed, Jan 12, 2022 at 12:06 PM Code Review <gerrit(a)ovirt.org> wrote: > > From Jenkins CI <jenkins(a)ovirt.org>: > > Jenkins CI has posted comments on this change. ( https://gerrit.ovirt.org/c/ovirt-engine/+/116920 ) > > Change subject: packaging: engine-setup: Use otopi's checkForSafeUpdate > ...................................................................... > > > Patch Set 6: > > Build Failed > > https://jenkins.ovirt.org/job/standard-enqueue/36418/ : > This change was not submitted to any change queues for system testing. You will need to create some 'build-artifacts' jobs if you want changes to be submitted to change queues, take part in the system tests and be deployed to the nightly snapshot repositories. If your project uses STDCI V2 and you have release branches configured, you may disregard this message. > > > https://jenkins.ovirt.org/job/ovirt-engine_standard-on-merge/2762/ : UNSTABLE I think it's because of: [2022-01-12T09:42:30.703Z] Traceback (most recent call last): [2022-01-12T09:42:30.703Z] File "/home/jenkins/agent/workspace/ovirt-engine_standard-on-merge(a)tmp/durable-ecea2c02/script.sh", line 10, in <module> [2022-01-12T09:42:30.703Z] change = GerritMergedChange.from_jenkins_env() [2022-01-12T09:42:30.703Z] File "/home/jenkins/agent/workspace/ovirt-engine_standard-on-merge/jenkins/stdci_libs/change_queue/changes/__init__.py", line 290, in from_jenkins_env [2022-01-12T09:42:30.703Z] o = cls(gerrit_patchset=GerritPatchset.from_jenkins_env()) [2022-01-12T09:42:30.703Z] File "/home/jenkins/agent/workspace/ovirt-engine_standard-on-merge/jenkins/stdci_libs/gerrit.py", line 157, in from_jenkins_env [2022-01-12T09:42:30.703Z] 'GERRIT_PATCHSET_UPLOADER', env [2022-01-12T09:42:30.703Z] File "/home/jenkins/agent/workspace/ovirt-engine_standard-on-merge/jenkins/stdci_libs/gerrit.py", line 97, in from_jenkins_env [2022-01-12T09:42:30.703Z] return cls(env[prefix + '_NAME'], env[prefix + '_EMAIL']) [2022-01-12T09:42:30.703Z] File "/usr/lib64/python3.6/os.py", line 669, in __getitem__ [2022-01-12T09:42:30.703Z] raise KeyError(key) from None [2022-01-12T09:42:30.703Z] KeyError: 'GERRIT_PATCHSET_UPLOADER_NAME' and I *think* it's because I commented 'ost check' on two patches, which were one above the other, and CI merged the upper one before finishing the gating of the lower one (current). Current case can most probably be ignored, but I wonder if we want to do something in the general case - perhaps the code already does everything well, didn't check - e.g. checking that all pending patches in the stack have all acks, etc. Best regards, -- Didi

1 0

[Action Required] otopi updated
by Yedidyah Bar David 12 Jan '22

12 Jan '22

Hi all, I now merged these patches: https://github.com/oVirt/otopi/pull/11 https://gerrit.ovirt.org/c/ovirt-engine/+/116920 https://gerrit.ovirt.org/c/ovirt-engine/+/118228 Please update otopi on your dev machines. Otherwise, engine-setup might fail. Best regards, -- Didi

1 0

VDSM have moved to github
by Nir Soffer 09 Jan '22

09 Jan '22

We are not using the gerrit project now, and it was changed to read-only. We are accepting now pull requests on github: https://github.com/oVirt/vdsm/pulls To contribute, use the standard github flow: 1. Fork vdsm on github Example: https://github.com/nirs/vdsm (you need to create a github account if you don't have one) 2. Clone your fork Example: git clone git@github.com:nirs/vdsm.git 3. Push changes to your fork and submit pull requests Example: https://github.com/oVirt/vdsm/pull/28 4. Check the github CI for your pull request Example: https://github.com/oVirt/vdsm/pull/28/checks Note: We don't do squash merges. When addressing comments, force push to your fork. Example: https://github.com/oVirt/ovirt-imageio/pull/15 Common issues: 1. How do I add reviewers to my pull request? Once https://github.com/oVirt/vdsm/pull/28 will be merged, we will have a CODEOWNERS file: https://github.com/oVirt/vdsm/blob/96320682a8b41e440fbbb8ca624fd73efa95bda0… so github will assign reviews automatically. Regardless you can add a comment on you patch like: @{reviewer} please review. 2. How do I run OST with my pull request? OST does not run yet automatically. You have 2 choices: - Run OST locally (ask here how to run it) - Use the Red Hat OST runner (ask on rhev-devel(a)redhat.com how to use it) When running OST, you can use the built rpms from your pull request: https://github.com/oVirt/vdsm/actions/runs/1673718827 (see the artifacts.zip at the bottom) 3. How to backport a patch to stable branches? Backport your patch(es) on top of the right stable branch (e.g. ovirt-4.4.z). When you create a pull request, please choose the right branch. The stable branches maintainers will be added for review automatically. 4. How to compare changes when a contributor submitted a new version? When contributor force pushes, github shows: nirs *force-pushed* the inactivity-timeout branch 2 times, most recently from *790cc4c* to *38d08c8* 22 days ago Click the "force-pushed" link to see the differences: https://github.com/oVirt/ovirt-imageio/compare/790cc4c44c9c6577dae0badb3fc6… 5. How to download a pull request to my machine? You can use the github command lline tool "gh": gh pr checkout 28 See https://cli.github.com/ for more info. (note: I did not try it yet) 6. How do I comment on commit message? Github does not have this feature, you can use the review comment, or add a separate comment. 7. How to run CI on a single patch in my PR? Github runs the CI for the entire PR. If your PR have several commits, issues in early commits fixed in later commits are hidden. To verify that all commits pass the tests you can post the submit a new branch to your local fork. Example flow: git checkout -b testing-foobar commit-id git push origin testing-foobar (check CI on your fork) Alternatively, use smaller pull requests. You can submit pull request based on another pull request. Nir

1 0

Need help in dumping a table
by Matthew.Stier＠fujitsu.com 05 Jan '22

05 Jan '22

I'm planning a re-organization of my oVirt environment. I need a Postgres command-line to dump a listing of VMs/disks/storage_domains.

1 0

Cannot build Engine rpm's on CentOS Stream 8
by Milan Zamazal 05 Jan '22

05 Jan '22

Hi, I've been having trouble to build Engine rpm's locally on up-to-date Stream 8 since about mid December, most likely due to javapackages-local update to 6.0.0-1.4.el8s. Engine compiles fine but building the rpm's fails on missing %add_maven_depmap rpm spec macro. There is a patch for Stream 9: https://gerrit.ovirt.org/c/ovirt-engine/+/116811. But when I rebase on it, I get the following error: [INFO maven.req] input: ['/root/rpmbuild/BUILDROOT/ovirt-engine-4.5.0-0.2.master.20220104124402.el8.x86_64/usr/share/maven-metadata/ovirt-engine-base.xml'] Traceback (most recent call last): File "/usr/lib/rpm/maven.req", line 393, in <module> builder = TagBuilder() File "/usr/lib/rpm/maven.req", line 71, in __init__ self.print_requires(metadata) File "/usr/lib/rpm/maven.req", line 200, in print_requires self._handle_unknown_deps(unknown_deps) File "/usr/lib/rpm/maven.req", line 258, in _handle_unknown_deps raise Exception(unknown_msg) Exception: Following dependencies were not resolved and requires cannot be generated. Either remove the dependencies from pom.xml or add proper packages to BuildRequires: commons-beanutils:commons-beanutils:1.9.4 required by org.ovirt.engine.core:utils commons-lang:commons-lang:2.6 required by org.ovirt.engine.core:aaa org.infinispan:infinispan-core:9.4.18.Final required by org.ovirt.engine.core:utils commons-collections:commons-collections:3.2.2 required by org.ovirt.engine.core:bll org.jboss.modules:jboss-modules:1.1.1.GA required by org.ovirt.engine.core:common org.hibernate.validator:hibernate-validator:6.0.18.Final required by org.ovirt.engine.core:common This happens with both maven 3.5 and 3.6. Any idea what's wrong and how to fix it on Stream 8? Thanks, Milan

2 3

Re: [oVirt/ovirt-release] Failed repoclosure job (Issue #60)
by Yedidyah Bar David 05 Jan '22

05 Jan '22

On Wed, Jan 5, 2022 at 1:09 PM github-actions[bot] <notifications(a)github.com> wrote: > ❌ The repoclosure CI job is still failing. Please investigate. > <https://github.com/oVirt/ovirt-release/actions/runs/1658041750> > It failed because we recently started building metrics and dwh on el9, which require stuff we do not have: - The engine, already discussed elsewhere, patches are WIP (apparently waiting for Artur? Not sure). - ansible. No idea why it's missing. Perhaps better not build new stuff on el9 before we fix these, or stop running repoclosure on el9 for now. Best regards, -- Didi

2 2

create a host using ssh
by Grace Chen 03 Jan '22

03 Jan '22

I am writing a script to create a host using public ssh key the function I am using is add_using_ssh: my ssh_key is a an Ssh type already ssh_key = types.Ssh(public_key=my_ssh_key_string) host = hosts_service.add_using_ssh( types.Host( name=name, description='', address=address, root_password=None, port=22, ssh=ssh_key, cluster=types.Cluster( name=cluster, ), ), ) When I choose from GUI, it doesn't ask me to put in root password, so I set it as None (Not sure if this is correct) I got error: ovirtsdk4.Error: Fault reason is "Request syntactically incorrect.". Fault detail is "For correct usage, see: ovirt-engine/apidoc#services/hosts/methods/add". HTTP response code is 400. looks like I didn't get all the parameters assigned? Can anybody help with this?

2 5