Configuration Known Issues and Limitations 

The items below are common known issues that you might encounter when configuring DataStax Enterprise clusters in Lifecycle Manager (LCM). Wherever possible, workarounds are included.

Updating configuration that affects OpsCenter clients 

When installing a cluster for the first time in Lifecycle Manager, the cluster is automatically added to the Edit Cluster - connection settings dialog in OpsCenter for monitoring going forward. Properties such as ports, credentials, and other security information are automatically configured for you. However, when modifying the Config Profile of an existing cluster in Lifecycle Manager, the Cluster Connection Settings in OpsCenter are not automatically updated. After the configuration changes have been applied to your cluster, you must manually update the cluster Connection Settings. If you have further questions, please contact DataStax Support and reference ticket OPSC-8544.

Encrypted DSE configuration values 

If DSE Configuration Encryption is enabled, you must supply the encrypted versions of sensitive properties to LCM. LCM does not encrypt these values for you.

DSE Graph properties (DSE 5.0.1+ only) 

DSE Graph configuration in dse.yaml, which is configurable through LCM Config Profiles. All Graph properties in dse.yaml can be managed through the LCM UI with the exception of gremlin_server.serializers and gremlin_server.scriptEngines. If you are using LCM and need to customize these properties, be sure to leverage the LCM API to make the changes. Future changes to the Config Profile via the LCM UI will retain properties set through the API.