[Gluster-Maintainers] 3.7.10 known issue

[Atin Mukherjee]

On 04/04/2016 07:43 PM, Atin Mukherjee wrote:
> 
> 
> On 04/04/2016 06:53 PM, Kaleb KEITHLEY wrote:
>> On 04/04/2016 09:11 AM, Kaleb KEITHLEY wrote:
>>> On 04/04/2016 07:41 AM, Niels de Vos wrote:
>>>> On Fri, Apr 01, 2016 at 09:56:45AM +0530, Atin Mukherjee wrote:
>>>>> Hi Kaushal,
>>>>>
>>>>> We hit a regression yesterday where GlusterD fails to restart when the
>>>>> volume has snapshots. Refer to [1] for more details. The work around is
>>>>> also a bit tedious where each snapshot brick folders have to be created
>>>>> manually and I don't think see any other alternative workaround here.
One correction here, the issue is seen only when the node reboots, not
glusterd. Considering that users won't reboot machines often, we can
still live with it for the next scheduled release? I'll be working on
the release note to put down the work around.
>>>>>
>>>>> IMO, we should mention this as known issue in the release note for 3.7.10.
>>>>
>>>> This sounds serious enough to not package 3.7.10 and have users update
>>>> to it automatically.
>>>
>>> That djinni is already out of the bottle.
>>
>> If there's a fix available then it seems (to me) that a better path
>> forward is to release 3.7.11 quickly.
> Patch http://review.gluster.org/#/c/13869 is under review.
>>
>> --
>>
>> Kaleb
>>
>>
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> http://www.gluster.org/mailman/listinfo/maintainers
>