- Devel - oVirt List Archives

planned Jenkins CI restart
by Evgheni Dereveanchin 08 Sep '21

08 Sep '21

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new CI jobs will be scheduled during this maintenance period. I will inform you once it is back online. -- Regards, Evgheni Dereveanchin

1 1

Jenkins blocking issue sitting 2 weeks without update
by Sandro Bonazzola 06 Sep '21

06 Sep '21

Hi, anyone available to have a look at why jenkins is not honoring .packages and .req file for STDCI? The ticket I opened 2 weeks ago here https://issues.redhat.com/browse/CPDEVOPS-242 is silent even if marked with priority blocker. -- 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 4.3 -> 4.4 upgrade and Self hosted HE storage migration
by erdosi.peter＠kifu.gov.hu 05 Sep '21

05 Sep '21

Hy! I've just finished the process in the subject, and want to share a few things with others, and also want to ask a question. Long story "short" (it's my IT infra@home, I've oVirt in bigger setups at work): I had 3 machines before: two desktop, and one Dell R710 server. One of the desktop running FreeNAS with an SSD RAID1, the other desktop and my Dell machine was my two hypervisors. Luckily, i've just got two HP DL380 G6, which become my hypervisors, and my Dell machine became the TrueNAS storage (redundant PSU, more core, more RAM, more disk :) ). When I started the procedure, I used the latest oVirt 4.3, but it was the time to upgrade the version, and also want to migrage all my Data (with the self hosted engine too) to the TrueNAS Dell machine (but... I've only have the two SSD on my old FreeNAS, so it has to be moved) After I replaced the hypervisors, and migrated all my VM data to the new storage to new disks (iSCSI->iSCSI, live and cold storage migration) it was the time, to shut off the FreeNAS, and start the HE redeploy. The main steps, what I take: - Undeployed the hosted-engine from the host with ID: 2 (the ID came from hosted-engine --vm-status command, the machine name is: Jupiter) - Moved all my VMs to this host, only the HE remained on the machine with ID: 1 (name: Saturn) - Removed the remained stuff with: "hosted-engine --clean-metadata --host-id=2 --force-clean", so the Saturn was the only machine capable of running the HE - Set Global maintenance mode=true - Stop the ovirt-engine in the old HE machine - Create a backup with "engine-backup --mode=backup --file=engine.backup --log=engine-backup.log" and copy it to an another machine (my desktop actually) - "hosted-engine --vm-shutdown" - Saturn shutdown, 4.4.6 installer in (it was written to DVD before, don't want to create another) Saturn complete reinstall. - FreeNAS shutdown, SSD moved to TrueNAS, RAID 1/zVol create, iSCSI export... - After the base network was created, and the backup was moved back to the new Saturn, I started the new host deploy with: "hosted-engine --deploy --restore-from-file=engine.backup" Catch 1 and 2: If you do this, you must know the old DC and the Cluster name! write it down somewhere! or you need to get out the PSQL dbs from the backup, and extract from it... (like i had to) The process goes almost flawless, but at some point, I've got a deployment error (code: 519) which tells me, the Saturn have missing networks, and I can connect to https://saturn.mope.local:6900/ovirt-engine Catch 3: this URL not worked, since it was not the HE's URL, and I cannot login because the FQDN checking... This may need some further improvement ;) After some thinking, finally I've made a socks proxy with SSH (1080 forwarded to Saturn) and I was able to login to the locally running HE and make the network changes, which was required to continue the deploy process... Also (since the old FreeNAS box was on my desk, the HE and the two hypervisor was unable to connect to my old SSD iSCSI, so I have to remove it... (cannot put on maintenance, but I was able to delete it from Storage->Domains tab) After this, Saturn came up, got the "green arrow", so I removed the lock file which the deploy give me, and the deploy continued... After this, I selected the new SSD RAID1 on my Dell iSCSI box, and the deploy was finally able to copy the HE to the iSCSI, so far so good :) Finally, I've got my new 4.4.6 setup, with Self hosted HE on my new TrueNAS@Dell. (and all my VMs running on Jupiter at this time, without any errors) The next step was to live migrate off Jupiter to Saturn, DVD in, Jupiter remove from the Cluster, and reinstall to 4.4.6, and readd Jupiter (this time, with HE deployed again) After I've put back Jupiter, and made the required initial setup with the network (VLANs pulled to the bonds, iSCSI IPs set, etc) the cluster was up and running. The next step was to upgrade the hypervisors to the latest image with rolling update, it was worked as before, so the time come to move the cluster and DC compatilbility level from 4.3 -> 4.6... This forced me to reboot all my VMs, as it written when I made this change, but this worked too. At last: I've restarted the HE with hosted-engine --vm-shutdown / --vm-start, because it has some "!" at the BIOS version... And this is my question actually: after the restart, the BIOS version of the HE machine remained the old one, and still have the "!" which states: "The chipset/firmware type doen not match the cluster chipset/firmware type" Doen anyone know, how can the HE BIOS updated after compatibility leve increase? Sorry, if my mail should be goes to the users list, but because of "Catch 3" I think is's better here. Also I want to write this down, maybe someone find usefull, and this procedure can be used in the Docs too, if you want! Regards: Peter

3 2

oVirt Node 4.4.8.3 Async update
by Sandro Bonazzola 03 Sep '21

03 Sep '21

oVirt Node 4.4.8.3 Async update On September 3rd 2021 the oVirt project released an async update for oVirt Node consuming the following packages: - ovirt-release44 4.4.8.3 - ovirt-node-ng-image-update 4.4.8.3 oVirt Node respin also consumed most recent CentOS Stream and Advanced Virtualization content. It also includes fixes for: - Bug 1996602 <https://bugzilla.redhat.com/show_bug.cgi?id=1996602> - VM remains in paused state when trying to write on a resized disk resides on iscsi - Via qemu-kvm-6.0.0-29.el8s which shipped live. Here’s the full list of changes: --- ovirt-node-ng-image-4.4.8.2.manifest-rpm 2021-09-01 12:59:05.195037688 +0200 +++ ovirt-node-ng-image-4.4.8.3.manifest-rpm 2021-09-03 13:27:52.006368887 +0200 @@ -47 +46,0 @@ -boost-iostreams-1.66.0-10.el8.x86_64 @@ -112 +111 @@ -device-mapper-persistent-data-0.9.0-1.el8.x86_64 +device-mapper-persistent-data-0.9.0-4.el8.x86_64 @@ -355 +354 @@ -libcap-2.26-4.el8.x86_64 +libcap-2.26-5.el8.x86_64 @@ -637 +636 @@ -osinfo-db-20210215-1.el8.noarch +osinfo-db-20210809-1.el8.noarch @@ -648 +647 @@ -ovirt-node-ng-image-update-placeholder-4.4.8.2-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.8.3-1.el8.noarch @@ -656,2 +655,2 @@ -ovirt-release-host-node-4.4.8.2-1.el8.noarch -ovirt-release44-4.4.8.2-1.el8.noarch +ovirt-release-host-node-4.4.8.3-1.el8.noarch +ovirt-release44-4.4.8.3-1.el8.noarch @@ -768 +767 @@ -python3-eventlet-0.25.2-3.el8.noarch +python3-eventlet-0.25.2-3.1.el8.noarch @@ -814 +813 @@ -python3-os-brick-4.0.3-1.el8.noarch +python3-os-brick-4.0.3-2.el8.noarch @@ -890,14 +889,14 @@ -qemu-guest-agent-6.0.0-27.el8s.x86_64 -qemu-img-6.0.0-27.el8s.x86_64 -qemu-kvm-6.0.0-27.el8s.x86_64 -qemu-kvm-block-curl-6.0.0-27.el8s.x86_64 -qemu-kvm-block-gluster-6.0.0-27.el8s.x86_64 -qemu-kvm-block-iscsi-6.0.0-27.el8s.x86_64 -qemu-kvm-block-rbd-6.0.0-27.el8s.x86_64 -qemu-kvm-block-ssh-6.0.0-27.el8s.x86_64 -qemu-kvm-common-6.0.0-27.el8s.x86_64 -qemu-kvm-core-6.0.0-27.el8s.x86_64 -qemu-kvm-docs-6.0.0-27.el8s.x86_64 -qemu-kvm-hw-usbredir-6.0.0-27.el8s.x86_64 -qemu-kvm-ui-opengl-6.0.0-27.el8s.x86_64 -qemu-kvm-ui-spice-6.0.0-27.el8s.x86_64 +qemu-guest-agent-6.0.0-29.el8s.x86_64 +qemu-img-6.0.0-29.el8s.x86_64 +qemu-kvm-6.0.0-29.el8s.x86_64 +qemu-kvm-block-curl-6.0.0-29.el8s.x86_64 +qemu-kvm-block-gluster-6.0.0-29.el8s.x86_64 +qemu-kvm-block-iscsi-6.0.0-29.el8s.x86_64 +qemu-kvm-block-rbd-6.0.0-29.el8s.x86_64 +qemu-kvm-block-ssh-6.0.0-29.el8s.x86_64 +qemu-kvm-common-6.0.0-29.el8s.x86_64 +qemu-kvm-core-6.0.0-29.el8s.x86_64 +qemu-kvm-docs-6.0.0-29.el8s.x86_64 +qemu-kvm-hw-usbredir-6.0.0-29.el8s.x86_64 +qemu-kvm-ui-opengl-6.0.0-29.el8s.x86_64 +qemu-kvm-ui-spice-6.0.0-29.el8s.x86_64 @@ -934,2 +933,2 @@ -selinux-policy-3.14.3-78.el8.noarch -selinux-policy-targeted-3.14.3-78.el8.noarch +selinux-policy-3.14.3-79.el8.noarch +selinux-policy-targeted-3.14.3-79.el8.noarch @@ -1007 +1006 @@ -virt-v2v-1.42.0-14.el8s.x86_64 +virt-v2v-1.42.0-15.el8s.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

[ANN] oVirt 4.4.8 Async update #2
by Sandro Bonazzola 01 Sep '21

01 Sep '21

oVirt 4.4.8 Async update #2 On September 1st 2021 the oVirt project released an async update to the following packages: - ovirt-release44 4.4.8.2 - vdsm 4.40.80.6 Fixing the following bugs: - Bug 1999032 <https://bugzilla.redhat.com/show_bug.cgi?id=1999032> - Failed to add rhel host to rhv engine server with error - VDSM host-38 command Get Host Capabilities failed: Internal JSON-RPC error: {'reason': "'libvirt'"} - Bug 1998865 <https://bugzilla.redhat.com/show_bug.cgi?id=1998865> - Host installation fails due to missing bond file - Bug 1996602 <https://bugzilla.redhat.com/show_bug.cgi?id=1996602> - VM remains in paused state when trying to write on a resized disk resides on iscsi oVirt Node respin is waiting for latest Advanced Virtualization build to land on mirrors providing: - hivex-1.3.18-22.el8s - libvirt-7.6.0-2.el8s - libvirt-python-7.6.0-1.el8s - qemu-kvm-6.0.0-27.el8s A separate announcement will be sent when the oVirt Node build will be available. -- 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 1

oVirt Node 4.4.8.2 Async update
by Sandro Bonazzola 01 Sep '21

01 Sep '21

oVirt Node 4.4.8.2 Async update On September 1st 2021 the oVirt project released an async update for oVirt Node consuming the following packages: - ovirt-release44 4.4.8.2 - vdsm 4.40.80.6 oVirt Node respin also consumed most recent CentOS Stream and Advanced Virtualization content. It also includes fixes for: - CVE-2021-31535 <https://access.redhat.com/security/cve/CVE-2021-31535> libX11: missing request length checks - CVE-2021-3564 <https://access.redhat.com/security/cve/CVE-2021-3564> kernel: double free in bluetooth subsystem when the HCI device initialization fails - CVE-2021-3573 <https://access.redhat.com/security/cve/CVE-2021-3573> kernel: use-after-free in function hci_sock_bound_ioctl() - CVE-2021-29155 <https://access.redhat.com/security/cve/CVE-2021-29155> kernel: protection for sequences of pointer arithmetic operations against speculatively out-of-bounds loads can be bypassed to leak content of kernel memory - CVE-2021-31829 <https://access.redhat.com/security/cve/CVE-2021-31829> kernel: protection of stack pointer against speculative pointer arithmetic can be bypassed to leak content of kernel memory - CVE-2021-33200 <https://access.redhat.com/security/cve/CVE-2021-33200> kernel: out-of-bounds reads and writes due to enforcing incorrect limits for pointer arithmetic operations by BPF verifier - CVE-2021-3679 <https://access.redhat.com/security/cve/CVE-2021-3679> kernel: DoS in rb_per_cpu_empty() - CVE-2020-26144 <https://access.redhat.com/security/cve/CVE-2020-26144> kernel: accepting unencrypted A-MSDU frames that start with RFC1042 header - CVE-2020-26145 <https://access.redhat.com/security/cve/CVE-2020-26145> kernel: accepting plaintext broadcast fragments as full frames - CVE-2020-24587 <https://access.redhat.com/security/cve/CVE-2020-24587> kernel: Reassembling fragments encrypted under different keys - CVE-2020-26141 <https://access.redhat.com/security/cve/CVE-2020-26141> kernel: not verifying TKIP MIC of fragmented frames - CVE-2020-24586 <https://access.redhat.com/security/cve/CVE-2020-24586> kernel: Fragmentation cache not cleared on reconnection - CVE-2020-26147 <https://access.redhat.com/security/cve/CVE-2020-26147> kernel: reassembling mixed encrypted/plaintext fragments - CVE-2021-3653 <https://access.redhat.com/security/cve/CVE-2021-3653> kernel: SVM nested virtualization issue in KVM (AVIC support) - CVE-2021-3656 <https://access.redhat.com/security/cve/CVE-2021-3656> kernel: SVM nested virtualization issue in KVM (VMLOAD/VMSAVE) Here’s the full list of changes: --- ovirt-node-ng-image-4.4.8.1.manifest-rpm 2021-08-27 08:11:54.863736688 +0200 +++ ovirt-node-ng-image-4.4.8.2.manifest-rpm 2021-09-01 12:59:05.195037688 +0200 @@ -3,6 +3,6 @@ -NetworkManager-1.32.8-1.el8.x86_64 -NetworkManager-config-server-1.32.8-1.el8.noarch -NetworkManager-libnm-1.32.8-1.el8.x86_64 -NetworkManager-ovs-1.32.8-1.el8.x86_64 -NetworkManager-team-1.32.8-1.el8.x86_64 -NetworkManager-tui-1.32.8-1.el8.x86_64 +NetworkManager-1.32.10-2.el8.x86_64 +NetworkManager-config-server-1.32.10-2.el8.noarch +NetworkManager-libnm-1.32.10-2.el8.x86_64 +NetworkManager-ovs-1.32.10-2.el8.x86_64 +NetworkManager-team-1.32.10-2.el8.x86_64 +NetworkManager-tui-1.32.10-2.el8.x86_64 @@ -24 +24 @@ -ansible-2.9.24-2.el8.noarch +ansible-2.9.25-1.el8.noarch @@ -39,5 +39,5 @@ -bind-export-libs-9.11.26-4.el8_4.x86_64 -bind-libs-9.11.26-4.el8_4.x86_64 -bind-libs-lite-9.11.26-4.el8_4.x86_64 -bind-license-9.11.26-4.el8_4.noarch -bind-utils-9.11.26-4.el8_4.x86_64 +bind-export-libs-9.11.26-6.el8.x86_64 +bind-libs-9.11.26-6.el8.x86_64 +bind-libs-lite-9.11.26-6.el8.x86_64 +bind-license-9.11.26-6.el8.noarch +bind-utils-9.11.26-6.el8.x86_64 @@ -46 +46 @@ -blivet-data-3.4.0-4.el8.noarch +blivet-data-3.4.0-5.el8.noarch @@ -68,2 +68,2 @@ -cockpit-250-1.el8.x86_64 -cockpit-bridge-250-1.el8.x86_64 +cockpit-251-1.el8.x86_64 +cockpit-bridge-251-1.el8.x86_64 @@ -71,3 +71,3 @@ -cockpit-storaged-250-1.el8.noarch -cockpit-system-250-1.el8.noarch -cockpit-ws-250-1.el8.x86_64 +cockpit-storaged-251-1.el8.noarch +cockpit-system-251-1.el8.noarch +cockpit-ws-251-1.el8.x86_64 @@ -94 +94 @@ -curl-7.61.1-18.el8_4.1.x86_64 +curl-7.61.1-21.el8.x86_64 @@ -118,2 +118,2 @@ -dnf-4.7.0-2.el8.noarch -dnf-data-4.7.0-2.el8.noarch +dnf-4.7.0-3.el8.noarch +dnf-data-4.7.0-3.el8.noarch @@ -123,5 +123,5 @@ -dracut-049-188.git20210802.el8.x86_64 -dracut-config-generic-049-188.git20210802.el8.x86_64 -dracut-live-049-188.git20210802.el8.x86_64 -dracut-network-049-188.git20210802.el8.x86_64 -dracut-squash-049-188.git20210802.el8.x86_64 +dracut-049-190.git20210811.el8.x86_64 +dracut-config-generic-049-190.git20210811.el8.x86_64 +dracut-live-049-190.git20210811.el8.x86_64 +dracut-network-049-190.git20210811.el8.x86_64 +dracut-squash-049-190.git20210811.el8.x86_64 @@ -138 +138 @@ -ethtool-5.8-6.el8.x86_64 +ethtool-5.8-7.el8.x86_64 @@ -184 +184 @@ -fontconfig-2.13.1-3.el8.x86_64 +fontconfig-2.13.1-4.el8.x86_64 @@ -188 +188 @@ -fstrm-0.6.0-3.el8.1.x86_64 +fstrm-0.6.1-2.el8.x86_64 @@ -206,3 +206,3 @@ -glibc-2.28-162.el8.x86_64 -glibc-common-2.28-162.el8.x86_64 -glibc-langpack-en-2.28-162.el8.x86_64 +glibc-2.28-164.el8.x86_64 +glibc-common-2.28-164.el8.x86_64 +glibc-langpack-en-2.28-164.el8.x86_64 @@ -240 +240 @@ -grubby-8.40-41.el8.x86_64 +grubby-8.40-42.el8.x86_64 @@ -249 +249 @@ -hivex-1.3.18-21.module_el8.5.0+821+97472045.x86_64 +hivex-1.3.18-22.el8s.x86_64 @@ -251 +251 @@ -hwdata-0.314-8.9.el8.noarch +hwdata-0.314-8.10.el8.noarch @@ -265,2 +265,2 @@ -iproute-5.12.0-2.el8.x86_64 -iproute-tc-5.12.0-2.el8.x86_64 +iproute-5.12.0-3.el8.x86_64 +iproute-tc-5.12.0-3.el8.x86_64 @@ -270,3 +270,3 @@ -iptables-1.8.4-19.el8.x86_64 -iptables-ebtables-1.8.4-19.el8.x86_64 -iptables-libs-1.8.4-19.el8.x86_64 +iptables-1.8.4-20.el8.x86_64 +iptables-ebtables-1.8.4-20.el8.x86_64 +iptables-libs-1.8.4-20.el8.x86_64 @@ -301,6 +301,6 @@ -kernel-4.18.0-331.el8.x86_64 -kernel-core-4.18.0-331.el8.x86_64 -kernel-modules-4.18.0-331.el8.x86_64 -kernel-tools-4.18.0-331.el8.x86_64 -kernel-tools-libs-4.18.0-331.el8.x86_64 -kexec-tools-2.0.20-56.el8.x86_64 +kernel-4.18.0-338.el8.x86_64 +kernel-core-4.18.0-338.el8.x86_64 +kernel-modules-4.18.0-338.el8.x86_64 +kernel-tools-4.18.0-338.el8.x86_64 +kernel-tools-libs-4.18.0-338.el8.x86_64 +kexec-tools-2.0.20-57.el8.x86_64 @@ -313,2 +313,2 @@ -krb5-libs-1.18.2-13.el8.x86_64 -krb5-workstation-1.18.2-13.el8.x86_64 +krb5-libs-1.18.2-14.el8.x86_64 +krb5-workstation-1.18.2-14.el8.x86_64 @@ -318,3 +318,3 @@ -libX11-1.6.8-4.el8.x86_64 -libX11-common-1.6.8-4.el8.noarch -libX11-xcb-1.6.8-4.el8.x86_64 +libX11-1.6.8-5.el8.x86_64 +libX11-common-1.6.8-5.el8.noarch +libX11-xcb-1.6.8-5.el8.x86_64 @@ -353 +353 @@ -libbpf-0.3.0-1.el8.x86_64 +libbpf-0.4.0-1.el8.x86_64 @@ -363 +363 @@ -libcurl-7.61.1-18.el8_4.1.x86_64 +libcurl-7.61.1-21.el8.x86_64 @@ -407 +407 @@ -libkadm5-1.18.2-13.el8.x86_64 +libkadm5-1.18.2-14.el8.x86_64 @@ -418 +418 @@ -libmodulemd-2.12.1-1.el8.x86_64 +libmodulemd-2.13.0-1.el8.x86_64 @@ -465 +465 @@ -libsepol-2.9-2.el8.x86_64 +libsepol-2.9-3.el8.x86_64 @@ -503,24 +503,24 @@ -libvirt-7.5.0-1.el8s.x86_64 -libvirt-client-7.5.0-1.el8s.x86_64 -libvirt-daemon-7.5.0-1.el8s.x86_64 -libvirt-daemon-config-network-7.5.0-1.el8s.x86_64 -libvirt-daemon-config-nwfilter-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-interface-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-network-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-nodedev-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-nwfilter-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-qemu-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-secret-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-core-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-disk-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-gluster-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-iscsi-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-iscsi-direct-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-logical-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-mpath-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-rbd-7.5.0-1.el8s.x86_64 -libvirt-daemon-driver-storage-scsi-7.5.0-1.el8s.x86_64 -libvirt-daemon-kvm-7.5.0-1.el8s.x86_64 -libvirt-libs-7.5.0-1.el8s.x86_64 -libvirt-lock-sanlock-7.5.0-1.el8s.x86_64 +libvirt-7.6.0-2.el8s.x86_64 +libvirt-client-7.6.0-2.el8s.x86_64 +libvirt-daemon-7.6.0-2.el8s.x86_64 +libvirt-daemon-config-network-7.6.0-2.el8s.x86_64 +libvirt-daemon-config-nwfilter-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-interface-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-network-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-nodedev-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-nwfilter-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-qemu-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-secret-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-core-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-disk-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-gluster-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-iscsi-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-iscsi-direct-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-logical-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-mpath-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-rbd-7.6.0-2.el8s.x86_64 +libvirt-daemon-driver-storage-scsi-7.6.0-2.el8s.x86_64 +libvirt-daemon-kvm-7.6.0-2.el8s.x86_64 +libvirt-libs-7.6.0-2.el8s.x86_64 +libvirt-lock-sanlock-7.6.0-2.el8s.x86_64 @@ -546,2 +546,2 @@ -lldpad-1.0.1-14.git036e314.el8.x86_64 -llvm-libs-12.0.0-1.module_el8.5.0+840+21214faf.x86_64 +lldpad-1.0.1-16.git036e314.el8.x86_64 +llvm-libs-12.0.1-1.module_el8.5.0+892+54d791e1.x86_64 @@ -553 +553 @@ -lsscsi-0.32-2.el8.x86_64 +lsscsi-0.32-3.el8.x86_64 @@ -555 +555 @@ -lua-libs-5.3.4-11.el8.x86_64 +lua-libs-5.3.4-12.el8.x86_64 @@ -603 +603 @@ -nftables-0.9.3-20.el8.x86_64 +nftables-0.9.3-21.el8.x86_64 @@ -605 +605 @@ -nmap-ncat-7.70-5.el8.x86_64 +nmap-ncat-7.70-6.el8.x86_64 @@ -609 +609 @@ -nspr-4.31.0-1.el8_4.x86_64 +nspr-4.32.0-1.el8_4.x86_64 @@ -636 +636 @@ -os-prober-1.74-6.el8.x86_64 +os-prober-1.74-9.el8.x86_64 @@ -648 +648 @@ -ovirt-node-ng-image-update-placeholder-4.4.8.1-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.8.2-1.el8.noarch @@ -656,2 +656,2 @@ -ovirt-release-host-node-4.4.8.1-1.el8.noarch -ovirt-release44-4.4.8.1-1.el8.noarch +ovirt-release-host-node-4.4.8.2-1.el8.noarch +ovirt-release44-4.4.8.2-1.el8.noarch @@ -664,3 +664,3 @@ -pacemaker-cluster-libs-2.1.0-6.el8.x86_64 -pacemaker-libs-2.1.0-6.el8.x86_64 -pacemaker-schemas-2.1.0-6.el8.noarch +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 @@ -715 +715 @@ -platform-python-3.6.8-39.el8.x86_64 +platform-python-3.6.8-40.el8.x86_64 @@ -718,3 +718,3 @@ -plymouth-0.9.4-9.20200615git1e36e30.el8.x86_64 -plymouth-core-libs-0.9.4-9.20200615git1e36e30.el8.x86_64 -plymouth-scripts-0.9.4-9.20200615git1e36e30.el8.x86_64 +plymouth-0.9.4-10.20200615git1e36e30.el8.x86_64 +plymouth-core-libs-0.9.4-10.20200615git1e36e30.el8.x86_64 +plymouth-scripts-0.9.4-10.20200615git1e36e30.el8.x86_64 @@ -744,2 +744,2 @@ -python3-bind-9.11.26-4.el8_4.noarch -python3-blivet-3.4.0-4.el8.noarch +python3-bind-9.11.26-6.el8.noarch +python3-blivet-3.4.0-5.el8.noarch @@ -753 +753 @@ -python3-cloud-what-1.28.20-1.el8.x86_64 +python3-cloud-what-1.28.21-2.el8.x86_64 @@ -762 +762 @@ -python3-dnf-4.7.0-2.el8.noarch +python3-dnf-4.7.0-3.el8.noarch @@ -797 +797 @@ -python3-libs-3.6.8-39.el8.x86_64 +python3-libs-3.6.8-40.el8.x86_64 @@ -800 +800 @@ -python3-libvirt-7.5.0-1.el8s.x86_64 +python3-libvirt-7.6.0-1.el8s.x86_64 @@ -811 +811 @@ -python3-nftables-0.9.3-20.el8.x86_64 +python3-nftables-0.9.3-21.el8.x86_64 @@ -834 +834 @@ -python3-perf-4.18.0-331.el8.x86_64 +python3-perf-4.18.0-338.el8.x86_64 @@ -864 +864 @@ -python3-rpm-4.14.3-15.el8.x86_64 +python3-rpm-4.14.3-18.el8.x86_64 @@ -876 +876 @@ -python3-subscription-manager-rhsm-1.28.20-1.el8.x86_64 +python3-subscription-manager-rhsm-1.28.21-2.el8.x86_64 @@ -878 +878 @@ -python3-syspurpose-1.28.20-1.el8.x86_64 +python3-syspurpose-1.28.21-2.el8.x86_64 @@ -889,15 +889,15 @@ -python36-3.6.8-37.module_el8.5.0+771+e5d9a225.x86_64 -qemu-guest-agent-6.0.0-26.el8s.x86_64 -qemu-img-6.0.0-26.el8s.x86_64 -qemu-kvm-6.0.0-26.el8s.x86_64 -qemu-kvm-block-curl-6.0.0-26.el8s.x86_64 -qemu-kvm-block-gluster-6.0.0-26.el8s.x86_64 -qemu-kvm-block-iscsi-6.0.0-26.el8s.x86_64 -qemu-kvm-block-rbd-6.0.0-26.el8s.x86_64 -qemu-kvm-block-ssh-6.0.0-26.el8s.x86_64 -qemu-kvm-common-6.0.0-26.el8s.x86_64 -qemu-kvm-core-6.0.0-26.el8s.x86_64 -qemu-kvm-docs-6.0.0-26.el8s.x86_64 -qemu-kvm-hw-usbredir-6.0.0-26.el8s.x86_64 -qemu-kvm-ui-opengl-6.0.0-26.el8s.x86_64 -qemu-kvm-ui-spice-6.0.0-26.el8s.x86_64 +python36-3.6.8-38.module_el8.5.0+895+a459eca8.x86_64 +qemu-guest-agent-6.0.0-27.el8s.x86_64 +qemu-img-6.0.0-27.el8s.x86_64 +qemu-kvm-6.0.0-27.el8s.x86_64 +qemu-kvm-block-curl-6.0.0-27.el8s.x86_64 +qemu-kvm-block-gluster-6.0.0-27.el8s.x86_64 +qemu-kvm-block-iscsi-6.0.0-27.el8s.x86_64 +qemu-kvm-block-rbd-6.0.0-27.el8s.x86_64 +qemu-kvm-block-ssh-6.0.0-27.el8s.x86_64 +qemu-kvm-common-6.0.0-27.el8s.x86_64 +qemu-kvm-core-6.0.0-27.el8s.x86_64 +qemu-kvm-docs-6.0.0-27.el8s.x86_64 +qemu-kvm-hw-usbredir-6.0.0-27.el8s.x86_64 +qemu-kvm-ui-opengl-6.0.0-27.el8s.x86_64 +qemu-kvm-ui-spice-6.0.0-27.el8s.x86_64 @@ -912,4 +912,4 @@ -rpm-4.14.3-15.el8.x86_64 -rpm-build-libs-4.14.3-15.el8.x86_64 -rpm-libs-4.14.3-15.el8.x86_64 -rpm-plugin-selinux-4.14.3-15.el8.x86_64 +rpm-4.14.3-18.el8.x86_64 +rpm-build-libs-4.14.3-18.el8.x86_64 +rpm-libs-4.14.3-18.el8.x86_64 +rpm-plugin-selinux-4.14.3-18.el8.x86_64 @@ -928,3 +928,3 @@ -sbd-1.4.2-2.el8.x86_64 -scap-security-guide-0.1.57-1.el8.noarch -scrub-2.5.2-14.el8.x86_64 +sbd-1.5.0-2.el8.x86_64 +scap-security-guide-0.1.57-4.el8.noarch +scrub-2.5.2-16.el8.x86_64 @@ -934,2 +934,2 @@ -selinux-policy-3.14.3-76.el8.noarch -selinux-policy-targeted-3.14.3-76.el8.noarch +selinux-policy-3.14.3-78.el8.noarch +selinux-policy-targeted-3.14.3-78.el8.noarch @@ -961 +961 @@ -subscription-manager-rhsm-certificates-1.28.20-1.el8.x86_64 +subscription-manager-rhsm-certificates-1.28.21-2.el8.x86_64 @@ -973,5 +973,5 @@ -systemd-239-49.el8.x86_64 -systemd-container-239-49.el8.x86_64 -systemd-libs-239-49.el8.x86_64 -systemd-pam-239-49.el8.x86_64 -systemd-udev-239-49.el8.x86_64 +systemd-239-50.el8.x86_64 +systemd-container-239-50.el8.x86_64 +systemd-libs-239-50.el8.x86_64 +systemd-pam-239-50.el8.x86_64 +systemd-udev-239-50.el8.x86_64 @@ -993,11 +993,11 @@ -vdo-6.2.5.65-14.el8.x86_64 -vdsm-4.40.80.5-1.el8.x86_64 -vdsm-api-4.40.80.5-1.el8.noarch -vdsm-client-4.40.80.5-1.el8.noarch -vdsm-common-4.40.80.5-1.el8.noarch -vdsm-gluster-4.40.80.5-1.el8.x86_64 -vdsm-http-4.40.80.5-1.el8.noarch -vdsm-jsonrpc-4.40.80.5-1.el8.noarch -vdsm-network-4.40.80.5-1.el8.x86_64 -vdsm-python-4.40.80.5-1.el8.noarch -vdsm-yajsonrpc-4.40.80.5-1.el8.noarch +vdo-6.2.5.74-14.el8.x86_64 +vdsm-4.40.80.6-1.el8.x86_64 +vdsm-api-4.40.80.6-1.el8.noarch +vdsm-client-4.40.80.6-1.el8.noarch +vdsm-common-4.40.80.6-1.el8.noarch +vdsm-gluster-4.40.80.6-1.el8.x86_64 +vdsm-http-4.40.80.6-1.el8.noarch +vdsm-jsonrpc-4.40.80.6-1.el8.noarch +vdsm-network-4.40.80.6-1.el8.x86_64 +vdsm-python-4.40.80.6-1.el8.noarch +vdsm-yajsonrpc-4.40.80.6-1.el8.noarch @@ -1021 +1021 @@ -yum-4.7.0-2.el8.noarch +yum-4.7.0-3.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

Re: VM timezone typo
by Yedidyah Bar David 01 Sep '21

01 Sep '21

On Wed, Sep 1, 2021 at 5:09 AM luwen.zhang <luwen.zhang(a)vinchin.com> wrote: > > Hello team, > > We found a minor issue on oVirt 4.4.8 version, it seems like a typo of the > VM timezone, it should be “GMT+01:00 Central European Standard Time” but on > 4.4.8 it’s “GMT+01:00 Central European Standard Tim”. > This lead to Vinchin VM restoration fail at VM creation stage if using VM > backups from previous oVirt versions. > Fix already merged, will be released with 4.4.9: https://gerrit.ovirt.org/q/I3fce6edf4e3af01f07dec9ae32f5a1a791e9c467 Thanks for the report, anyway :-) Best regards, -- Didi

2 1

Re: VM timezone typo
by Arik Hadas 01 Sep '21

01 Sep '21

On Wed, Sep 1, 2021 at 5:09 AM luwen.zhang <luwen.zhang(a)vinchin.com> wrote: > > Hello team, > > We found a minor issue on oVirt 4.4.8 version, it seems like a typo of the > VM timezone, it should be “GMT+01:00 Central European Standard Time” but on > 4.4.8 it’s “GMT+01:00 Central European Standard Tim”. > This lead to Vinchin VM restoration fail at VM creation stage if using VM > backups from previous oVirt versions. > > > We had adjusted our programing to deal with this specific issue, but hope > it can be fix soon. > Thanks for reporting this issue We've already merged a fix for that ( https://gerrit.ovirt.org/#/c/ovirt-engine/+/116260/) A possible way to resolve this before the aforementioned fix is available is to fix the typo in /usr/share/ovirt-engine/conf/timezones-defaults.properties (changes will be overridden when updating ovirt-engine) or adding "Europe/Warsaw=Central European Standard Time" to a new configuration in /etc/ovirt-engine/timezones/ (see https://github.com/oVirt/ovirt-site/pull/2554/files) > Thanks & regards! > > > *Luwen Zhang* | Product Manager > > *Mobile*: +8613880424687 | *Skype*: luwen.zhang_cn > > *WhatsApp*: +8613880424687 | *WeChat*: +8613880424687 > > *Website*: www.vinchin.com > > *Address*: F5, Block 8, National Information Security Industry Park, > > No.333 Yunhua Road, Hi-tech Zone, Chengdu, China | *Zip*: 610015 > > *INNOVATIVE VM BACKUP EXPERT* > > VMware Backup <https://www.vinchin.com/en/hypervisor/vmware-backup.html> > | XenServer/Citrix Hypervisor/XCP-ng Backup > <https://www.vinchin.com/en/hypervisor/xcp-ng-xenserver-backup.html> | Hyper-V > Backup <https://www.vinchin.com/en/hypervisor/hyper-v-backup.html> > > RHEV/oVirt Backup > <https://www.vinchin.com/en/hypervisor/red-hat-virtualization-ovirt-backup.h…> > | OLVM Backup > <https://www.vinchin.com/en/hypervisor/oracle-linux-virtualization-manager-b…> > | Sangfor HCI Backup > <https://www.vinchin.com/en/hypervisor/sangfor-hci-backup.html> | OpenStack > Backup <https://www.vinchin.com/en/hypervisor/openstack-backup.html> > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-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/devel@ovirt.org/message/42KMIMK6CKK25… >

2 1

VM timezone typo
by luwen.zhang 01 Sep '21

01 Sep '21

1 0

Python SDK 4.4.15 problems
by francesco＠shellrent.com 27 Aug '21

27 Aug '21

Hi, in a new deployed host (Centos8, oVirt 4.4) with python module ovirt-engine-sdk-python 4.4.15 I was unable to use the Python SDK API. The script hanged in the connection test, with the following strace: .... futex(0x7fc03e47a9e8, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1629103636, tv_nsec=938478000}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out) futex(0x7fc03e47aa40, FUTEX_WAKE_PRIVATE, 1) = 0 futex(0x7fc03e47a9e8, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1629103636, tv_nsec=943557000}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out) futex(0x7fc03e47aa40, FUTEX_WAKE_PRIVATE, 1) = 0 futex(0x7fc03e47a9e8, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1629103636, tv_nsec=948631000}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection timed out) futex(0x7fc03e47aa40, FUTEX_WAKE_PRIVATE, 1) = 0 ... API via a simple curl worked fine, in another host (still Centos8, oVirt 4.4) with the module version 4.4.14 everything works fine. Downgrading the python module from 4.4.15 to 4.4.14 via pip3 fixed the problem. What could be the problem and it could be related to the recent branches split (I doubt but...). Regards, Francesco

4 3