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.

Development for nvme-stas is now considered complete with 2.1.1. All features that we wanted have all been implemented with the exception of support for TP8019.

Updating nvme-stas from 2.0 to 2.1.1 may be a good idea. There's no major problems with 2.0, but our test team found a few issues that have now been fixed in 2.1.1. 

For a description of all the changes between 2.0 and 2.1.1 you can check out https://github.com/linux-nvme/nvme-stas/blob/main/NEWS.md.

Marco, I have a new nvme-stas.rpm available at: 

https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=1788323

I've tested this out on rhel-storage-68 and everything looks like it's working fine.

Please set QA+ for this BZ.

Marco can you test the new nvme-stas RPM at: https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=1788323

No new issues were found with nvme-stas-2.1.1-1:

# rpm -qa nvme-stas
nvme-stas-2.1.1-1.el9.noarch

https://beaker.engineering.redhat.com/jobs/7472308
https://beaker.engineering.redhat.com/jobs/7473026

No new issues were found with nvme-stas-2.1.1-1:

# rpm -qa nvme-stas
nvme-stas-2.1.1-1.el9.noarch

https://beaker.engineering.redhat.com/jobs/7535308
https://beaker.engineering.redhat.com/jobs/7536654

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 (nvme-stas 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/RHEA-2023:2244