Bug 874734

Summary:	[RHEV-RHS]: VM's event messages showed "VM is not responding" when self-heal was in progress, though console was accessible.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Rahul Hinduja <rhinduja>
Component:	glusterfs	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED DUPLICATE	QA Contact:	Sudhir D <sdharane>
Severity:	medium	Docs Contact:
Priority:	high
Version:	2.0	CC:	grajaiya, pkarampu, rhs-bugs, vbellur, vraman
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-15 07:56:28 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 Rahul Hinduja 2012-11-08 18:22:57 UTC

Description of problem:

VM's event messages showed "VM is not responding" though console was accessible. When checked status was Green.


Version-Release number of selected component (if applicable):
glusterfs 3.3.0rhsvirt1 built on Oct 28 2012 23:50:59

(glusterfs-3.3.0rhsvirt1-8.el6rhs.x86_64)




Steps Carried:


1. distributed-replicate setup (rhs-client1.lab.eng.blr.redhat.com, rhs-client16.lab.eng.blr.redhat.com, rhs-client17.lab.eng.blr.redhat.com, rhs-client18.lab.eng.blr.redhat.com)

2. Created two VM's (VM1 and VM2). VM1 was "thin partitioned" and VM2 was "preallocated"

3. Powered-off rhs-client1.lab.eng.blr.redhat.com,  and rhs-client17.lab.eng.blr.redhat.com.

4. Started VM1

5. Deleted VM2

6. Created 2 new VM's (VM3 and VM4)

7. Performed the following on VM1 : rhn_register the vm, yum update, reboot the VM1

8. Started VM3 and rhn_register VM3. 

9. Powered-on server1 rhs-client1.lab.eng.blr.redhat.com,  and rhs-client17.lab.eng.blr.redhat.com.

10. performed yum update on VM3 and started VM4.

11. Checked the VM1 event messages and found "VM VM1 not responding".

This has been observed multiple times, hence raising the bug

Comment 5 Amar Tumballi 2012-11-12 05:22:52 UTC

not sure if its actually a storage issue. Can some one with VDSM skills check the logs? Bala?

Comment 6 Pranith Kumar K 2012-11-15 03:43:05 UTC

Federico wants this bug to be recreated and the setup to be shown to him before we can move forward with this bug. Could you please re-create and show the setup to him.

Thanks
Pranith.

Comment 7 Pranith Kumar K 2012-11-15 07:56:28 UTC


*** This bug has been marked as a duplicate of bug 874045 ***