Bug 1754407

Summary: geo-rep: non-root session going fault due improper sub-command
Product: Red Hat Gluster Storage Reporter: Sunny Kumar <sunkumar>
Component: geo-replicationAssignee: Sunny Kumar <sunkumar>
Status: CLOSED ERRATA QA Contact: Kshithij Iyer <kiyer>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: amukherj, avishwan, bugs, csaba, khiremat, kiyer, rhinduja, rhs-bugs, rkothiya, sheggodu, storage-qa-internal, vdas
Target Milestone: ---   
Target Release: RHGS 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-15 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1753928 Environment:
Last Closed: 2019-10-30 12:23:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1753928, 1755213    
Bug Blocks: 1696809    

Description Sunny Kumar 2019-09-23 07:54:21 UTC
+++ This bug was initially created as a clone of Bug #1753928 +++

Description of problem:

Non-root session going faulty due to improper sub-command during worker start.



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

mainline

How reproducible:

Always

Steps to Reproduce:
1.
2.
3.

Actual results:

Session going faulty.

Expected results:

Session should not go faulty.


Additional info:

--- Additional comment from Worker Ant on 2019-09-20 19:59:32 UTC ---

REVIEW: https://review.gluster.org/23465 (geo-rep : fix sub-command during worker connection) posted (#1) for review on master by Sunny Kumar

Comment 2 Sunny Kumar 2019-09-23 07:56:15 UTC
Upstream Patch:

https://review.gluster.org/#/c/glusterfs/+/23465/

Comment 16 errata-xmlrpc 2019-10-30 12:23:00 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/RHEA-2019:3249