Junko IKEDA
2013-04-10 09:13:45 UTC
Hi,
I set upper-case hostname (GUEST03/GUEST4) and run Pacemaker 1.1.9 +
Corosync 2.3.0.
[***@GUEST04 ~]# crm_mon -1
Last updated: Wed Apr 10 15:12:48 2013
Last change: Wed Apr 10 14:02:36 2013 via crmd on GUEST04
Stack: corosync
Current DC: GUEST04 (3232242817) - partition with quorum
Version: 1.1.9-e8caee8
2 Nodes configured, unknown expected votes
1 Resources configured.
Online: [ GUEST03 GUEST04 ]
dummy (ocf::pacemaker:Dummy): Started GUEST03
for example, call crm shell with lower-case hostname.
[***@GUEST04 ~]# crm node standby guest03
ERROR: bad lifetime: guest03
"crm node standby GUEST03" surely works well,
so crm shell just doesn't take into account the hostname conversion.
It's better to accept the both of the upper/lower-case.
"node standby", "node delete", "resource migrate(move)" get hit with this
issue.
Please see the attached.
Thanks,
Junko
I set upper-case hostname (GUEST03/GUEST4) and run Pacemaker 1.1.9 +
Corosync 2.3.0.
[***@GUEST04 ~]# crm_mon -1
Last updated: Wed Apr 10 15:12:48 2013
Last change: Wed Apr 10 14:02:36 2013 via crmd on GUEST04
Stack: corosync
Current DC: GUEST04 (3232242817) - partition with quorum
Version: 1.1.9-e8caee8
2 Nodes configured, unknown expected votes
1 Resources configured.
Online: [ GUEST03 GUEST04 ]
dummy (ocf::pacemaker:Dummy): Started GUEST03
for example, call crm shell with lower-case hostname.
[***@GUEST04 ~]# crm node standby guest03
ERROR: bad lifetime: guest03
"crm node standby GUEST03" surely works well,
so crm shell just doesn't take into account the hostname conversion.
It's better to accept the both of the upper/lower-case.
"node standby", "node delete", "resource migrate(move)" get hit with this
issue.
Please see the attached.
Thanks,
Junko