Bug 1787994

Summary: [geo-rep] Help for positional argument SLAVE in schedule_georep.py.in isn't clear.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Kshithij Iyer <kiyer>
Component: geo-replicationAssignee: Sunny Kumar <sunkumar>
Status: CLOSED ERRATA QA Contact: Leela Venkaiah Gangavarapu <lgangava>
Severity: low Docs Contact:
Priority: low    
Version: rhgs-3.5CC: bugs, csaba, khiremat, nchilaka, pprakash, rhs-bugs, rkothiya, sabose, sheggodu, storage-qa-internal, sunkumar
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.5.z Batch Update 3   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-6.0-38 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1786276 Environment:
Last Closed: 2020-12-17 04:51:13 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: 1786276    
Bug Blocks:    

Description Kshithij Iyer 2020-01-06 04:32:44 UTC
+++ This bug was initially created as a clone of Bug #1786276 +++

Description of problem:
SLAVE positional argument doesn't provide a clear picture of what it is when compared to mastervol and slavevol in schedule_georep.py.in. It would be better if we change it to something like "Slave hostame (<username>@SLAVEHOST or SLAVEHOST)"

Present:
----------
positional arguments:
  mastervol            Master Volume Name
  SLAVE                SLAVEHOST or root@SLAVEHOST or user@SLAVEHOST 
  slavevol             Slave Volume Name


Suggested:
-----------
positional arguments:
  mastervol            Master Volume Name
  SLAVE                Slave hostname (<username>@SLAVEHOST or SLAVEHOST)
  slavevol             Slave Volume Name


Version-Release number of selected component (if applicable):
Whatever it the latest

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2019-12-24 07:38:05 UTC ---

REVIEW: https://review.gluster.org/23919 ([geo-rep] Improving help message in schedule_georep.py.in) posted (#1) for review on master by Kshithij Iyer

--- Additional comment from Worker Ant on 2020-01-06 04:06:56 UTC ---

REVIEW: https://review.gluster.org/23919 ([geo-rep] Improving help message in schedule_georep.py.in) merged (#5) on master by Kshithij Iyer

Comment 12 errata-xmlrpc 2020-12-17 04:51:13 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 (glusterfs bug fix and enhancement 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/RHBA-2020:5603