Bug 958199

Summary:	cmd_log shows failure even though peer probe is successful
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	shilpa <smanjara>
Component:	glusterd	Assignee:	Krutika Dhananjay <kdhananj>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.1	CC:	amarts, rhs-bugs, sasundar, saujain, sdharane, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.15rhs	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	961339 (view as bug list)		Environment:
Last Closed:	2013-09-23 22:39:35 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:
Bug Blocks:	961339

Description shilpa 2013-04-30 14:57:33 UTC

Description of problem: cmd_log_history shows failure even though peer probe is successful


Version-Release number of selected component (if applicable):
RHS-2.1-20130415.n.2-RHS-x86_64-DVD1


How reproducible:
Always

Steps to Reproduce:
1. Run peer probe command

2. Check the probe status. All peers show connected
gluster peer status
Number of Peers: 3
 
Hostname: shanks-rhsvm2
Port: 24007
Uuid: aa1b0817-64c4-452c-a8b9-433b5279aa06
State: Peer in Cluster (Connected)
 
Hostname: shanks-rhsvm3
Port: 24007
Uuid: 3c68949e-133c-4750-9874-d83b1b4d1120
State: Peer in Cluster (Connected)
 
Hostname: shanks-rhsvm4
Port: 24007
Uuid: c66f680c-bec0-4c28-b5a4-a682206b7071
State: Peer in Cluster (Connected)

3. less /var/log/glusterfs/.cmd_log_history
[2013-04-30 02:15:32.318891]  : vol set help : SUCCESS
[2013-04-30 02:15:37.566846]  : vol set help : SUCCESS
[2013-04-30 13:54:29.082084] peer probe :  on host shanks-rhsvm2:24007
[2013-04-30 13:54:29.099872] peer probe : on host shanks-rhsvm2:24007 SUCCESS
[2013-04-30 13:54:32.723353] peer probe :  on host shanks-rhsvm3:24007
[2013-04-30 13:54:32.739905] peer probe : on host shanks-rhsvm3:24007 FAILED
[2013-04-30 13:54:33.605673] peer probe :  on host shanks-rhsvm4:24007
[2013-04-30 13:54:33.627015] peer probe : on host shanks-rhsvm4:24007 FAILED
 
  
Actual results:

cmd_log_history:
peer probe : on host shanks-rhsvm3:24007 FAILED


Expected results:

cmd_log_history
peer probe : on host shanks-rhsvm3:24007 SUCCESS

Additional info:
cmd_log_history shows failure even though peer probe is successful

Comment 2 Krutika Dhananjay 2013-07-11 11:00:18 UTC

*** Bug 962623 has been marked as a duplicate of this bug. ***

Comment 3 Krutika Dhananjay 2013-08-01 12:47:06 UTC

https://code.engineering.redhat.com/gerrit/#/c/11026/ <--- Posted in downstream for review.

Comment 4 SATHEESARAN 2013-08-07 07:44:39 UTC

Verified with glusterfs-3.4.0.17rhs-1

Comment 5 Scott Haines 2013-09-23 22:39:35 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.

http://rhn.redhat.com/errata/RHBA-2013-1262.html

Comment 6 Scott Haines 2013-09-23 22:43:46 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.

http://rhn.redhat.com/errata/RHBA-2013-1262.html