Bug 1488859

Summary:	[gfapi] Application VMs goes in to non-responding state
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED DEFERRED	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	medium
Version:	rhhi-1.1	CC:	rhs-bugs
Target Milestone:	---	Keywords:	Tracking
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1488863 (view as bug list)		Environment:
Last Closed:	2019-04-17 12:16:47 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:
Bug Depends On:	1488863, 1515149
Bug Blocks:

Description SATHEESARAN 2017-09-06 11:06:56 UTC

Description of problem:
-----------------------
With the RHHI setup with RHV 4.1.6 & RHGS 3.3.0 interim, the application VMs goes in to non-responding state after some idle time.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHEL 7.4 Server
RHGS 3.3.0 RC ( glusterfs-3.8.4-43.el7rhgs )
RHV 4.1.6 nightly

How reproducible:
-----------------
2/2

Steps to Reproduce:
-------------------
1. Create a 3 node cluster with gluster and virt capability enabled.
2. Enable libgfapi access by editing the cluster
3. Create a RHEL 7.4 VM, seal the VM and create a template.
4. Using the template, create 30 VMs across the cluster.
5. Leave the setup idle for sometime

Actual results:
---------------
After sometime, VMs gone in to non-responding state

Expected results:
-----------------
VMs should be up and healthy

Comment 1 Sahina Bose 2017-10-11 11:16:49 UTC

Moving to 1.2, as this issue happens only with gfapi

Comment 2 Sahina Bose 2018-10-15 05:58:54 UTC

Setting to medium - as gfapi change in limbo