Testing pacemaker/drbd failover on two nodes active-standby cluster based on rocky9.5/pacemaker 2.1.8

Rocky Linux Help & Support
1

Hi,

There are two services (nfs and iscsi) colocated to always run on the same node.

So if I set active node as standby node,

pcs node standby memverge

two services successfully moved to another node memverge2,

Node List:

  • Node memverge (27): standby, feature set 3.19.5
  • Node memverge2 (28): online, feature set 3.19.5

Full List of Resources:

  • ipmi-fence-memverge (stonith:fence_ipmilan): Started memverge2
  • ipmi-fence-memverge2 (stonith:fence_ipmilan): Stopped
  • Clone Set: ha-nfs-clone [ha-nfs] (promotable):
    • ha-nfs (ocf:linbit:drbd): Promoted memverge2
    • ha-nfs (ocf:linbit:drbd): Stopped
  • Resource Group: g_nfs:
    • p_pb_block (ocf:heartbeat:portblock): Started memverge2
    • p_virtip (ocf:heartbeat:IPaddr2): Started memverge2
    • p_fs_nfs_internal_info_HA (ocf:heartbeat:Filesystem): Started memverge2
    • p_fs_nfsshare_exports_HA (ocf:heartbeat:Filesystem): Started memverge2
    • p_nfsserver (ocf:heartbeat:nfsserver): Started memverge2
    • p_expfs_nfsshare_exports_HA (ocf:heartbeat:exportfs): Started memverge2
    • p_pb_unblock (ocf:heartbeat:portblock): Started memverge2
  • Clone Set: ha-iscsi-clone [ha-iscsi] (promotable):
    • ha-iscsi (ocf:linbit:drbd): Promoted memverge2
    • ha-iscsi (ocf:linbit:drbd): Stopped
  • Resource Group: g_iscsi:
    • p_iscsi_portblock_on_drbd3 (ocf:heartbeat:portblock): Started memverge2
    • p_iscsi_ip0 (ocf:heartbeat:IPaddr2): Started memverge2
    • p_iscsi_ip1 (ocf:heartbeat:IPaddr2): Started memverge2
    • p_iscsi_target_drbd3 (ocf:heartbeat:iSCSITarget): Started memverge2
    • p_iscsi_lun_drbd3 (ocf:heartbeat:iSCSILogicalUnit): Started memverge2
    • p_iscsi_portblock_off_drbd3 (ocf:heartbeat:portblock): Started memverge2

After that switching, two additional records appeared in the cib

      <expression attribute="#uname" operation="ne" value="memverge2" id="drbd-fence-by-handler-ha-iscsi-expr-28-ha-iscsi-clone"/>
      <expression attribute="#uname" operation="ne" value="memverge2" id="drbd-fence-by-handler-ha-nfs-expr-28-ha-nfs-clone"/>

And if I do unstandby inactive node and standby active node, two services stopped without switching,

pcs node unstandby memverge

pcs node standby memverge2

Node List:

  • Node memverge (27): online, feature set 3.19.5
  • Node memverge2 (28): standby, feature set 3.19.5

Full List of Resources:

  • ipmi-fence-memverge (stonith:fence_ipmilan): Stopped
  • ipmi-fence-memverge2 (stonith:fence_ipmilan): Started memverge
  • Clone Set: ha-nfs-clone [ha-nfs] (promotable):
    • ha-nfs (ocf:linbit:drbd): Unpromoted memverge
    • ha-nfs (ocf:linbit:drbd): Stopped
  • Resource Group: g_nfs:
    • p_pb_block (ocf:heartbeat:portblock): Stopped
    • p_virtip (ocf:heartbeat:IPaddr2): Stopped
    • p_fs_nfs_internal_info_HA (ocf:heartbeat:Filesystem): Stopped
    • p_fs_nfsshare_exports_HA (ocf:heartbeat:Filesystem): Stopped
    • p_nfsserver (ocf:heartbeat:nfsserver): Stopped
    • p_expfs_nfsshare_exports_HA (ocf:heartbeat:exportfs): Stopped
    • p_pb_unblock (ocf:heartbeat:portblock): Stopped
  • Clone Set: ha-iscsi-clone [ha-iscsi] (promotable):
    • ha-iscsi (ocf:linbit:drbd): Unpromoted memverge
    • ha-iscsi (ocf:linbit:drbd): Stopped
  • Resource Group: g_iscsi:
    • p_iscsi_portblock_on_drbd3 (ocf:heartbeat:portblock): Stopped
    • p_iscsi_ip0 (ocf:heartbeat:IPaddr2): Stopped
    • p_iscsi_ip1 (ocf:heartbeat:IPaddr2): Stopped
    • p_iscsi_target_drbd3 (ocf:heartbeat:iSCSITarget): Stopped
    • p_iscsi_lun_drbd3 (ocf:heartbeat:iSCSILogicalUnit): Stopped
    • p_iscsi_portblock_off_drbd3 (ocf:heartbeat:portblock): Stopped

Any ideas why there is no switching back to the node memverge2 ?

Now only one record remains in cib,

and only if I remove above record from the cib, two services automatically start on the node memverge.

Anton

1 Like