Bug 1556891 - Fuse mount crashed with only engine VM running with its image on that volume
Summary: Fuse mount crashed with only engine VM running with its image on that volume
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: RHHI-V 1.5
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1556895 1585044 1585046
Blocks: 1520836
TreeView+ depends on / blocked
 
Reported: 2018-03-15 13:04 UTC by SATHEESARAN
Modified: 2018-11-08 05:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1556895 (view as bug list)
Environment:
Last Closed: 2018-11-08 05:38:52 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:3523 0 None None None 2018-11-08 05:39:26 UTC

Description SATHEESARAN 2018-03-15 13:04:18 UTC
Description of problem:
-----------------------
With single node RHHI installation, engine volume is the only one VM running with its image on the gluster volume. After sometime, the fuse mount crashed

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHV 4.2.2-4
RHGS 3.4.0 - glusterfs-3.12.2-5.el7rhgs ( interim build )

How reproducible:
-----------------
Hit it once

Steps to Reproduce:
-------------------
1. Create distribute volume ( 1x1 ) and fuse mount it
2. Engine VM is running with its image on gluster volume

Actual results:
---------------
Observed fuse mount crash

Expected results:
-----------------
Fuse mount should not crash

Comment 1 SATHEESARAN 2018-04-29 10:37:30 UTC
Tested with RHV 4.2 & RHGS 3.4.0 nightly ( glusterfs-3.12.2-8.el7rhgs )

1. Created a engine VM on the distributed gluster volume.
2. Repeatedly created many VMs, on the distributed gluster volume and ran fio workload for a day. The issue is no longer observed

Comment 6 errata-xmlrpc 2018-11-08 05:38:52 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-2018:3523


Note You need to log in before you can comment on or make changes to this bug.