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.

Bug 1448945

Summary: Document multipathd reset command
Product: Red Hat Enterprise Linux 7 Reporter: Steven J. Levine <slevine>
Component: device-mapper-multipathAssignee: Steven J. Levine <slevine>
Status: CLOSED NOTABUG QA Contact: Lin Li <lilin>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: agk, bmarzins, heinzm, hutter2, jbrassow, lilin, msnitzer, mthacker, prajnoha, tgummels, woodard
Target Milestone: rcKeywords: Documentation, FutureFeature
Target Release: 7.4   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1416569 Environment:
Last Closed: 2017-05-12 17:19:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1416569    
Bug Blocks: 1289208, 1332226, 1384257    

Comment 2 Steven J. Levine 2017-05-12 17:19:20 UTC
Checking into this further, I don't think we need to add anything to the DM multipath manual.

Currently we do not document the multipathd options individually, although we do document how to find the wildcard strings and we also document raw format -- but those are general multipathd usage things rather than specific commands. Instead we refer to the man page:

"The multipathd commands can be used to administer the multipathd daemon. For information on the available multipathd commands, see the multipathd(8) man page."

This is in Section 5.12 here (The multipathd Commands):

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/DM_Multipath/multipathd_commands.html

So if we want to document this specific command we should probably document all the commands (to document this without documenting stats would be confusing), but everything is right there in the man page. 

I'm closing this BZ as not a bug, since I'm the one who opened it in the first place when I editied the release note description for the feature.  We mention this in the release notes.

However:  I don't see this documented in the multipathd man page on the latest 7.4 build I have.  I'll ping Ben about this -- but that's not part of this BZ.

If somebody things I should re-open this BZ or open a separate BZ to provide documentation for all of the multipathd commands in the DM Multipath manual (in addition to the man page), let me know, but I don't know what that would add except perhaps some examples.