Bug 1664335 - [geo-rep]: Transport endpoint not connected with arbiter volumes
Summary: [geo-rep]: Transport endpoint not connected with arbiter volumes
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Shwetha K Acharya
QA Contact:
URL:
Whiteboard:
Depends On: 1640573
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-08 13:46 UTC by Harpreet Kaur Lalwani
Modified: 2020-01-31 10:13 UTC (History)
3 users (show)

Fixed In Version:
Clone Of: 1640573
Environment:
Last Closed: 2020-01-31 10:13:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22001 0 None Merged geo-rep: Fix for \"Transport End Point not connected\" issue 2020-01-31 10:13:43 UTC

Comment 1 Worker Ant 2019-01-08 13:52:51 UTC 
REVIEW: https://review.gluster.org/22001 (geo-rep: Fix for \"Transport End Point not connected\" issue) posted (#4) for review on master by Harpreet Kaur Lalwani
Comment 3 Worker Ant 2019-01-09 07:30:56 UTC 
REVIEW: https://review.gluster.org/22001 (geo-rep: Fix for \"Transport End Point not connected\" issue) posted (#6) for review on master by Harpreet Kaur Lalwani
Comment 6 Worker Ant 2020-01-31 10:13:44 UTC 
REVIEW: https://review.gluster.org/22001 (geo-rep: Fix for \"Transport End Point not connected\" issue) merged (#9) on master by Sunny Kumar
Note You need to log in before you can comment on or make changes to this bug.