Hitachi Content Platform for Cloud Scale v2.0.1 Release Notes

Port 8000 for System Management App GUI

Port 9084 for MAPI and Object Storage Management App GUI

Note: Separate license required for Docker Enterprise Edition

Note: Technical support not available for Docker Community Edition

Note: Technical support not available for Docker Community Edition

A Metadata Gateway service instance becomes unavailable if the container or physical node hosting it fails. This can cause underprotection.

Resolution

This issue is resolved. If a Metadata Gateway instance becomes unavailable, the service automatically restores protection by rearranging its data to other available Metadata Gateway instances.

When a storage component is created using the HTTPS protocol, registration can fail with the error "Certificate for address doesn't match any of the subject alternative names."

Resolution

This issue is resolved:

• If the host name doesn't match one of the Subject Alternative Names (SANs) in the certificate of the storage component server, the Common Name is used.
• The host name suffix is no longer validated against the public suffix list.

The user name displayed in the S3 Console is actually the user group name.

Resolution

This issue is resolved. The user name is displayed.

After changing the cluster hostname, the change is not automatically made externally visible.

Workaround

Restart the S3 Gateway:

1. In the System Management application, select Services.
2. Select the S3-Gateway service.
3. Click REPAIR.

When manually deploying a four-node, multi-instance system, the Tracing Agent service returns an alert that the service is below the needed instance count even when the correct number of service instances are deployed.

Workaround

If you have deployed the correct number of instances you can safely ignore this alert.

A number of API methods refer to jobs. Jobs are not supported in this release.

Authentication and authorization use a system management authorization client service which has a different timeout interval. If a management API authorization or authentication request times out but the underlying client service doesn't, the thread is blocked.

Workaround

Stop and restart the MAPI Gateway service container.

The MAPI schema includes public API methods, which do not need OAuth tokens.

Workaround

None needed. The public API methods do not need OAuth tokens.

The storage component to which data is written is selected at random. If a filled storage component is selected, the write might fail.

Workaround

Use the Object Storage Management application or the MAPI method PATCH /storage_component/update to set the filled storage component's readOnly flag to true.

If two accounts try to set the encryption flag simultaneously, either using the GUI or the management API method /s3_encryption/set, existing storage components can become inaccessible.

Workaround

• If you intend to use encryption, set it before defining storage components.
• If you have already defined storage components and intend to use encryption, do not try to set encryption from multiple accounts, or by multiple calls to the API method /s3_encryption/set, simultaneously.

AWS calculates the size of a record returned in an S3 Select query as the total size of the record, including any delimiters. HCP for cloud scale calculates the size as the total data of each column returned. These calculations can sometimes differ slightly.

When configuring a storage component, the last segment of the host name can't begin with a number (for example, company.9com), but the field validation allows it, resulting in a invalid hostname error at the end of the process.

Workaround

Ensure that the last segment of the host name does not begin with a number before proceeding.

The characters null (NUL) and backslash (\) are not supported in object keys for S3 operations. The operations fail with the error 400 BadRequest.

Workaround

Do not use the null or backslash characters in object keys.

After encryption is enabled, the encryption status is immediately displayed as on. However, there can be a delay before all storage components begin encrypting ingested objects. Objects stored without encryption remain unencrypted.

Workaround

After enabling encryption, wait 15 minutes before putting new objects into storage.

The Refresh Token Timeout configuration value in the System Management application (Configuration > Security > Settings) has no effect.

Before v2.0 the Metrics service could be scaled up to more than one instance. In v2.0 the service is restricted to one instance. If you upgrade an HCP for cloud scale system running more than one Metrics service instance to v2.0, the service is not scaled down to one instance.

Workaround

Use the System Management application to scale the Metrics service down to one instance manually. Once scaled to one instance, you can't scale up to more instances.

Before starting an update, you are prompted to specify the network configuration for any new services included in the version that you're updating to. However, you can specify only the port numbers for the new service. You cannot specify the network type (that is, internal or external) for the service to use. Each new service gets the default network type, which is determined by the service itself.

If a system instance enters the Down state, when you try to upload an update package, the upload fails. However, after the system instance recovers, when you try again to upload an update package, the upload again fails, even though the system is in a healthy state.

Workaround

1. In the System Management application, go to the page Monitoring > Processes and for the task Upload Plugin Bundle click Retry Task.
2. Upload the update package again.

During installation, you can configure volumes for system services by specifying different values in the file volume.config on each system instance. Each volume is correctly configured with the settings you specify, but the page Monitoring > Services > Service Details in the System Management application incorrectly shows each volume as having identical configurations.

The Cassandra service can fail to deploy with the error Could not contact node over JMX. The log file on the node running the service instance includes the following entry: java.lang.RuntimeException: A node required to move the data consistently is down (/nnn.nnn.nnn.nnn). If you wish to move the data from a potentially inconsistent replica, restart the node with -Dcassandra.consistent.rangemovement=false

Workaround

1. Restart the Cassandra container running on that node.
2. Redeploy the service.

Validation of volume configuration values is not honored by the upgrade process. As a result, configuration values passed to Docker are not valid.

Workaround

Use caution when specifying volume values.

HCP for cloud scale uses a System Management function to validate tokens. The function does not time out. If the identity provider is unavailable, the requesting thread is blocked.

The copyright date on System Management application pages is 2019, not 2020.

Workaround

This product is copyrighted in 2020.