Skip to main content
FlashGrid.io

Updating FlashGrid software using FlashGrid Cluster Node Update package

  • Updated
  • Products: FlashGrid Cluster on Azure
  • Products: FlashGrid Cluster on GCP
  • Products: FlashGrid Cluster on AWS
 

FlashGrid Cluster Node Update package is a single self-extracting bash script file that allows updating the following components:

  • FlashGrid Storage Fabric RPM
  • FlashGrid Diagnostics RPM
  • FlashGrid Cloud Area Network RPM
  • FlashGrid Health Checker RPM

Using this package makes it easier to have the update performed to the latest validated set of software components and helps avoid accidental installation of incompatible software versions.

Prerequisites

Determine your current version of FlashGrid by running the following as root:

# rpm -qi flashgrid-skycluster

Follow the necessary steps based on the update scenario outlined in the table below:

Update Scenario OS Version Required Action
Major update (e.g., 22.03.x → 22.06.x, or 21.x → 23.x) All Review release notes and check with FlashGrid support before updating.
On OL8 OL8 Ensure that a known bad rpm package version is not installed: rpm-4.14.3-31.0.2.el8.x86_64. Check version: rpm -q rpm. If you have the bad version, update to a newer version, e.g. rpm-4.14.3-31.0.3.el8.x86_64.rpm.
From v24.05 or older All Install audispd-plugins package before updating. If missing, Node Update will attempt to install it via yum, but may fail without Internet access. If needed, install manually: yum install audispd-plugins and re-run the Node Update script.
From v24.05 or older RHEL8/OL8 Ensure bcc package version is at least 0.24.0. If below, Node Update will fail with: "ERROR! Installed version of bcc rpm is lower than the minimally required version". Check version: rpm -q bcc. Update using: yum update bcc, then re-run the Node Update script.
From v23.11 or older All Ensure mcelog package is installed. If missing, update will fail with: "error: Failed dependencies: mcelog". Install using: yum install mcelog.
From v21.06 or older RHEL7/OL7 Install openssl11-libs manually before updating. If missing, update may fail with: "Requires: libcrypto.so.1.1()(64bit)". Install from EPEL repository or manually download from: openssl11-libs RPM.
From v21.02 or older RHEL7 Manually install jq package (OL7 installs it automatically). Required dependencies: libjq1, oniguruma, jq.

Notes 

  • Simultaneously updating FlashGrid software and applying Grid Infrastructure patches in rolling fashion is not recommended. FlashGrid services should not be stopped while GI cluster is in rolling patching mode.
  • From v22.9, the "skip-kernel-update" option was removed from the node update script. OS updates are no longer applied as part of the FlashGrid update process.
  • Only if updating the OS simultaneously with the FlashGrid software, please also check Notes in the Updating OS article. 

Rolling update procedure, one node at a time (no database downtime required)

This procedure is recommended when database services must stay up during the update.

To update software using FlashGrid Cluster Node Update package on a running cluster, repeat the following steps on each node, one node at a time:

  1. Create backup snapshot of the OS disk

    a. Flush OS buffers:

    # sync; sync;

    b. Create snapshot of the OS disk using the cloud console or CLI.

  2. Make sure there are no other nodes that are in offline or resync state. All disk groups must have zero offline disks and Resync = No:

    # flashgrid-cluster

  3. If the node is a database node,

    a. Stop all local database instances running on the node.

    b. Stop Oracle CRS on the node:

    # crsctl stop crs

  4. Stop the FlashGrid Diagnostics monitoring service:

    # systemctl stop flashgrid-node-monitor

  5. Stop the FlashGrid Storage Fabric services on the node:

    # flashgrid-node stop

  6. Stop the FlashGrid Cloud Area Network service on the node:

    # systemctl stop flashgrid-clan

  7. Run the update script as root. Use the file name with a correct version number.

    # bash flashgrid_cluster_node_update-X.Y.Z.NNNNN.sh
    Note: When updating from version 20.06 or earlier, the following error may be reported: FlashGrid Cluster setup not found. In such case, double-check that you are running the update on a correct system and then re-run it with force-cluster the command parameter added.
  8. (Optional) Only if updating the OS simultaneously with the FlashGrid software, install the OS updates:
    # yum update

  9. Flush the OS buffers and reboot the node:

    # sync; sync; reboot

  10. Before updating the next node, wait until the node boots up, all disks are back online, and resync operations complete on all disk groups. All disk groups must have zero offline disks and Resync = No before it is safe to update the next node.

    # flashgrid-cluster

Note: After the update the flashgrid-cluster command may show the "Configuration check: FAILED" and "Cluster verification: FAILED" messages. This happens because configuration updates are applied locally. This message should disappear after the update is applied to all nodes in the cluster.

After the software update is complete on all nodes, upload diags to FlashGrid support. This will allow FlashGrid support to have up-to-date records of the software versions used on your systems.

 

Procedure for simultaneous update on all nodes (requires database downtime)

This procedure is recommended for faster deployment of a FlashGrid software update on non-production systems or during a maintenance window when database downtime is allowed.

  1. Create a backup snapshot of the OS disk from all database and quorum nodes

    a. Flush OS buffers:

    # sync; sync

    b. Create snapshot of the OS disk using the cloud console or CLI.

  2. Make sure there are no nodes that are in offline or resync state. All disk groups must have zero offline disks and Resync = No, by running the following on any node:

    # flashgrid-cluster

  3. Stop all databases

  4. Stop Oracle cluster services, by running the following command on any database node:

    # crsctl stop cluster -all

  5. Stop the FlashGrid Diagnostics monitoring service on all nodes (including storage/quorum):

    # systemctl stop flashgrid-node-monitor

  6. Stop the FlashGrid Storage Fabric services on all nodes (including storage/quorum):

    # flashgrid-node stop

  7. Stop the FlashGrid Cloud Area Network service on all nodes (including storage/quorum):

    # systemctl stop flashgrid-clan

  8. Run the update script as root on all nodes (including storage/quorum). Use the file name with a correct version number.

    # bash flashgrid_cluster_node_update-X.Y.Z.NNNNN.sh
    Note: When updating from version 20.06 or earlier, the following error may be reported: FlashGrid Cluster setup not found. In such case, double-check that you are running the update on the correct system and then re-run it with force-cluster command parameter added.
  9. (Optional) Only if updating the OS simultaneously with the FlashGrid software, install the OS updates:
    # yum update

  10. Reboot all nodes (including storage/quorum). The reboot can be done simultaneously or one by one. 

    # sync; sync; reboot

  11. Wait until all nodes boot up, all disks are back online, and resync operations complete on all disk groups. All disk groups must have zero offline disks and Resync = No 

    # flashgrid-cluster

After the software update is complete on all nodes, upload diags to FlashGrid support. This will allow FlashGrid support to have up-to-date records of the software versions used on your systems.