Bug 2175794
| Summary: | Upgrade CRIU to 3.16 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Adrian Reber <areber> |
| Component: | criu | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED ERRATA | QA Contact: | Chao Ye <cye> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.8 | CC: | ajia, areber, jnovy |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | criu-3.17-1.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-11-14 15:28:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Adrian Reber
2023-03-06 14:56:54 UTC
@jnovy I assigned you this ticket as you have been handling the CRIU updates in the container module. Is this still correct? Hi Adrian, I have in my notes criu is maintained by you and I shouldn't touch it. Of course I can help? (In reply to Jindrich Novy from comment #2) > Hi Adrian, I have in my notes criu is maintained by you and I shouldn't > touch it. Just in RHEL 9. My assumption was in RHEL 8 you are looking at it. Basically because I have no idea how to work with modules. In RHEL 9 it is back in appstream and not in the module. So I am looking after in RHEL 9. > Of course I can help? If you can do an update in the RHEL 8 module to 3.16, that would be perfect. In the meantime - until this one is getting QE approved - assuming it's https://github.com/checkpoint-restore/criu/releases/tag/v3.16.1 that needs to land in RHEL8? How about RHAOS? Yes, 3.16.1. Or 3.17 like in RHEL 9 (https://gitlab.com/redhat/centos-stream/rpms/criu/-/blob/c9s/criu.spec). RHAOS - not sure what that stands for, but I see the acronym RHAOS used in release strings in Red Hat Enterprise Linux CoreOS (RHCOS???) RPMs. That is the place I actually need the new CRIU version. At least 3.16.1 is needed, but I think there is nothing against going directly to 3.17 like in RHEL 9. Adrian, seems criu-3.17 is not buildable in RHEL8: DEBUG util.py:634: Error: DEBUG util.py:634: Problem: package protobuf-c-devel-1.3.0-6.el8.x86_64 requires protobuf-c-compiler(x86-64) = 1.3.0-6.el8, but none of the providers can be installed DEBUG util.py:634: - conflicting requests DEBUG util.py:634: - nothing provides libprotobuf.so.15()(64bit) needed by protobuf-c-compiler-1.3.0-6.el8.x86_64 DEBUG util.py:634: - nothing provides libprotoc.so.15()(64bit) needed by protobuf-c-compiler-1.3.0-6.el8.x86_64 DEBUG util.py:636: (try to add '--skip-broken' to skip uninstallable packages) DEBUG util.py:787: Child return code was: 1 Do you know what might be causing this? That is a strange error. Both missing dependencies are available from RHEL8: [root@server01 ~]# dnf repoquery --whatprovides 'libprotoc.so.15()(64bit)' protobuf-compiler-0:3.5.0-13.el8.x86_64 protobuf-compiler-0:3.5.0-15.el8.x86_64 [root@server01 ~]# dnf info protobuf-compiler-3.5.0-15.el8.x86_64 From repo : rhel-8-for-x86_64-appstream-rpms # dnf repoquery --whatprovides 'libprotobuf.so.15()(64bit)' protobuf-0:3.5.0-13.el8.x86_64 protobuf-0:3.5.0-15.el8.x86_64 protobuf-0:3.5.0-7.el8.x86_64 [root@server01 ~]# dnf info protobuf-3.5.0-15.el8.x86_64 From repo : rhel-8-for-x86_64-appstream-rpms Both missing dependencies (on an up to date RHEl 8.7) system are from rhel-8-for-x86_64-appstream-rpms. Is your error from brew? Yes, it comes from a scratch build: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=51670374 Unfortunately I do understand how the build tag rhaos-4.13-rhel-8-build is configured. Did you try to build it against something without rhaos? The missing packages are default appstream packages and are usually available. The scratch build in c8s for stream-container-tools-rhel8-rhel-8.9.0 indeed passes: https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=2093143 But I'm unable to push the change: $ centpkg push fatal: The upstream branch of your current branch does not match the name of your current branch. To push to the upstream branch on the remote, use git push jnovy HEAD:stream-container-tools-rhel8-rhel-8.9.0 To push to the branch of the same name on the remote, use git push jnovy HEAD To choose either option permanently, see push.default in 'git help config'. To avoid automatically configuring an upstream branch when its name won't match the local branch, see option 'simple' of branch.autoSetupMerge in 'git help config'. Could not execute push: Failed to execute command. Note I can push changes without issues in other packages of container-tools which hints I might not be listed somewhere to be able to push/create MR. Not sure if you are asking me, but I don't think I can help you. I am not sure how the gitlab setup works. I have seen that some branches, even after forking, are protected. I had to push to a branch with another name to create a MR or remove the branch protection. Both approaches have worked for me. The criu-3.17 is still not available in RHEL 8. The issue I described in comment #10 was a build infra issue, I see it works now: https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=2115537 The criu-3.17-1.module+el8.9.0+18629+8bc384ce is available in 8.9.0 and owned by container-tools:rhel8. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: container-tools:rhel8 security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:6939 |