i INOUE
> >
> > > -Original Message-----
> > > From: Ken Gaillot [mailto:kgail...@redhat.com]
> > > Sent: Tuesday, August 15, 2017 2:42 AM
> > > To: Cluster Labs - All topics related to open-source clustering welcomed
> > > Subject: Re: [ClusterLabs]
+ ringnumber_1 : 192.168.102.132 is UP
>
> Regards,
> Kazunori INOUE
>
> > -Original Message-
> > From: Ken Gaillot [mailto:kgail...@redhat.com]
> > Sent: Tuesday, August 15, 2017 2:42 AM
> > To: Cluster Labs - All topics related to o
On Tue, 2017-08-15 at 08:42 +0200, Jan Friesse wrote:
> Ken Gaillot napsal(a):
> > On Mon, 2017-08-14 at 12:33 -0500, Ken Gaillot wrote:
> >> On Wed, 2017-08-02 at 09:59 +, 井上 和徳 wrote:
> >>> Hi,
> >>>
> >>> In Pacemaker-1.1.17, the attribute updated while starting pacemaker is
> >>> not
Ken Gaillot napsal(a):
On Mon, 2017-08-14 at 12:33 -0500, Ken Gaillot wrote:
On Wed, 2017-08-02 at 09:59 +, 井上 和徳 wrote:
Hi,
In Pacemaker-1.1.17, the attribute updated while starting pacemaker is not
displayed in crm_mon.
In Pacemaker-1.1.16, it is displayed and results are different.
On Mon, 2017-08-14 at 12:33 -0500, Ken Gaillot wrote:
> On Wed, 2017-08-02 at 09:59 +, 井上 和徳 wrote:
> > Hi,
> >
> > In Pacemaker-1.1.17, the attribute updated while starting pacemaker is not
> > displayed in crm_mon.
> > In Pacemaker-1.1.16, it is displayed and results are different.
> >
>
On Wed, 2017-08-02 at 09:59 +, 井上 和徳 wrote:
> Hi,
>
> In Pacemaker-1.1.17, the attribute updated while starting pacemaker is not
> displayed in crm_mon.
> In Pacemaker-1.1.16, it is displayed and results are different.
>
>
Hi,
In Pacemaker-1.1.17, the attribute updated while starting pacemaker is not
displayed in crm_mon.
In Pacemaker-1.1.16, it is displayed and results are different.
https://github.com/ClusterLabs/pacemaker/commit/fe44f400a3116a158ab331a92a49a4ad8937170d
This commit is the cause, but the
