rg
> Subject: Re: [ClusterLabs] Node attribute disappears when pacemaker is started
>
> Hi,
>
> Looking at the incident around May 26 16:40:00, here is what happens:
>
> You are setting the attribute for rhel73-2 from rhel73-1, while rhel73-2
> is not part of cluster from rh
attached -- my mail client says it's 0 bytes.
>>
>>>> -Original Message-
>>>> From: Ken Gaillot [mailto:kgail...@redhat.com]
>>>> Sent: Friday, May 26, 2017 4:23 AM
>>>> To: users@clusterlabs.org
>>>> Subject: Re: [ClusterLabs
y, May 26, 2017 4:23 AM
>> To: users@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 sta
Hi Ken,
I got crm_report.
Regards,
Kazunori INOUE
> -Original Message-
> From: Ken Gaillot [mailto:kgail...@redhat.com]
> Sent: Friday, May 26, 2017 4:23 AM
> To: users@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
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
