Issues Fixed in Altus Director
The following sections describe fixed issues in each Altus Director release.
Issues Fixed in Altus Director 6.0
Simple setup with CentOS or RHEL 7.4 fails in some Azure regions
OS mappings for were not defined for azure-germany and azure-us-government regions. Attempts to bootstrap a cluster using a simple setup conf file that selected these combinations would result in a validation error. OS mappings have been added for Red Hat Enterprise Linux 7.4 and Cloudera-published CentOS 7.4 for Azure cloud environments where available.
Cloudera Issue: DIR-8671
UI Simple Setup ignores worker count
The UI Simple Setup form ignores the value in the worker count field and always uses the default value.
Workaround: Grow or shrink the workers group to the desired number of instances after bootstrap completes.
Cloudera Issue: DIR-8714
Custom Cloudera Manager service configurations not applied after cluster bootstrap or update
Cloudera Altus Director versions 2.7.x and 2.8.x fail to apply custom configuration properties for Cloudera Manager services, instead setting them back to automatic defaults as determined by Cloudera Manager. Common examples of affected configuration properties are memory settings for the Cloudera Manager service monitor and host monitor services.
Workaround: After cluster bootstrap or cluster update (grow or shrink), re-apply desired custom Cloudera Manager service configuration property values using the Cloudera Manager UI or API.
Cloudera Issue: DIR-8470
Director fails to add worker nodes to a cluster that was created with Simple Setup
In previous versions, Director would fail to add worker nodes to a cluster that was created with Simple Setup. The error occurred because of the placement of ZooKeeper Server roles on worker nodes. The ZooKeeper Server role has been moved to the single master node.
Cloudera Issue: DIR-8699
Azure simple cluster setup fails when cluster name contains capital letters
Azure simple setup cluster installation fails when the cluster name contains capital letters.
Workaround: Use only lowercase letters in cluster names.
Cloudera Issue: DIR-8335
Terminating a deployment fails when the Cloudera Manager instance has been deleted without using Altus Director
If the cloud instance hosting Cloudera Manager for a deployment is deleted without going through Altus Director, then deployment termination might fail while attempting to clean up the Kerberos credentials associated with Cloudera Manager. This failure only occurs when Altus Director cannot contact Cloudera Manager directly over its web port and must instead use an SSH tunnel to reach it.
Workaround: Command Altus Director to terminate the deployment again, and it will succeed.
Cloudera Issue: DIR-8331
Autorepair on Azure can remove healthy instances
An Azure cluster with autorepair enabled can have healthy instances removed if there's a failure to communicate with Azure.
Workaround: None. Do not enable autorepair on Azure for Director 2.6 and higher.
Cloudera Issue: DIR-8291
Erroneous error code 406 and error message returned when simple setup cluster is launched with incorrect data
When attempting to launch a cluster with the simple setup procedure, Altus Director server might return an HTTP error code of 406 with the message: Could not find acceptable representation. This occurs when there is an error in the data supplied for the cluster, and the server is unable to formulate a correct error response. This error code and message should not occur when the data for simple cluster setup is correct.
Workaround: Look in the Altus Director server log to find the underlying problem with the data supplied for the cluster.
Cloudera Issue: DIR-8241
FirstRun command occasionally fails
When executing FirstRun, Director's list of commands was correct, but misordered. Due to the timing, this results in infrequent failures during FirstRun while bootstrapping clusters.
Cloudera Issue: DIR-7977
Swagger model schema for external databases is incorrect
The Swagger model schema for external databases is not displayed correctly.
Cloudera Issue: DIR-941