Bug 1002614 - Dist-geo-reo: geo-rep monitor process crashes saying "list index out of range" during init.
Summary: Dist-geo-reo: geo-rep monitor process crashes saying "list index out of range...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: 2.1
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: ---
Assignee: Venky Shankar
QA Contact: Vijaykumar Koppad
URL:
Whiteboard:
Depends On:
Blocks: 980049 1003807
TreeView+ depends on / blocked
 
Reported: 2013-08-29 14:44 UTC by Vijaykumar Koppad
Modified: 2014-08-25 00:50 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.4.0.28rhs-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 22:38:53 UTC
Embargoed:

Attachments (Terms of Use)

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 2 Amar Tumballi 2013-08-29 18:51:33 UTC 
https://code.engineering.redhat.com/gerrit/#/c/12208/
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
Note You need to log in before you can comment on or make changes to this bug.