[Pacemaker] Node name problems after upgrading to 1.1.9

[Bernardo Cabezas Serra]

Hello,

Ohhh, sorry, but I have deleted node selavi and restarted, and now works
OK and I can't reproduce the bug :(

El 27/06/13 12:32, Andrew Beekhof escribió:
> o, more likely a bug.  Which is concerning since I thought I had this particular kind ironed out. 
> 
> Could you set PCMK_trace_functions=crm_get_peer on selavi and repeat the test?
>
> The exact way to do this will depend on your distro (which is?).
> On most rpm based distros its done in /etc/sysconfig/pacemaker

the distro is ubuntu 12.04 LTS (precise)

As I have installed all in /opt/ha, file is /opt/ha/etc/default/pacemaker.
The setting is only for debug, isn't it?  I can't see more info, but now
it works.

The strange thing is that I previously deleted both nodes, and cleaned
up selavi var/lib/pacemaker state, but it continued to fail.

The long explanation of what I have done:
- Reverting back selavi corosync to 2.3.0 (turifel still on 2.3.0.66 git
version)
- On starting, issue persisted
- On turifel, crm node status, I saw two nodes with same uname (selavi)
but different Ids.
- From turifel crm, deleted selavi two times (with some warnings).
- Put the cluster unmanaged
- Rebooted turifel node (because of a dlm lock failure due to wrong
corosync stop)
- Set up PCMK_trace_functions=crm_get_peer setting on both nodes.
- On start, all worked :/
- Upgraded back selavi corosync to 2.3.0.66 git
- Still working.


Will continue trying to reproduce issue.

PS: the PCMK_trace_functions environ is only for debugging purposes,
isn't it? (I mean: can't have resolved the issue)

Thans so much for your help!
Regards,
Bernardo

-- 
APSL
*Bernardo Cabezas Serra*
*Responsable Sistemas*
Camí Vell de Bunyola 37, esc. A, local 7
07009 Polígono de Son Castelló, Palma
Mail: bcabezas at apsl.net
Skype: bernat.cabezas
Tel: 971439771