Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
No it won't Gerd.
We're expecting a rebase only on 8.6
Since this got moved to 8.5, the BZ is not ready for release.
Please Agree with QE into a ITM and set it.
(In reply to Danilo Cesar Lemes de Paula from comment #38)
> No it won't Gerd.
>
> We're expecting a rebase only on 8.6
Ok, so either delay to 8.6 or backport for 8.5.
Backport should be easy, so I think we should go for the later (so current ITR is fine).
(In reply to Gerd Hoffmann from comment #40)
> > backport for 8.5.
>
> Whoch of course implies this should go back to assigned state.
It doesn't. Unless you want.
The fact that the patch was sent for 8.4 and we're moving to 8.5, but there's no rebase on 8.5, means that your patch applies cleanly in 8.5.
So we can just reuse it.
Unless you want to resend it, but I assume you don't.
> The fact that the patch was sent for 8.4 and we're moving to 8.5, but
> there's no rebase on 8.5, means that your patch applies cleanly in 8.5.
Ok, good, moving the existing patch to 8.5 makes sense. Flipping back to POST then.
Reproduce this issue against qemu-kvm-4.2.0-48.module+el8.4.0+10368+630e803b.x86_64 by following the steps in comment 16 and verify this issue against qemu-kvm-4.2.0-49.module+el8.5.0+10804+ce89428a.x86_64
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: virt:rhel and virt-devel:rhel security, bug fix, and enhancement 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-2021:4191
<sound model='ich6'> <alias name='ua-e236289b-90f8-49f2-83ef-57d893217698'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound>