[Bugs] [Bug 1278390] Data Tiering:Regression:Detach tier commit is passing when detach tier is in progress

bugzilla at redhat.com bugzilla at redhat.com
Wed Nov 25 04:09:30 UTC 2015


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

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(byarlaga at redhat.c
                   |                            |om)



--- Comment #7 from Atin Mukherjee <amukherj at redhat.com> ---
(In reply to Bhaskarakiran from comment #5)
> I am not sure if it gets hit with one brick. The setup i configured is 8+4
> ec volume and 2x2 dist-rep tier volume for it.
Well, I do not think the number of bricks matter here as the validation is in
the staging and we do not really check how many number of bricks are configured
for the volume at this point. However, I'll try to execute the same steps and
see whether the issue persists.
> 
> 1. Create 8+4 ec volume and attach 2x2 dist-rep tier volume
> 2. Start linux untar and some parallel writes
> 3. Start detach-tier
> 4. Once the status shows as completed on any of the node, issue detach-tier
> commit command and it passes. 
Were you sure that at the time you performed a detach commit, other nodes
haven't finished the ongoing scan? How did you guarantee that? It could very
well be that you executed the command on other nodes to check the status and at
that time it showed that detach is in progress but by the time you executed
detach commit, the scan was completed?
> 
> If the commit is run on any of the node which has in-progress status, it
> would fail with correct message.

-- 
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=KV9of8yOxu&a=cc_unsubscribe


More information about the Bugs mailing list