[Bugs] [Bug 1183229] New: Geo-Replication creation of common_secret.pem.pub file with gsec_create

bugzilla at redhat.com bugzilla at redhat.com
Sat Jan 17 13:02:47 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1183229

            Bug ID: 1183229
           Summary: Geo-Replication creation of common_secret.pem.pub file
                    with gsec_create
           Product: GlusterFS
           Version: mainline
         Component: geo-replication
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: aavati at redhat.com, avishwan at redhat.com,
                    csaba at redhat.com, gluster-bugs at redhat.com,
                    jcastillo at redhat.com, khiremat at redhat.com,
                    ndevos at redhat.com, nlevinki at redhat.com,
                    storage-qa-internal at redhat.com, vumrao at redhat.com
        Depends On: 1126843
             Group: redhat



+++ This bug was initially created as a clone of Bug #1126843 +++

Description of problem:

In a two way geo-replication environment, we create one more session between
original slave to original master and while doing it we do use gsec_create from
origianl slave to origianl master which overwrites the content of
common_secret.pem.pub file.

And 

in a disaster recovery fail-over/fail-back situation also this is applicable
when we create fail-back session from original slave to original master for
fail-back.


How reproducible:
Always

Steps to Reproduce:
Explained in description 


Actual results:
overwrites the content of common_secret.pem.pub file.

Expected results:
We should avoid to do that , may be one file per cluster.

Additional info:

Two Way geo-replication environment :

Master volume : master1 and Slave volume : slave1

master1                         slave1  
Node1:Brick1 ----- Active ----> Node1:Brick1
Node2:Brick2 ---- Passive ----> Node2:Brick2

Master Volume : master2 and Slave volume : slave2

slave2                          master2  
Node1:Brick3 <----- Active ---- Node1:Brick3
Node2:Brick4 <---- Passive ---- Node2:Brick4

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Bugs mailing list