Content Platform v9.0.0 Release Notes - Customer

00541835

01130910

00541835

00746713

00776503

00800531

01545968

HCP-34159

HCP-35429

The time zone data package for Fedora is updated to tzdata-2019c

Note: Online upgrades can sometimes fail in regions where time zone rules have changed. As a workaround in such instances, either change the HCP system time to UTC, or perform an offline upgrade.

Updated the HCP G10 Hardware Setup tool

BMC and LSI firmware are updated.

HDS02362606

HDS04005699

01638405

Resolved an issue that prevented a replication link from resuming after it automatically paused due to duplicate namespaces on each side of the link

Note: You might need to click the Resume Link button twice to fully repair the replication link.

HCP-35966

HCP-36067

01560538

01579992

01643497

Resolved an issue where retention hold changes made by means of the HCP S3 extension were not being replicated

In an active/active replication configuration, this could result in deletion of a held object.

01671178

01755325

HCP-33074

HCP-35329

• HCP no longer supports SSL v1, v2, and v3 protocols.
• HCP conforms more closely to RFC 7230, and no longer allows header folding.

HCP Data Migrator can set the value of the hold parameter to true, but not to false

HCP Data Migrator can be used to place an object on hold by updating the system metadata for the object to set the hold parameter to true. However, you cannot use the HCP Data Migrator to remove a hold from an object because the HCP Data Migrator cannot set the value of the hold parameter to false.

Browser caching

When an object is added to a namespace, deleted, and then added again with the same name, it may appear to have the old content when viewed through a web browser.

Workaround: To see the new content, clear the browser cache. Be sure to use the applicable browser option to do this rather than restarting the computer.

Displaying UTF-16-encoded objects

Objects with content that uses UTF-16 character encoding may not be displayed as expected due to the limitations of some browser and operating system combinations. Regardless of the appearance on the screen, the object content HCP returns is guaranteed to be identical to the data before it was stored.

Node restart with cross-mapped storage

In SAIN systems, if a cross-mapped node restarts while one of its physical paths to the storage array is broken, the node remains unavailable.

Workaround: Fix the broken path and restart the node from the System Management Console.

Exposed internal mechanism for dead properties for collections HCP uses an internal mechanism for storing WebDAV dead properties for a collection. This mechanism entails the creation of a dummy object named .webdav_properties. This object is inappropriately:

• Included in the count of objects in the namespace
• Exposed through the HTTP, CIFS, and NFS protocols
• Returned by searches for which it meets the search criteria

If you are storing dead properties for collections, do not delete any .webdav_properties objects.

Missed log messages when no leader node

Normally, one node in an HCP system is responsible for writing messages to the system log. This node is called the leader node. Rarely, brief periods occur during which no leader node exists (for example, because the leader node has failed and a new leader node has not yet been established). During such periods, messages for which the leader node is responsible are not written to the log.

Shredding in SAIN systems

In SAIN systems, HCP may not effectively execute all three passes of the shredding algorithm when shredding objects. This is due to the fact that some storage arrays make extensive use of disk caching. Depending on the particular hardware configuration and the current load on the system, some of the writes from the shredding algorithm may not make it from the cache to disk.

Log display skips messages

When you page through a display of log messages in the System Management Console or Tenant Management Console, some messages may be skipped. This happens because the Console retrieves the next or previous group of messages based on the message timestamps.

Each time you request a next page of messages, the Console starts the new page with the message with the next later timestamp from the last message on the current page. If a page boundary falls between multiple messages with the same timestamp, retrieving messages starting with the next timestamp skips the messages that come after the page break. The equivalent process happens when you request a previous page of message.

As additional messages are added to the log, the page boundaries change, with the result that previously skipped messages reappear.

Browser pages for large directories

You can view the contents of a namespace in a web browser through HTTP (default namespace only) or WebDAV. Some browsers, however, may not be able to successfully render pages for directories that contain a very large number of objects.

Using NFS to delete objects open for read

Using NFS, if you try to delete an object that is currently open for read on the same client, HCP returns this error: Read-only file system.

Appending to objects on unavailable nodes

If an object is open for append on a node that becomes unavailable, attempts to append to the object fail.

Cannot ingest very large email attachments

HCP fails to ingest email attachments substantially greater than 400 MB. In such cases, the client receives a 221 return code.

SNMP version 2c traps sent for version 3 traps

HCP can be configured to use SNMP version 3. However, when configured this way, HCP sends version 2c traps instead of the expected version 3 traps.

Workaround: To receive traps from HCP, have your SNMP application accept SNMP version 2c traps.

WebDAV does not correctly list objects with custom metadata

Namespaces can be configured to store WebDAV dead properties in custom-metadata.xml files. If regular custom metadata is stored for one or more objects in a directory before this configuration is set, subsequent WebDAV requests for listings of that directory fail with an XML parsing error.

Workaround: Do not use custom-metadata.xml files to store WebDAV properties for an object if any objects in the same directory already have custom metadata.

Using Internet Explorer, cannot log in to HCP as a local user

With Internet Explorer, if the Active Directory user account with which you’re currently logged into Windows is not an account that’s recognized by HCP and any of these applies, Internet Explorer displays a Connect window instead of the page with the link to the login page for the target interface:

• You are trying to access the System Management Console, and support for Active Directory is enabled at the system level.
• You are trying to access the Tenant Management Console for an HCP tenant, and Active Directory is enabled as an authentication type for the tenant.
• You are trying to access the Namespace Browser for an HCP namespace, and Active Directory single sign-on is enabled for the namespace.

If you enter credentials for an HCP user account in the Connect window, Internet Explorer returns an error message.

Workaround: To access the target interface using an HCP user account, click on the Cancel button in the Connect window to display the page with the link to the login page for the target interface.

Changed computer account not added to all applicable groups in Active Directory

When you enable HCP support for Active Directory, the HCP computer account you specify is automatically added to the groups in Active Directory that include the user account you specify. If you then remove the computer account from one or more of those groups and reconfigure Active Directory support with a new computer account, the new computer account is not automatically added to the groups from which the previous computer account was removed.

Workaround: Do not remove the old computer account from the groups in Active Directory until after you have changed the computer account in HCP. If you have already removed the old computer account from one or more groups, resubmit the Active Directory configuration in HCP without changing the computer account. This puts that computer account back in the groups from which it was removed. When you subsequently change the computer account in HCP, the new computer account will be added to all the groups that include the user account.

HCP unresponsive after Active Directory cache cleared while Active Directory is unavailable

If you clear the Active Directory cache while HCP cannot communicate with Active Directory, the HCP system becomes unresponsive for up to ten minutes.

No success or error message in response to action taken in Console

Occasionally, the System Management Console and Tenant Management Console do not display any success or error messages in response to an action that results in a fresh display of the page on which the action was taken.

Objects incorrectly reported as irreparable or unavailable after data migration

During a data migration, the migration service may incorrectly report one or more objects as irreparable or unavailable. After the data migration is complete, you can run the Content Verification service to clear these errors.

Downloads with HTTPS fail in Internet Explorer 9

With Internet Explorer 9, attempts to download files (such as chargeback reports and SSL certificates) from URLs that use SSL security (that is, URLs that start with HTTPS) fail.

Workaround: In Internet Explorer 9:

1. On the Tools menu, select Internet Options.
2. In the Internet Options window, click on the Advanced tab.
3. On the Advanced page, under Security, deselect the Do not save encrypted pages to disk option.
4. Click on OK.

Node restart due to large element content in annotation

While XML checking of custom metadata is enabled, if an annotation is added to an object where the content of an element in the annotation is very large, a node may restart itself.

Workaround: Disable XML checking for the namespace that contains the object.

DPL 2 object object copies stored on same node

If a DPL 2 namespace service plan is configured so that the namespace stores one object copy on primary running storage and the other copy on an external storage volume, both copies can be stored on the same node, which can cause the object unavailablility if the node fails.

Delayed read from replica when external storage unavailable

In a replicated namespace, if the only copy of the data for an object is in external storage and that storage is unavailable, NFS and WebDAV requests for the object may time out for several tries before HCP retrieves the object from the replica.

Workaround: Either bring the external storage back online, or retry the request in five minutes.

Alert about Active Directory connection with online HCP upgrade

In an HCP system that’s configured to support Active Directory, during an online upgrade and for a short time after the upgrade is complete, the System Management Console may show an alert indicating a problem with support for Active Directory. This alert is most likely false and will go away on its own. If Active Directory authentication is working, the alert can be safely ignored.

Network interface event upon MTU change

When you change the MTU for a network, the network interface may go down and then come back up on nodes that are Dell 1950 servers.

Username mappings are applied to Active Directory users of HCP namespaces

For the default namespace, Active Directory user authentication is implemented through the use of a username mapping file that associates AD usernames with UIDs and GIDs. If an AD user included in the username mapping file also has access to an HCP namespace, the objects that the user stores in the HCP namespace have the UID and GID specified in the username mapping file.

As a result, a user using CIFS for authenticated access who is included in the username mapping file or a user using NFS has access to such an object only if one of these is true:

• With CIFS, the UID for the user in the username mapping file matches the object UID.
• With NFS, the user’s UID matches the object UID.
• With CIFS, the user is included in the AD group identified by the object GID.
• With NFS, the user is included in the group identified by the object GID.
• WIth CIFS, the user has been granted access to the object by the object ACL.
• The object ACL grants all users access to the object.
• The minimum data access permissions for the namespace grant all users access to all objects in the namespace.

Users using HTTP, HS3, WebDAV, CIFS for authenticated access who are not included in the username mapping file, or CIFS for anonymous access have access to such an object regardless of the object UID and GID.

Cannot use ssh -6 to connect to a node using a link local IPv6 address

HCP does not support using SSH to connect to a node using its link local IPv6 address.

This issue is caused by Red Hat bug 719178: Applications can't connect to IPv6 link-local addresses learned through nss-mdns and Avahi.

False alerts for network with same name as deleted network

If you create a network with at least one node IP address, then delete the network, and then create a new network with the same name as the deleted network and no node IP addresses, the Overview, Hardware, Storage Node, and Networks pages in the System Management Console display alerts indicating that a network error exists. Additionally, HCP writes this message to the system log:

Network interface bond0.xxxx for network network-name is not functioning properly.

When you subsequently assign IP addresses for the network to one or more nodes, the alerts disappear.

Nodes may fail with the error message “Max Connections hit: Could not get a connection, pool is exhausted”

Even if the supported limit of 200 connections is not reached, if too many clients attempt to connect to the same namespace at the same time, one or more nodes in the HCP system may fail with the error message, “Max Connections hit: Could not get a connection, pool is exhausted”.

Workaround: Upgrade to release 7.1 or later of HCP and increase your system RAM on all nodes. At least 32GB of RAM needs to be added.

When performing an add-drives procedure on an HCP node, an existing node sometimes issues a “barrierWait” message and then hangs

When performing an add-drives procedure on an HCP node, if one node fails, its partner node may issue a "Waiting for others at barrierWait" message and then hang.

Workaround: To get the existing node back into a working state, press CtrlC to cancel the drive addition procedure. You can then restart the procedure.

Cannot use a domain name to connect to a namespace on an IPv6 or dual-mode HCP network

HCP-DM does not support the use of IPv6 addresses to connect to a namespace on an HCP system.

HCP-DM can use IPv4 addresses to connect to a namespace on a dualmode HCP network. However, if HCP-DM tries to use a domain name to connect to a namespace on a dual-mode network, when the DNS resolves the domain name, it will return both IPv6 and IPv4 addresses for the network. If HCP-DM then tries to use the IPv6 addresses to connect to the namespace, the connection will fail.

Workaround: To ensure that HCP-DM can successfully connect to a namespace on a dual-mode HCP network, you need to configure HCP-DM to connect to that namespace using the IPv4 addresses for the network.

Clearing the AD cache causes inconsistent directory permissions

Following a clearing of the AD cache on an HCP system that’s accessing AD over CIFS, when users access a given CIFS share, they will find that their file permissions have changed to root/root, with the exception of the first user to access the share following the clearing of the AD cache. That user will see the original permissions on his/her file/folders, but all others will be root/root. All other users that connect to the CIFS share will only see root/root for existing files/folders.

When using AD for HCP authentication, if a user has an AD username that includes a % character, that user cannot access the HCP system

If you attempt to log into the HCP System Management Console or Tenant Management Console using an Active Directory username that includes a % (percent) character, the HCP user authentication fails.

When attempting to update annotations for objects that have been tiered to one or more types of cloud storage, HCP sometimes returns a 503 error

When a HCP attempts to update annotations on objects that have been tiered to cloud storage, the updates will fail with a 503 error if HCP is unable to connect to the applicable cloud storage service endpoints or if HCP is unable to access the applicable cloud storage buckets, containers, or namespaces.

Workaround: Restore the connections between HCP and each applicable cloud storage service endpoint and make sure HCP can successfully access each applicable cloud storage bucket, container, and namespace. You should then be able to successfully update the annotations for any objects stored in each bucket, container, and namespace.

Hitachi Device Manager cannot send updates to an HCP system with IPv6 only mode enabled

An HCP system with IPv6 only mode enabled can successfully connect to the Hitachi Device Manager server, but cannot receive Hitachi Device Manager updates.

When performing the TrueCopy storage array replication procedure, the san_update command may fail

When using the TrueCopy procedure to replicate the HCP system OS and data LUNs to a different storage array, the san_update command may fail with an error that the file system on the source system differs from the file system on the second.

While HTTPS is enabled, HCP S Series Nodes fail to create storage components when added to the HCP system by virtual IP

An S Series Node cannot use HTTPS when being added by virtual IP to HCP. While HTTP is enabled, HCP does not create storage components for S Series Nodes added by virtual IP address.

Workaround: On the System Management Console, when adding an S Series Node through virtual IP, go to the Connection tab of the Add Node wizard, deselect the Use HTTP for management option and, under the Advanced panel, deselect the Use HTTPS for data access option before completing the add node procedure.

Pausing or failing an NFS write operation may cause HCP system processes to hang

Pausing or failing an NFS write operation increases the chances of HCP system processes hanging.

While the Migration service is running, the migration status occasionally shows incorrect values

Occasionally while the Migration service is running, the migration status values for the total number of bytes being migrated and the total number of objects being migrated are incorrect. This occurs regardless of how many bytes or objects are actually migrated. Once the migration completes, the migration status values become accurate.

AD 100 Winbind error occasionally causes HCP nodes to restart

HCP system communication errors with AD may cause winbind to restart. If this happens more than 100 times, the HCP system restarts.

Upgrade NTP to fix vulnerabilities

The NTP that HCP currently uses was discovered to have some vulnerabilities. For information about these vulnerabilities, refer to the NTP security advisory document found here.

lf your HCP system has data tiered to public cloud, the upgrade process to version 7.1 of HCP is extended

If your HCP system has data tiered to public cloud, metrics need to recompute when upgrading to version 7.1 of HCP. This extends the upgrade time.

Node recovery does not work for the HCP 500XL with new disks

Node recovery procedures fail with unformatted database drives.

The Adding Logical Volumes service might fail if adding previously used, formatted LUNs

Occasionally during the add LUN service procedure, previously used, formatted LUNs might not be added to all nodes. If this occurs, the error message, "Failed to execute Partx" appears.

Workaround: Restart the service procedure.

Incorrectly shutting down and restarting a replication link when updating the signed certificate causes the replication link to fail

If you incorrectly shut down and restart a replication link while uploading an SSL certificate, the replication link refutes the certificate and fails.

Workaround: Follow this certificate upload procedure:

1. Upload a new certificate on the primary and replica systems.
2. Remove the expired certificate from the primary and replica systems.
3. Select the Shut down all links option from the Replication settings menu on the primary and replica systems.
4. Select Start up all links on the primary and replica systems.

Upgrading to HCP 7.2 or later prevents HCP from connecting to HCP Data Migrator

Release 7.2 and later of HCP use a different SSL cipher than previous releases. HCP Data Migrator does not support these ciphers if HCP Data Migrator is run with an outdated Java runtime.

Log download fails under certain conditions

Log download initiated through the System Management Console could fail due to external issues such as networking.

Workaround: Restart the log download.

HCP-26127

and

HCP-26128

HTTPS certificate errors appear during failover

Sending HTTPS requests to system A in a replication link that has failed over causes report certificate errors because the Subject Common Name in the certificate does not match the domain name in the request.

Workaround: Add Subject Alternative Name entries to the certificates used by HCP for HTTPS.

Under specific conditions, creating an active/active replication link between two systems causes nodes to reboot

Under specific conditions, creating a replication link between two systems running version 7.1.1 of HCP that have ingested objects and have multiple namespaces causes nodes to reboot.

Cannot download certificates from HCP through Internet Explorer 8

When you try to download a certificate from HCP using Internet Explorer (IE) 8, you may receive the "Unable to download." error message. This is caused by a known I.E 8 issue.

Workaround: For more information on this issue, see the Microsoft Knowledge Base article, https://support.microsoft.com/enus/kb/323308.

Cannot download HCP system logs during an online upgrade to release 7.2 of HCP

During an online upgrade to release 7.2 of HCP, the HCP system logs cannot be downloaded from the System Management Console.

Workaround: During the online upgrade, access the System Management Console by entering the IP address of a node that has already upgraded into your web browser. Perform the log download procedure through the targeted node.

The Network page Advanced Settings tab appears blank when the HCP system is read only

When an HCP system is in a read only state, the Advanced Settings tab on the System Management Console Configuration Networks page appears blank.

HCP system raises full capacity alarm if a single volume is over 95% full

If a single volume in an HCP system becomes 95% full, the full file system warning is triggered for the system.

Active Directory node account not removed when node retired

Running the retire node procedure on a node with Active Directory enabled does not remove the node computer account from the domain controllers.

Workaround: Remove the node computer account from the domain controllers.

When switching tabs during a replication schedule update, an incorrect error message is occasionally displayed

After creating an active/active replication link, clicking on the Update Schedule button on the System Management Console Services Replication Schedule page, and switching between the local and remote schedule tabs, an error may appear even though the replication link is working properly.

After upgrade to 7.2, some third party applications receive HTTP 401 error to PUT requests

With release 7.2 of HCP, SPNEGO changes make certain third party applications incompatible with HCP.

Workaround: Contact Hitachi Vantara Support to enable third-party compatibility.

Changing HCP-VM network adapter from e1000 to VMXnet3 causes VLAN performance issues

On an HCP-VM with VLANs enabled, converting from an e1000 to VMXnet3 network adapter causes VLAN performance issues.

HCP-29612

HCP-29301

Database connections exhausted

On high-load HCP systems that are balancing metadata, nodes can restart due to exceeding the database connection limit.

AD falsely report missing SPNs due to replication topology with tenant or namespaces on custom network

In a replication topology where systems have full SSO support, HCP may incorrectly report missing SPN errors for replicating tenants and namespaces that are using a custom network with a non-default domain name.

Namespace browser cannot load directory due to ASCII characters in object name

The namespace browser cannot display the contents of a directory that contains an object with any of the following ASCII characters in its name: %00-%0F, %10-%1F, or %20.

HS3 500 Internal Server Error due to double slash (//) in object name

If an object has a double slash (//) in its object name and the object is ingested using HS3, HCP returns a HTTP 500 internal server error.

Irreparable objects appearing due to migrating objects ingest in HCP release 5.0 to new nodes in HCP release 7.0 or later

If objects with custom metadata are ingested in a system on HCP release version 5.X or earlier and the system is chain upgraded to release 7.0 or later and the objects are migrated to new nodes, the objects become irreparable.

Workaround: Run the Content Verification service between each upgrade in the upgrade chain.

CR220S system installation or upgrade fails in HCP release version 8.0 due to active processor set to one core in BIOS

If an HCP system uses CR220S servers and has the active processor setting set to one core in the BIOS, the installation or upgrade procedure fails for HCP release version 8.0.

Workaround: Before installing or upgrading an HCP system, set the active processor setting in the BIOS to max cores.

Replication link shutdown error remains after replication resumes

If all replication links shut down, HCP shows a "Replication Links Shut Down - All activity on all links to and from this system has been stopped" error message on the System Management Console Services

Links page. When the replication links resume, the error message does not go away.

Workaround: Once all replication links resume, create a new replication link to make the error message go away.

DNS failover fails due to domain name change in active/passive replication link

If a system is in a active/passive replication link and has its domain name changed, the replica system does not receive the updated domain name which causes DNS failover to fail.

Workaround: After you change the domain name for the primary system, update any setting on the tenant overview page to replicate the new domain name.

HCP vulnerable to brute-force password detection attacks

With an HTTP-based interface (that is, the HTTP REST, HS3, HSwift, and management APIs), if you authenticate using an HCP user account, HCP does not lock out the user account after multiple failed attempts to access the system. Similarly, HCP does not lock out HCP user accounts after multiple failed attempts to change the account password.

Because accounts are not locked out under these circumstances, HCP is vulnerable to brute-force password detection attacks.

Note: With Active Directory authentication, AD lockout policies enforce account lockouts.

Node restarts slowed due to configuring 32 or more LUNs on CR220 nodes with AMS 2500 arrays

For an HCP system with CR220 nodes and AMS2500 arrays, configuring 32 or more LUNs causes simultaneous node restarts to take longer than normal. The restarts take longer for every extra LUN after LUN 31.

DNS failover not working for replication link converted from active/passive to active/active

After a replication link is converted from active/passive to active/active, DNS failover no longer works for that link.

Workaround: Delete the active/passive replication link and then recreate it as an active/active link.

Tar gzip compressed objects fail MD5 check due to Firefox browser issue

Tar gzip compressed objects downloaded from HCP through the Firefox browser fail the MD5 check.

Links in a geo-protection replication topology can be added to replication chain

Geo-protection replication chains are not supported. If a system in the geo-replication topology becomes unavailable, the geo-protected systems outside of the topology could experience data unavailability

System restart due to to unavailable node not receiving management network IP address

If a node is unavailable when the management network is enabled, the node does not receive the management network IP address. If any other change is made to the management network, the HCP system shuts down so the node can receive the management network IP address.

Workaround: Only enable the management network when all nodes are available.

Inconsistent case sensitivity for Hitachi API for Amazon S3 multipart upload query parameters

Case sensitivity is inconsistent among the query parameters used with S3 compatible API requests related to multipart uploads. For example, the uploadId query parameter used in requests to upload a part is not case sensitive, while the uploadId query parameter used in requests to list the parts of a multipart upload or complete or abort a multipart upload is case sensitive.

System restart fails after changing management network configuration

The HCP system should restart each time a chang is made to the management network configuration, but after enabling the management network for the first time the HCP system does not restart again from changes made to management network configuration.

HCP-31721

and

HCP-29790

Duplicate elimination service cannot deduplicate compressed objects in S Series storage pools

When duplicate objects are compressed in an S Series pool, the compression process creates unique files that the duplicate elimination service cannot deduplicate.

IPMI v2.0 password hash disclosure

A vulnerability regarding IPMI v2.0 puts password protection at risk. For more information on this, see https://nvd.nist.gov/vuln/detail/CVE-2013-4786.

Only newly-added disks should be verified in HCP system prechecks

During the HCP system prechecks in the add drive procedure, the disk size of only the newly-added LUN should be verified by the HCP system.

Complete multipart upload operation failure due to generated ETAG

The ETAG generated by HCP on a complete multipart upload operation is based on the default namespace hash scheme. This causes complete multipart upload operations to fail with TSM.

Workaround: Use MD5 as the hash scheme for writing to a namespace with TSM.

AWS SDK failure due to invalid Content-Type

When an invalid Content-Type request header is specified, this causes the AWS SDK to fail.

Incorrect information included in object configuration files

In certain object configuration files, incorrect information is included.

Delete old database procedure hangs.

When administering namespaces with 100,000 objects or more, the Delete Old Database procedure is known to run indefinitely and display #, even though the deletion has completed.

Search Security Deny List not working correctly

In the HCP System Management Console, the Deny List on the Search Security page does not deny access to the clients listed.

In the HCP System Management Console, the Hardware page does not report the status of the management NIC when the NIC has been enabled and subsequently removed on the VM node

If the link status of the management port network connection fails on a VMware ESXi server or KVM host, HCP cannot detect the link failure and does not raise any corresponding alarms. There should not be complete isolation from HCP management access since there are at least three other nodes providing management port network connectivity.

After upgrading to HCP 8.2, some third-party applications receive an HTTP 401 error to PUT requests

With release 7.2 of HCP, SPNEGO changes make certain third-party applications incompatible with HCP.

Workaround: Contact Hitachi Vantara Support to enable third-party compatibility.

01247729

01247736

When a zero-copy-failover partner node reboots after a failover, the metadata query engine does not recover

Workaround: Edit the following files:

• In the /opt/arc/solr/solr/solr.xml file, add the shards that are on the standby volumes.
• In the /opt/arc/solr/solr/cores file, create symlinks that point to the shards on the standby volumes.

01312806

01310161

Overflowed, thin-provisioned block storage might cause data loss

Workaround: Do not over provision dynamic pools.

In the HCP Search Console UI, the login ID changes to null and a subsequent search returns "500 Error: Internal server error"

When you open the Tenant Management Console from the System Management Console, initiate a search by logging in to the Search Console with your system-level credentials, and either refresh the page or click the search button, the following events occur:

• You are returned to the login page.
• The login ID changes to null.

If you log in to the Search Console again with your tenant-level credentials and initiate a search, the query returns the following error message:

500 Error: Internal server error

Workaround: Depending on the circumstances that led to this error, complete the first or both of the following steps:

1. On the Security page of the System Management Console and Tenant Management Console, keep the Log users out if inactive for more than value the same.
2. If you initiated a search and then refreshed the page before the results were displayed, clear cookies in your browser window. Then, log in to the Search Console again with your tenant-level credentials.

01354829

01331997

00704591

00781620

SNMP returns the incorrect replication link name

Workaround: Use the HCP Management API to return the correct replication link name.

01377407

01448466

HCP continues to report "Metadata query engine usage is at 100%" several days after the Maximum Allowed Size on Shared Volumes field value is increased

The metadata query engine index size is inconsistent with the actual space taken by the index. A symptom of this issue is that the metadata query engine frequently runs out of memory, and the following error is reported on the Overview page of the System Management Console: Metadata query engine ran out of memory for indexing