Bug 1002614

Summary: Dist-geo-reo: geo-rep monitor process crashes saying "list index out of range" during init.
Product: Red Hat Gluster Storage Reporter: Vijaykumar Koppad <vkoppad>
Component: geo-replicationAssignee: Venky Shankar <vshankar>
Status: CLOSED ERRATA QA Contact: Vijaykumar Koppad <vkoppad>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 2.1CC: aavati, amarts, bbandari, csaba, racpatel, rhs-bugs, surs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.4.0.28rhs-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 22:38:53 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:
Bug Depends On:    
Bug Blocks: 980049, 1003807    

Description Vijaykumar Koppad 2013-08-29 14:44:30 UTC
Description of problem: geo-rep monitor crashes saying "list index out of range" during init. 


Version-Release number of selected component (if applicable):glusterfs-3.4.0.27rhs-1.el6rhs.x86_64


How reproducible:happens everytime 


Steps to Reproduce:
1.create and start a geo-rep relationship between master and slave. 
2.check the status


Actual results: monitor crashes saying "list index out of range"

Expected results:geo-rep should start properly. 


Additional info:

Comment 3 Vijaykumar Koppad 2013-09-04 11:57:50 UTC
verified on glusterfs-3.4.0.30rhs-2.el6rhs.x86_64

Comment 4 Scott Haines 2013-09-23 22:38:53 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 5 Scott Haines 2013-09-23 22:41:31 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