December 2021 - 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

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

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

Re: [oVirt/ovirt-release] Failed repoclosure job (Issue #55)
by Yedidyah Bar David 28 Dec '21

28 Dec '21

On Mon, Dec 27, 2021 at 2:38 PM github-actions[bot] <notifications(a)github.com> wrote: > > ❌ The repoclosure CI job is still failing. Please investigate. I think this started failing recently (on el9) due to a combination of: - The engine is still not built on el9 in copr. I tried building it myself there and so far got stuck - it seems like the fix is an existing pending patch [1] (failed at %add_maven_depmap). - ovirt-engine-keycloak is now built also for el9, but requires an engine package, so we fail on repoclosure. Unless we have concrete plans to fix this very soon, I suggest to stop the noise for now - either not build (or publish?) keycloak for el9, or do not run repoclosure on el9, or perhaps filter the output to not fail if it's only on these packages, etc. [1] https://gerrit.ovirt.org/c/ovirt-engine/+/116811 -- Didi

2 2

OST fails with "Error loading module from /usr/share/ovirt-engine/modules/common/org/springframework/main/module.xml"
by Marcin Sobczyk 27 Dec '21

27 Dec '21

Hi All, OST currently fails all the time during engine setup. Here's a piece of ansible log that's seen repeatedly and I think describes the problem: 11:07:54 E "engine-config", 11:07:54 E "-s", 11:07:54 E "OvfUpdateIntervalInMinutes=10" 11:07:54 E ], 11:07:54 E "delta": "0:00:01.142926", 11:07:54 E "end": "2021-12-24 11:06:37.894810", 11:07:54 E "invocation": { 11:07:54 E "module_args": { 11:07:54 E "_raw_params": "engine-config -s OvfUpdateIntervalInMinutes='10' ", 11:07:54 E "_uses_shell": false, 11:07:54 E "argv": null, 11:07:54 E "chdir": null, 11:07:54 E "creates": null, 11:07:54 E "executable": null, 11:07:54 E "removes": null, 11:07:54 E "stdin": null, 11:07:54 E "stdin_add_newline": true, 11:07:54 E "strip_empty_ends": true, 11:07:54 E "warn": false 11:07:54 E } 11:07:54 E }, 11:07:54 E "item": { 11:07:54 E "key": "OvfUpdateIntervalInMinutes", 11:07:54 E "value": "10" 11:07:54 E }, 11:07:54 E "msg": "non-zero return code", 11:07:54 E "rc": 1, 11:07:54 E "start": "2021-12-24 11:06:36.751884", 11:07:54 E "stderr": "Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false", 11:07:54 E "stderr_lines": [ 11:07:54 E "Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false" 11:07:54 E ], 11:07:54 E "stdout": "Error loading module from /usr/share/ovirt-engine/modules/common/org/springframework/main/module.xml", 11:07:54 E "stdout_lines": [ 11:07:54 E "Error loading module from /usr/share/ovirt-engine/modules/common/org/springframework/main/module.xml" We do set some config values for the engine in OST when running engine-setup. I tried commenting these out, but then engine failed health check anyway: "Status code was 503 and not [200]: HTTP Error 503: Service Unavailable" The last working set of OST images was the one from Dec 23, 2021 2:05:08 AM. The first broken one is from Dec 24, 2021 2:05:09 AM. The shipped ovirt-engine RPMs doesn't seem to contain any important changes for these two sets, but AFAICS the newer ovirt-dependencies RPM did take in a couple of patches that look suspicious [1][2][3]. The patches were merged on November 16th, but it seems they were first used in that broken set from Dec 24 (the one from Dec 23 seems to contain ovirt-dependencies RPM based on this [4] commit). I wanted to try out an older version of ovirt-dependencies, but I think they were wiped out from resources.ovirt.org. I will disable cyclic el8stream OST runs for now, cause all of them fail. If there's anyone working and able to make a build with those patches reverted and test that out, please ping me and I'll re-enable them. Regards, Marcin [1] https://gerrit.ovirt.org/c/ovirt-dependencies/+/114699 [2] https://gerrit.ovirt.org/c/ovirt-dependencies/+/113877 [3] https://gerrit.ovirt.org/c/ovirt-dependencies/+/114654 [4] https://gerrit.ovirt.org/c/ovirt-dependencies/+/117459

2 1

Re: [ovirt-users] Re: using stop_reason as a vdsm hook trigger into the UI
by Nathanaël Blanchet 22 Dec '21

22 Dec '21

Le 22/12/2021 à 14:56, John Taylor a écrit : > Maybe use the events api and search for the shutdown and reason in there? > > api/events;from={event_id}?search={query}" rel="events/search"/> > > -John Exact! that's precisely the workaround I already tested this morning as well :) and it works because the event contains the stop_reason in the description field before vm is in the stopped status! > > On Tue, Dec 21, 2021 at 9:00 AM Nathanaël Blanchet <blanchet(a)abes.fr > <mailto:blanchet@abes.fr>> wrote: > > Thanks for responding, > > Le 20/12/2021 à 21:42, Nir Soffer a écrit : >> On Mon, Dec 20, 2021 at 9:59 PM Nathanaël Blanchet<blanchet(a)abes.fr> <mailto:blanchet@abes.fr> wrote: >> >> Adding the devel list since question is more about extending oVirt >> ... >>> The idea is to use the stop_reason element into the vm xml definition. But after hours, I realized that this element is writed to the vm definition file only after the VM has been destroyed. >> So you want to run the clean hook only if stop reason == "clean"? >> >> I think the way to integrate hooks is to define a custom property >> in the vm, and check if the property was defined in the hook. >> >> For example how the localdisk hook is triggered: >> >> def main(): >> backend = os.environ.get('localdisk') >> if backend is None: >> return >> if backend not in [BACKEND_LVM, BACKEND_LVM_THIN]: >> hooking.log("localdisk-hook: unsupported backend: %r" % backend) >> return >> ... >> >> The hook runs only if the environment variable "localdisk" is defined >> and configured properly. >> >> vdsm defines the custom properties as environment variables. >> >> On the engine side, you need to add a user defined property: >> >> engine-config -s UserDefinedVMProperties='localdisk=^(lvm|lvmthin)$' >> >> And configure a custom property with one of the allowed values, like: >> >> localdisk=lvm >> >> See vdsm_hooks/localdisk/README for more info. >> >> If you want to control the cleanup, by adding a "clean" stop reason only when >> needed, this will not help, and vdsm hook is probably not the right way >> to integrate this. > Sure >> If your intent is to clean a vm in some special events, but you want >> to integrate >> this in engine, maybe you should write an engine ui plugin? >> >> The plugin can show the running vms, and provide a clean button that will >> shut down the vm and run your custom code. > too complex for doing what I want >> But maybe you don't need to integrate this in engine, and having a simple >> script using ovirt engine API/SDK to shutdown the vm and run the cleanup >> code. > My playbook/scripts work already fine, but this is not my goal. >> Nir >> > I will sum up my initial question: *Is there any way to get the > value of "stop_reason" (value of the field in the UI) so as to > reuse this variable into a vdsm hook?* > > Thank you > > > -- > Nathanaël Blanchet > > Supervision réseau > SIRE > 227 avenue Professeur-Jean-Louis-Viala > 34193 MONTPELLIER CEDEX 5 > Tél. 33 (0)4 67 54 84 55 > Fax 33 (0)4 67 54 84 14 > blanchet(a)abes.fr <mailto:blanchet@abes.fr> > > _______________________________________________ > Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> > To unsubscribe send an email to users-leave(a)ovirt.org > <mailto:users-leave@ovirt.org> > Privacy Statement: https://www.ovirt.org/privacy-policy.html > <https://www.ovirt.org/privacy-policy.html> > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > <https://www.ovirt.org/community/about/community-guidelines/> > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/OSM572SLKKAFO… > <https://lists.ovirt.org/archives/list/users@ovirt.org/message/OSM572SLKKAFO…> > -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

1 1

Re: [ovirt-users] using stop_reason as a vdsm hook trigger into the UI
by Nir Soffer 21 Dec '21

21 Dec '21

On Mon, Dec 20, 2021 at 9:59 PM Nathanaël Blanchet <blanchet(a)abes.fr> wrote: Adding the devel list since question is more about extending oVirt ... > The idea is to use the stop_reason element into the vm xml definition. But after hours, I realized that this element is writed to the vm definition file only after the VM has been destroyed. So you want to run the clean hook only if stop reason == "clean"? I think the way to integrate hooks is to define a custom property in the vm, and check if the property was defined in the hook. For example how the localdisk hook is triggered: def main(): backend = os.environ.get('localdisk') if backend is None: return if backend not in [BACKEND_LVM, BACKEND_LVM_THIN]: hooking.log("localdisk-hook: unsupported backend: %r" % backend) return ... The hook runs only if the environment variable "localdisk" is defined and configured properly. vdsm defines the custom properties as environment variables. On the engine side, you need to add a user defined property: engine-config -s UserDefinedVMProperties='localdisk=^(lvm|lvmthin)$' And configure a custom property with one of the allowed values, like: localdisk=lvm See vdsm_hooks/localdisk/README for more info. If you want to control the cleanup, by adding a "clean" stop reason only when needed, this will not help, and vdsm hook is probably not the right way to integrate this. If your intent is to clean a vm in some special events, but you want to integrate this in engine, maybe you should write an engine ui plugin? The plugin can show the running vms, and provide a clean button that will shut down the vm and run your custom code. But maybe you don't need to integrate this in engine, and having a simple script using ovirt engine API/SDK to shutdown the vm and run the cleanup code. Nir

2 1

selinux for Ganesha absent in master?
by lejeczek 21 Dec '21

21 Dec '21

Hi guys. I get: -> $ dnf install glusterfs-ganesha.x86_64 Mine and private 2.9 MB/s | 3.0 kB 00:00 Error: Problem: cannot install the best candidate for the job - nothing provides nfs-ganesha-gluster >= 2.7.6 needed by glusterfs-ganesha-10.0-1.el9s.x86_64 that is with: ovirt-release-master-4.5.0-0.0.master.20211206152702.gitebb0229.el9.noarch many thanks, L.

3 2

ovirt-engine has been tagged (ovirt-engine-4.4.10.2)
by Martin Perina 21 Dec '21

21 Dec '21

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

1 0

OST failing
by Vojtech Juranek 20 Dec '21

20 Dec '21

Hi, OST is constantly failing today in test_verify_add_hosts with 19:34:33 E assert find_up_host() -> False != True after 1800 seconds 19:34:33 E + where find_up_host() -> False != True after 1800 seconds = <function true_within at 0x7fa62ac860d0>(<function test_verify_add_hosts.<locals>.find_up_host at 0x7fa628f97940>, timeout=1800) 19:34:33 E + where <function true_within at 0x7fa62ac860d0> = assert_utils.true_within 19:34:33 E + and 1800 = constants.ADD_HOST_TIMEOUT See e.g. https://redir.apps.ovirt.org/dj/job/ds-ost-baremetal_manual/23661 Any idea what's wrong? Thanks Vojta

2 2

Vdsm: Failing storage tests when run by non-root in a container
by Milan Zamazal 17 Dec '21

17 Dec '21

Hi, when I run Vdsm tests as a non-root user in vdsm-test-centos-8 container, they systematically fail on several storage tests. I run the tests as podman run -it -v $HOME:$HOME --userns=keep-id vdsm-test-centos-8 $HOME/test.sh where test.sh is #!/bin/sh export TRAVIS_CI=1 cd .../vdsm ./autogen.sh --system make clean make make lint make tests make tests-storage The failing tests are in devicemapper_test.py, outofprocess_test.py and qemuimg_test.py. I have also seen a test failure in nbd_test.py but not always. Is it a problem of the tests or of my environment? Thanks, Milan

2 3

ovirt-engine has been tagged (ovirt-engine-4.4.10.1)
by Sandro Bonazzola 17 Dec '21

17 Dec '21

ovirt-engine has been tagged (ovirt-engine-4.4.10.1) -- 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

Vdsm: Failing storage test
by Milan Zamazal 16 Dec '21

16 Dec '21

Hi, it seems a recent commit causes a storage test failure on GitHub: ================================== FAILURES =================================== ________________ test_prepare_connection_without_initiator_name ________________ def test_prepare_connection_without_initiator_name(): con_def = [{ "password": "password", "port": "3260", "iqn": "iqn.2016-01.com.ovirt:444", "connection": "192.168.1.2", "ipv6_enabled": "false", "id": "994a711a-60f3-411a-aca2-0b60f01e8b8c", "user": "", "tpgt": "1", }] > conn = storageServer._prepare_connections(sd.ISCSI_DOMAIN, con_def) E AttributeError: module 'vdsm.storage.storageServer' has no attribute '_prepare_connections' Could you please fix it quickly or disable the test? @all: Beware that CI on Vdsm no longer runs the tests and patches must be tested on GitHub before merging. Thanks, Milan

3 3

Fwd: [ovirt-users] [FOSDEM][CFP] Virtualization & IaaS Devroom
by Sandro Bonazzola 16 Dec '21

16 Dec '21

Sending to devel list as well, deadline is in 4 days. ---------- Forwarded message --------- Da: Piotr Kliczewski <pkliczew(a)redhat.com> Date: mar 30 nov 2021 alle ore 14:54 Subject: [ovirt-users] [FOSDEM][CFP] Virtualization & IaaS Devroom To: users <users(a)ovirt.org> Cc: Tal Nisan <tnisan(a)redhat.com> We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2022, to be hosted virtually on February 5th 2022. This year will mark FOSDEM’s 22nd anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. Due to Covid-19, FOSDEM will be held virtually this year on February 5th & 6th, 2022. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at users or developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 20th of December Acceptance notifications: 25th of December Final schedule announcement: 31st of December Recorded presentations upload deadline: 15th of January Devroom: 6th February 2022 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will need to be pre-recorded and put into our system at least a couple of weeks before the event. The presentations should be uploaded by 15th of January and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend the virtual FOSDEM event for the Q&A. We will not consider proposals from prospective speakers who are unsure whether they will be able to attend the FOSDEM virtual event. If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance with helping speakers to record the presentation as well as helping with streaming and chat moderation for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] https://penta.fosdem.org/submission/FOSDEM22 [2] iaas-virt-devroom at lists.fosdem.org _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XUOYT3H5GNCNL… -- 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

[ANN] oVirt Node 4.4.9.3 Async update
by Sandro Bonazzola 15 Dec '21

15 Dec '21

oVirt Node 4.4.9.3 Async update On December 15th 2021 the oVirt project released an async update of oVirt Node (4.4.9.3) delivering fixes for the following issues: Bug 2031911 <https://bugzilla.redhat.com/show_bug.cgi?id=2031911> - oVirt Node 4.4.9.1 and 4.4.9.2 are missing UEFI support due to a build issue Bug 2026432 <https://bugzilla.redhat.com/show_bug.cgi?id=2026432> - rsyslog-openssl is missing Reverted lvm2 package to previous version as workaround for Bug 2026370 <https://bugzilla.redhat.com/show_bug.cgi?id=2026370> - oVirt node fail to boot if lvm filter uses /dev/disk/by-id/lvm-pv-uuid-* Several bug fixes and improvements from CentOS Stream. Here’s the full list of changes: --- ovirt-node-ng-image-4.4.9.2.manifest-rpm 2021-12-10 09:09:24.084642608 +0100 +++ ovirt-node-ng-image-4.4.9.3.manifest-rpm 2021-12-15 15:40:13.501764699 +0100 @@ -1,0 +2 @@ +ModemManager-glib-1.18.2-1.el8.x86_64 @@ -46,0 +48 @@ +bubblewrap-0.4.0-1.el8.x86_64 @@ -97,3 +99,3 @@ -dbus-1.12.8-14.el8.x86_64 -dbus-common-1.12.8-14.el8.noarch -dbus-daemon-1.12.8-14.el8.x86_64 +dbus-1.12.8-18.el8.x86_64 +dbus-common-1.12.8-18.el8.noarch +dbus-daemon-1.12.8-18.el8.x86_64 @@ -101,6 +103,6 @@ -dbus-libs-1.12.8-14.el8.x86_64 -dbus-tools-1.12.8-14.el8.x86_64 -device-mapper-1.02.181-1.el8.x86_64 -device-mapper-event-1.02.181-1.el8.x86_64 -device-mapper-event-libs-1.02.181-1.el8.x86_64 -device-mapper-libs-1.02.181-1.el8.x86_64 +dbus-libs-1.12.8-18.el8.x86_64 +dbus-tools-1.12.8-18.el8.x86_64 +device-mapper-1.02.177-10.el8.x86_64 +device-mapper-event-1.02.177-10.el8.x86_64 +device-mapper-event-libs-1.02.177-10.el8.x86_64 +device-mapper-libs-1.02.177-10.el8.x86_64 @@ -109 +111 @@ -device-mapper-persistent-data-0.9.0-5.el8.x86_64 +device-mapper-persistent-data-0.9.0-6.el8.x86_64 @@ -117 +119 @@ -dnf-plugins-core-4.0.21-6.el8.noarch +dnf-plugins-core-4.0.21-7.el8.noarch @@ -127,0 +130,3 @@ +efi-filesystem-3-3.el8.noarch +efibootmgr-16-1.el8.x86_64 +efivar-libs-37-4.el8.x86_64 @@ -187,0 +193 @@ +fwupd-1.5.9-1.el8_4.x86_64 @@ -199,5 +205,5 @@ -glib2-2.56.4-157.el8.x86_64 -glibc-2.28-170.el8.x86_64 -glibc-common-2.28-170.el8.x86_64 -glibc-gconv-extra-2.28-170.el8.x86_64 -glibc-langpack-en-2.28-170.el8.x86_64 +glib2-2.56.4-158.el8.x86_64 +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 @@ -229,0 +236 @@ +grub2-efi-x64-2.02-106.el8.x86_64 @@ -251,0 +259 @@ +iotop-0.6-16.el8.noarch @@ -274,13 +282,13 @@ -iwl100-firmware-39.31.5.1-103.el8.1.noarch -iwl1000-firmware-39.31.5.1-103.el8.1.noarch -iwl105-firmware-18.168.6.1-103.el8.1.noarch -iwl135-firmware-18.168.6.1-103.el8.1.noarch -iwl2000-firmware-18.168.6.1-103.el8.1.noarch -iwl2030-firmware-18.168.6.1-103.el8.1.noarch -iwl3160-firmware-25.30.13.0-103.el8.1.noarch -iwl5000-firmware-8.83.5.1_1-103.el8.1.noarch -iwl5150-firmware-8.24.2.2-103.el8.1.noarch -iwl6000-firmware-9.221.4.1-103.el8.1.noarch -iwl6000g2a-firmware-18.168.6.1-103.el8.1.noarch -iwl6050-firmware-41.28.5.1-103.el8.1.noarch -iwl7260-firmware-25.30.13.0-103.el8.1.noarch +iwl100-firmware-39.31.5.1-105.el8.1.noarch +iwl1000-firmware-39.31.5.1-105.el8.1.noarch +iwl105-firmware-18.168.6.1-105.el8.1.noarch +iwl135-firmware-18.168.6.1-105.el8.1.noarch +iwl2000-firmware-18.168.6.1-105.el8.1.noarch +iwl2030-firmware-18.168.6.1-105.el8.1.noarch +iwl3160-firmware-25.30.13.0-105.el8.1.noarch +iwl5000-firmware-8.83.5.1_1-105.el8.1.noarch +iwl5150-firmware-8.24.2.2-105.el8.1.noarch +iwl6000-firmware-9.221.4.1-105.el8.1.noarch +iwl6000g2a-firmware-18.168.6.1-105.el8.1.noarch +iwl6050-firmware-41.28.5.1-105.el8.1.noarch +iwl7260-firmware-25.30.13.0-105.el8.1.noarch @@ -332,15 +340,15 @@ -libblockdev-2.24-7.el8.x86_64 -libblockdev-crypto-2.24-7.el8.x86_64 -libblockdev-dm-2.24-7.el8.x86_64 -libblockdev-fs-2.24-7.el8.x86_64 -libblockdev-kbd-2.24-7.el8.x86_64 -libblockdev-loop-2.24-7.el8.x86_64 -libblockdev-lvm-2.24-7.el8.x86_64 -libblockdev-mdraid-2.24-7.el8.x86_64 -libblockdev-mpath-2.24-7.el8.x86_64 -libblockdev-nvdimm-2.24-7.el8.x86_64 -libblockdev-part-2.24-7.el8.x86_64 -libblockdev-plugins-all-2.24-7.el8.x86_64 -libblockdev-swap-2.24-7.el8.x86_64 -libblockdev-utils-2.24-7.el8.x86_64 -libblockdev-vdo-2.24-7.el8.x86_64 +libblockdev-2.24-8.el8.x86_64 +libblockdev-crypto-2.24-8.el8.x86_64 +libblockdev-dm-2.24-8.el8.x86_64 +libblockdev-fs-2.24-8.el8.x86_64 +libblockdev-kbd-2.24-8.el8.x86_64 +libblockdev-loop-2.24-8.el8.x86_64 +libblockdev-lvm-2.24-8.el8.x86_64 +libblockdev-mdraid-2.24-8.el8.x86_64 +libblockdev-mpath-2.24-8.el8.x86_64 +libblockdev-nvdimm-2.24-8.el8.x86_64 +libblockdev-part-2.24-8.el8.x86_64 +libblockdev-plugins-all-2.24-8.el8.x86_64 +libblockdev-swap-2.24-8.el8.x86_64 +libblockdev-utils-2.24-8.el8.x86_64 +libblockdev-vdo-2.24-8.el8.x86_64 @@ -363 +371 @@ -libdnf-0.63.0-4.el8.x86_64 +libdnf-0.63.0-5.el8.x86_64 @@ -372 +380,2 @@ -libgcc-8.5.0-4.el8_5.x86_64 +libgcab1-1.1-1.el8.x86_64 +libgcc-8.5.0-6.el8.x86_64 @@ -384 +393 @@ -libgomp-8.5.0-4.el8_5.x86_64 +libgomp-8.5.0-6.el8.x86_64 @@ -390,0 +400 @@ +libgusb-0.3.0-1.el8.x86_64 @@ -404 +414 @@ -libldb-2.3.0-2.el8.x86_64 +libldb-2.4.1-1.el8.x86_64 @@ -407,0 +418 @@ +libmbim-1.26.0-2.el8.x86_64 @@ -435,0 +447 @@ +libqmi-1.30.2-1.el8.x86_64 @@ -458,0 +471 @@ +libsmbios-2.4.1-2.el8.x86_64 @@ -470 +483 @@ -libstdc++-8.5.0-4.el8_5.x86_64 +libstdc++-8.5.0-6.el8.x86_64 @@ -472 +485 @@ -libtalloc-2.3.2-1.el8.x86_64 +libtalloc-2.3.3-1.el8.x86_64 @@ -475 +488 @@ -libtdb-1.4.3-1.el8.x86_64 +libtdb-1.4.4-1.el8.x86_64 @@ -493,24 +506,24 @@ -libvirt-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-client-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-config-network-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-config-nwfilter-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-interface-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-network-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-nodedev-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-nwfilter-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-qemu-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-secret-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-storage-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-storage-core-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-storage-disk-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-storage-gluster-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-storage-iscsi-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-storage-iscsi-direct-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-storage-logical-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-storage-mpath-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-storage-rbd-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-driver-storage-scsi-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-daemon-kvm-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-libs-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 -libvirt-lock-sanlock-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-client-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-config-network-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-config-nwfilter-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-interface-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-network-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-nodedev-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-nwfilter-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-qemu-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-secret-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-storage-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-storage-core-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-storage-disk-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-storage-gluster-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-storage-iscsi-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-storage-iscsi-direct-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-storage-logical-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-storage-mpath-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-storage-rbd-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-driver-storage-scsi-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-daemon-kvm-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-libs-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 +libvirt-lock-sanlock-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 @@ -528,0 +542 @@ +libxmlb-0.1.15-1.el8.x86_64 @@ -533 +547 @@ -linux-firmware-20210702-103.gitd79c2677.el8.noarch +linux-firmware-20211119-105.gitf5d51956.el8.noarch @@ -536 +550 @@ -llvm-compat-libs-12.0.1-3.module_el8.6.0+1029+6594c364.x86_64 +llvm-compat-libs-12.0.1-4.module_el8.6.0+1041+0c503ac4.x86_64 @@ -546,2 +560,2 @@ -lvm2-2.03.14-1.el8.x86_64 -lvm2-libs-2.03.14-1.el8.x86_64 +lvm2-2.03.12-10.el8.x86_64 +lvm2-libs-2.03.12-10.el8.x86_64 @@ -557,0 +572 @@ +memtest86+-5.01-20.el8.x86_64 @@ -564,0 +580 @@ +mokutil-0.3.0-11.el8.x86_64 @@ -590 +606 @@ -nftables-0.9.3-23.el8.x86_64 +nftables-0.9.3-24.el8.x86_64 @@ -593,2 +609,2 @@ -nmstate-1.2.0-0.1.alpha1.el8.noarch -nmstate-plugin-ovsdb-1.2.0-0.1.alpha1.el8.noarch +nmstate-1.2.0-0.1.alpha2.el8.x86_64 +nmstate-plugin-ovsdb-1.2.0-0.1.alpha2.el8.noarch @@ -628,2 +644,2 @@ -ovirt-host-4.4.8-1.el8.x86_64 -ovirt-host-dependencies-4.4.8-1.el8.x86_64 +ovirt-host-4.4.9-2.el8.x86_64 +ovirt-host-dependencies-4.4.9-2.el8.x86_64 @@ -635 +651 @@ -ovirt-node-ng-image-update-placeholder-4.4.9.2-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.9.3-1.el8.noarch @@ -643,2 +659,2 @@ -ovirt-release-host-node-4.4.9.2-1.el8.noarch -ovirt-release44-4.4.9.2-1.el8.noarch +ovirt-release-host-node-4.4.9.3-1.el8.noarch +ovirt-release44-4.4.9.3-1.el8.noarch @@ -732 +748 @@ -python3-blockdev-2.24-7.el8.x86_64 +python3-blockdev-2.24-8.el8.x86_64 @@ -750,2 +766,2 @@ -python3-dnf-plugin-versionlock-4.0.21-6.el8.noarch -python3-dnf-plugins-core-4.0.21-6.el8.noarch +python3-dnf-plugin-versionlock-4.0.21-7.el8.noarch +python3-dnf-plugins-core-4.0.21-7.el8.noarch @@ -764 +780 @@ -python3-hawkey-0.63.0-4.el8.x86_64 +python3-hawkey-0.63.0-5.el8.x86_64 @@ -780 +796 @@ -python3-libdnf-0.63.0-4.el8.x86_64 +python3-libdnf-0.63.0-5.el8.x86_64 @@ -782 +798 @@ -python3-libnmstate-1.2.0-0.1.alpha1.el8.noarch +python3-libnmstate-1.2.0-0.1.alpha2.el8.noarch @@ -787 +803 @@ -python3-libvirt-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +python3-libvirt-7.10.0-1.module_el8.6.0+1046+bd8eec5e.x86_64 @@ -789 +805 @@ -python3-linux-procfs-0.6.3-3.el8.noarch +python3-linux-procfs-0.6.3-4.el8.noarch @@ -798 +814 @@ -python3-nftables-0.9.3-23.el8.x86_64 +python3-nftables-0.9.3-24.el8.x86_64 @@ -853 +869 @@ -python3-setools-4.3.0-2.el8.x86_64 +python3-setools-4.3.0-3.el8.x86_64 @@ -906,0 +923 @@ +rsyslog-openssl-8.2102.0-6.el8.x86_64 @@ -920,2 +937,2 @@ -selinux-policy-3.14.3-84.el8.noarch -selinux-policy-targeted-3.14.3-84.el8.noarch +selinux-policy-3.14.3-85.el8.noarch +selinux-policy-targeted-3.14.3-85.el8.noarch @@ -926 +943,3 @@ -shadow-utils-4.6-15.el8.x86_64 +shadow-utils-4.6-16.el8.x86_64 +shared-mime-info-1.9-3.el8.x86_64 +shim-x64-15-15.el8_2.x86_64 @@ -931 +950 @@ -sos-4.2-6.el8.noarch +sos-4.2-7.el8.noarch @@ -946 +965 @@ -sudo-1.8.29-7.el8_4.1.x86_64 +sudo-1.8.29-8.el8.x86_64 @@ -956 +975 @@ -sysstat-11.7.3-6.el8.x86_64 +sysstat-11.7.3-7.el8.x86_64 @@ -989,3 +1008,3 @@ -virt-install-3.2.0-1.el8.noarch -virt-manager-common-3.2.0-1.el8.noarch -virt-v2v-1.42.0-16.module_el8.6.0+983+a7505f3f.x86_64 +virt-install-3.2.0-2.el8.noarch +virt-manager-common-3.2.0-2.el8.noarch +virt-v2v-1.42.0-18.module_el8.6.0+1046+bd8eec5e.x86_64 @@ -995 +1014 @@ -xfsprogs-5.0.0-9.el8.x86_64 +xfsprogs-5.0.0-10.el8.x86_64 -- 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

Can't find build.xml for ant
by 천지환 15 Dec '21

15 Dec '21

Hi, i have trouble in 'ovirt-engine-extension-aaa-jdbc' when i follow the README.developer(https://github.com/jihwahn1018/ovirt-engine-extension-aaa-… i can't run '$ant check.IntegrationTest' because there is no build.xml where can i find it? Thanks, Jihwan

2 1

[OST] Documentation update needed
by Aviv Litman 15 Dec '21

15 Dec '21

Hi All, I tried to follow the steps documented in oVirt System Tests Docs <https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/inde…> . After consulting with Marcin, I understand that we haven't use ./run_suite.sh for a loong time now. I think the right command is for example: ./ost.sh run basic-suite-master el8stream --custom-repo= https://jenkins.ovirt.org/job/ovirt-dwh_standard-check-patch/1346/ We don't know who maintains this docs. Thanks! -- Aviv Litman BI Associate Software Engineer Red Hat <https://www.redhat.com/> alitman(a)redhat.com <https://www.redhat.com/>

3 3

CI not working again
by Milan Zamazal 14 Dec '21

14 Dec '21

Hi, it looks like Jenkins CI jobs don't finish in any reasonable time. In case of Vdsm, at least jenkins-psi2 jobs run but they fail early with Cannot download x86_64/python3-ioprocess-1.4.2-1.202111071801.git53786ff.el8.x86_64.rpm: All mirrors were tried Is there a way to get fixed at least one of the runners? Thanks, Milan

5 11

[ANN] oVirt Node 4.4.9.2 Async update
by Sandro Bonazzola 10 Dec '21

10 Dec '21

On December 10th 2021 the oVirt project released an async update of oVirt Node (4.4.9.2) delivering updates fixing CVEs: - CVE-2021-43267 <https://access.redhat.com/security/cve/CVE-2021-43267> [important] kernel: Insufficient validation of user-supplied sizes for the MSG_CRYPTO message type - CVE-2021-43527 <https://access.redhat.com/security/cve/CVE-2021-43527> [critical] nss: Memory corruption in decodeECorDsaSignature with DSA signatures (and RSA-PSS) And several other low/moderate CVEs. The oVirt project initially released a 4.4.9.1 version which contained a newer version of qemu-kvm (6.1.0) which has been reported as affected by a few severe bugs. A new version 4.4.9.2 has been issued reverting this. Here’s the full list of changes: --- ovirt-node-ng-image-4.4.9.1.manifest-rpm 2021-12-09 08:46:57.837930268 +0100 +++ ovirt-node-ng-image-4.4.9.2.manifest-rpm 2021-12-10 09:09:24.084642608 +0100 @@ -635 +635 @@ -ovirt-node-ng-image-update-placeholder-4.4.9.1-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.9.2-1.el8.noarch @@ -643,2 +643,2 @@ -ovirt-release-host-node-4.4.9.1-1.el8.noarch -ovirt-release44-4.4.9.1-1.el8.noarch +ovirt-release-host-node-4.4.9.2-1.el8.noarch +ovirt-release44-4.4.9.2-1.el8.noarch @@ -878,13 +878,13 @@ -qemu-img-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-block-curl-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-block-gluster-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-block-iscsi-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-block-rbd-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-block-ssh-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-common-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-core-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-docs-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-hw-usbredir-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-ui-opengl-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 -qemu-kvm-ui-spice-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-img-6.0.0-33.el8s.x86_64 +qemu-kvm-6.0.0-33.el8s.x86_64 +qemu-kvm-block-curl-6.0.0-33.el8s.x86_64 +qemu-kvm-block-gluster-6.0.0-33.el8s.x86_64 +qemu-kvm-block-iscsi-6.0.0-33.el8s.x86_64 +qemu-kvm-block-rbd-6.0.0-33.el8s.x86_64 +qemu-kvm-block-ssh-6.0.0-33.el8s.x86_64 +qemu-kvm-common-6.0.0-33.el8s.x86_64 +qemu-kvm-core-6.0.0-33.el8s.x86_64 +qemu-kvm-docs-6.0.0-33.el8s.x86_64 +qemu-kvm-hw-usbredir-6.0.0-33.el8s.x86_64 +qemu-kvm-ui-opengl-6.0.0-33.el8s.x86_64 +qemu-kvm-ui-spice-6.0.0-33.el8s.x86_64 --- ovirt-node-ng-image-4.4.9.manifest-rpm 2021-10-27 15:01:15.835959707 +0200 +++ ovirt-node-ng-image-4.4.9.1.manifest-rpm 2021-12-09 08:46:57.837930268 +0100 @@ -2,7 +2,6 @@ -ModemManager-glib-1.18.2-1.el8.x86_64 -NetworkManager-1.34.0-0.2.el8.x86_64 -NetworkManager-config-server-1.34.0-0.2.el8.noarch -NetworkManager-libnm-1.34.0-0.2.el8.x86_64 -NetworkManager-ovs-1.34.0-0.2.el8.x86_64 -NetworkManager-team-1.34.0-0.2.el8.x86_64 -NetworkManager-tui-1.34.0-0.2.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 @@ -44 +43 @@ -binutils-2.30-108.el8.x86_64 +binutils-2.30-111.el8.x86_64 @@ -46 +45 @@ -blivet-data-3.4.0-6.el8.noarch +blivet-data-3.4.0-7.el8.noarch @@ -48 +46,0 @@ -bubblewrap-0.4.0-1.el8.x86_64 @@ -51 +49 @@ -c-ares-1.13.0-5.el8.x86_64 +c-ares-1.13.0-6.el8.x86_64 @@ -59 +57 @@ -certmonger-0.79.13-4.el8.x86_64 +certmonger-0.79.13-5.el8.x86_64 @@ -63,6 +61,6 @@ -clevis-15-1.el8.x86_64 -clevis-dracut-15-1.el8.x86_64 -clevis-luks-15-1.el8.x86_64 -clevis-systemd-15-1.el8.x86_64 -cockpit-255-1.el8.x86_64 -cockpit-bridge-255-1.el8.x86_64 +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 @@ -70,3 +68,3 @@ -cockpit-storaged-251.1-1.el8.noarch -cockpit-system-255-1.el8.noarch -cockpit-ws-255-1.el8.x86_64 +cockpit-storaged-255-1.el8.noarch +cockpit-system-258-1.el8.noarch +cockpit-ws-258-1.el8.x86_64 @@ -81 +79 @@ -corosynclib-3.1.5-1.el8.x86_64 +corosynclib-3.1.5-2.el8.x86_64 @@ -88,2 +86,2 @@ -crypto-policies-20210617-1.gitc776d3e.el8.noarch -crypto-policies-scripts-20210617-1.gitc776d3e.el8.noarch +crypto-policies-20211116-1.gitae470d6.el8.noarch +crypto-policies-scripts-20211116-1.gitae470d6.el8.noarch @@ -92 +90 @@ -cups-libs-2.2.6-40.el8.x86_64 +cups-libs-2.2.6-41.el8.x86_64 @@ -98 +96 @@ -daxctl-libs-71.1-2.el8.x86_64 +daxctl-libs-71.1-3.el8.x86_64 @@ -105,7 +103,7 @@ -device-mapper-1.02.177-10.el8.x86_64 -device-mapper-event-1.02.177-10.el8.x86_64 -device-mapper-event-libs-1.02.177-10.el8.x86_64 -device-mapper-libs-1.02.177-10.el8.x86_64 -device-mapper-multipath-0.8.4-17.el8.x86_64 -device-mapper-multipath-libs-0.8.4-17.el8.x86_64 -device-mapper-persistent-data-0.9.0-4.el8.x86_64 +device-mapper-1.02.181-1.el8.x86_64 +device-mapper-event-1.02.181-1.el8.x86_64 +device-mapper-event-libs-1.02.181-1.el8.x86_64 +device-mapper-libs-1.02.181-1.el8.x86_64 +device-mapper-multipath-0.8.4-20.el8.x86_64 +device-mapper-multipath-libs-0.8.4-20.el8.x86_64 +device-mapper-persistent-data-0.9.0-5.el8.x86_64 @@ -117,4 +115,4 @@ -dnf-4.7.0-4.el8.noarch -dnf-data-4.7.0-4.el8.noarch -dnf-plugins-core-4.0.21-3.el8.noarch -dnsmasq-2.79-19.el8.x86_64 +dnf-4.7.0-5.el8.noarch +dnf-data-4.7.0-5.el8.noarch +dnf-plugins-core-4.0.21-6.el8.noarch +dnsmasq-2.79-20.el8.x86_64 @@ -130,8 +128,5 @@ -efi-filesystem-3-3.el8.noarch -efibootmgr-16-1.el8.x86_64 -efivar-libs-37-4.el8.x86_64 -elfutils-0.185-1.el8.x86_64 -elfutils-default-yama-scope-0.185-1.el8.noarch -elfutils-libelf-0.185-1.el8.x86_64 -elfutils-libs-0.185-1.el8.x86_64 -ethtool-5.8-7.el8.x86_64 +elfutils-0.186-1.el8.x86_64 +elfutils-default-yama-scope-0.186-1.el8.noarch +elfutils-libelf-0.186-1.el8.x86_64 +elfutils-libs-0.186-1.el8.x86_64 +ethtool-5.13-1.el8.x86_64 @@ -139,38 +134,38 @@ -fence-agents-all-4.2.1-78.el8.x86_64 -fence-agents-amt-ws-4.2.1-78.el8.noarch -fence-agents-apc-4.2.1-78.el8.noarch -fence-agents-apc-snmp-4.2.1-78.el8.noarch -fence-agents-bladecenter-4.2.1-78.el8.noarch -fence-agents-brocade-4.2.1-78.el8.noarch -fence-agents-cisco-mds-4.2.1-78.el8.noarch -fence-agents-cisco-ucs-4.2.1-78.el8.noarch -fence-agents-common-4.2.1-78.el8.noarch -fence-agents-compute-4.2.1-78.el8.noarch -fence-agents-drac5-4.2.1-78.el8.noarch -fence-agents-eaton-snmp-4.2.1-78.el8.noarch -fence-agents-emerson-4.2.1-78.el8.noarch -fence-agents-eps-4.2.1-78.el8.noarch -fence-agents-heuristics-ping-4.2.1-78.el8.noarch -fence-agents-hpblade-4.2.1-78.el8.noarch -fence-agents-ibm-powervs-4.2.1-78.el8.noarch -fence-agents-ibm-vpc-4.2.1-78.el8.noarch -fence-agents-ibmblade-4.2.1-78.el8.noarch -fence-agents-ifmib-4.2.1-78.el8.noarch -fence-agents-ilo-moonshot-4.2.1-78.el8.noarch -fence-agents-ilo-mp-4.2.1-78.el8.noarch -fence-agents-ilo-ssh-4.2.1-78.el8.noarch -fence-agents-ilo2-4.2.1-78.el8.noarch -fence-agents-intelmodular-4.2.1-78.el8.noarch -fence-agents-ipdu-4.2.1-78.el8.noarch -fence-agents-ipmilan-4.2.1-78.el8.noarch -fence-agents-kdump-4.2.1-78.el8.x86_64 -fence-agents-mpath-4.2.1-78.el8.noarch -fence-agents-redfish-4.2.1-78.el8.x86_64 -fence-agents-rhevm-4.2.1-78.el8.noarch -fence-agents-rsa-4.2.1-78.el8.noarch -fence-agents-rsb-4.2.1-78.el8.noarch -fence-agents-sbd-4.2.1-78.el8.noarch -fence-agents-scsi-4.2.1-78.el8.noarch -fence-agents-vmware-rest-4.2.1-78.el8.noarch -fence-agents-vmware-soap-4.2.1-78.el8.noarch -fence-agents-wti-4.2.1-78.el8.noarch +fence-agents-all-4.2.1-83.el8.x86_64 +fence-agents-amt-ws-4.2.1-83.el8.noarch +fence-agents-apc-4.2.1-83.el8.noarch +fence-agents-apc-snmp-4.2.1-83.el8.noarch +fence-agents-bladecenter-4.2.1-83.el8.noarch +fence-agents-brocade-4.2.1-83.el8.noarch +fence-agents-cisco-mds-4.2.1-83.el8.noarch +fence-agents-cisco-ucs-4.2.1-83.el8.noarch +fence-agents-common-4.2.1-83.el8.noarch +fence-agents-compute-4.2.1-83.el8.noarch +fence-agents-drac5-4.2.1-83.el8.noarch +fence-agents-eaton-snmp-4.2.1-83.el8.noarch +fence-agents-emerson-4.2.1-83.el8.noarch +fence-agents-eps-4.2.1-83.el8.noarch +fence-agents-heuristics-ping-4.2.1-83.el8.noarch +fence-agents-hpblade-4.2.1-83.el8.noarch +fence-agents-ibm-powervs-4.2.1-83.el8.noarch +fence-agents-ibm-vpc-4.2.1-83.el8.noarch +fence-agents-ibmblade-4.2.1-83.el8.noarch +fence-agents-ifmib-4.2.1-83.el8.noarch +fence-agents-ilo-moonshot-4.2.1-83.el8.noarch +fence-agents-ilo-mp-4.2.1-83.el8.noarch +fence-agents-ilo-ssh-4.2.1-83.el8.noarch +fence-agents-ilo2-4.2.1-83.el8.noarch +fence-agents-intelmodular-4.2.1-83.el8.noarch +fence-agents-ipdu-4.2.1-83.el8.noarch +fence-agents-ipmilan-4.2.1-83.el8.noarch +fence-agents-kdump-4.2.1-83.el8.x86_64 +fence-agents-mpath-4.2.1-83.el8.noarch +fence-agents-redfish-4.2.1-83.el8.x86_64 +fence-agents-rhevm-4.2.1-83.el8.noarch +fence-agents-rsa-4.2.1-83.el8.noarch +fence-agents-rsb-4.2.1-83.el8.noarch +fence-agents-sbd-4.2.1-83.el8.noarch +fence-agents-scsi-4.2.1-83.el8.noarch +fence-agents-vmware-rest-4.2.1-83.el8.noarch +fence-agents-vmware-soap-4.2.1-83.el8.noarch +fence-agents-wti-4.2.1-83.el8.noarch @@ -182,2 +177,2 @@ -firewalld-0.9.3-7.el8.noarch -firewalld-filesystem-0.9.3-7.el8.noarch +firewalld-0.9.3-11.el8.noarch +firewalld-filesystem-0.9.3-11.el8.noarch @@ -193 +187,0 @@ -fwupd-1.5.9-1.el8.x86_64 @@ -196 +190 @@ -gdb-headless-8.2-16.el8.x86_64 +gdb-headless-8.2-17.el8.x86_64 @@ -199 +193 @@ -gdisk-1.0.3-6.el8.x86_64 +gdisk-1.0.3-8.el8.x86_64 @@ -203 +197 @@ -git-core-2.27.0-1.el8.x86_64 +git-core-2.31.1-2.el8.x86_64 @@ -206,4 +200,4 @@ -glibc-2.28-167.el8.x86_64 -glibc-common-2.28-167.el8.x86_64 -glibc-gconv-extra-2.28-167.el8.x86_64 -glibc-langpack-en-2.28-167.el8.x86_64 +glibc-2.28-170.el8.x86_64 +glibc-common-2.28-170.el8.x86_64 +glibc-gconv-extra-2.28-170.el8.x86_64 +glibc-langpack-en-2.28-170.el8.x86_64 @@ -235,7 +229,6 @@ -grub2-common-2.02-99.el8_4.1.noarch -grub2-efi-x64-2.02-99.el8_4.1.x86_64 -grub2-pc-2.02-99.el8_4.1.x86_64 -grub2-pc-modules-2.02-99.el8_4.1.noarch -grub2-tools-2.02-99.el8_4.1.x86_64 -grub2-tools-extra-2.02-99.el8_4.1.x86_64 -grub2-tools-minimal-2.02-99.el8_4.1.x86_64 +grub2-common-2.02-106.el8.noarch +grub2-pc-2.02-106.el8.x86_64 +grub2-pc-modules-2.02-106.el8.noarch +grub2-tools-2.02-106.el8.x86_64 +grub2-tools-extra-2.02-106.el8.x86_64 +grub2-tools-minimal-2.02-106.el8.x86_64 @@ -251 +244 @@ -hivex-1.3.18-22.el8s.x86_64 +hivex-1.3.18-23.module_el8.6.0+983+a7505f3f.x86_64 @@ -259 +251,0 @@ -iotop-0.6-16.el8.noarch @@ -267,2 +259,2 @@ -iproute-5.12.0-4.el8.x86_64 -iproute-tc-5.12.0-4.el8.x86_64 +iproute-5.15.0-1.el8.x86_64 +iproute-tc-5.15.0-1.el8.x86_64 @@ -272,3 +264,3 @@ -iptables-1.8.4-21.el8.x86_64 -iptables-ebtables-1.8.4-21.el8.x86_64 -iptables-libs-1.8.4-21.el8.x86_64 +iptables-1.8.4-22.el8.x86_64 +iptables-ebtables-1.8.4-22.el8.x86_64 +iptables-libs-1.8.4-22.el8.x86_64 @@ -295 +287 @@ -jansson-2.12-5.el8.x86_64 +jansson-2.14-1.el8.x86_64 @@ -298 +290 @@ -json-c-0.13.1-2.el8.x86_64 +json-c-0.13.1-3.el8.x86_64 @@ -303,6 +295,6 @@ -kernel-4.18.0-348.el8.x86_64 -kernel-core-4.18.0-348.el8.x86_64 -kernel-modules-4.18.0-348.el8.x86_64 -kernel-tools-4.18.0-348.el8.x86_64 -kernel-tools-libs-4.18.0-348.el8.x86_64 -kexec-tools-2.0.20-59.el8.x86_64 +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 @@ -311,4 +303,4 @@ -kmod-25-18.el8.x86_64 -kmod-kvdo-6.2.5.72-79.el8.x86_64 -kmod-libs-25-18.el8.x86_64 -kpartx-0.8.4-17.el8.x86_64 +kmod-25-19.el8.x86_64 +kmod-kvdo-6.2.5.72-81.el8.x86_64 +kmod-libs-25-19.el8.x86_64 +kpartx-0.8.4-20.el8.x86_64 @@ -355 +347 @@ -libbpf-0.4.0-1.el8.x86_64 +libbpf-0.4.0-2.el8.x86_64 @@ -362 +354 @@ -libcomps-0.1.16-2.el8.x86_64 +libcomps-0.1.18-1.el8.x86_64 @@ -371,2 +363,2 @@ -libdnf-0.63.0-3.el8.x86_64 -libdrm-2.4.106-2.el8.x86_64 +libdnf-0.63.0-4.el8.x86_64 +libdrm-2.4.108-1.el8.x86_64 @@ -379,3 +371,2 @@ -libffi-3.1-22.el8.x86_64 -libgcab1-1.1-1.el8.x86_64 -libgcc-8.5.0-3.el8.x86_64 +libffi-3.1-23.el8.x86_64 +libgcc-8.5.0-4.el8_5.x86_64 @@ -389,5 +380,5 @@ -libglvnd-1.3.2-1.el8.x86_64 -libglvnd-egl-1.3.2-1.el8.x86_64 -libglvnd-gles-1.3.2-1.el8.x86_64 -libglvnd-glx-1.3.2-1.el8.x86_64 -libgomp-8.5.0-3.el8.x86_64 +libglvnd-1.3.4-1.el8.x86_64 +libglvnd-egl-1.3.4-1.el8.x86_64 +libglvnd-gles-1.3.4-1.el8.x86_64 +libglvnd-glx-1.3.4-1.el8.x86_64 +libgomp-8.5.0-4.el8_5.x86_64 @@ -396,5 +387,5 @@ -libguestfs-1.44.0-3.el8s.x86_64 -libguestfs-tools-c-1.44.0-3.el8s.x86_64 -libguestfs-winsupport-8.2-2.el8s.x86_64 -libgusb-0.3.0-1.el8.x86_64 -libibverbs-35.0-1.el8.x86_64 +libguestfs-1.44.0-4.module_el8.6.0+983+a7505f3f.x86_64 +libguestfs-appliance-1.44.0-4.module_el8.6.0+983+a7505f3f.x86_64 +libguestfs-tools-c-1.44.0-4.module_el8.6.0+983+a7505f3f.x86_64 +libguestfs-winsupport-8.6-1.module_el8.6.0+983+a7505f3f.x86_64 +libibverbs-37.1-1.el8.x86_64 @@ -404 +395 @@ -libipa_hbac-2.5.2-2.el8.x86_64 +libipa_hbac-2.5.2-2.el8_5.1.x86_64 @@ -406 +397 @@ -libiscsi-1.18.0-8.module_el8.5.0+746+bbd5d70c.x86_64 +libiscsi-1.18.0-8.module_el8.6.0+983+a7505f3f.x86_64 @@ -417 +407,0 @@ -libmbim-1.26.0-2.el8.x86_64 @@ -425 +415 @@ -libnfsidmap-2.3.3-46.el8.x86_64 +libnfsidmap-2.3.3-47.el8.x86_64 @@ -446 +435,0 @@ -libqmi-1.30.2-1.el8.x86_64 @@ -451,2 +440,2 @@ -librdkafka-0.11.4-1.el8.x86_64 -librdmacm-35.0-1.el8.x86_64 +librdkafka-0.11.4-3.el8.x86_64 +librdmacm-37.1-1.el8.x86_64 @@ -454 +443 @@ -librepo-1.14.0-2.el8.x86_64 +librepo-1.14.2-1.el8.x86_64 @@ -463 +452 @@ -libseccomp-2.5.1-1.el8.x86_64 +libseccomp-2.5.2-1.el8.x86_64 @@ -470,2 +459 @@ -libsmbios-2.4.1-2.el8.x86_64 -libsolv-0.7.19-1.el8.x86_64 +libsolv-0.7.20-1.el8.x86_64 @@ -474,9 +462,9 @@ -libssh-0.9.4-3.el8.x86_64 -libssh-config-0.9.4-3.el8.noarch -libsss_autofs-2.5.2-2.el8.x86_64 -libsss_certmap-2.5.2-2.el8.x86_64 -libsss_idmap-2.5.2-2.el8.x86_64 -libsss_nss_idmap-2.5.2-2.el8.x86_64 -libsss_simpleifp-2.5.2-2.el8.x86_64 -libsss_sudo-2.5.2-2.el8.x86_64 -libstdc++-8.5.0-3.el8.x86_64 +libssh-0.9.6-3.el8.x86_64 +libssh-config-0.9.6-3.el8.noarch +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-4.el8_5.x86_64 @@ -492 +480 @@ -libtirpc-1.1.4-5.el8.x86_64 +libtirpc-1.1.4-6.el8.x86_64 @@ -494 +482 @@ -libtpms-0.7.4-6.20201106git2452a24dab.el8s.x86_64 +libtpms-0.7.4-6.20201106git2452a24dab.module_el8.6.0+983+a7505f3f.x86_64 @@ -500 +488 @@ -libuser-0.62-23.el8.x86_64 +libuser-0.62-24.el8.x86_64 @@ -505,24 +493,24 @@ -libvirt-7.6.0-4.el8s.x86_64 -libvirt-client-7.6.0-4.el8s.x86_64 -libvirt-daemon-7.6.0-4.el8s.x86_64 -libvirt-daemon-config-network-7.6.0-4.el8s.x86_64 -libvirt-daemon-config-nwfilter-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-interface-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-network-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-nodedev-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-nwfilter-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-qemu-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-secret-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-storage-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-storage-core-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-storage-disk-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-storage-gluster-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-storage-iscsi-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-storage-iscsi-direct-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-storage-logical-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-storage-mpath-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-storage-rbd-7.6.0-4.el8s.x86_64 -libvirt-daemon-driver-storage-scsi-7.6.0-4.el8s.x86_64 -libvirt-daemon-kvm-7.6.0-4.el8s.x86_64 -libvirt-libs-7.6.0-4.el8s.x86_64 -libvirt-lock-sanlock-7.6.0-4.el8s.x86_64 +libvirt-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-client-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-config-network-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-config-nwfilter-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-interface-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-network-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-nodedev-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-nwfilter-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-qemu-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-secret-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-storage-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-storage-core-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-storage-disk-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-storage-gluster-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-storage-iscsi-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-storage-iscsi-direct-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-storage-logical-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-storage-mpath-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-storage-rbd-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-driver-storage-scsi-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-daemon-kvm-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-libs-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 +libvirt-lock-sanlock-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 @@ -541 +528,0 @@ -libxmlb-0.1.15-1.el8.x86_64 @@ -549 +536 @@ -llvm-libs-12.0.1-2.module_el8.6.0+937+1cafe22c.x86_64 +llvm-compat-libs-12.0.1-3.module_el8.6.0+1029+6594c364.x86_64 @@ -559,2 +546,2 @@ -lvm2-2.03.12-10.el8.x86_64 -lvm2-libs-2.03.12-10.el8.x86_64 +lvm2-2.03.14-1.el8.x86_64 +lvm2-libs-2.03.14-1.el8.x86_64 @@ -571,7 +558,6 @@ -memtest86+-5.01-20.el8.x86_64 -mesa-dri-drivers-21.1.5-1.el8.x86_64 -mesa-filesystem-21.1.5-1.el8.x86_64 -mesa-libEGL-21.1.5-1.el8.x86_64 -mesa-libGL-21.1.5-1.el8.x86_64 -mesa-libgbm-21.1.5-1.el8.x86_64 -mesa-libglapi-21.1.5-1.el8.x86_64 +mesa-dri-drivers-21.3.0-1.el8.x86_64 +mesa-filesystem-21.3.0-1.el8.x86_64 +mesa-libEGL-21.3.0-1.el8.x86_64 +mesa-libGL-21.3.0-1.el8.x86_64 +mesa-libgbm-21.3.0-1.el8.x86_64 +mesa-libglapi-21.3.0-1.el8.x86_64 @@ -579 +564,0 @@ -mokutil-0.3.0-11.el8.x86_64 @@ -584,8 +569,8 @@ -nbdkit-1.24.0-1.el8s.x86_64 -nbdkit-basic-filters-1.24.0-1.el8s.x86_64 -nbdkit-basic-plugins-1.24.0-1.el8s.x86_64 -nbdkit-curl-plugin-1.24.0-1.el8s.x86_64 -nbdkit-python-plugin-1.24.0-1.el8s.x86_64 -nbdkit-server-1.24.0-1.el8s.x86_64 -nbdkit-ssh-plugin-1.24.0-1.el8s.x86_64 -nbdkit-vddk-plugin-1.24.0-1.el8s.x86_64 +nbdkit-1.24.0-3.module_el8.6.0+983+a7505f3f.x86_64 +nbdkit-basic-filters-1.24.0-3.module_el8.6.0+983+a7505f3f.x86_64 +nbdkit-basic-plugins-1.24.0-3.module_el8.6.0+983+a7505f3f.x86_64 +nbdkit-curl-plugin-1.24.0-3.module_el8.6.0+983+a7505f3f.x86_64 +nbdkit-python-plugin-1.24.0-3.module_el8.6.0+983+a7505f3f.x86_64 +nbdkit-server-1.24.0-3.module_el8.6.0+983+a7505f3f.x86_64 +nbdkit-ssh-plugin-1.24.0-3.module_el8.6.0+983+a7505f3f.x86_64 +nbdkit-vddk-plugin-1.24.0-3.module_el8.6.0+983+a7505f3f.x86_64 @@ -595,7 +580,7 @@ -ndctl-71.1-2.el8.x86_64 -ndctl-libs-71.1-2.el8.x86_64 -net-snmp-5.8-22.el8.x86_64 -net-snmp-agent-libs-5.8-22.el8.x86_64 -net-snmp-libs-5.8-22.el8.x86_64 -net-snmp-utils-5.8-22.el8.x86_64 -netcf-libs-0.2.8-12.module_el8.5.0+746+bbd5d70c.x86_64 +ndctl-71.1-3.el8.x86_64 +ndctl-libs-71.1-3.el8.x86_64 +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 +netcf-libs-0.2.8-12.module_el8.6.0+983+a7505f3f.x86_64 @@ -604,3 +589,3 @@ -nfs-utils-2.3.3-46.el8.x86_64 -nftables-0.9.3-22.el8.x86_64 -nispor-1.1.1-1.el8.x86_64 +nfs-utils-2.3.3-47.el8.x86_64 +nftables-0.9.3-23.el8.x86_64 +nispor-1.2.2-1.el8.x86_64 @@ -612,6 +597,6 @@ -nss-3.67.0-6.el8_4.x86_64 -nss-softokn-3.67.0-6.el8_4.x86_64 -nss-softokn-freebl-3.67.0-6.el8_4.x86_64 -nss-sysinit-3.67.0-6.el8_4.x86_64 -nss-tools-3.67.0-6.el8_4.x86_64 -nss-util-3.67.0-6.el8_4.x86_64 +nss-3.67.0-7.el8_5.x86_64 +nss-softokn-3.67.0-7.el8_5.x86_64 +nss-softokn-freebl-3.67.0-7.el8_5.x86_64 +nss-sysinit-3.67.0-7.el8_5.x86_64 +nss-tools-3.67.0-7.el8_5.x86_64 +nss-util-3.67.0-7.el8_5.x86_64 @@ -626,7 +611,7 @@ -openscap-1.3.5-6.el8.x86_64 -openscap-scanner-1.3.5-6.el8.x86_64 -openssh-8.0p1-9.el8.x86_64 -openssh-clients-8.0p1-9.el8.x86_64 -openssh-server-8.0p1-9.el8.x86_64 -openssl-1.1.1k-4.el8.x86_64 -openssl-libs-1.1.1k-4.el8.x86_64 +openscap-1.3.5-10.el8.x86_64 +openscap-scanner-1.3.5-10.el8.x86_64 +openssh-8.0p1-12.el8.x86_64 +openssh-clients-8.0p1-12.el8.x86_64 +openssh-server-8.0p1-12.el8.x86_64 +openssl-1.1.1k-5.el8_5.x86_64 +openssl-libs-1.1.1k-5.el8_5.x86_64 @@ -643,2 +628,2 @@ -ovirt-host-4.4.9-2.el8.x86_64 -ovirt-host-dependencies-4.4.9-2.el8.x86_64 +ovirt-host-4.4.8-1.el8.x86_64 +ovirt-host-dependencies-4.4.8-1.el8.x86_64 @@ -650 +635 @@ -ovirt-node-ng-image-update-placeholder-4.4.9-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.9.1-1.el8.noarch @@ -658,2 +643,2 @@ -ovirt-release-host-node-4.4.9-1.el8.noarch -ovirt-release44-4.4.9-1.el8.noarch +ovirt-release-host-node-4.4.9.1-1.el8.noarch +ovirt-release44-4.4.9.1-1.el8.noarch @@ -666,3 +651,3 @@ -pacemaker-cluster-libs-2.1.0-8.el8.x86_64 -pacemaker-libs-2.1.0-8.el8.x86_64 -pacemaker-schemas-2.1.0-8.el8.noarch +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 @@ -673 +657,0 @@ -pciutils-3.7.0-1.el8.x86_64 @@ -683 +667 @@ -perl-Errno-1.28-420.el8.x86_64 +perl-Errno-1.28-421.el8.x86_64 @@ -689 +673 @@ -perl-IO-1.38-420.el8.x86_64 +perl-IO-1.38-421.el8.x86_64 @@ -706,3 +690,3 @@ -perl-interpreter-5.26.3-420.el8.x86_64 -perl-libs-5.26.3-420.el8.x86_64 -perl-macros-5.26.3-420.el8.x86_64 +perl-interpreter-5.26.3-421.el8.x86_64 +perl-libs-5.26.3-421.el8.x86_64 +perl-macros-5.26.3-421.el8.x86_64 @@ -723,2 +707,2 @@ -policycoreutils-2.9-16.el8.x86_64 -policycoreutils-python-utils-2.9-16.el8.noarch +policycoreutils-2.9-17.el8.x86_64 +policycoreutils-python-utils-2.9-17.el8.noarch @@ -747 +731 @@ -python3-blivet-3.4.0-6.el8.noarch +python3-blivet-3.4.0-7.el8.noarch @@ -765,3 +749,3 @@ -python3-dnf-4.7.0-4.el8.noarch -python3-dnf-plugin-versionlock-4.0.21-3.el8.noarch -python3-dnf-plugins-core-4.0.21-3.el8.noarch +python3-dnf-4.7.0-5.el8.noarch +python3-dnf-plugin-versionlock-4.0.21-6.el8.noarch +python3-dnf-plugins-core-4.0.21-6.el8.noarch @@ -773 +757 @@ -python3-firewall-0.9.3-7.el8.noarch +python3-firewall-0.9.3-11.el8.noarch @@ -780 +764 @@ -python3-hawkey-0.63.0-3.el8.x86_64 +python3-hawkey-0.63.0-4.el8.x86_64 @@ -795,3 +779,3 @@ -python3-libcomps-0.1.16-2.el8.x86_64 -python3-libdnf-0.63.0-3.el8.x86_64 -python3-libipa_hbac-2.5.2-2.el8.x86_64 +python3-libcomps-0.1.18-1.el8.x86_64 +python3-libdnf-0.63.0-4.el8.x86_64 +python3-libipa_hbac-2.5.2-2.el8_5.1.x86_64 @@ -803 +787 @@ -python3-libvirt-7.6.0-1.el8s.x86_64 +python3-libvirt-7.9.0-1.module_el8.6.0+983+a7505f3f.x86_64 @@ -805 +789 @@ -python3-linux-procfs-0.6.3-1.el8.noarch +python3-linux-procfs-0.6.3-3.el8.noarch @@ -814,2 +798,2 @@ -python3-nftables-0.9.3-22.el8.x86_64 -python3-nispor-1.1.1-1.el8.noarch +python3-nftables-0.9.3-23.el8.x86_64 +python3-nispor-1.2.2-1.el8.noarch @@ -821 +805 @@ -python3-oslo-context-3.1.1-2.el8.noarch +python3-oslo-context-3.1.2-1.el8.noarch @@ -837 +821 @@ -python3-perf-4.18.0-348.el8.x86_64 +python3-perf-4.18.0-348.2.1.el8_5.x86_64 @@ -842 +826 @@ -python3-policycoreutils-2.9-16.el8.noarch +python3-policycoreutils-2.9-17.el8.noarch @@ -875,3 +859,3 @@ -python3-sss-2.5.2-2.el8.x86_64 -python3-sss-murmur-2.5.2-2.el8.x86_64 -python3-sssdconfig-2.5.2-2.el8.noarch +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 @@ -893,14 +877,14 @@ -qemu-guest-agent-6.0.0-33.el8s.x86_64 -qemu-img-6.0.0-33.el8s.x86_64 -qemu-kvm-6.0.0-33.el8s.x86_64 -qemu-kvm-block-curl-6.0.0-33.el8s.x86_64 -qemu-kvm-block-gluster-6.0.0-33.el8s.x86_64 -qemu-kvm-block-iscsi-6.0.0-33.el8s.x86_64 -qemu-kvm-block-rbd-6.0.0-33.el8s.x86_64 -qemu-kvm-block-ssh-6.0.0-33.el8s.x86_64 -qemu-kvm-common-6.0.0-33.el8s.x86_64 -qemu-kvm-core-6.0.0-33.el8s.x86_64 -qemu-kvm-docs-6.0.0-33.el8s.x86_64 -qemu-kvm-hw-usbredir-6.0.0-33.el8s.x86_64 -qemu-kvm-ui-opengl-6.0.0-33.el8s.x86_64 -qemu-kvm-ui-spice-6.0.0-33.el8s.x86_64 +qemu-guest-agent-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-img-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-block-curl-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-block-gluster-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-block-iscsi-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-block-rbd-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-block-ssh-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-common-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-core-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-docs-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-hw-usbredir-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-ui-opengl-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 +qemu-kvm-ui-spice-6.1.0-5.module_el8.6.0+1040+0ae94936.x86_64 @@ -910 +893,0 @@ -rdma-core-35.0-1.el8.x86_64 @@ -912 +895 @@ -rng-tools-6.13-1.git.d207e0b6.el8.x86_64 +rng-tools-6.14-4.git.b2b7934e.el8.x86_64 @@ -920,5 +903,4 @@ -rsyslog-8.2102.0-5.el8.x86_64 -rsyslog-elasticsearch-8.2102.0-5.el8.x86_64 -rsyslog-mmjsonparse-8.2102.0-5.el8.x86_64 -rsyslog-mmnormalize-8.2102.0-5.el8.x86_64 -rsyslog-openssl-8.2102.0-5.el8.x86_64 +rsyslog-8.2102.0-6.el8.x86_64 +rsyslog-elasticsearch-8.2102.0-6.el8.x86_64 +rsyslog-mmjsonparse-8.2102.0-6.el8.x86_64 +rsyslog-mmnormalize-8.2102.0-6.el8.x86_64 @@ -935,2 +917,2 @@ -seabios-bin-1.14.0-1.el8s.noarch -seavgabios-bin-1.14.0-1.el8s.noarch +seabios-bin-1.14.0-1.module_el8.6.0+983+a7505f3f.noarch +seavgabios-bin-1.14.0-1.module_el8.6.0+983+a7505f3f.noarch @@ -938,2 +920,2 @@ -selinux-policy-3.14.3-81.el8.noarch -selinux-policy-targeted-3.14.3-81.el8.noarch +selinux-policy-3.14.3-84.el8.noarch +selinux-policy-targeted-3.14.3-84.el8.noarch @@ -943,4 +925,2 @@ -sgabios-bin-0.20170427git-3.module_el8.5.0+746+bbd5d70c.noarch -shadow-utils-4.6-14.el8.x86_64 -shared-mime-info-1.9-3.el8.x86_64 -shim-x64-15-15.el8_2.x86_64 +sgabios-bin-0.20170427git-3.module_el8.6.0+983+a7505f3f.noarch +shadow-utils-4.6-15.el8.x86_64 @@ -951 +931 @@ -sos-4.1-5.el8.noarch +sos-4.2-6.el8.noarch @@ -956,9 +936,9 @@ -sshpass-1.06-9.el8.x86_64 -sssd-client-2.5.2-2.el8.x86_64 -sssd-common-2.5.2-2.el8.x86_64 -sssd-common-pac-2.5.2-2.el8.x86_64 -sssd-dbus-2.5.2-2.el8.x86_64 -sssd-ipa-2.5.2-2.el8.x86_64 -sssd-kcm-2.5.2-2.el8.x86_64 -sssd-krb5-common-2.5.2-2.el8.x86_64 -sssd-tools-2.5.2-2.el8.x86_64 +sshpass-1.09-4.el8.x86_64 +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 @@ -966,5 +946,5 @@ -sudo-1.8.29-7.el8.x86_64 -supermin-5.2.1-1.el8s.x86_64 -swtpm-0.6.0-2.20210607gitea627b3.el8s.x86_64 -swtpm-libs-0.6.0-2.20210607gitea627b3.el8s.x86_64 -swtpm-tools-0.6.0-2.20210607gitea627b3.el8s.x86_64 +sudo-1.8.29-7.el8_4.1.x86_64 +supermin-5.2.1-1.module_el8.6.0+983+a7505f3f.x86_64 +swtpm-0.6.0-2.20210607gitea627b3.module_el8.6.0+983+a7505f3f.x86_64 +swtpm-libs-0.6.0-2.20210607gitea627b3.module_el8.6.0+983+a7505f3f.x86_64 +swtpm-tools-0.6.0-2.20210607gitea627b3.module_el8.6.0+983+a7505f3f.x86_64 @@ -990 +970 @@ -tzdata-2021c-1.el8.noarch +tzdata-2021e-1.el8.noarch @@ -997 +977 @@ -vdo-6.2.5.74-14.el8.x86_64 +vdo-6.2.6.7-14.el8.x86_64 @@ -1008,4 +988,4 @@ -vim-minimal-8.0.1763-16.el8.x86_64 -virt-install-2.2.1-4.el8.noarch -virt-manager-common-2.2.1-4.el8.noarch -virt-v2v-1.42.0-15.el8s.x86_64 +vim-minimal-8.0.1763-16.el8_5.2.x86_64 +virt-install-3.2.0-1.el8.noarch +virt-manager-common-3.2.0-1.el8.noarch +virt-v2v-1.42.0-16.module_el8.6.0+983+a7505f3f.x86_64 @@ -1014 +994 @@ -which-2.21-16.el8.x86_64 +which-2.21-17.el8.x86_64 @@ -1025 +1005 @@ -yum-4.7.0-4.el8.noarch +yum-4.7.0-5.el8.noarch -- 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

Helper script
by Ales Musil 09 Dec '21

09 Dec '21

Hi, with recent switch to GH I made myself a little helper to sync fork and rebase your branch on top of that. Hopefully someone will find it useful. The usage is "./script.sh $NAME_OF_MASTER" (usually master for gerrit projects, newer GH have main). #!/bin/bash -e ORIGIN=$(git branch --show-current) # Go to master/main/base (gco) git checkout $1 # Fetch all remotes (gfa) git fetch --all --prune # Merge upstream remote into master/main/base (gm) git merge upstream/$1 # Push master/main/base into origin (gp) git push origin $(git branch --show-current) # Switch back to previous branch (gco) git checkout $ORIGIN # Rebase the branch (gl) git pull --rebase Best regards, Ales -- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

1 0

Help installing oVirt on single machine, without cockpit
by Cameronsplaze222＠gmail.com 08 Dec '21

08 Dec '21

I'm trying to have a single machine, run both the engine (so I get the API), and hypervisor itself to run VM's on. My goal is to write some custom scripts that use the API, so I'm hoping cockpit isn't needed. I've tried two different routes, but both got blocked eventually. Maybe someone has an idea on how to continue? # Using CentOS 9 stream: Tried following the directions [here](https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_…, but in 3.2 where you add the modules, they couldn't be found. I tried skipping it, but in 3.3.2 where you run `dnf install ovirt-engine`, it says ovirt-engine doesn't exist. The closest thing I see is `ovirt-hosted-engine-setup-2.5.4-1.el9.noarch`, is that what I want maybe? # Using oVirt node iso, and installing an engine to that: I added the networking to the install, but it didn't save to the machine itself, and I wasn't sure on how to add it. I tried hooking a direct cable, but still unable to ping 8.8.8.8, or anything. My goal is for a minimal installation, only running the API and hypervisor, so I'm definitely open to other routes too. Is this something that's possible to do?

1 0

Switching to GH actions build: some not-yet-clear parts and some tips
by Martin Perina 06 Dec '21

06 Dec '21

Hi, I've tried to move ovirt-engine-extensions-api <https://github.com/ovirt/ovirt-engine-extensions-api> to github and setup GH action to build to have some sort of a basic template for all our Java based projects: https://github.com/oVirt/ovirt-engine-extensions-api/blob/master/.github/wo… During the work I discovered some parts which should be further discussed: 1. Most of projects requires packages from ovirt-master-release RPM repositories to build itself - In past we have been using https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm to fetch the latest version of this RPM - Do we plan to keep it and have this URL as the main source for oVirt master repositories? - ovirt-engine-extensions-api projects requires only Virt SIG repo so I've applied below hack to provide it: https://github.com/oVirt/ovirt-engine-extensions-api/blob/master/.automatio… - I don't like the solution, it would be much nicer to have a constant URL for the latest ovirt-release-master RPM 2. Providing RPM repositories for different OS inside single build artifact - I wanted to build the project for both CentOS Stream 8 and 9, but I figured out that upload-artifact action merges results for all different OS builds into a single directory, so created repositories are mixed together. - I've use GH strategy option and used centos-stream-8 for CS8 and centos-stream-9 for CS9 builds: https://github.com/oVirt/ovirt-engine-extensions-api/blob/master/.github/wo… - Do we already have that documented so an OST plugin to use those artifacts per OS can be created? If not, where to put it? 3. Using maven cache for Java project builds - When build maven projects in jenkins.ovirt.org we were using artifactory.ovirt.org to cache maven artifacts (and also save download bandwidth to PHX datacenter) - It doesn't make to use artifactory.ovirt.org inside GH actions, so I've tried to define a GH action specific cache: https://github.com/oVirt/ovirt-engine-extensions-api/blob/master/.github/wo… 4. Caching required dependencies - Above maven dependencies helps for maven invocations before RPM build but it doesn't help to fetch all required RPM dependencies for pro RPM maven based build - Right now it's almost 500 GB of packages to download and install on top of the default container and it for ovirt-engine-extensions-api it takes 50 % of the whole build time just to download and install those packages (I know it's just 1 minute, but anyway :-) - I've noticed that VDSM is using its own customized container <https://github.com/oVirt/vdsm/blob/master/.github/workflows/ci.yml#L8> - Wouldn't it be worthwhile to also create customized containers for Java based projects? 5. Differences between CS8 and CS9 - There are again some disturbing changes between CS8 and CS9: - PowerTools repo from CS8 is now called CRB in CS9 - pki-deps javapackages-tools modules from CS8 don't exist in CS9 - Core DNF plugins are not installed by default in CS9 container - To bypass those differences I've create 2 different shell scripts and plug them into a single workflow job: https://github.com/oVirt/ovirt-engine-extensions-api/blob/master/.github/wo… https://github.com/oVirt/ovirt-engine-extensions-api/blob/master/.automatio… https://github.com/oVirt/ovirt-engine-extensions-api/blob/master/.automatio… 6. git commands cannot be easily used inside GH action - GH doesn't checkout the project completely during checkout action, so .git directory is not present - In the past I've been using 'git archive' <https://gerrit.ovirt.org/gitweb?p=ovirt-engine-extensions-api.git;a=blob;f=…> to create .tar.gz source archive, but on GH it needed to be switched to a classic tar <https://github.com/oVirt/ovirt-engine-extensions-api/blob/master/.automatio…> - In the past I've been using 'git rev-list' <https://gerrit.ovirt.org/gitweb?p=ovirt-engine-extensions-api.git;a=blob;f=…> to fetch short git hash for snapshot builds, but on GH it needed to be switched to below hack <https://github.com/oVirt/ovirt-engine-extensions-api/blob/master/.github/wo…> Regards, Martin -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

3 3

Proposal: moving to building oVirt RPMs via containers
by Yaniv Kaul 06 Dec '21

06 Dec '21

With the move to Github, I think we have an opportunity to move to building oVirt packages via containers. You may want to look at https://github.com/gluster/Gluster-Builds - building Gluster RPMs by running a container (the 'build container'), which has the required dependencies and is updated once a month, or when there's a new dependency. It fits nicely with Github actions or any other system that uses containers, from your laptop to K8S. What I personally really like about it is the fact that the Dockerfile becomes the self-describing build process. Thoughts? Y.

1 0

Updates on oVirt Node and oVirt appliance building outside Jenkins
by Sandro Bonazzola 04 Dec '21

04 Dec '21

Hi, just a quick update on current issues in trying to build oVirt Node and the engine appliance outside Jenkins. 1) Using GitHub Actions: an attempt to build it is in progress here: https://github.com/sandrobonazzola/ovirt-appliance/pull/1 it's currently failing due to lorax not being able to perform the build. It kind of make sense as we are trying to do a virt-install within a container without the needed virtualization hardware exposed. I'm currently investigating how to make use of software virtualization in order to drop the requirement on missing hardware / nested virtualization. Also investigating on how to use self hosted runners for providing a build system with usable virtualization hardware. 2) Using COPR: we have basically the same issue: lorax fails not having access to the virtualization hardware 3) Using CentOS Community Build System This is a fully fledged Koji instance and it allows to build using the image-build variant. It has a completely different configuration system and it is more similar to what we are doing within the downstream build of oVirt Node. An attempt of providing the configuration started here: https://gerrit.ovirt.org/c/ovirt-appliance/+/117801 The issue there is that all the packages needed to be included within Node and Appliance must be built within CentOS Community Build System build root. The system has no external access to the internet so everything we need it needs to come from CentOS infra. I haven't started digging into oVirt Node but the build flow is very similar to the appliance one, so once one is solved, the other should be simple. -- 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 2

oVirt Community - open discussion around repositories and workflows
by Sandro Bonazzola 03 Dec '21

03 Dec '21

Dear community members, We would like to take some next steps in improving usability and general decision making for our community and are interested in your thoughts and suggestions. The first step is a decision regarding our version control and workflows associated with it. Contributions to new features and general improvements for oVirt outside of Red Hat have been rare and we would like to hear from you if we could simplify this process for you. One suggestion we have is that we could simplify the contribution process and improve the contributor experience by moving our repositories to GitHub or GitLab. Currently, our Gerrit (gerrit.ovirt.org) instance is mirrored to GitHub and we already have several repositories that are exclusively developed there, including their CI running on GitHub Actions, for example: * https://github.com/oVirt/go-ovirt-client * https://github.com/oVirt/512-byte-vm There are also various related projects that run on GitLab, such as: * https://gitlab.com/qemu-project * https://gitlab.com/libvirt One recent project that moved from Gerrit to GitLab with a very similar discussion is mediawiki: https://www.mediawiki.org/wiki/GitLab_consultation/Discussion_summary Once we hear more of your thoughts around this and if the decision falls on moving to either GitHub or GitLab, our plan would be to start changing existing workflows and CI project by project as it makes sense. Both platforms offer similar features. Two key points that stand out for us are that: * GitLab is open source while GitHub isn't * GitHub is more visible which allows contributors to amplify their contributions and raise their profile by contributing to various big projects, including oVirt We are looking forward to hearing your thoughts, -- 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.*

4 10

Integrating OST with artifacts built in github
by Nir Soffer 02 Dec '21

02 Dec '21

Looking this very helpful document https://ovirt.org/develop/developer-guide/migrating_to_github.html The suggested solution is to create artifacts.zip with all the rpms for a project. But to use the rpms in OST, we need to create a yum repository before uploading the artifacts, so we can pass a URL of a zip file with a yum repository. Here is what we have now in ovirt-imageio: 1. We build for multiple distros: https://github.com/nirs/ovirt-imageio/blob/790e6b79e756de24ef5134aa583bea46… 2. Every build creates a repo in exported-artifacts https://github.com/nirs/ovirt-imageio/blob/790e6b79e756de24ef5134aa583bea46… 3. Every build uploads the exported artifacts to rpm-{distro}.zip https://github.com/nirs/ovirt-imageio/blob/790e6b79e756de24ef5134aa583bea46… An example build: https://github.com/nirs/ovirt-imageio/actions/runs/1531658722 To start OST manually, developer can copy a link the right zip file (e.g for centos stream 8): https://github.com/nirs/ovirt-imageio/suites/4535392764/artifacts/121520882 And pass the link to OST build with parameters job. In this solution, OST side gets a repo that can be included in the build without any additional code or logic - just unzip and use the repo from the directory. I think this is the minimal solution to allow running OST with built artifacts from github. For triggering jobs automatically, we will need a way to find the right artifacts for a build, or use some convention for naming the artifacts in all projects. I started with the simple convention of jobname-containername since it is easy to integrate with the infrastructure we already have in the project. Nir

2 1

Another CI failure
by Milan Zamazal 02 Dec '21

02 Dec '21

Hi, as demonstrated in https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31133/, OST builds can at least start now but still fail, apparently due to the following: + sudo -n usermod -a -G jenkins qemu usermod: user 'qemu' does not exist + log ERROR 'Failed to add user qemu to group jenkins' + local level=ERROR + shift + local 'message=Failed to add user qemu to group jenkins' + local prefix + [[ 4 -gt 1 ]] + prefix='global_setup[lago_setup]' + echo 'global_setup[lago_setup] ERROR: Failed to add user qemu to group jenkins' global_setup[lago_setup] ERROR: Failed to add user qemu to group jenkins + return 1 + failed=true What can be done about it? Thanks, Milan

3 4

IPV6 on github actions container
by Nir Soffer 02 Dec '21

02 Dec '21

I'm trying to add a github action workflow for ovirt-imageio. The yml file is simple: https://github.com/nirs/ovirt-imageio/commit/21da91274b7b4722167c2415d1c1b5… And all the jobs run, but tons of tests are failing: https://github.com/nirs/ovirt-imageio/actions/runs/1527728851 The typical failure is: 2021-12-01T20:50:07.6424921Z address = ('::', 43001), timeout = <object object at 0x7f2cb7d16270> 2021-12-01T20:50:07.6425749Z source_address = None 2021-12-01T20:50:07.6425985Z 2021-12-01T20:50:07.6426421Z def create_connection(address, timeout=_GLOBAL_DEFAULT_TIMEOUT, 2021-12-01T20:50:07.6426954Z source_address=None): ... 2021-12-01T20:50:07.6435579Z host, port = address 2021-12-01T20:50:07.6435942Z err = None 2021-12-01T20:50:07.6436563Z for res in getaddrinfo(host, port, 0, SOCK_STREAM): 2021-12-01T20:50:07.6437402Z af, socktype, proto, canonname, sa = res 2021-12-01T20:50:07.6437834Z sock = None 2021-12-01T20:50:07.6438146Z try: 2021-12-01T20:50:07.6438522Z sock = socket(af, socktype, proto) 2021-12-01T20:50:07.6439032Z if timeout is not _GLOBAL_DEFAULT_TIMEOUT: 2021-12-01T20:50:07.6439538Z sock.settimeout(timeout) 2021-12-01T20:50:07.6440109Z if source_address: 2021-12-01T20:50:07.6440522Z sock.bind(source_address) 2021-12-01T20:50:07.6440916Z > sock.connect(sa) 2021-12-01T20:50:07.6441573Z E OSError: [Errno 99] Cannot assign requested address I guess that ipv6 is disabled, and google confirms that github actions and ipv6 is an issue. In travis we enabled ipv6 in docker using this script: https://github.com/oVirt/ovirt-imageio/blob/master/travis/configure-docker.… Run before starting the job: https://github.com/oVirt/ovirt-imageio/blob/61f023bf1e45da4e98593278451030f… I did not try to run this script yet, since I'm not sure we have a way to run stuff *before* the container runs in github actions. I hope someone has some insight on a way to solve this. Nir

2 3

COPR's ovirt-master-snapshot replacing resources.ovirt.org's "tested" repo
by Michal Skrivanek 02 Dec '21

02 Dec '21

Hi all, COPR[1] is effectively replacing the "tested" repo - the one that gets all built artifacts after a patch is merged (and is actually not tested:) Sandro started to move projects to COPR for merged patches some time ago and we believe it's complete except appliance and node. So we can all start switching to it as it is currently more up to date anyway Please start modifying your CI setup, other automation, your own updates, wherever really, and just switch from [2] to [3] (adjust the platform/arch accordingly as well, so e.g. [4]) Thanks, michal [1] https://copr.fedorainfracloud.org/coprs/ovirt/ovirt-master-snapshot/ [2] https://resources.ovirt.org/repos/ovirt/tested/master/rpm/ [3] https://download.copr.fedorainfracloud.org/results/ovirt/ovirt-master-snaps… [4] https://download.copr.fedorainfracloud.org/results/ovirt/ovirt-master-snaps…

1 1

Failed CI for engine patches - java-client-kubevirt otopi
by Shani Leviim 01 Dec '21

01 Dec '21

Hi, I have a series of engine patches that keep failing although the chain is rebased on the latest master. I ran 'ci build' a couple of minutes ago and it failed with this one: 11:08:45 No match for argument: otopi 11:08:45 Error: Unable to find a match: java-client-kubevirt otopi https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15286/conso… The engine patches: https://gerrit.ovirt.org/q/topic:%22copy-template-mbs-disk%22+(status:open%… Can someone assist, please? *Regards,* *Shani Leviim*

7 11