[Pacemaker] corosync does not reflect the node status correctly

Hi, we just upgraded to corosync-1.4.5-2.5 from the suse build server. On one cluster we have the problem, that corosync-objctl does not reflect the status of nodes properly. Even when the other node stops corosync we still see: runtime.totem.mrp.srp.members.ID.status=joined But the log says:

Re: [Pacemaker] corosync does not reflect the node status correctly

Michael, Michael Schwartzkopff napsal(a): Hi, we just upgraded to corosync-1.4.5-2.5 from the suse build server. On one cluster we have the problem, that corosync-objctl does not reflect the status So if I understand it correctly, you have multiple clusters and all of them was upgraded and

[Pacemaker] Interval-origin in monitor operations does not work

Using interval-origin in monitor operation definition does not work any more. Veryfied on Pacemaker 1.1.10, but we think it does not work since 1.1.8 until now. Pengine calculates start delay in function unpack_operation and calls there crm_time_subtract. The call to crm_time_subtract with

Re: [Pacemaker] What is the reason which the node in which failure has not occurred carries out lost?

Hi, Andrew crm_mon has the processing which makes cib the newest, when pcmk_err_old_data is still received. Since this processing can be considered to be unnecessary like the processing changed by stonithd, I correct this. Please merge the following, if satisfactory.