Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-34276

Pacemaker remote resource migration failed

    • pacemaker-2.1.9-1.el9
    • None
    • Important
    • rhel-sst-high-availability
    • 13
    • 5
    • Dev ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Bug Fix
    • Hide
      .Successful recovery of an interrupted Pacemaker remote connection

      Before this update, when network communication was interrupted between a Pacemaker remote node and the cluster node hosting its connection during the TLS handshake portion of the initial connection, the connection in some cases blocked and could not be recovered on another cluster node. With this update, the TLS handshake is asynchronous and a remote connection is successfully recovered elsewhere.
      Show
      .Successful recovery of an interrupted Pacemaker remote connection Before this update, when network communication was interrupted between a Pacemaker remote node and the cluster node hosting its connection during the TLS handshake portion of the initial connection, the connection in some cases blocked and could not be recovered on another cluster node. With this update, the TLS handshake is asynchronous and a remote connection is successfully recovered elsewhere.
    • Done
    • x86_64
    • None

      What were you trying to do that didn't work?  

      The cluster consists of 2 quorum nodes and 2 Pacemaker remote nodes.  When a quorum node was fenced (this is part of the testing), the Pacemaker remote resource that was running on that node migrated to run on the other quorum node.  However, it failed to restart with this error as seen the pacemaker.log file:
      Apr 25 11:40:18.247 ps-4 pacemaker-schedulerd[3072816] (unpack_rsc_op) error: Preventing ps-1 from restarting on ps-4 because of hard failure (invalid parameter: Key was rejected by service) | ps-1_last_failure_0

      Please provide the package NVR for which bug is seen: 

      Pacemaker 2.1.6-4.db2pcmk.el9

      How reproducible: Frequent

      Steps to reproduce

      1. Set up a cluster with 2 quorum nodes and 2 Pacemaker remote node, with fencing agent define to perform the fencing.
      2. Run ifconfig <eth> down to take down the main interface on one quorum node
      3. The Pacemaker remote resource that was running on the fenced node, migrated to run on the other quorum node but failed to start.

      Expected results: Pacemaker remote resource migrated successfully

      Actual results: Pacemaker remote resource failed to start and stayed in stopped state.

      pcmk-Thu-25-Apr-2024.tar.bz2

              rhn-support-clumens Christopher Lumens
              lpham@ca.ibm.com Lan Pham
              IBM Confidential Group
              Kenneth Gaillot Kenneth Gaillot (Inactive)
              Jana Rehova Jana Rehova
              Steven Levine Steven Levine
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: