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.
Update DTM=15 - package updates should be completed before ITM=20 (around mid January) for inclusion with Comprehensive Test Cycle 2.
I do suggest you talk with Cole Robinson about rebasing upstream into RHEL 8 as he expressed concerns about some defaults that may have changed upstream that won't be compatible with RHEL 8.
@crobinso
As John mentions above, I do vaguely recall you advising against rebasing in past rhel8 releases. I thought it was mostly about the significant UI changes, but I guess there were some defaults that were changed as well. Do you still think we should keep virt-manager at v3.2 in 8.8?
Yeah I don't think we should rebase. The main concerning bit in 4.0 is virt-install mandating --os-variant. Breaking people's scripts at this point in RHEL8 cycle seems like it could start some fires.
Is there any particular pressing issue that requires a rebase?
No, there's nothing pressing that requires a rebase. I just thought it would make maintenance easier to have rhel 8 and 9 on similar releases, but I had forgotten about the incompatibilities. We should be able to backport stuff to rhel8 without too much trouble.