Skip to main content
Close

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Updating HCP for cloud scale

  1. Last updated
  2. Save as PDF

The following procedures describe how to update the HCP for cloud scale software.

Updates are managed by the System Management (Admin) application. Instances are shut down, updated, and restarted one at a time automatically, so you can update the HCP for cloud scale software to a newer version without interrupting availability or reingesting data. S3 API methods remain available, so that users can continue to read and write data and create and configure buckets.

During an update, management API methods that don't change the configuration remain available, so you can continue to create, monitor, and manage storage components. Tracing and the collection of metrics aren't affected.

When updating from a version of HCP for cloud scale prior to 2.3 to a version that implements consistent listing, event messages appear in the Object Storage Management app to inform you of the migration progress: when it has started, when it is in progress, when cleanup has started, and when it has completed. Once completed, the alerts clear.

Restrictions

You cannot downgrade HCP for cloud scale to a previous version.

You cannot upgrade to v1.3.0 from any previous version.

During an update, you cannot make changes to the configuration. After an update, you might need to reconfigure services.

Child Topics

Items and information you need

To update an HCP for cloud scale system, you need the appropriate update archive file hcpcs-version_number.update and, for verification purposes, its MD5 checksum file hcpcs-version_number.md5.

This document shows the path to the HCP for cloud scale folder as install_path. The best folder path is /opt.

This document shows the HCP for cloud scale folder as product. The best folder name is hcpcs.

Parent Topic

Verify and place the update archive
On the server or virtual machine from which you want to start the update:

Procedure

  1. Download the update archive and MD5 checksum file and store the files in a folder on the server or virtual machine.

  2. The best practice is to verify the integrity of the update archive. For example:

    md5sum -c hcpcs-version_number.update.md5If the archive integrity is verified, the command displays product-version_number.update: OK.

  3. In the largest disk partition on the server or virtual machine, create a product update folder. For example:

    mkdir /opt/hcpcs

  4. Move the update archive from the folder where you stored it to the product update folder. For example:

    mv hcpcs-version_number.update /opt/hcpcs/hcpcs-version_number.update

  5. Navigate to the update folder. For example:

    cd /opt/hcpcs
Parent Topic

Use the System Management application to update the system

The update process is controlled by the System Management application (the Admin App).

Procedure

  1. From the System Management application, select Configuration.

    The Configuration page opens.

  2. Click Update.

    The Update page opens.

  3. Select the Install tab.

    The Upload area opens.

  4. Click and drag the update file into the Upload area, or click Click to Upload, select the update archive, and click Open.

    The update archive is uploaded and verified. These processes will take several minutes. When the archive is verified, the page displays information about the update process. If the update contains a new service, you can optionally configure network, volume, or log file settings.

    Install tab after update archive is verified

  5. When you're ready to begin, click Apply Update.

    The System Management application displays the message Successfully started update package installation and then applies the update to the cluster (each server or virtual machine in the HCP for cloud scale system).
    Note The update process can trigger alarms on the Status tab, or emails if notification is enabled, that services have gone down, exited abnormally, or become underprotected. These notifications are expected during an update and you can safely ignore them. Update alarms should clear automatically when the update finishes.

Results

When the system is updated:
  • The Successfully started banner message is removed.
  • In the Status tab, the Update Status displays None and the event Update Completed appears.

    Event Details window showing an "Update Completed" message

  • Update-related alarms are cleared from the Status tab.
  • The update version appears in the lower right corner of the Login page.
NoteIf the update process encounters an unexpected error, update stops and the Install tab displays the message The update has failed! Click retry to attempt the update again. On the Status tab, click on the error message to get more details about the error. Click Retry, or click Cancel, correct the problem, and then restart the update. Some errors might not be resolvable by restarting the update. If a retry doesn't work, contact Support.
Parent Topic

Configure the system for your users
After your system is up and running, you can begin configuring it for your users.

For information about these procedures, see the Administration Guide or the online help that's available from the HCP for cloud scale application.

The overview of tasks is:

Procedure

  1. Configure the connection to an IdP and create user accounts.

  2. Define storage components.

  3. Assign a name for your HCP for cloud scale cluster.

    The host name is required for access to the System Management application and the S3 API.

  4. Configure DNS servers to resolve both the fully qualified domain name for your cluster and the wildcard *.hcpcs_cluster_name.

  5. Update Secure Socket Layer (SSL) certificates for the system, storage components, or synchronized buckets.

  6. If your system uses encryption, enable it.

  7. Obtain S3 authorization credentials.

Parent Topic

Troubleshooting

You might encounter these issues during an update.

Service doesn't start

Rarely, a system deployment, service management action, or system update fails because a service fails to start. When this happens, the System Management application is inaccessible from the instance where the failure occurred.

The logs in the watchdog-service log folder contain this error:

Error response from daemon: Conflict. The name "service-name" is already in use by container Docker-container-id. You have to remove (or rename) that container to be able to reuse that name.

To resolve this issue, restart the Docker service on the instance where the service failed to start. For example, if you are using systemd to run Docker, run:

systemctl restart docker

After restarting Docker, try the system deployment, service management action, or system update again.

PUT and GET calls on encrypted objects fail

After you turn on encryption, PUTS and GETS of objects require the key management server (KMS) to be up and unsealed. During an update the KMS can restart multiple times, including when the master nodes and services are upgraded and when the Vault service is updated. When the KMS service restarts, it is sealed, which can interrupt service.

If you are using encryption, monitor the Vault service closely during an update to prevent interruptions. Whenever the service restarts and gets sealed, unseal it.

If you have access to the Aspen administration app, you can monitor the health of the KMS by checking for the alert "Failed to connect to KMS server." When you see this alert, you know that the KMS is either down or sealed.

Another approach is to load the KMS page, which is at port 8200 of the system. The status of the KMS is displayed in the upper right corner. A red dot indicates that it is sealed.

Parent Topic