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.
while live-migrating many instances concurrently, libvirt sometimes return internal error: migration was active, but no RAM info was set [rhel-8.4.0.z]
Do we need to fix and verify this bug for RHEL Non-AV 8.4.z? We already have RHEL AV 8.4.z bug to track this issue:
Bug 2168214 - while live-migrating many instances concurrently, libvirt sometimes return internal error: migration was active, but no RAM info was set [rhel-av 8.4z]
Comment 4Dr. David Alan Gilbert
2023-02-14 14:40:27 UTC
The fix is already done here; so just needs to confirm the same tests as the others.
Comment 5Germano Veit Michel
2023-02-14 22:03:41 UTC
The original request was 8.4AV only to cover OSP 16.2, but if its already done then why not.
Comment 6Dr. David Alan Gilbert
2023-02-15 09:43:35 UTC
Actually, it turns out that the non-AV one doesn't build; although I can fix it, if we're saying we don't actually need it, then lets kill it off.
If someone does need it, then we can easily reopen.