5.3 Updating Software Packages on Cluster Nodes

WARNING: Active Cluster Stack

Before starting an update for a node, either stop the cluster stack on that node or put the node into maintenance mode, depending on whether the cluster stack is affected or not. See Step 1 for details.

If the cluster resource manager on a node is active during the software update, this can lead to unpredictable results like fencing of active nodes.

  1. Before installing any package updates on a node, check the following:

    • Does the update affect any packages belonging to SUSE Linux Enterprise High Availability Extension or the Geo clustering extension? If yes: Stop the cluster stack on the node before starting the software update:

      root # systemctl stop pacemaker
    • Does the package update require a reboot? If yes: Stop the cluster stack on the node before starting the software update:

      root # systemctl stop pacemaker
    • If none of the situations above apply, you do not need to stop the cluster stack. In that case, put the node into maintenance mode before starting the software update:

      root # crm node maintenance NODE_NAME

      For more details on maintenance mode, see Section 16.2, Different Options for Maintenance Tasks.

  2. Install the package update using either YaST or Zypper.

  3. After the update has been successfully installed:

    • Either start the cluster stack on the respective node (if you stopped it in Step 1):

      root # systemctl start pacemaker
    • or remove the maintenance flag to bring the node back to normal mode:

      root # crm node ready NODE_NAME
  4. Check the cluster status with crm status or with Hawk2.