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

[Kostiantyn Ponomarenko]

The idea is to have NTP daemon syncing time right after boot, while
the cluster software starts automatically also at the boot time.
So, there is a slight possibilities that the time will be changed after the
cluster has been started.
That is my concern.

Thank you,
Kostya

On Fri, Jul 24, 2015 at 8:56 AM, Ulrich Windl <
Ulrich.Windl at rz.uni-regensburg.de> wrote:

> >>> Kostiantyn Ponomarenko <konstantin.ponomarenko at gmail.com> schrieb am
> 23.07.2015
> um 18:09 in Nachricht
> <CAEnTH0eKJV8udjp5GobJpp8yOVzRcT_XSuV7gn93topPALCh2g at mail.gmail.com>:
> > Hi,
> >
> > If you do:
> >     # date --set="1990-01-01 01:00:00"
>
> Why would you do that in a running cluster?
>
> > when only one node is present in the cluster and while the cluster is
> > working, and then stop a resource (any resource), the cluster fails the
> > resource once, shows it as Started, but the resource actually is still
> > stopped.
> >
> > Is it the expected behavior in the cluster?
> > Is it prohibited to change time/date while the cluster is working?
> >
> > The environment: two node cluster with just one node up; pacemaker
> 1.1.12.
> >
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20150724/1dccff9e/attachment.htm>