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 1700474 - nvme-cli: Revert stop-on-failure with connect-all
Summary: nvme-cli: Revert stop-on-failure with connect-all
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nvme-cli
Version: 7.7
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: 7.7
Assignee: David Milburn
QA Contact: Zhang Yi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-16 16:36 UTC by David Milburn
Modified: 2019-08-06 13:17 UTC (History)
5 users (show)

Fixed In Version: nvme-cli-1.8.1-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:17:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2317 0 None None None 2019-08-06 13:17:57 UTC

Description David Milburn 2019-04-16 16:36:19 UTC 
The patch that added special treatment for EALREADY connect failures
also changed the behavior on what happens if a discovery log contains
an entry that is not connectable by the system or host port. If it
encounters a log entry that can't be connected to, it will not attempt
to connect to any log entries beyond it. This can leave lots of devices
unconnected to.

Revert the stop-on-failure introduced by the previous patch.

Specifically, this failed for me on an FC array that had a discovery log
entry for a port that was not visible via zoning for the initiator
port being used.

<more notes from James Smart>
A regression where nvme cli will stop it's connect-all loop if it 
encounters a discovery log entry that cannot be connected to. The 
regression as added in rev 1.7 of the cli and continues to exist in 
1.8 of the cli.  A fix was posted upstream today, but is not yet in 
the nvme-cli repository.     Description: Anything that was in the log 
up to that point would be connected. Anything after that would not 
even be attempted to be connected to. It appears this is a common 
thing on NetApp arrays. Their discovery log contains all target FC 
ports for the array and it's not uncommon for an initiator to not be 
zoned with all ports on the array - so its not uncommon to encounter 
failures connecting to a log entry (which is the following dmesg string:
Failed to write to /dev/nvme-fabrics: No such file or directory"
and kernel: nvme_fc: nvme_fc_create_ctrl: 
nn-0x200000a0986a8b5f:pn-0x200400a0986a8b5f - 
nn-0x200000109b3c081f:pn-0x100000109b3c081f combination not found
Any entries in the log would not be connected to - so nvme controllers 
won't be seen for them.

A fix for this error is to build the cli with this patch: 
http://lists.infradead.org/pipermail/linux-nvme/2019-April/023319.html
Comment 7 David Milburn 2019-04-24 17:06:01 UTC 
Hi Laurie, just FYI we are going to try and update nvme-cli
to v1.8.1 consistent with RHEL8 version. Thanks.
Comment 8 James Smart 2019-04-24 17:51:52 UTC 
Thank you Dave!
Comment 11 errata-xmlrpc 2019-08-06 13:17:54 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, 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-2019:2317
Note You need to log in before you can comment on or make changes to this bug.