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.
(In reply to Jiri Dluhos from comment #5)
> qa_ack'd 🦆 - apologies for the delay.
That's OK. You set ITM to 7 which is smaller than DTM-8 set by me. Is this a mistake? Another issue is you haven't set "+" for qa_ack.
(In reply to Jiri Dluhos from comment #7)
> Oops... apologies again - it seems I had an acute case of brain eclipse :(
> qa_ack+ set.
> ITM set to 9 - please tell if more time is needed.
That's fine. The upstream patch has been ready. So ITM9 is reasonable:)
Hi Jiri,
I've done the scratch-build. Do you need to test it? If yes, the link is https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=36257231.
Btw, previously after finishing scractch-building and the testing, I directly ran rhpkg build and create an advisory on errata. This seems to be inappropriate. I'm new to the process. If I make a mistake before getting familiar with the procedure, please correct me. Thanks
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 (dmidecode 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-2021:4376