24 Upgrading Your Cluster and Updating Software Packages #

SUSE Linux Enterprise High Availability 12 cluster stack comes with major changes in various components (for example, /etc/corosync/corosync.conf, disk formats of OCFS2). Therefore, a cluster rolling upgrade from any SUSE Linux Enterprise High Availability 11 version is not supported. Instead, all cluster nodes must be offline and the cluster needs to be upgraded as a whole as described below.

1. Log in to each cluster node and stop the cluster stack with:

   # rcopenais stop

2. For each cluster node, perform an upgrade to the desired target version of SUSE Linux Enterprise Server and SUSE Linux Enterprise High Availability. If you have an existing Geo cluster setup and want to upgrade it, see the additional instructions in the Geo Clustering for SUSE Linux Enterprise High Availability Geo Clustering Quick Start. To find the details for the individual upgrade processes, see Section 24.2.1, “Supported Upgrade Paths for SLE HA and SLE HA Geo”.

3. After the upgrade process has finished, reboot each node with the upgraded version of SUSE Linux Enterprise Server and SUSE Linux Enterprise High Availability.

4. If you use OCFS2 in your cluster setup, update the on-device structure by executing the following command:

   # o2cluster --update PATH_TO_DEVICE

   It adds additional parameters to the disk which are needed for the updated OCFS2 version that is shipped with SUSE Linux Enterprise High Availability 12 and 12 SPx.

5. To update /etc/corosync/corosync.conf for Corosync version 2:

   1. Log in to one node and start the YaST cluster module.

   2. Switch to the Communication Channels category and enter values for the following new parameters: Cluster Name and Expected Votes. For details, see Procedure 4.1, “Defining the First Communication Channel (Multicast)” or Procedure 4.2, “Defining the First Communication Channel (Unicast)”, respectively.

      If YaST should detect any other options that are invalid or missing according to Corosync version 2, it will prompt you to change them.

   3. Confirm your changes in YaST. YaST will write them to /etc/corosync/corosync.conf.

   4. If Csync2 is configured for your cluster, use the following command to push the updated Corosync configuration to the other cluster nodes:

      # csync2 -xv

      For details on Csync2, see Section 4.7, “Transferring the Configuration to All Nodes”.

      Alternatively, synchronize the updated Corosync configuration by manually copying /etc/corosync/corosync.conf to all cluster nodes.

6. Log in to each node and start the cluster stack with:

   # systemctl start pacemaker

7. Check the cluster status with crm status or with Hawk2.

8. Configure the following services to start at boot time:

   # systemctl enable pacemaker
   # systemctl enable hawk
   # systemctl enable sbd

1. Log in as root on the node that you want to upgrade and stop the cluster stack:

   # systemctl stop pacemaker

2. Perform an upgrade to the desired target version of SUSE Linux Enterprise Server and SUSE Linux Enterprise High Availability. To find the details for the individual upgrade processes, see Section 24.2.1, “Supported Upgrade Paths for SLE HA and SLE HA Geo”.

3. Restart the cluster stack on the upgraded node to make the node rejoin the cluster:

   # systemctl start pacemaker

4. Take the next node offline and repeat the procedure for that node.

5. Check the cluster status with crm status or with Hawk2.

1. Make a backup of your cluster configuration. A minimum set of files are shown in the following list:

   /etc/corosync/corosync.conf
   /etc/corosync/authkey
   /etc/sysconfig/sbd
   /etc/modules-load.d/watchdog.conf
   /etc/hosts
   /etc/ntp.conf

   Depending on your resources, you may also need the following files:

   /etc/services
   /etc/passwd
   /etc/shadow
   /etc/groups
   /etc/drbd/*
   /etc/lvm/lvm.conf
   /etc/mdadm.conf
   /etc/mdadm.SID.conf

2. Start with node alice.

   1. Put the node into standby node. That way, resources can move off the node:

      # crm --wait node standby alice reboot

      With the option --wait, the command returns only when the cluster finishes the transition and becomes idle. The reboot option has the effect that the node will be already out of standby mode when it is online again. Despite its name, the reboot option works as long as the node goes offline and online.

   2. Stop the cluster services on node alice:

      # crm cluster stop

   3. At this point, alice does not have running resources anymore. Upgrade the node alice and reboot it afterward. Cluster services are assumed not to start on boot.

   4. Copy your backup files from Step 1 to the original places.

   5. Bring back node alice into cluster:

      # crm cluster start

   6. Check that resources are fine.

3. Repeat Step 2 for node bob.