Bug 1753229

Summary:	fence_mpath: use -n/--plug/port parameter to be able to use pcmk_host_map (RHEL7)
Product:	Red Hat Enterprise Linux 7	Reporter:	Oyvind Albrigtsen <oalbrigt>
Component:	fence-agents	Assignee:	Oyvind Albrigtsen <oalbrigt>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.8	CC:	cluster-maint, cluster-qe, mjuricek, sbradley
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	fence-agents-4.2.1-28.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1753228	Environment:
Last Closed:	2020-03-31 20:01:27 UTC	Type:	---
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:	1753228
Bug Blocks:

Description Oyvind Albrigtsen 2019-09-18 12:50:36 UTC

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

Description of problem:
The lack of -n/--plug support in fence_mpath makes users unable to use a single fence device for all their nodes.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Setup fence_mpath
2. Look for WARNING:root:Parse error: Ignoring unknown option 'port=<NODENAME>' errors in the logfile.
3.

Actual results:
Error seen in logfile, and hostname/pcmk_host_map ignored.

Expected results:
hostname/pcmk_host_map used for key unless --key specified (for backwards compatibility).

Additional info:
https://github.com/ClusterLabs/fence-agents/pull/295

Comment 3 Oyvind Albrigtsen 2019-09-20 13:37:16 UTC

New build w/additional fixes found by QE: https://github.com/ClusterLabs/fence-agents/pull/298

Comment 6 errata-xmlrpc 2020-03-31 20:01:27 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-2020:1111