Print Email PDF

Qumulo in GCP: Upgrade an Unconfigured Node

IN THIS ARTICLE 

This article explains how you can upgrade an unconfigured Qumulo node on GCP to a more recent version of Qumulo Core.

REQUIREMENTS

  • An unconfigured Qumulo node on GCP with Qumulo Core 4.1.5 (or higher) 
  • A .qimg file for your node. For more information, see Product Releases.
  • GCP Console Access
  • Command line (qq CLI) tools installed using the API Tools in the Web UI

DETAILS

One of the benefits of cloud-hosted storage is the ability to add storage dynamically. If the Qumulo Core version of your new node is older than that of your cluster, you must upgrade the node before adding it to your cluster. To upgrade your note, you must start it and then use the qq CLI.

For more information about creating a new node, see Qumulo in GCP: Launch a New Node for an Existing Cloud Cluster.

To Upgrade an Unconfigured Node

To upgrade a  node, you must upload the upgrade .qimg to a node-accessible location. For Google Cloud, we recommend uploading the .qimg file to Google Cloud Object Storage and then generating a pre-signed object URL.

  1. Download a .qimg file from Product Releases.
  2. Upload the file by running the following command (with the gsutil cli utility configured and authenticated):
    gsutil cp <local qimg file path> <object path>
  3. To grant the new node permission to read the upgrade file, generate a pre-signed URL.
    NOTE: You use this pre-signed URL in the following steps. If your node has permission to access the object directly (for exactly permissions inherited through the VPC), you can skip this step.

    gsutil signurl <service account key file path> <object path>
  4. Connect to the new node using SSH and the node's IP address.
    ssh admin@node_IP_address
  5. Prepare the upgrade using the following command and the path to the pre-signed URL generated for the upgrade image that you uploaded to Google Cloud Object Storage.
    NOTE: For clusters running Qumulo Core 4.1.0 or lower, the commands in the following examples differ. In this case, remove the "unconfigured_" portion from each command.
    qq unconfigured_upgrade_config_set --path <pre-signed URL to qimg> --target "prepare"
  6. Use the following command to monitor the prepare status and wait for it to finish.
    qq unconfigured_upgrade_status --monitor
  7. When the UPGRADE_PREPARED message appears, run the following command to begin the upgrade.
    qq unconfigured_upgrade_config_set --path <pre-signed URL to qimg> --target "arm"
    After a few minutes, the node restarts.
  8. To check that the upgrade was successful, running the following command and verify the new version number:
    qq version
    Your node is upgraded. When the node and cluster software versions match, you can add the node to your cluster. For more information, see Qumulo in GCP: Add a Node to an Existing Cloud Cluster.
    NOTE: If your node still runs an older version, repeat this process with all subsequent upgrades until the versions match.

Troubleshooting

If you can't upgrade your unconfigured node successfully, test that the node can access the .qimg file.

  1. Connect to the new node using SSH and the node's IP address.
    ssh admin@node_IP_address
  2. To verify access, run the following command.
    curl "<object url>" --range 0-10

If the curl command doesn't work and you receive an error, try the following:

  • Use a pre-signed URL
  • Check that the object is accessible from another computer in the same VPC using the same URL

Once you no longer receive an error using the curl command, try upgrading the node again. If the upgrade continues to be unsuccessful, contact Qumulo Care.

RESOLUTION 

You now know how to upgrade an unconfigured Qumulo node on GCP.

ADDITIONAL RESOURCES

Qumulo in GCP: Launch a New Node for an Existing Cloud Cluster

Qumulo in GCP: Add a Node to an Existing Cloud Cluster

Qumulo in GCP: Deploy a Cloud Cluster

 

Like what you see? Share this article with your network!

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Have more questions?
Open a Case
Share it, if you like it.