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.

+++ This bug was initially created as a clone of Bug #1680156 +++

Per James Smart:

There's one significant issue in the cli where it broke FC. 1.7 "release" was cut on 1/10/19

Please include the FC fix which went in on 2/4/19. 

https://github.com/linux-nvme/nvme-cli/commit/324fce3d6adacdd0aad37e3b1962ab59f601050e

Thank you
Laurie

--- Additional comment from David Milburn on 2019-02-22 21:11:13 UTC ---

Thanks Laurie, I have requested v1.7 to be pulled into Fedora.
As long as that happens in time, I plan on pulling v1.7 into RHEL7.7,
so please also file a RHEL7.7 BZ.

(we may have to start pinging the Fedora maintainer)
https://bugzilla.redhat.com/show_bug.cgi?id=1677081

Verified with the RHEL-7.7 Snapshot 3 compose RHEL-7.7-20190619.0:

# nvme version
nvme version 1.8.1

# rpm -qa nvme-cli
nvme-cli-1.8.1-3.el7.x86_64

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.