On 31/05/2022 16:11, Ken Gaillot wrote:
On Tue, 2022-05-31 at 13:16 +, Andreas Hasenack wrote:
Hi,
corosync 3.1.6
pacemaker 2.1.2
crmsh 4.3.1
TL;DR
I only seem to get a "name" attribute in the "corosync-cmapctl | grep
nodelist" output if I set an explicit name in corosync.conf's
nodelist.
Hi,
On Tue, May 31, 2022 at 1:35 PM Jan Friesse wrote:
>
> Hi,
>
> On 31/05/2022 15:16, Andreas Hasenack wrote:
> > Hi,
> >
> > corosync 3.1.6
> > pacemaker 2.1.2
> > crmsh 4.3.1
> >
> > TL;DR
> > I only seem to get a "name" attribute in the "corosync-cmapctl | grep
> > nodelist" output if I set
On Tue, 2022-05-31 at 13:16 +, Andreas Hasenack wrote:
> Hi,
>
> corosync 3.1.6
> pacemaker 2.1.2
> crmsh 4.3.1
>
> TL;DR
> I only seem to get a "name" attribute in the "corosync-cmapctl | grep
> nodelist" output if I set an explicit name in corosync.conf's
> nodelist. If I rely on the
Dne 31. 05. 22 v 15:34 Jan Friesse napsal(a):
Hi,
On 31/05/2022 15:16, Andreas Hasenack wrote:
Hi,
corosync 3.1.6
pacemaker 2.1.2
crmsh 4.3.1
TL;DR
I only seem to get a "name" attribute in the "corosync-cmapctl | grep
nodelist" output if I set an explicit name in corosync.conf's
nodelist. If
>>> Andreas Hasenack schrieb am 31.05.2022 um 15:16 in
Nachricht
:
> Hi,
>
> corosync 3.1.6
> pacemaker 2.1.2
> crmsh 4.3.1
>
> TL;DR
> I only seem to get a "name" attribute in the "corosync‑cmapctl | grep
> nodelist" output if I set an explicit name in corosync.conf's
> nodelist. If I rely on
Hi,
On 31/05/2022 15:16, Andreas Hasenack wrote:
Hi,
corosync 3.1.6
pacemaker 2.1.2
crmsh 4.3.1
TL;DR
I only seem to get a "name" attribute in the "corosync-cmapctl | grep
nodelist" output if I set an explicit name in corosync.conf's
nodelist. If I rely on the default of "name will be uname
Hi,
corosync 3.1.6
pacemaker 2.1.2
crmsh 4.3.1
TL;DR
I only seem to get a "name" attribute in the "corosync-cmapctl | grep
nodelist" output if I set an explicit name in corosync.conf's
nodelist. If I rely on the default of "name will be uname -n if it's
not set", I get nothing.
I formed a test