Bug 2193038
Summary: | virt-launcher has old packages, Dockerfile using virt:av instead of virt:rhel on 8.6 | ||
---|---|---|---|
Product: | Container Native Virtualization (CNV) | Reporter: | Germano Veit Michel <gveitmic> |
Component: | Virtualization | Assignee: | sgott |
Status: | CLOSED ERRATA | QA Contact: | Kedar Bidarkar <kbidarka> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 4.12.2 | CC: | abologna, dholler, fdeutsch, kbidarka, mrashish, nashok, nkoenig, sgott, ycui, ymankad, zpeng |
Target Milestone: | --- | ||
Target Release: | 4.12.3 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | cnv v4.12.3-62 / virt-launcher v4.12.3-12 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-05-23 22:31:22 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: | |||
Bug Depends On: | |||
Bug Blocks: | 2169168 |
Description
Germano Veit Michel
2023-05-04 05:17:42 UTC
@sgott @dholler on what side do we need to address this? Kedar, how can we prevent this in future? Michal, is this BZ accurate? We were tracking that RHEL-AV was going away in RHEL-9. Is it true that 8.6 was shipped but is no longer maintained? Or is the problem that OSBS hasn't gotten refreshed snapshots? (In reply to Fabian Deutsch from comment #4) > @sgott @dholler on what side do we need to address > this? > > Kedar, how can we prevent this in future? We will add new testcases, to capture the virt packages on the virt-launcher images, to track this. podman run --rm -it --entrypoint=/usr/bin/rpm registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-virt-launcher:v4.12.3-12 -qa | grep qemu-kvm qemu-kvm-core-6.2.0-11.module+el8.6.0+18167+43cf40f3.8.x86_64 qemu-kvm-common-6.2.0-11.module+el8.6.0+18167+43cf40f3.8.x86_64 I can reproduce this with CNV-v4.12.3-49 verify with build: CNV-v4.12.3-62 step: 1. deploy cnv 2. create and start vm 3. login virt-launcher and check qemu version sh-4.4$ rpm -qa | grep qemu-kvm qemu-kvm-core-6.2.0-11.module+el8.6.0+18167+43cf40f3.8.x86_64 qemu-kvm-common-6.2.0-11.module+el8.6.0+18167+43cf40f3.8.x86_64 sh-4.4$ dnf module list | grep virt virt rhel [e] common Virtualization module sh-4.4$ dnf list --showduplicates qemu-kvm-core | grep el8.6 qemu-kvm-core.x86_64 15:6.2.0-11.module+el8.6.0+18167+43cf40f3.8 @odcs-1991437 sh-4.4$ rpm -qa |grep libvirt libvirt-daemon-8.0.0-5.9.module+el8.6.0+18552+b96c5a91.x86_64 libvirt-daemon-driver-qemu-8.0.0-5.9.module+el8.6.0+18552+b96c5a91.x86_64 move to verified. 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 (OpenShift Virtualization 4.12.3 Images), 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/RHEA-2023:3283 |