Known issues in 1.5.5 SP3
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 SP2 and lower releases are carried into Cloudera Data Engineering
on premises 1.5.5 SP3. For more details, see
For known issues fixed since Cloudera Data Engineering on premises 1.5.5 SP2, see Fixed issues in 1.5.5 SP3.
- DEX-23208: Spark jobs fail to interact with Ozone after Cloudera Base on Premises upgrade due to stale ozone-parcel-image
- When upgrading a Cloudera Base on premises cluster (example, from 7.1.9 to 7.3.2
SP1) while running Cloudera Data Engineering, the upgrade orchestration fails to
automatically update the Cloudera Data Engineering
ozone-parcel-image. As a result, the environment continues to use a stale image that contains a classpath incompatibility (Protobuf 2.x vs 3.x). This causes Spark jobs or sessions attempting to read from or write to Ozone to fail immediately with ajava.lang.NoClassDefFoundError: com/google/protobuf/LiteralByteString. - DEX-20780: Airflow XCom tab appears blank for VC Users instead of displaying access error
- In the Airflow task details user interface, the
XCom tab remains visible to VC Users despite Role-Based Access
Control (RBAC) restrictions being in place to block their access. If a VC User clicks on
the XCom tab, the webpage encounters an error and goes completely
blank instead of displaying a standard
403 Forbiddenor access denied message. VC Users must avoid clicking the Xcom tab on the task details page. - DEX-22009: Broken "Troubleshooting Guide" link in the CDE stale configuration synchronization feature
- Within the Cloudera Data Engineering user interface, the Troubleshooting Guide link located inside the stale configuration synchronization feature points to an invalid or incorrect URL, preventing users from accessing the documentation.
- DEX-22010: Incorrect "Release Notes" documentation link on the CDE home page
- Within the Cloudera Data Engineering user interface, the Release Notes link on the home page incorrectly directs users to the documentation for version 1.5.5-SP2 instead of the current 1.5.5-SP3 version.
