Issues Fixed in Altus Director

Altus Director can be configured to use a backing LDAP server, such as OpenLDAP or Active Directory, for its own user accounts. When configured as such, Altus Director fails to correctly collect usage information from itself that is needed to perform usage-based billing. This does not affect the normal functioning of Altus Director, but only causes the creation of malformed usage information that Cloudera is unable to process into billing records.

Cloudera Issue: DIR-8905

In cases where Altus Director returns HOCON for a deployment template, such as exporting a cluster configuration file, the Kerberos administrative password, if present, was rendered instead as the Kerberos administrative username.

Cloudera Issue: DIR-8791

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

The UI Simple Setup form ignores the value in the worker count field and always uses the default value.

Cloudera Issue: DIR-8714

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.

Cloudera Issue: DIR-8470

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 setup cluster installation fails when the cluster name contains capital letters.

Cloudera Issue: DIR-8335

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.

Cloudera Issue: DIR-8331

An Azure cluster with autorepair enabled can have healthy instances removed if there's a failure to communicate with Azure.

Cloudera Issue: DIR-8291

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.

Cloudera Issue: DIR-8241

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

The Swagger model schema for external databases is not displayed correctly.

Cloudera Issue: DIR-941