Why does pacemaker stop the unpromoted resource resource when pengine reports "Pre-allocation failed"?
Issue
-
The monitor operation of the PRIMARY/Master
SAPHanaresource failed and the cluster started the recovery process. During the recovery, the cluster reported the following problem:pengine: notice: color_instance: Pre-allocation failed: got node01 instead of node02 pengine: info: native_deallocate: Deallocating rsc_SAPHana_SID_HDB00:0 from node01 -
This resulted in the SECONDARY/Slave
SAPHanaresource being stopped due to the next decision taken by the cluster:pengine: notice: LogAction: * Move rsc_SAPHana_SID_HDB00:0 ( Slave node02 -> Master node01 ) pengine: notice: LogAction: * Start rsc_SAPHana_SID_HDB00:1 ( node02 ) pengine: notice: process_pe_message: Calculated transition 50175, saving inputs in /var/lib/pacemaker/pengine/pe-input-2444.bz2
Environment
- Red Hat Enterprise Linux Server 7, 8, 9 (with the High Availability Add On)
- Pacemaker
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.