Known issues in 1.5.5 SP2

You might run into some known issues while using Cloudera Data Engineering on premises.

Existing known issues from Cloudera Data Engineering on premises 1.5.5 SP1 and earlier releases are carried into Cloudera Data Engineering on premises 1.5.5 SP2. For more details, see

Known issues and limitations in Cloudera Data Engineering on Cloudera Data Services on premises 1.5.5
Known issues in Cloudera Data Engineering on Cloudera Data Services on premises 1.5.5 SP1

For known issues fixed since Cloudera Data Engineering on premises 1.5.5 SP1, see Fixed issues in 1.5.5 SP2.

DEX-20335: Erroneous LDAPGroupsMapping lookups in Cloudera Data Engineering Ozone-based Spark or Hive jobs: In Cloudera Data Services on premises 1.5.5, some Cloudera Data Engineering Ozone-based Spark or Hive external table jobs may emit repeated LDAP warnings and incur unnecessary LDAP authentication attempts when the base cluster is configured with LDAPGroupsMapping configurations in Cloudera Manager. Due to a Cloudera Manager API/client configuration change in 1.5.5, the LDAP bind user password is not propagated to the Cloudera Data Engineering client configurations, so the job’s LDAP group lookup is attempted with a null password and fails. This can lead to excessive failed LDAP binds (visible in Job logs as WARN LdapGroupsMapping... javax.naming.NamingException... successful bind must be completed) and, in some environments, may overwhelm the LDAP or AD server or even trigger bind account lockouts due to security policies.; None
DEX-19498: Users or machine users with roles assigned through group memberships loose access temporarily: For OpenShift Container Platform, users who get roles such as VC User, VC Admin, Service User, Service Admin, and DEAdmin through group membership may lose access temporarily.; Assign Service User role directly to all the group users who want to access any Virtual Cluster in that Cloudera Data Engineering Service.
DEX-17854: Spark UI does not show all the executors: Spark UI does not show all the executors although Cloudera Data Engineering UI shows logs for all of them.; None
DEX-18512: Some stages or jobs in the Spark UI remain in the running state: Some stages or Jobs in the Spark UI remain in the running state even after the overall job is completed.; None
DEX-19060: The Configuration tab on Jobs runs does not show the details of data connectors: The Configuration tab on the Jobs runs page does not show the details of data connectors even though the job that was run used a data connector.; You can check the Configuration tab on the Job page, where the data connectors details are visible.