[Bugs] [Bug 1482064] Bringing down data bricks in cyclic order results in arbiter brick becoming the source for heal.

[bugzilla at redhat.com]

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



--- Comment #1 from Karthik U S <ksubrahm at redhat.com> ---
Description of problem:
When data bricks in arbiter volume are brought down in a cyclic manner i see
that arbiter brick becomes the source for heal which should not happen as this
brick just contains meta data.

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

How reproducible:
Hit it once

Steps to Reproduce:
1. Install HC stack on arbiter volumes
2. start doing I/O on the vms
3. While IO is going on bring down one of the brick and after some time bring
up the brick and bring down another data brick 
4.After some time Bring up the down brick and i observed few VM's are getting
paused and arbiter brick becomes the source for other two bricks.

Actual results:
Vms are getting paused and i see that arbiter brick becomes source for the
other two bricks.

Expected results:
Arbiter brick should not become source for other two bricks as it does not hold
any data.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=pwbFSOJL1d&a=cc_unsubscribe