Bug 990424 - Dist-geo-rep : replace-brick operations on master won't be allowed if the geo-rep session is stopped
Summary: Dist-geo-rep : replace-brick operations on master won't be allowed if the geo...
Keywords:
Status: CLOSED DUPLICATE of bug 1176824
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: 2.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Kotresh HR
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard: usability
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-31 07:42 UTC by Vijaykumar Koppad
Modified: 2015-04-16 14:06 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-31 07:07:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Vijaykumar Koppad 2013-07-31 07:42:32 UTC
Description of problem: Even if the geo-rep session is stopped, replace-brick operations won't be allowed, You need to delete a session in run replace-brick operations. 


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


How reproducible:Happens every time 


Steps to Reproduce:
1.Create, start and stop geo-rep relationship between master and slave.
2.try start replace-brick operation on master.

Actual results: replace-brick start fails,even if the geo-rep session is stopped 


Expected results: Replace-brick should succeed to start, if geo-rep is stopped. It need not have to be deleted , to start replace-brick 


Additional info:

Comment 2 Scott Haines 2013-09-27 17:08:03 UTC
Targeting for 3.0.0 (Denali) release.

Comment 3 Vivek Agarwal 2014-04-07 11:40:09 UTC
Per bug triage, between dev, PM and QA, moving these out of denali

Comment 4 Nagaprasad Sathyanarayana 2014-05-06 10:35:06 UTC
BZs not targeted for Denali.

Comment 6 Aravinda VK 2014-12-24 07:06:37 UTC
Seems like a duplicate of 1176824

Comment 7 Aravinda VK 2015-03-31 07:07:42 UTC
As per Comment 6, Closing this Bug.

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


Note You need to log in before you can comment on or make changes to this bug.