| 4.23.0-0.nightly-2026-08-06-113242 |
Expected 4.23.9.8.202608050254-0/aarch64 image to contain assembly selected RPM build cri-o-4.23.0-202608051006.p2.gff3df29.assembly.stream.el9 but found cri-o-4.23.0-202607311814.p2.g701e877.assembly.stream.el9 installed; Expected 4.23.9.8.202608050254-0/ppc64le image to contain assembly selected RPM build cri-o-4.23.0-202608051006.p2.gff3df29.assembly.stream.el9 but found cri-o-4.23.0-202607311814.p2.g701e877.assembly.stream.el9 installed; Expected 4.23.9.8.202608050254-0/s390x image to contain assembly selected RPM build cri-o-4.23.0-202608051006.p2.gff3df29.assembly.stream.el9 but found cri-o-4.23.0-202607311814.p2.g701e877.assembly.stream.el9 installed; Expected 4.23.9.8.202608050254-0/x86_64 image to contain assembly selected RPM build cri-o-4.23.0-202608051006.p2.gff3df29.assembly.stream.el9 but found cri-o-4.23.0-202607311814.p2.g701e877.assembly.stream.el9 installed; RHCOS and 'driver-toolkit' should use the same build of package 'kernel', but RHCOSBuild:aarch64:4.23.9.8.202608050254-0 has kernel-modules-core-5.14.0-687.35.1.el9_8 and driver-toolkit-container-v4.23.0-202608051806.p2.gb63b175.assembly.stream.el9 has kernel-modules-core-5.14.0-687.36.1.el9_8 in kernel-5.14.0-687.36.1.el9_8; (...and more) |