Bug 1810516

Summary: gluster-cli commands are failing with request timeout error
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Sri Vignesh Selvan <sselvan>
Component: glusterdAssignee: Xavi Hernandez <jahernan>
Status: CLOSED ERRATA QA Contact: Kshithij Iyer <kiyer>
Severity: urgent Docs Contact:
Priority: urgent    
Version: rhgs-3.5CC: aloganat, jahernan, kiyer, nchilaka, pprakash, puebele, rcyriac, rhinduja, rhs-bugs, rkothiya, sheggodu, srakonde, storage-qa-internal, ykaul
Target Milestone: ---Keywords: Automation, AutomationBlocker, Reopened, ZStream
Target Release: RHGS 3.5.z Batch Update 2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-6.0-36 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-16 06:19:39 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:

Comment 2 Yaniv Kaul 2020-03-05 13:48:17 UTC
What did you see in the gluster logs? Any interesting errors?

Comment 4 Sanju 2020-03-06 06:02:40 UTC
Hi Vignesh,

Can you please elaborate the reproducer? Please let me know which test case in the automation suite has failed and what are the steps it performs?

Thanks,
Sanju

Comment 10 Sanju 2020-03-09 07:07:33 UTC
Hi Vignesh,

I have looked at the test cases, as you said they are basic commands which are timing out. Can you please provide output of "pstack `pidof glusterd`" when the command hungs. Bala tried to capture pstack output for https://bugzilla.redhat.com/show_bug.cgi?id=1714460. If you need help in capturing pstack output while running glusto test cases, you might want to reach out to him.

Thanks,
Sanju

Comment 12 Sanju 2020-03-13 17:10:23 UTC
*** Bug 1813294 has been marked as a duplicate of this bug. ***

Comment 102 errata-xmlrpc 2020-06-16 06:19:39 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:2572