Release Notes: IBM Aspera Transfer Cluster Manager 1.2.6 for AWS and IBM Cloud
Product Release: May 2, 2018
Release Notes Updated: May 2, 2018
ISSUES FIXED IN THIS RELEASE
NODE-643 - When the content_protection_secret is specified in an access key (that is created with /access_keys), uploads are correctly encrypted but downloads do not use the secret and files are not decrypted.
NODE-641 - When a file is renamed, the UI might temporarily show the renamed file twice.
NODE-565 - When ATC nodes are upgraded from 3.8.0 to 3.8.1, the transfer history is lost.
TRAP-122 - Azure access keys do not support Azure Premium storage because the Azure API type defaults to BLOCK, but Azure Premium requires PAGE.
AMAZON MACHINE IMAGE (AMI) INFORMATIONCluster Manager Image
IBM CLOUD (SOFTLAYER) MACHINE IMAGE INFORMATION
Cluster Manager Image
|Data Center||Registered Image|
|ams01, ams03, che01, dal01, dal05, dal06, dal09, dal10, dal12, dal13, fra02, hkg02, hou02, lon02, lon04, lon06, mel01, mex01, mil01, mon01, osl01, par01, sao01, sea01, seo01, sjc01, sjc03, sjc04,sng01, syd01, syd04, tok02, tor01, wdc01, wdc04, wdc06, wdc07||16c42e06-c30a-479c-8c33-0ddbb5521a91|
Transfer Node Image
|Data Center||Registered Image|
|ams01, ams03, che01, dal01, dal05, dal06, dal09, dal10, dal12, dal13, fra02, hkg02, hou02, lon02, lon04, lon06, mel01, mex01, mil01, mon01, osl01, par01, sao01, sea01, seo01, sjc01, sjc03, sjc04, sng01, syd01, syd04, tok02, tor01, wdc01, wdc04, wdc06, wdc07||10c47fd8-11c0-4e81-acce-b831df7f8078|
PREVIOUS RELEASE NOTES
Release Notes: IBM Aspera Transfer Cluster Manager 1.2.5 for AWS and IBM Cloud
Release Notes: IBM Aspera Transfer Cluster Manager 1.2.4 for AWS and IBM Cloud
IBM Aspera Cluster Manager 1.2.3 Release Notes
IBM Aspera Cluster Manager 1.2.2 Release Notes
IBM Aspera Cluster Manager 1.2.0 Release Notes (AWS)
ATC-480 - Nodes that are not visible to ATC Manager, such as those that fail to register, can still report events to the statestore.
ATC-478 - When a cluster's global entitlement expires, the cluster nodes are marked as degraded and cycle between degraded and replacing. The error cycle stops once the entitlement is updated.
ATC-441/ATC-377 - ATC Manager stores a version of an access key that can become different from the access key in the node database if the access key is updated in the ATC Manager UI rather than through the ATCM API. For example, if the server-side encryption setting for an ATCM access key is changed in the ATC Manager GUI, the "token_verifcation_key" value in the access key is removed and the access key is no longer valid.
ATC-410 - [AWS] If the ATC cluster name contains capital letters, ATC Manager attempts to recreate the DNS record and reports the error, "Failed to update cluster IPs in DNS".
ATC-327 - [AWS] Route 53 DNS updates fail intermittently with the error, "com.amazonaws.services.route53.model.InvalidInputException".
ATC-322 - Syncing Console 3.2.0 access keys from the ATC Manager UI deletes sub-access keys. (CIM-543)
ATC-320 - Trapd can take up to 5 minutes to timeout when attempting to browse an unreachable IP address.
ATC-292 - ATC Manager does not support concurrent uploads of the same content to the same destination by separate ascp sessions.
ATC-207 - The ATC Manager UI displays a maximum of ten access keys in the access keys table and in the transfer statistics drop-down menu.
ATC-29 - During a node upgrade, if an invalid node image ID is configured, ATC Manager cannot launch new nodes and is stuck in "UPGRADING" state. The configuration cannot be corrected once the invalid image ID is entered.
For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.