[Bugs] [Bug 1292084] [georep+tiering]: Geo-replication sync is broken if cold tier is EC

[bugzilla at redhat.com]

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

Kotresh HR <khiremat at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |khiremat at redhat.com



--- Comment #2 from Kotresh HR <khiremat at redhat.com> ---
Description of problem:
=======================

If cold tier is Distributed-Disperse (2x{4+2}) and hot tier is
distributed-replicate(2x2), then the total subvolumes in the system are 4. But
the lock files created under shared storage are 3 and hence only 3 bricks from
3 subvolume acquires the lock and participate in syncing. While the remaining
one subvolume never participates in syncing. 

But if both cold and hot tier are Distributed-Replicate (2x2), then the lock
files created are 4 and all 4 subvolume participates in syncing

I am suspecting an issue with the xml output generation of a volume file. 

A) If cold tier is Distributed-Disperse and hot tier is Distributed-Replicate,
the xml output wrongly shows hot tier as REPLICATE: Example:

            <hotBrickType>Replicate</hotBrickType>
            <numberOfBricks>0 x 6 = 4</numberOfBricks>

B) If cold tier and hot tier both are Distributed-Replicate, the xml output is
correctly shows hot tier as Distributed-Replicate: Example:

            <hotBrickType>Distributed-Replicate</hotBrickType>
            <numberOfBricks>2 x 2 = 4</numberOfBricks>

Version-Release number of selected component (if applicable):
=============================================================
mainline


How reproducible:
=================
2/2

Steps to Reproduce:
===================
1. Create master and slave cluster
2. Create Master volume (Cold Tier as distributed-disperse and Hot tier as
Distributed-Replicate)
3. Create Slave volume (Distributed-Replicate)
4. Create and Start geo-rep session between master and slave

Actual results:
===============

Only brick from one subvolume in hot tier becomes ACTIVE


Expected results:
================

One brick from each subvolume in hot tier should become ACTIVE

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.