Skip to main content
Hitachi Vantara Knowledge

Resolved and known issues

Issues resolved in the current release

The following table lists issues that are resolved in release 8.1.2 of HCP. The issues are listed in order by reference number.

Ref. number






CVE-2017-5715, CVE-2017-5753, and CVE-2017-5754: Meltdown and Spectre security vulnerabilities

For more information, see:

HCP-33577 00705518 Inconsistent treatment of security roles for local vs AD user

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Issues resolved in 8.1 patch releases

The table below lists issues that were resolved in the patch releases of release 8.1 of HCP. The issues are listed in order by reference number.

Ref. number




Patch Release

HCP- 33436


Remove signed AWS signature from error response
HCP- 33458


S3 PUT through JAVA AWS SDK fails to parse XML if the file name contains an ampersand character '&'
HCP- 33460


SMTP ingestion hit limit of 500 for queue files

HCP- 33462


Object pausing MQE indexing with error
HCP-33623 00900452 Eliminate potential node restarts during replication

Patch Release



Node restart due to an issue in a logging component that occurs when repeated Java exceptions are raised


Fixes an installation issue where the disk write cache was not disabled for internal drives



Updated Apache Commons FileUpload to resolve vulnerability caused by CVE-2016-1000031

Patch Release



Continuous node restarts due to concurrent unavailability of at least one node in each system in a replication topology

HCP-33216 HDS00685201 Metadata query engine index stalls due to objects not appearing on policy state table

Patch Release



Node restart due to objects occasionally missing custom metadata manifest

Patch Release

HCP-33056 HDS00608366 Updated Apache Struts version to resolve vulnerability caused by CVE-2018-11776

Patch Release

HCP-33028 HDS00495884
Replication link between HCP version 8.1 and 7.3.3 systems breaks due to version difference creating high object replication error count
HCP-33029 HDS00603130
HCP-VM system with VLAN enabled becomes unavailable after upgrade to HCP version 8.1

Patch Release

HCP-33005 HDS00553335
Object tiering requests to S3-compatible storage components return 503 (Service unavailable) error due to dropped client connections remaining open

Patch Release

HCP-33008 HDS00545674

HCP-VM  system install fails if system is configured with eight or more storage volumes per node and volume numbers include the number zero

Patch Release

HCP-32976 HDS00517582 SSH service fails to start during installation on HCP system with VLAN enabled

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Issues resolved in release 8.0

The table below lists issues that were resolved in release 8.0 of HCP. The issues are listed in order by reference number.

Ref. number






CIFS clients cannot negotiate SMBv3.0 for mounting a CIFS share from HCP



HCP requires wildcard in domain certificate common name (CN) field


- Enabling service plan selection for an existing tenant causes all namespaces owned by that tenant to inherit the default service plan


- Ingest performance slows due to increased index generation during high MQE



Occasionally misleading error messages triggered by slow replication between domain controllers when HCP joins AD


- Nonreplicating object replication success not reported by event log



Event log message does not explain why HCP disables AD



Service Plan Tenants list scrolls indefinitely


- Node restart due to HCP system restart and node attempting to join



Error code response incorrect to HEAD or GET request on aborted HTTP object scheduled for garbage collection



Replication stalled due to repeated creating and deleting of namespaces and objects


- Valid MQE object-based queries return 503 (service unavailable) error code despite Index Protection Level (IPL) 2 during online HCP system upgrade


- HCP system restart due to tiering to NFS when primary storage is above 95% capacity


- Online and offline upgrades fail at precheck due to service user account creation and HCP system timezone change


- HCP system restart due to two different namespaces using same port when performing simultaneous requests



Process using risfs server socket not reported to internal logs


- Upgrade fails due to upgrade proceeding without system restart


- HCP system performance slowed due to shredding service running as high priority service


- Default namespace top-level directories fail to replicate due to directory name case insensitivity


- Replication stalled on object with missing data


- Node restart due to repeated admin JVM resourceMetrics command


HDS03384992 Replication collisions due to repeated store and delete operations



System fails to restart due to time zone changes not updating across all nodes



SNMP OID replicationLinkStatus fails to report replication link stalls


- Modifications to active replication link may cause replication failure



System fails to start due to performing second storage array hardware swap procedure with OS drive on the storage array



Tenant-level user account password security issue


- Node restart due to simultaneous requests to specify custom metadata on same object


- Upgrade fails due to prior node recovery procedure performed on failed node



Node restart due to very frequent log download operations


- Node restart due to exception when rehydrating from cloudstorage endpoint



HS3 PUT request failure due to HCP not supporting AWS signature version 4 unsigned payload authentication



Data distributed unevenly due capacity balancing service running after ZCF failback



HCP software install fails due to nodes with unequal number of primary volumes on ZCF node pair



External volume failure alert falsely reported due to multiple failed PUT COPY requests to object in storage volume



Namespace browser and MQE fail to load objects due to null character in object names ingested through HS3 and HSwift



Slowed system performance due to spammed unreadable URL request internal log warning message



Replication link stalls during failback processing due to system continuously retrying to calculate objects pending metrics



Nodes occasionally restarts when writing objects to HCP S Series Nodes



Unavailable objects due to storage pool not updating when new bucket account selected



Node restart due to memory leak from performing large number of custom metadata reads over long period of time



Node restart due to rehydration running on object from deleted namespace


- HEAD and GET requests slowed due to returning unneeded X-HCP-Replicated response header returned with each GET and HEAD request


HDS04236963 HDS04336127 HDS04380153

Node restart due to memory leak caused by replication thread management



HCP repeatedly restarts due to deleting _kerboros SRV records for domain controllers from DNS server after HCP joins AD



HS3 requests with AWS v4 redirected to wrong system in active/active replication link and to wrong system during DNS failover



Null JVM manifest due to irreparable objects in the INVALID, MISMATCHED_CUSTOM_METADATA state



DNS zones not populating during DNS failover in an active/passive replication link



Node swap procedure times out when replacing a CR210 node with G10 node



Node restart due to running simultaneous write and delete operations



Object system metadata missing due to failed HS3 with AWSv4 authentication PUT request



Upgrade fails on system with large database due to upgrade timeout



HCP-VM node hangs due to insufficient system resources



Node restart due to large number of simultaneous message logs to node under heavy load



Retention date cannot be set to dates past year 2038 through CIFS or NFS



System performance issues due to too many simultaneous objects ingests and deletes



Periodic node restarts due to memory leak from prior node restarts



Download logs procedure takes long time to prepare logs for download

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Issues with workarounds

The table below lists known issues in the current release of HCP for which workarounds exist. The issues are listed in order by reference number.

Ref. number



HCP-5179 -

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.

HCP-7108 -

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.

HCP-13183 -

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.

HCP-13574 -

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.

HCP-16516 -

Cannot log into HCP interface as local user in Internet Explorer
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.

HCP-18233 -

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-19128 -

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 the OK button.

HCP-20401 -

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.

HCP-20827 -

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.

HCP-23881 -

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.

HCP-24155 -

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 Control-C to cancel the drive addition procedure. You can then restart the procedure.

HCP-24156 -

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 dual-mode 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.

HCP-24589 -

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.

HCP-25388 -

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.

HCP-26037 - 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.

HCP-26043 -

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.
HCP-26066 -

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.


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.

HCP-26775 -

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,

HCP-27121 -

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.

HCP-27757 - 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.

HCP-27882 -

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 HCP support services to enable third party compatibility.

HCP-30529 -

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.


CR220 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 CR220 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.

HCP-30765 - 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 ConsoleServicesLinks 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.
HCP-30958 -

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-31097 - 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.

HCP-31257 -

Broken volumes due to spindown storage in HCP release version 8.0
An HCP SAIN system with spindown storage that is running HCP release version 8.0 experiences broken volumes when disks spin up.

Workaround: Do not upgrade HCP systems with spindown storage to HCP release version 8.0.

HCP-31488 -

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.

HCP-32818 -

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.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Other known issues

The table below lists known issues in the current release of HCP for which no workarounds exist. The issues are listed in order by reference number. Where applicable, the service request number is also shown.

Ref. number



HCP-804 -

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.

HCP-5153 - False log messages with lowest-numbered node addition
When a new node is added to an HCP system, a message about it is written to the system log. If the number of the new node is lower than that of any existing nodes, the same message is written for each existing node, as if it were newly added.
HCP-7043 - 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.
HCP-8385 -

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.

HCP-8570 - 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.
HCP-8665 - 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.
HCP-9212 -

Log display skips messages
When you page through a display of log messages in the System 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.

HCP-9360 - 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.
HCP-11317 - 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.
HCP-11667 - 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.
HCP-12089 - 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.
HCP-18352 - 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.
HCP-18654 - No success or error message in response to action taken in Console
Occasionally, the System and Tenant Management Consoles 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.
HCP-18700 - Standby spindown volumes possibly not reported in data migrations
In an HCP SAIN system with spindown storage, when you configure a data migration, the logical volumes (LUNs) reported for each node in the Configuration panel on the Migration page in the HCP System Management Console may not include standby volumes on spindown storage. Additionally, the standby spindown volumes may not be included in the downloaded configuration report. Although these volumes may not be reported, they are always properly included in the data migration.
HCP-19123 - 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.
HCP-20706 - 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.
HCP-21365 - 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.
HCP-21056 - 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.
HCP-22241 -

Username mappings applied to AD 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.

HCP-23070 -

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.

HCP-24436 - 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.
HCP-24472 - 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.


- HDvM 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 HDvM server, but cannot receive HDvM updates.
HCP-24887 - 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.


- 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.


- Occasionally while migration service runs, migration status 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.


- Occasionally an offline upgrade procedure on HCP system with spindown fails
Occasionally an HCP system with spindown may fail an offline upgrade because the disk mounting procedure times out.
HCP-25697 - 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.
HCP-25731 - 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:
HCP-25761 - 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.
HCP-25997 - Node recovery does not work for the HCP 500XL with new disks
Node recovery procedures fail with unformatted database drives.


- 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-DM does not support these ciphers if HCP-DM is run with an outdated Java runtime.
HCP-26158 - 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.


- 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.


- Occasionally incorrect error message appears when switching tabs during replication schedule update
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.
HCP-29471 -

No alerts when volume at less than 95% capacity becomes read-only
If a logical volume that is less than 95 percent full becomes read-only, HCP does not generate an alert because the database holds a reservation on the remaining space on the volume.

HCP-29573 - 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.
- Database connections exhausted
On high-load HCP systems that are balancing metadata, nodes can restart due to exceeding the database connection limit.
HCP-29645 -

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.

HCP-30018 - 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.
HCP-30058 - 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.
HCP-31061 -

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.

HCP-31082 -

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.

HCP-31400 - Tar-gzipped objects fail MD5 check due to Firefox browser issue
Tar-gzipped objects downloaded from HCP through the Firefox browser fail the MD5 check.
HCP-31431 -

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

HCP-31499 - Inconsistent case sensitivity for HS3 multipart upload query parameters
Case sensitivity is inconsistent among the query parameters used with HS3 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.
HCP-31529 -

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.


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.

HCP-31841 -

IPMI v2.0 password hash disclosure
A vulnerability regarding IPMI v2.0 puts password protection at risk. For more information on this, see

HCP-31972 -

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.

HCP-32417 -

System restart when adding, removing, and then re-adding a management port network adapter
When you add, remove, and then re-add a management port network adapter to an HCP-VM system, a system restart is required.

HCP-32690 -

Arc-deploy should wait for newly-added nodes to become available before adding more nodes
When adding nodes to an HCP system, arc-deploy should wait for newly-added nodes to become available before continuing to add more nodes to the system.

HCP-32819 -

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

HCP-32845 -

Incorrect information included in object configuration files
In certain object configuration files, incorrect information is included.

HCP-32856 -

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.

HCP-32900 -

Management port network status not detected on Hardware page
If the link status of the management port network connection fails on an 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.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.