[Gluster-devel] gluster volume stop and the regressions

[Nithya Balachandran]

On 1 February 2018 at 09:46, Milind Changire <mchangir at redhat.com> wrote:

> If a *volume stop* fails at a user's production site with a reason like
> *rebalance session is active* then the admin will wait for the session to
> complete and then reissue a *volume stop*;
>
> So, in essence, the failed volume stop is not fatal; for the regression
> tests, I would like to propose to change a single volume stop to
> *EXPECT_WITHIN 30* so that a if a volume cannot be stopped even after 30
> seconds, then it could be termed fatal in the regressions scenario
>
> Any comments about the proposal ?
>

I would prefer to find out why it could not be stopped as in most test
cases we would expect that the operation should succeed. If a particular
test is failing because rebalance is taking longer than expected, we need
to find out why.

>
>
> --
> Milind
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20180201/659305a8/attachment.html>