Bug 1845583

Summary: exportfs: describe clientspec format in metadata
Product: Red Hat Enterprise Linux 8 Reporter: Oyvind Albrigtsen <oalbrigt>
Component: resource-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.2CC: agk, cluster-maint, fdinitto, mjuricek, phagara
Target Milestone: rc   
Target Release: 8.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: resource-agents-4.1.1-55.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 02:19:46 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:

Description Oyvind Albrigtsen 2020-06-09 14:50:03 UTC
Description of problem:
Point out the standard of the format is aligned with man exportfs, and also point out the correct way to deal with the use case to export the same directory(-ies) to multiple subnets.

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


How reproducible:
100%

Steps to Reproduce:
1. pcs resource describe exportfs
2.
3.

Actual results:
Doesnt describe clientspec format.

Expected results:
Describes clientspec format.

Additional info:

Comment 7 errata-xmlrpc 2020-11-04 02:19:46 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 (Low: resource-agents security and bug fix 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/RHSA-2020:4605