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.
Bug 2076535 - virtio-win RPM for rhel-9.0.z
Summary: virtio-win RPM for rhel-9.0.z
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Qianqian Zhu
URL:
Whiteboard:
Depends On:
Blocks: 2082607
TreeView+ depends on / blocked
 
Reported: 2022-04-19 09:47 UTC by Vadim Rozenfeld
Modified: 2022-11-15 11:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2082607 (view as bug list)
Environment:
Last Closed: 2022-11-15 10:45:57 UTC
Type: ---
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-119181 0 None None None 2022-04-19 09:52:18 UTC
Red Hat Product Errata RHBA-2022:8261 0 None None None 2022-11-15 10:46:13 UTC

Description Vadim Rozenfeld 2022-04-19 09:47:55 UTC 
This bug is a clone https://bugzilla.redhat.com/show_bug.cgi?id=2044343
for 9.0.z stream virtio-win rpm
Comment 1 Yash Mankad 2022-04-22 15:44:42 UTC 
Hi Vadim, 
If the 9.0 bug is VERIFIED, why are you requesting a clone for 9.0z?
Is it for process only?
Comment 2 Vadim Rozenfeld 2022-04-26 01:22:13 UTC 
Hey Yash,
I'm a bit confused here. For 9.0.z do I need to open a bug for 8.7 or 9.1 first
and ask for z-stream?

Best regards,
Vadim.
Comment 3 Yash Mankad 2022-04-29 15:28:41 UTC 
(In reply to Vadim Rozenfeld from comment #2)
> Hey Yash,
> I'm a bit confused here. For 9.0.z do I need to open a bug for 8.7 or 9.1
> first
> and ask for z-stream?
> 

Hi Vadim,

Yes, to request a BZ for 9.0z, you need a 9.1 BZ, and then request 9.0z on that BZ.
I've set ITR=9.1.0 for this one, so we can use this BZ as the 9.1 bug, and once it has release+ (missing ITM), I will grant it zstream+ and create the 9.0z clone.
Comment 4 Vadim Rozenfeld 2022-05-02 07:13:54 UTC 
(In reply to Yash Mankad from comment #3)
> (In reply to Vadim Rozenfeld from comment #2)
> > Hey Yash,
> > I'm a bit confused here. For 9.0.z do I need to open a bug for 8.7 or 9.1
> > first
> > and ask for z-stream?
> > 
> 
> Hi Vadim,
> 
> Yes, to request a BZ for 9.0z, you need a 9.1 BZ, and then request 9.0z on
> that BZ.
> I've set ITR=9.1.0 for this one, so we can use this BZ as the 9.1 bug, and
> once it has release+ (missing ITM), I will grant it zstream+ and create the
> 9.0z clone.

Thanks a lot, Yash.
Comment 9 errata-xmlrpc 2022-11-15 10:45:57 UTC 
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-2022:8261
Note You need to log in before you can comment on or make changes to this bug.