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.
Building virtio-win package is our standard procedure that always takes a place AFTER HCK testing and WHQL signing virtio-win drivers.
This bug is not related to any virtio-win drivers related issue, but needed as a placeholder to satisfy the build system requirements
that needs a bug to be opened in RH Bugzilla as well as exception+ flag to be set on, since the virtio-win package build ALWAYS happens
after the code freeze stage.
Please grant exception+ to this bug.
Thanks,
Vadim.
Hi Vadim,
The BZ already has blocker+ and release+ for 9.2.0, so the exception is not required, I am clearing it.
Regarding the ZStream request, this BZ has been created because the 9.1.0 virtio-win RPM request was approved as an exception: https://bugzilla.redhat.com/show_bug.cgi?id=2106282
So, why do you need a ZStream for the RPM that is already present in 9.1.0? Are you introducing changes to the RPM in 9.1.0z?
trying to understand the virtio-win RPM process -- you already have a 9.1.0 and 9.2.0 BZ
9.1.0: https://bugzilla.redhat.com/show_bug.cgi?id=2106282 (exception+, VERIFIED)
9.2.0: https://bugzilla.redhat.com/show_bug.cgi?id=2123350 (blocker+, NEW) [This BZ]
Why do you require a 9.1.0z BZ?
Is this a build requirement for how virtio-win process works?
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 (virtio-win 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/RHBA-2023:2451