[ClusterLabs] Antw: Re: Antw: Re: Antw: Re: Antw: pacemaker doesn't correctly handle a resource after time/date change

[Kostiantyn Ponomarenko]

I agree that the possibility of this to happen is really really small =)
But the consequences can be huge =(

Thank you,
Kostya

On Fri, Aug 21, 2015 at 4:06 PM, Kostiantyn Ponomarenko <
konstantin.ponomarenko at gmail.com> wrote:

> As I wrote in the previous email, it could happen when NTP servers are
> unreachable before Pacemaker's start, and then, after some time, NTP
> becomes reachable again.
> So it is possible that time will be synchronized in any direction: 15 min
> or 23 min or 1 hour or 12 hours backward/forward.
> And in that case the bug will appear itself.
>
> Thank you,
> Kostya
>
> On Mon, Aug 17, 2015 at 3:01 AM, Andrew Beekhof <andrew at beekhof.net>
> wrote:
>
>>
>> > On 8 Aug 2015, at 12:43 am, Kostiantyn Ponomarenko <
>> konstantin.ponomarenko at gmail.com> wrote:
>> >
>> > Hi Andrew,
>> >
>> > So the issue is:
>> >
>> > Having one node up and running, set time on the node backward to, say,
>> 15 min (generally more than 10 min), then do "stop" for a resource.
>> > That leads to the next - the cluster fails the resource once, then
>> shows it as "started", but the resource actually remains "stopped".
>> >
>> > Do you need more input from me on the issue?
>>
>> I think “why” :)
>>
>> I’m struggling to imagine why this would need to happen.
>>
>> >
>> > Thank you,
>> > Kostya
>> >
>> > On Wed, Aug 5, 2015 at 3:01 AM, Andrew Beekhof <andrew at beekhof.net>
>> wrote:
>> >
>> > > On 4 Aug 2015, at 7:31 pm, Kostiantyn Ponomarenko <
>> konstantin.ponomarenko at gmail.com> wrote:
>> > >
>> > >
>> > > On Tue, Aug 4, 2015 at 3:57 AM, Andrew Beekhof <andrew at beekhof.net>
>> wrote:
>> > > Github might be another.
>> > >
>> > > I am not able to open an issue/bug here
>> https://github.com/ClusterLabs/pacemaker
>> >
>> > Oh, for pacemaker bugs see http://clusterlabs.org/help.html
>> > Can someone clearly state what the issue is?  The thread was quite
>> fractured and hard to follow.
>> >
>> > >
>> > > Thank you,
>> > > Kostya
>> > > _______________________________________________
>> > > Users mailing list: Users at clusterlabs.org
>> > > http://clusterlabs.org/mailman/listinfo/users
>> > >
>> > > Project Home: http://www.clusterlabs.org
>> > > Getting started:
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> > > Bugs: http://bugs.clusterlabs.org
>> >
>> >
>> > _______________________________________________
>> > Users mailing list: Users at clusterlabs.org
>> > http://clusterlabs.org/mailman/listinfo/users
>> >
>> > Project Home: http://www.clusterlabs.org
>> > Getting started:
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> > Bugs: http://bugs.clusterlabs.org
>> >
>> > _______________________________________________
>> > Users mailing list: Users at clusterlabs.org
>> > http://clusterlabs.org/mailman/listinfo/users
>> >
>> > Project Home: http://www.clusterlabs.org
>> > Getting started:
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> > Bugs: http://bugs.clusterlabs.org
>>
>>
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org
>> http://clusterlabs.org/mailman/listinfo/users
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20150821/49503d11/attachment.htm>