[ClusterLabs] Node attribute disappears when pacemaker is started

[井上 和徳]

Hi Ken,

I'm sorry. Attachment size was too large.
I attached it to GitHub, so look at it.
https://github.com/inouekazu/pcmk_report/blob/master/pcmk-Fri-26-May-2017.tar.bz2

> -----Original Message-----
> From: Ken Gaillot [mailto:kgaillot at redhat.com]
> Sent: Thursday, June 01, 2017 8:43 AM
> To: users at clusterlabs.org
> Subject: Re: [ClusterLabs] Node attribute disappears when pacemaker is started
> 
> On 05/26/2017 03:21 AM, 井上 和徳 wrote:
> > Hi Ken,
> >
> > I got crm_report.
> >
> > Regards,
> > Kazunori INOUE
> 
> I don't think it attached -- my mail client says it's 0 bytes.
> 
> >> -----Original Message-----
> >> From: Ken Gaillot [mailto:kgaillot at redhat.com]
> >> Sent: Friday, May 26, 2017 4:23 AM
> >> To: users at clusterlabs.org
> >> Subject: Re: [ClusterLabs] Node attribute disappears when pacemaker is started
> >>
> >> On 05/24/2017 05:13 AM, 井上 和徳 wrote:
> >>> Hi,
> >>>
> >>> After loading the node attribute, when I start pacemaker of that node, the attribute disappears.
> >>>
> >>> 1. Start pacemaker on node1.
> >>> 2. Load configure containing node attribute of node2.
> >>>    (I use multicast addresses in corosync, so did not set "nodelist {nodeid: }" in corosync.conf.)
> >>> 3. Start pacemaker on node2, the node attribute that should have been load disappears.
> >>>    Is this specifications ?
> >>
> >> Hi,
> >>
> >> No, this should not happen for a permanent node attribute.
> >>
> >> Transient node attributes (status-attr in crm shell) are erased when the
> >> node starts, so it would be expected in that case.
> >>
> >> I haven't been able to reproduce this with a permanent node attribute.
> >> Can you attach logs from both nodes around the time node2 is started?
> >>
> >>>
> >>> 1.
> >>> [root at rhel73-1 ~]# systemctl start corosync;systemctl start pacemaker
> >>> [root at rhel73-1 ~]# crm configure show
> >>> node 3232261507: rhel73-1
> >>> property cib-bootstrap-options: \
> >>>   have-watchdog=false \
> >>>   dc-version=1.1.17-0.1.rc2.el7-524251c \
> >>>   cluster-infrastructure=corosync
> >>>
> >>> 2.
> >>> [root at rhel73-1 ~]# cat rhel73-2.crm
> >>> node rhel73-2 \
> >>>   utilization capacity="2" \
> >>>   attributes attrname="attr2"
> >>>
> >>> [root at rhel73-1 ~]# crm configure load update rhel73-2.crm
> >>> [root at rhel73-1 ~]# crm configure show
> >>> node 3232261507: rhel73-1
> >>> node rhel73-2 \
> >>>   utilization capacity=2 \
> >>>   attributes attrname=attr2
> >>> property cib-bootstrap-options: \
> >>>   have-watchdog=false \
> >>>   dc-version=1.1.17-0.1.rc2.el7-524251c \
> >>>   cluster-infrastructure=corosync
> >>>
> >>> 3.
> >>> [root at rhel73-1 ~]# ssh rhel73-2 'systemctl start corosync;systemctl start pacemaker'
> >>> [root at rhel73-1 ~]# crm configure show
> >>> node 3232261507: rhel73-1
> >>> node 3232261508: rhel73-2
> >>> property cib-bootstrap-options: \
> >>>   have-watchdog=false \
> >>>   dc-version=1.1.17-0.1.rc2.el7-524251c \
> >>>   cluster-infrastructure=corosync
> >>>
> >>> Regards,
> >>> Kazunori INOUE
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.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