On 10. 11. 2022, at 1:16, Erkan E via Users <users@ovirt.org> wrote:

Hello,

I have the same issue issue with my oVirt v4.5.x system installed by following the oVirt official installation document at https://www.ovirt.org/download/install_on_rhel.html

The oVirt hosts are Rocky Linux v8.6. When trying to upgrade the oVirt hosts using oVirt's webadmin GUI or by executing the "yum upgrade" command on the oVirt hosts, it fails due to a dependency issue.

"Problem 1: cannot install the best update candidate for package vdsm-4.50.2.2-1.el8.x86_64 - nothing provides qemu-kvm >= 15:6.2.0-11.module+el8.6.0+16360+9e5d914e.4 needed by vdsm-4.50.3.4-1.el8.x86_64"

The oVirt package vdsm-4.50.3.4-1.el8.x86_64 requires qemu-kvm-6.2.0-11.module+el8.6.0+16360+9e5d914e.4 or newer, whereas Rocky Linux provides qemu-kvm-6.2.0-11.module+el8.6.0+1052+ff61d164.6.

For the qemu-kvm package, even though their version numbers are exactly the same (6.2.0-11.module+el8.6.0), dnf/yum thinks that the "1052" build number for RockyLinux is older than the 16360 build number required for vdsm-4.50.3.4-1.el8.x86_64.

And rightly, because 1050 is "older" than 16360. Unfortunately for virt module builds we need to match the whole thing, all of the 8.6.z builds are based on qemu-kvm 6.2.0-11 and we need a zerocopy migration change that has been introduced(backported) only into later builds

When I chatted with Rocky Linux developers, they've explained me that this issue's caused by how the vendor (oVirt) developers pack their software and setting out build requirements. OVirt packages uses the exact version numbers, including the build numbers, which increment on each module build. Unfortunately, Red Hat has a higher increment than all the EL8 derivatives.

I have no idea why rocky is building the modules with different series than RHEL. This way we would indeed have to have a different requirement than rocky, and alma too. We do not test on rocky, but feel free to post a patch for that. Note we're moving away from EL8 entirely and in EL9 the module is (fortunately) gone and the versioning is straightforward again. Thanks, michal

Is it possible to solve this issue if you (oVirt developers) are able to re-set the requirements without using any build numbers (by only saying BuildRequires: qemu-kvm >= 6.2.0-11) to increase the compatibility with the other Enterprise Linux operating systems?

Thank you Erkan E _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/RGMDHPXA6DH2FH...

Hi Michal, Thanks for your reply. Yes, unfortunately, oVirt's official RPMs do not completely support other Enterprise Linux (EL) derivatives now, due to this "build number" difference between RHEL and other EL derivatives, such as Rocky Linux. It's strongly possible that we would have the same build number compatibility issue with EL9. As I understand, it's also not possible to say if Rocky Linux's 1050 build number is "older" or "newer" than RHEL's 16360 build number as RHEL and Rocky have their own individual building systems. Hi Giannis, Yes, after creating a user for you at [1], you can reach my conversation with Louis Abel, the Rocky Linux Release Engineering Lead, in their "General" chatroom between 11:17AM and 12:23PM on 2022-11-09. Our conversation is publicly available at [2]. [1] https://chat.rockylinux.org/signup_user_complete [2] https://chat.rockylinux.org/rocky-linux/pl/w54wdpenwjfwxen4myyo9xy7ar Thanks. Cheers, Erkan E