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.
Created attachment 1568781[details]
1903 hlk screenshot
Description of problem:
I hit an issue when packing win10-1903 netkvm whql jobs, the product type is empty which should be "Lan(Server)" before.
I try to add some features in the HLk studio and found that we need to add "Device.Network.LAN.UdpSegmentationOffload" to make the product type be "Lan(Server)". The total job number does not change after adding this feature.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Still hit this issue using HLK 2004 (Guest win10-2004)
Thanks
Yu Wang
Comment 6Yvugenfi@redhat.com
2020-06-01 07:38:42 UTC
(In reply to Yu Wang from comment #5)
> Still hit this issue using HLK 2004 (Guest win10-2004)
>
> Thanks
> Yu Wang
Can you use the same workaround as before?
Thanks,
Yan.
(In reply to Yan Vugenfirer from comment #6)
> (In reply to Yu Wang from comment #5)
> > Still hit this issue using HLK 2004 (Guest win10-2004)
> >
> > Thanks
> > Yu Wang
>
> Can you use the same workaround as before?
Yes, the workaround also works
>
> Thanks,
> Yan.
Comment 12Yvugenfi@redhat.com
2021-01-04 08:37:31 UTC
This bug should stay open. The changes required by this BZ should be implemented in a year time span in order to support new MS requirments.
Comment 20RHEL Program Management
2021-08-01 07:27:06 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 21leidwang@redhat.com
2021-08-02 01:33:19 UTC
Comment 23leidwang@redhat.com
2021-10-25 02:30:50 UTC
Hi Yan,
Could you set the DTM? Thanks in advance!
Comment 24Yvugenfi@redhat.com
2021-10-25 07:22:45 UTC
(In reply to leidwang from comment #23)
> Hi Yan,
>
> Could you set the DTM? Thanks in advance!
Sorry, no DTM yet. A lot of upstream work on host side is pending in order to complete this task.
Created attachment 1568781 [details] 1903 hlk screenshot Description of problem: I hit an issue when packing win10-1903 netkvm whql jobs, the product type is empty which should be "Lan(Server)" before. I try to add some features in the HLk studio and found that we need to add "Device.Network.LAN.UdpSegmentationOffload" to make the product type be "Lan(Server)". The total job number does not change after adding this feature. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: