8.3. In-service Software Update to Red Hat Gluster Storage 3.1.x from 3.y.z

Important

In-service software update includes minor bug fixes and enhancements. You can update your system from Red Hat Gluster Storage 3.0.x to 3.1.y or from 3.1.x to 3.1.y.
To update your system to Red Hat Gluster Storage 3.1.x, follow these steps. The following steps must be performed on each node of the replica pair:

Note

Warning

  • While Red Hat Gluster Storage supports in-service upgrades, the SMB and CTDB services do not. The procedure outlined in this section does involve service interruptions to the SMB and CTDB services.
  • Samba version 3 is being deprecated from Red Hat Gluster Storage 3.0 Update 4. Further updates will not be provided for samba-3.x. It is recommended that you upgrade to Samba-4.x, which is provided in a separate channel or repository, for all updates including the security updates.
  • Downgrading Samba from Samba 4.x to Samba 3.x is not supported.
  • Ensure that Samba is upgraded on all the nodes simultaneously, as running different versions of Samba in the same cluster will lead to data corruption.
  1. Stop the gluster services on the storage server using the following commands:
    # service glusterd stop 
    # pkill glusterfs 
    # pkill glusterfsd
    1. For Red Hat Gluster Storage 3.0.4 or later on Red Hat Enterprise Linux 6.7, if you require Samba, then enable the following repository:
      # subscription-manager repos --enable=rh-gluster-3-samba-for-rhel-6-server-rpms
    2. Stop the CTDB and SMB services across all nodes in the Samba cluster using the following command. This is because different versions of Samba cannot run in the same Samba cluster.
      # service ctdb stop
      Stopping the CTDB service also stops the SMB service.
    3. To verify if the CTDB and SMB services are stopped, execute the following command:
      ps axf | grep -E '(ctdb|smb|winbind|nmb)[d]'
  2. Update the server using the following command:
    # yum update
  3. Reboot the server if a kernel update was included as part of the update process in the previous step.

    Note

    If a reboot of the server was not required, then start the gluster services on the storage server using the following command:
    # service glusterd start
    1. If the CTDB and SMB services were stopped earlier, then start the services by executing the following command.
      # service ctdb start
    2. To verify if the CTDB and SMB services have started, execute the following command:
      ps axf | grep -E '(ctdb|smb|winbind|nmb)[d]'
  4. Start self-heal on the volume.
    # gluster volume heal volname
  5. To verify if you have upgraded to the latest version of the Red Hat Gluster Storage server execute the following command:
    # gluster --version
  6. Ensure that all the bricks are online. To check the status, execute the following command:
    # gluster volume status
  7. Ensure self-heal is complete on the replica using the following command:
    # gluster volume heal volname info
  8. Repeat the above steps on the other node of the replica pair.

    Note

    In the case of a distributed-replicated setup, repeat the above steps on all replica pairs.
  9. When all nodes have been upgraded, run the following command to update the op-version of the cluster. This helps to prevent any compatibility issues within the cluster.
    # gluster volume set all cluster.op-version 30707