Bug 1633177
Summary: | gluster-NFS crash while expanding volume | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vijay Avuthu <vavuthu> | |
Component: | gluster-nfs | Assignee: | Jiffin <jthottan> | |
Status: | CLOSED ERRATA | QA Contact: | Jilju Joy <jijoy> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | rhgs-3.4 | CC: | amukherj, dang, grajoria, jthottan, kkeithle, mbenjamin, rcyriac, rgowdapp, rhinduja, rhs-bugs, sanandpa, sankarshan, sheggodu, skoduri, storage-qa-internal, vavuthu, ykaul | |
Target Milestone: | --- | Keywords: | AutomationBlocker, AutomationTriaged, ZStream | |
Target Release: | RHGS 3.4.z Batch Update 3 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.12.2-33 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1651439 (view as bug list) | Environment: | ||
Last Closed: | 2019-02-04 07:41:25 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
Vijay Avuthu
2018-09-26 11:02:07 UTC
If this is fairly reproducible and we find this use case to be important why we're not marking it as blocker for 3.4.2 so that this can come to the triage queue of blocker/exception proposed bugs? What's blocking us here? (Of course, not all BZs should be marked as blocker through automation test, but this seems important?) Jiffin - have we got a chance to look at the automation test which leads to this crash? Have we tried the same in our local setup? (In reply to Atin Mukherjee from comment #6) > If this is fairly reproducible and we find this use case to be important why > we're not marking it as blocker for 3.4.2 so that this can come to the > triage queue of blocker/exception proposed bugs? What's blocking us here? > I was waiting for the discussion to close properly on flags and keywords on the program mailing list and hence approached via need_info. This wasnt a inflight bug. However, based on the discussion. Moving forward with below explanation. During the automation run on nfs client, we are either seeing 1. client hung Bug 1648783 Or 2. NFS crash Bug 1633177 From the automation runs perspective, I consider these as AutomationBlocker for NFS protocols (Different usecases) and hence setting the appropriate keyword and flag for traction and decision. Checked manually and through automation. No crash was observed even after executing the testcase multiple times. Observed hang(bz 1648783) a couple of times. Volume types used: Distribute, Distributed-Replicate, Distributed-Replicate(arbiter) Verified in version: glusterfs-3.12.2-36.el7rhgs.x86_64 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-2019:0263 |